Comments on: Flare pros and cons

Comments on: Flare pros and cons http://www.itauthor.com/2007/07/01/flare-pros-and-cons/ Stuff about technical writing and software Wed, 28 Jul 2010 06:25:59 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Paul Pehrson http://www.itauthor.com/2007/07/01/flare-pros-and-cons/comment-page-1/#comment-1001 Paul Pehrson Thu, 12 Jul 2007 05:09:34 +0000 http://www.itauthor.com/wordpress/2007/07/01/flare-pros-and-cons/#comment-1001 Hey, thanks for the links on your blog! You're right. I don't use structured Frame, principally because I've never had experience with it. I should try it sometime, just for the experience. But since Flare is my first experience with an XML editor, I was pleasantly surprised at how cool it was. I agree with your assessment that it isn't yet perfect, and there are some things I'd love to see change, I think it is pretty darn good. But again, I've not got much to compare it to. As for the CSS editor, there are some things there that drive me crazy as well. For instance, I think that some of the organization of the tree nodes is kind of convoluted. You'll set properties for GlossaryPageTerm as a child of the 'a' node, but you set properties for GlossaryDefinition, GlossaryEntry, GlossaryTerm, and GlosaryHeading as children of the 'div' node. And yet again, there are separate nodes for GlossaryProxy and GlossaryTerm. Can't they all be in one place? However, the new v3 of Flare is out today, and they've made substantial changes to the CSS editor, so you should go check it out to see if you like the new version. Hey, thanks for the links on your blog!

You're right. I don't use structured Frame, principally because I've never had experience with it. I should try it sometime, just for the experience.

But since Flare is my first experience with an XML editor, I was pleasantly surprised at how cool it was. I agree with your assessment that it isn't yet perfect, and there are some things I'd love to see change, I think it is pretty darn good. But again, I've not got much to compare it to.

As for the CSS editor, there are some things there that drive me crazy as well. For instance, I think that some of the organization of the tree nodes is kind of convoluted. You'll set properties for GlossaryPageTerm as a child of the 'a' node, but you set properties for GlossaryDefinition, GlossaryEntry, GlossaryTerm, and GlosaryHeading as children of the 'div' node. And yet again, there are separate nodes for GlossaryProxy and GlossaryTerm. Can't they all be in one place?

However, the new v3 of Flare is out today, and they've made substantial changes to the CSS editor, so you should go check it out to see if you like the new version.

]]>