Oliver Vogel schrieb:
Hi!
i agree with kent.
we all here are programmes (if we are not, we can't use qooxdoo ;-). if
we are programming "our" part and you (sebastian) are bringing these
pats together, it may be the best for qooxdoo.
You forgot to mention that developers are not simply developers. They
are different. I have developed around fifty percent (probably more) of
qooxdoo. I would not like to just manage incoming additions. I would
like to code myself. Also there are just not enough people which have
deep understandings of the current qooxdoo internals. How would such
developers, even if they are quite good, handle the further development
of the library? It is not just to develop new classes but also fix
errors and to bring the core of qooxdoo step-by-step to new eras.
i know, it's your child and you want to be the one who is making it. but
if you don't delegate your free-time goes lesser and lesser.
you can do what you want, but i think it is better to have some widgets
(like the datetimepicker and the progressbar) 80% perfect that to wait
until they are 100% perfect (but never will be released ;-).
"you want to be the one who is making it" is just not true. If I want it
this way, we have not published qooxdoo as open-source. True is, that
there must be a group of leading developers which control the direction
of development.
Our current widgets try to be comparable to other commercial stuff from
typical operating system libraries. We don't want to be a pool of many
incomplete or half working widgets. Don't get me wrong here. I don't
want to say, that the existing widgets in qooxdoo are completely perfect
or that your contributed widgets are so bad. I have added a contributed
folder some days ago which is nice to develop new widgets with the
community. We will see how many really great widgets will be developed
there and will be moved later to the qooxdoo core.
Sebastian
Olli
Kent Olsson schrieb:
Hej!
we think there were really great discussions on what features a new AJAX
layer of qooxdoo should have. I have now started to create a new one,
which is based on many ideas of Chris Ricks. Thank you again Chris.
He has been doing a great job.
We have some other ideas added. We want a special request (QxRequest)
and response (QxResponse) object to handle the data between the
different communication layers in qooxdoo. Also we think to have a queue
is great. But we think it is better placed outside the xmlhttp related
stuff. We have done this in our new class QxRequestQueue. This class
create instances of the class QxTransport which handles the wrapping to
the different transport implementations. For example this could be the
classical xmlhttp (QxXmlHttpTransport) or iframes (QxIframeTransport).
It can easily be integrated with what Chris has been doing. DO not
invent the wheel twice.
This concept allows us to add new transport implementations easily if
they appear on the horizon.
Might be an option, but prefer the tool gets ready before that. Are the
priorities correct here?
There are some possibilities of Chris Ricks work missing. Like timeouts
for example. This is something I think should be placed in
QxRequestQueue, too. QxRequestQueue is somewhat basic currently and does
no real queuing.
I agree.
As I have no more time to work on these classes before the final release
of the next version of qooxdoo, this will be also the versions of the
release. Afterwards we will continue the work. You are all invited to
help. Chris, sorry, I hope I have not dis encouraged you with our plans
and decisions. I would really like it, if you could help us, to extend
and modify the newly existing stuff to your needs.
I guess it would be good to delegate these ideas to CHris. He is well
able to finish it if he takes on the task. That releases time for you.
It is not meant that you, Sebastian, have enough time to finish
everything by yourself, because then the limiting factor will be you in
this project. Delegate!
I am still waiting for your response for all the widgets I have
uploaded. I guess that would be better for you to focus on, as many more
people is needing those widgets.
For any further work, please keep the new code more prototype style and
try to omit to send complete full-working classes. We should really
discuss the additions and changes in detail before coding them. Thanks.
I think it would be good Sebastian, if you you could speak clearly about
your ideas here and someone else can take on.
What about data aware widgets? What are your ideas here?
Delegation of Qooxdoo is the future else I guess you will be overloaded
and running around like a rabbit. I guess there are a lot more guys out
here well able to code and deliver. LET THEM IN!!!
The best for Qooxdoo!
Kent
Best regards,
Sebastian
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
