Hello,
Since I'm not doing any qooxdoo projects right now therefore my
thoughts won't have "what users want to get from IDE" ideas and
suggestions, but I would like to focus on some moments behind the scene.
As understandable from the discussion there are 2 ways to implement
the IDE. One of them is to write it on top of existing desktop IDE,
e.g. as Eclipse plugin, it has some advantages but it's harder to
implement visual builder there since native qooxdoo environment is
javascript (well, it'll require much time rather than "in-browser
IDE"). Another way is to write a "in-browser" IDE and as far as I
understand Derrell is going to stick this way.
Ok, here are my thought what I would implement in such an IDE:
1) I would pay close attention to internal representation of the UI.
IDE will have a possibility to save work in progress and it will be
stored in some internal, intermediate format (right?). This is a form
and UI serialization which we discussed in other threads. Maybe it
makes sense to provide independent library which builds UI from this
intermediate format and users will be able to use it as well to build
UI on the fly? Also my interest on this particular topic is that I
will be able to translate it to QxTransformer xml easily.
2) If it's going to be a pure JS IDE, I would take a look at Adobe AIR
and/or Appcelerator Titanium technologies. I don't thinks that it's
very convenient to write code right in browser, so you can get benefit
from AIR/Titanium and distribute the application as desktop like. Also
Titanium has built-in Python integration which would allow using power
of qooxdoo tool chain I suppose.
Cheers,
Siarhei
On Oct 12, 2009, at 4:03 AM, Derrell Lipman wrote:
On Wed, Oct 7, 2009 at 12:24, Derrell Lipman <derrell.lip...@unwireduniverse.com
> wrote:
For a many months, I've considered what an advanced, easy-to-use
development environment for qooxdoo applications would look like.
I want to thank all of you who have taken the time to provide
detailed feedback to my request for comments. I have intentionally
stayed out of the fray as the topic was discussed on the mailing
list, and it has been really interesting playing the fly-on-the-
wall, just listening to all of the recommendations. I really
appreciate it! As Thomas surmised, my questions were in fact
intentionally fairly general, allowing sufficient freedom to ensure
that the discussion was not overly constrained. It did wander a bit
farther off the path I intended than expected, but not overly so.
All of the comments were useful.
A few of the suggestions from the community would take me on a
longer journey of discovery than I can afford right now. In
particular, I fully appreciate the comments that suggested that if I
want to work on an IDE, I should write a plug-in for an existing IDE
rather than writing one myself. That may well be true, but it's not
in the cards right now. What I have knowledge of is qooxdoo. For
now, at least, and for the purpose of my Human Computer Interaction
course, I need to work on a qooxdoo application and focus on the
usability of the interface for some subset functionality. I
evaluated the comments and suggestions looking for frequency of
similar or related requests, and prioritized my "wish list" to try
to accommodate some of the most frequently-requested features. I
expect that this project will grow well beyond what I'm able to
complete for this one term project, and that as it moves from the
current realm of plans and vaporware into the realm of real, working
software, the priorities will change. As I begin this project, I'm
going to focus on the ability to easily create the user interface
portion of qooxdoo applications, with a live application view and a
source code view. As I develop this, I'll be keeping in mind the
various other requests, to try to make it as easy as possible to
incorporate as many of them as possible as the application grows in
capability.
If you're interested in seeing my project proposal that I've posted
on our course wiki, I believe it should be publicly visible here:
http://91-527-f2009.wiki.uml.edu/qooxit+for+qooxdoo
Thanks again! Feel free to continue contributing to the discussion.
Derrell
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart
your
developing skills, take BlackBerry mobile applications to market and
stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
