Hi Derrell,


Derrell Lipman wrote:
> 
> Since I'm back in
> grad school now, though, I have decided to do a Phase I of this as my term
> project for my Human Computer Interaction course.
> 

It's great to know you are thinking about this, I really feel like this
would be an great helper for the qooxdoo community, specially when
starting-up. ;-)



Derrell Lipman wrote:
> 
>    1. What do you find to be your most time-consuming or tedious tasks
> while
>    developing qooxdoo applications?
> 

Crawling through the documentation. The API viewer included with Qooxdoo is
great, but having to crawl for methods/properties every time is pretty
time-consuming.



Derrell Lipman wrote:
> 
>    2. If you could have a tool to handle various aspects of your qooxdoo
>    application development, what aspects would those be, and what would
> you
>    hope the tool would do for you?
> 

I'd say that these would be nice:
 * Visual designer (like Tartan BluePrint but supporting all qooxdoo
widgets): this is already stated in the aims list;
 * Code completion/list of properties/methods for a given scope (a.k.a.
"Intellisense");
 * Background source/build preparation;
 * Background code validation (invoking the "lint" targets and showing
results in a task list, like Visual Studio does when compile errors are
triggered): this was already suggested by Bruce Bockius;
 * Easy insertion of  http://qooxdoo.org/contrib contributions  and/or 
http://qooxdoo.org/documentation/0.8/snippets code snippets  into a project
(automatically setting up the required environment, dynamically fetching the
list of contributions/code snippets from the qooxdoo site, ...).



Derrell Lipman wrote:
> 
>    3. What is your current qooxdoo application development environment,
> and
>    in it, what features do you find lacking and what features are critical
> to
>    you?
> 

Currently, I'm using Microsoft Visual Studio on Windows, but only as an
IDE/code editor:
 * Aggregate important files into a project;
 * Setup utility build tasks into build targets (I use Cygwin for the main
build tasks).



Derrell Lipman wrote:
> 
>    4. Please add any additional comments or suggestions
> 

I'm convinced that  http://www.aptana.org/studio Aptana Studio  (previously
known as Aptana IDE), which is Eclipse-based, would be a nice base for
development of such a tool. Aptana already supports most of the things being
aimed milestones, including code completion and debugging (apparently for
free only for Firefox, paid for IE). This means that such a project could
potentially be modeled into developing a plug-in for Aptana, mostly taking
care of tweaking the IDE to fit the expected qooxdoo environment. :-)



Derrell Lipman wrote:
> 
> Thanks!
> Derrell
> 

Hope this helps,
 Helder
-- 
View this message in context: 
http://www.nabble.com/qooxdoo-%22IDE%22----Request-for-Comments-tp25789918p25802421.html
Sent from the qooxdoo-devel mailing list archive at Nabble.com.


------------------------------------------------------------------------------
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

Reply via email to