I've begun adding some features to Fusebox 5.5. I'd like to keep the discussion a centralized as possible, I turned comments off on the blog so please leave comments in this thread.
The features part (there is more in the entry if interested):
I've not tried to hide my disdain for circuit XML in Fusebox (have no
fear it is going no where and will get lovin' when it needs lovin', too
many of you people are masochists and like the XML). As a sign of good
faith I added a feature to the XML fusebox that had always really
bugged me (I'd like feedback on the good/bad side of this change). I've
always hated having 15 circuit.xml files open in the editor which lead
to the addition to the circuit.xml finding algorithm. Fusebox (in the
BER that I plan to push sometime this weekend) will now find alias.xml or alias.xml.cfm in the path specified in Fusebox.xml.
The second feature that I added was something I really wanted to see,
and I wanted it at Kroger. Fusebox now supports defining No XML
circuits in fusebox.xml. What this means is you do not have to rely on
Fusebox's location conventions to leverage No XML circuits. In Kroger
our application layout does not match the conventions that Fusebox
wanted to impose. I had a long discussion with some friends and
colleagues about changing Kroger's application layout vs adding some
functionality to Fusebox. In the end I felt it was a feature that would
give Fusebox users a nice mesh between configuration and convention.
Feel free to post additional feature requests in this thread.
I've begun adding some features to Fusebox 5.5. I'd like to keep the discussion a centralized as possible, I turned comments off on the blog so please leave...
... see, and I ... application ... I had a ... So, if I understand correctly, <circuit alias="member" path="_Controller/member/"/> ... will now work with...
... Not quite. right now it is not looking for CFCs its only looking for the XML. I suppose it could look for the CFC as well I'll have to give that some...
So what is the format and details about the alias.xml file? Is it just the circuits from fusebox.xml file? If so, isn't that making it more files to open?...
Its the same amount of files to open, its just they are not all named the same bloody thing (circuit.xml). I am all for reducing the # of files to open if you...
Ok. Then perhaps I don't have enough information. I thought there would be 1 alias.xml file in the fusebox.xml directory that would be all the aliases. So what...
Actually, using your example, if the alias of the circuit is "Users", you'd have to make sure you named the file "Users.xml(.cfm)", so that it would be found...
... picky, picky, picky. ... Yeah i was just typing it quickly. ... Dude that is fantastic. Adam, when you do commit your changes - can you quickly, you know,...
Amen to that. It's tough having 8 files open, not knowing which one goes to which subdirectory. Have to hover over the filename in cfeclipse for it to ...
Adam, #1: This is fantastic and will certainly solve some big annoyances for me. Another similar problem is that I have a number of directories with nothing ...
Could we take #1 a step further. A master circuit.xml file that you could include other circuit.xml files if you so choose. I would think it would cut down on...
... Yep with this update this usecase should work now. So you should be able to do something like: <circuit alias="main" path="app/controller/" /> <circuit...
I was glad to read about the change to allow for circuits to be named [alias].xml.cfm. After trying to implement it, am I wrong in finding that it doesn't work...
Correct this is not implemented, or at least I did not intentionally do that ;) I could look at this beginning of next year. I guess I should have posted this...
Sweet! I'll be sad if release-notes for next version of FB don't include "Hitch Hikers Guide-inspired" next to certain items. ;-) ... do that ... posted ... ...
Adam, #1 I prefer the XML configuration files (seem to be in the minority) and consider the No XML a nice feature for getting a site up quickly, but too...
Derek, If you're referring to what I think you are, they're not backing off it so much as they're providing an include tag so you can include external config...
I'd like to clarify. ... I think I was the only person who suggested the idea. No, I wouldn't like it personally. My editor shows me the full path of a file,...
I LOVE having an entire application in a single switch file. As long as the editor supports code folding and has a good outline view for nav, it's great....
Thanks for all the feedback so far everyone! ... Ok... what is limited about it? I want it to be as good [ok ok I want it to be better] as Traditional Fusebox....
... Honestly, I don't like it. I think the current solution of 2 files is good enough. Right now, you can have fusebox.xml file define one circuit, then put...
I would not be a huge fan of changing the name of circuit.xml as I think it loses portability and increases dependency. If you decide to rename a folder, you...
Adam said it was optional. circuit.xml[.cfm] is still the default, just now it supports an alias-named file as well. So you needn't change anything if you...
... Increases dependency on what? ... If you change the folder name you have to update everything as it is. The new name for your circuit doesn't change a...
Having problems with message search?
Offline 
Send Email
