On Mon, 2009-10-12 at 09:55 -0700, panyasan wrote:
> What I would find cool is if the manual would be a
> qooxdoo application itself, just like the API viewer....
>
I agree in principal - I always felt like a software project should take
it's own medicine, so to speak.
This relates to the IDE project in a couple of ways, first being this
comment about a Qooxdoo manual written using Qooxdoo. The second has to
do with building this IDE within Qooxdoo rather than as an add-in to an
existing IDE like Eclipse.
Here's an interesting story that highlights this issue for me...
A few years back, I worked on a team for a corporate database
application, providing the feedback path between the engineering users
and the IT project team. This application included documentation
management and change management functionality for the engineering
business processes. Our IT team (I was an engineering representative on
this team) developed the requirements documentation and handled the
change request review and prioritization activities for this corporate
data system, constantly driving application improvements to enhance it's
functionality for the engineering users. The thing that never made
sense to me is that we did all of our documentation management and
change management in another completely unrelated system outside of the
engineering application itself, completely unrelated to the technology
used in the business process application.
It seemed to me that using the business application for this purpose
would have enabled us to better understand the challenges that faced the
normal users of this system on a day to day basis. However, management
had their own esoteric reasons for not using the business application in
this way. I just never really quite got it myself, and I always felt
like we didn't grasp all of the needs of the user community as a result.
So, I think Qooxdoo can benefit from this same philosophy - we should
strive to use Qooxdoo's framework and features in every aspect of the
Qooxdoo project in order to better understand how to apply it in real
world situations. If it's truly the best solution for web development
of RIA's, then it should serve as the best solution for the various
Qooxdoo RIA's as well, like it does for the API and demo applications
today. How often does a Qooxdoo developer dig into the code of the API
or demobrowser to see how something is accomplished and apply it in
their development work (maybe not often enough, but hopefully you get my
point). The more real-world applications of Qooxdoo that can be
studied, the better a developer can get a sense for how to use the tool
properly in their own development work.
Just my additional $0.02 worth,
Gene
------------------------------------------------------------------------------
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
