pd - FUEL is being reviewed at this moment (I was told on IRC). We (John & I) expect to have a few iterations of changes, but it should land soon, unless we really messed something up. Also, moving people from DeamWeaver or Visual Studio to a yet to be built XUL IDE is not only false logic, but a false hope. I don’t plan on wasting whatever effort we have on a false hope. I do believe that creating a package of tools/applets that can integrate into existing IDEs are the best hope in the short to mid term.

Todd - That is exactly the plan. Build tools/applets (or extensions in the case of Komodo) that we can leverage across multiple IDEs. I’ll probably be asking for help from you guys

* provides project templates for managing extensions (project structure, rdf, jar and zip features)
* provides completions and calltips for XUL, JavaScript.

Then add to it, since it’s based on Mozilla itself, you create extensions (or macros) for Komodo, to add other features like:
* previewing XUL
* XUL WYSIWYG editor

Most of the work is done already.

Note: I have a slightly biased view as I work/develop on Komodo itself at ActiveState

Cheers,
Todd

The notion that developers are religious about their editors and therefore are less likely to ’switch’ to an IDE is, for me, false logic. Surely one of the aims of XUL is to bring quasi-developers into desktop app development? I’m talking about those whose guilty pleasure might be Dreamweaver or those who are hand coders and can’t be rooted stuffing around with anything but a quick drag and drop interface builder.

Who says that developers are limited to one tool?

The sort of developers who are religious about their tools are surely the sort of developers who are that far advanced, they don’t need all that much help with XUL anyway?

Or perhaps all that is false logic on my behalf ?

However I see no reason why all the work being done on XUL - as disjointed as it is - cannot be harnessed and built into a much more effective development platform.

Oh wait, Mozilla doesn’t really care enough about XUL, that’s the reason!

Paul Rouget (from Xulfr staff), develop a plugin which embed scintilla editor. I saw it (it’s not available for the public for the moment), and it will be a good start for an IDE based on xulrunner. You can read post about it : http://blog.mozbox.org/tag/codeeditor

You talk about FUEL. This is a great project. But i don’t understand why there isn’t a will to put it into the toolkit, instead of into the browser package. The result : we can’t have FUEL into xulrunner app, although many of FUEL objects could be very usefull.