I am not the right one to answering this wonderful initiative, but this
is the real spirit! I hope you can find collaborators!
Meanwhile, on a more constructive note, maybe you want to see how far
you can get even with the 0.1 version of qooxdoo. I have put an public
version of it here:
http://m15s08.vlinux.de/~cboulanger/devel/ (Login with test/test)
(Beware: it runs painfully slow in the Internet Explorer, please use
Firefox).
It has a lot of issues, such as a problem with UTF-8 characters
(because MySQl is version 3.x), and the famous Mozilla - "I don't see a
cursor and cannot select text in textfields" - bug. Most problems are
related to my code and not to qooxdoo. And this is version 0.1 ! Code is
available on request and a real mess. I hope I can find the time to port
the application to 0.5.
Best regards,
Christian
Christoph Dorn schrieb:
Quick background:
The more I work with qooxdoo the more I like it. Its structured well,
runs reliable and it looks like it will be worth making a significant
investment in to choose it as a core component. I primarily develop
all my applications in PHP. I found qooxdoo while looking for a
JavaScript/Ajax framework to use for building admin systems for sites
I develop. I was looking for an easy way to create powerful user
interfaces fed by a standard PHP API.
I think qooxdoo relies on JavaScript a lot more than other frameworks
(some use DIV tags for layout etc...) and I believe that traditional
server-based programmers (PHP/Perl/JSP) may be scared to jump to a
complete JavaScript client without more information on how it performs
and how to structure it for a complex application. That was the case
with me anyway.
The idea:
Re-implement a moderately complex open-source application such as
squirrelmail (just core without plugins for now) with a Qooxdoo
front-end. In the process we would define recommended standards and
tools for development, application layout, server communication,
debugging etc... on both client and server side. This would allow
someone interested in qooxdoo as well as existing qooxdoo users to
view how a complex live application would be structured for best
performance, compatibly, expandability and scalability. By
re-implementing an existing popular project we could also gain a lot
of attention quickly.
Putting it together:
I have a lot of PHP programming experience with PHP content management
systems and application frameworks. I could make recommendations on
and refine a PHP API to communicate with qooxdoo. I could also
implement all the hooks/patches for squirrelmail so we can communicate
with it. I would need to work with a qooxdoo expert to make
recommendations on how to structure the qooxdoo javascript code for a
complex application. I am not an expert in JavaScript.
Why my involvement:
I need to know how to structure qooxdoo code for a complex application
and methodologies to develop with it efficiently. I also need a
standard PHP API to work with qooxdoo and I need web-mail capability
in my qooxdoo applications.
What do you think?
Christoph
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
