« The Dopefly Tech Blog Main page
I finally got around to updating the Fusebox XML cheat sheet. The first version I released was for Fusebox 4.1, so this is now 3 major releases later. Remember to update your offline copies.
Here are the links:
Fusebox 5.5 XML Cheat Sheet, HTML (printer friendly!)
Fusebox 5.5 XML Cheat Sheet, 5 page PDF
The 4.1 version is still available at the Fusebox 4.1 XML Cheat Sheet page.
Recently, I made my first contribution to the Fusebox core files (Previous contributions were in the form of lexicons, which are valuable add-ons but not core files). My change was just an update to the HTML rendered from the Fusebox 5.5 debugging trace output.
The older debugging output had hard-coded styles on the tags, and no identifying overall element. If you wanted to change or fix a style, or even the entire block, there was really no good, reliable way to do it, short of modifying the Fusebox core files. With ColdFusion debugging output, you can use the .cfdebug selector to change the server debugging, but no such luck for Fusebox.
It's a superficial, mild annoyance, at best, but still a spot for improvement, so, I made the change and submitted it in an issue to the Fusebox Trac site.
For this change, I created a small style sheet, removed the inline styles, made some default styles and added an identifiable container for the block.
Now, how can you change the display?
The style sheet I made has a handful of styles that all start with .fuseboxdebug. With CSS, if you make a more specific selector, you can override options in the less specific selectors. A selector and style such as .fuseboxdebug h3 {color:green; background:blue;} will be overwritten by div.fuseboxdebug h3 {color:red}. The resulting h3 style from these examples will have red text on a blue background.
So, if you want to do something like hide the debugging output using CSS (Sean Corfield says you can do it in Fusebox with myFusebox.showDebug = false), the code would be:div.fuseboxdebug {display:none;}
Some added benefits include the download size of the debugging output, cut in half, and it should stay a little more consistent across different site designs all while being customizable. See, CSS is good all around.
PS - Fusebox 5.5 is due out December 1st, and it's been perfectly stable with my 4.x and 5.x apps.
Bookmark this link: Fusebox Full Flush.
You can click it on this page, don't worry, you won't hurt my site.
When you select this bookmarklet from your own bookmarks on one of your sites running fusebox, it will prompt you for your fusebox password (you do have one, right?). Type it in and it will send the fusebox magical reloading URL parameters to your site:
fusebox.load=true
fusebox.parse=true
fusebox.loadclean=true
fusebox.password=(your password)
useful!
The list of new features for Fusebox 5.5 is growing. There's a fair amount of chatter on the list surrounding what's going to be in there. Here are some of the things Sean has been talking about.
If you work with Fusebox and would like to have an Eclipse plugin that helps you out in your development, Mark Drew is asking for your help on dreaming up features for a new version of his Fusebox Eclipse plugin. Leave a comment on Mark's blog with your wish list of what you think a Fusebox IDE can do.
(Discuss with Disqus!)With a little time on a spare project (or spare time on a little project? it's 2:am), I hammered out some really quickie basic lexicon tags for Coldspring and Reactor.
Download my quick ColdSpring lexicon
Consists of an instantiate tag (call in your appinit), and a get tag (call from anywhere). Hers's a quick sample:
Another thing I've been playing with lately is getting tag insight (you know, those little drop-downs while you type) to work on fusebox.xml and circuit.xml files. I'm no kind of Eclipse hacker, so the easy way to do it is make a DTD file for the XML editor you may already have in Eclipse.
Mmmkay... how does that help me? Glad you asked!
First, do you have an XML editor? You'll need one for this exercise. I prefer the WST XML editor from the Eclipse org., and it's easy for you to get. Go to your auto-update tool (under the help menu), and search the Eclipse update site for new plugins. Locate the WST (Web Standards Tools), select it and hit the 'select required' button. Now install and restart.
Next, you need to add the DTDs to the local DTD registry. What I did was hit the Eclipse prefs, and found the XML Catalog section under Web and XML. Then I added 2 user specified entries, for fusebox.xml and circuit.xml, pointed them to the appropriate DTD file on my local disk, made them a Public ID key type and gave the key a name (I used circuit.dtd and fusebox.dtd).
Next, in my XML files, I added this doctype to my circuits:<!DOCTYPE fusebox:circuit PUBLIC "circuit.dtd" "circuit.dtd">
And to my Fusebox.xml:<!DOCTYPE fusebox PUBLIC "fusebox.dtd" "fusebox.dtd">
I wish I knew what that all meant, but i'm ignorant out of lack for good books and time to read them ;)
And there it is. Restart Eclipse (for good measure) and it should all just work!
All you need is the DTDs to try it yourself, so here you go:
Fusebox 4.1 Document Type Definitions
These were copied and modified from the ones by Sandy Clark - Sandy, hope you don't mind. Good work getting it started, thanks!
Hope you all like. Let me know if any of you have any updates to these, as it's my first real stab at DTDs.
One thing I've always wanted when working with Fusebox 4, is a quick XML cheat sheet. What goes in the fusebox.xml file? What was that verb tag again for my circuit.xml? Was that returnvariable, contentvariable or just variable?
Googling and searching only found the PDFs for a $75 book, which is helpful but not ideal, and miscellaneous sources, too spread out to be useful. Since there wasn't one, I had to create one myself, and now that it's done, I got permission and am sharing it with the community at large.
So, without further ado, the Fusebox XML Cheat Sheet (with a little bonus info at the end)
P.S., I also added a print stylesheet, so feel free to print it out and hang it on your wall, or whatever.
P.P.S., Fuseboxers, feel free to check my work and make corrections and suggestions - thanks!