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.

Yes, but we want to make it even better ;)


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.

No, I think not. Some ideas are really different. We want to handle the queuing and the timeouts inside the queue system which should be on-top the different transport layers. We don't need to really invent stuff here. We must just code it.


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?

For us, yes. Because the next release is that big that it should really get released to the people. Otherwise we would wait again some weeks until the new AJAX stuff is completly ready. Better in my opinion would be that we create another major version after the next release which will be promoted with enhanced AJAX support.


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!

Delegation is not that easy in open-source projects because you have no real always available resources which you can manage. Currently it costs me to much time to even delegate this work. I am sorry. I will do this after the next release comes out.


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?

Binding, yes, this will come after(!) we have a stable well-tested AJAX layer.


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

I will let them in if they are there. To really deliver great work is more than just write a class, submit it and you're done. This includes the further updates to the class, to keep the community up-to-data, writing documentation, answering questions and so on.

I am free to give people developer CVS access on qooxdoo. Especially after the next release is out.

Sebastian


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

Reply via email to