Hi Andy -
Just saw your commits last night. What are you planning to implement with JSON and Ajax? We were thinking about doing an auto-complete for the form widget lookup with prototype.js this week, by the way. Best Regards, Si [hidden email] |
Has anybody tried Dojo toolkit for Ajax?
If it was then What are the its cons over prototype.js. If we know more on this will help us to make better decisions in future on, How to pick third party library that can be proposed to Ofbiz community. Regards Anil Patel On 12/12/06, Si Chen <[hidden email]> wrote: > > Hi Andy - > > Just saw your commits last night. What are you planning to implement > with JSON and Ajax? > > We were thinking about doing an auto-complete for the form widget > lookup with prototype.js this week, by the way. > > Best Regards, > > Si > [hidden email] > > > > > |
Hi,
Talking about JavaScript toolkits is becoming like talking about programming languages: it's an endless debate about religious zealotry, really ;) Dojo is good, it works. Prototype is good, it works. Dojo is being adopted as a standard by some Java libraries, like Struts 2 IIRC. Prototype is a de-facto standard in the Ruby on Rails world. Hence my first sentence above. As long as you're considering options for OFBiz, I'd throw another candidate in the ring: jQuery (http://jquery.com/). It's a fantastic little library that also works well, but importantly for me, solves my biggest complaints about Dojo and prototype: size. Both Dojo and prototype end up adding hundreds of KBs to the size of your web page. Sure they might get cached on the client or elsewhere along the way, but still, the software engineer in me hates the thought of all that baggage. Yoav On 12/12/06, Anil Patel <[hidden email]> wrote: > Has anybody tried Dojo toolkit for Ajax? > If it was then What are the its cons over prototype.js. > If we know more on this will help us to make better decisions in future on, > How to pick third party library that can be proposed to Ofbiz community. > > Regards > Anil Patel > > > > On 12/12/06, Si Chen <[hidden email]> wrote: > > > > Hi Andy - > > > > Just saw your commits last night. What are you planning to implement > > with JSON and Ajax? > > > > We were thinking about doing an auto-complete for the form widget > > lookup with prototype.js this week, by the way. > > > > Best Regards, > > > > Si > > [hidden email] > > > > > > > > > > > > |
In reply to this post by Anil Patel
We're actually using JSON on the backend and Dojo on the front end of
an application that we're building right now. We've done research into GWT and a full JSON solution (front end included) as well. Dojo seems quite simple - prototype.js is just about the same - as is Yahoo. Seems to me that the JSON backend is something we can standardize on - and everyone can just pick the front of their choice. Cheers, Tim -- Tim Ruppert HotWax Media http://www.hotwaxmedia.com o:801.649.6594 f:801.649.6594 On Dec 12, 2006, at 10:16 AM, Anil Patel wrote: > Has anybody tried Dojo toolkit for Ajax? > If it was then What are the its cons over prototype.js. > If we know more on this will help us to make better decisions in > future on, > How to pick third party library that can be proposed to Ofbiz > community. > > Regards > Anil Patel > > > > On 12/12/06, Si Chen <[hidden email]> wrote: >> >> Hi Andy - >> >> Just saw your commits last night. What are you planning to implement >> with JSON and Ajax? >> >> We were thinking about doing an auto-complete for the form widget >> lookup with prototype.js this week, by the way. >> >> Best Regards, >> >> Si >> [hidden email] >> >> >> >> >> |
In reply to this post by Yoav Shapira-2
On Tuesday 12 December 2006 12:08, Yoav Shapira wrote:
> Hi, > Talking about JavaScript toolkits is becoming like talking about > programming languages: it's an endless debate about religious > zealotry, really ;) > > Dojo is good, it works. Prototype is good, it works. Dojo is being > adopted as a standard by some Java libraries, like Struts 2 IIRC. > Prototype is a de-facto standard in the Ruby on Rails world. Hence my > first sentence above. > > As long as you're considering options for OFBiz, I'd throw another > candidate in the ring: jQuery (http://jquery.com/). It's a fantastic > little library that also works well, but importantly for me, solves my > biggest complaints about Dojo and prototype: size. Both Dojo and > prototype end up adding hundreds of KBs to the size of your web page. > Sure they might get cached on the client or elsewhere along the way, > but still, the software engineer in me hates the thought of all that > baggage. <trolling> We need something thin, like OFBiz! ;-) From a strategic point of view I think that Dojo has a lot of inertia developing in the Java community and that is going to pay off for us. Everyone with any sense knows that Ruby is doomed to be subsumed by the unstoppable Linux+Java stack since no one seriously believes that Linux+Ruby is a viable adversary against Windows+.NET. </trolling> Actually, this JQuery stuff looks intruiging. -- Ean Schuessler, CTO [hidden email] 214-720-0700 x 315 Brainfood, Inc. http://www.brainfood.com |
subsumed? I had never heard that word before. Thanks for the vocabulary lesson.
Main Entry: sub·sume Pronunciation: s&b-'süm Function: transitive verb Inflected Form(s): sub·sumed; sub·sum·ing Etymology: New Latin subsumere, from Latin sub- + sumere to take up -- more at CONSUME : to include or place within something larger or more comprehensive : encompass as a subordinate or component element <red, green, and yellow are subsumed under the term "color"> -Al On 12/12/06, Ean Schuessler <[hidden email]> wrote: > On Tuesday 12 December 2006 12:08, Yoav Shapira wrote: > > Hi, > > Talking about JavaScript toolkits is becoming like talking about > > programming languages: it's an endless debate about religious > > zealotry, really ;) > > > > Dojo is good, it works. Prototype is good, it works. Dojo is being > > adopted as a standard by some Java libraries, like Struts 2 IIRC. > > Prototype is a de-facto standard in the Ruby on Rails world. Hence my > > first sentence above. > > > > As long as you're considering options for OFBiz, I'd throw another > > candidate in the ring: jQuery (http://jquery.com/). It's a fantastic > > little library that also works well, but importantly for me, solves my > > biggest complaints about Dojo and prototype: size. Both Dojo and > > prototype end up adding hundreds of KBs to the size of your web page. > > Sure they might get cached on the client or elsewhere along the way, > > but still, the software engineer in me hates the thought of all that > > baggage. > > <trolling> > We need something thin, like OFBiz! ;-) > > From a strategic point of view I think that Dojo has a lot of inertia > developing in the Java community and that is going to pay off for us. > Everyone with any sense knows that Ruby is doomed to be subsumed by the > unstoppable Linux+Java stack since no one seriously believes that Linux+Ruby > is a viable adversary against Windows+.NET. > </trolling> > > Actually, this JQuery stuff looks intruiging. > > -- > Ean Schuessler, CTO > [hidden email] > 214-720-0700 x 315 > Brainfood, Inc. > http://www.brainfood.com > |
Administrator
|
We use(d?) it a lot in AI (at least here in Europe?). I thought it came from English (like most computer words) never searched ;o)
BTW not really surprised that it's derived from Latin. Jacques ----- Original Message ----- From: "Al Byers" <[hidden email]> To: <[hidden email]> Sent: Tuesday, December 12, 2006 8:27 PM Subject: Re: json + prototype + ajax? > subsumed? I had never heard that word before. Thanks for the vocabulary lesson. > > Main Entry: sub·sume > Pronunciation: s&b-'süm > Function: transitive verb > Inflected Form(s): sub·sumed; sub·sum·ing > Etymology: New Latin subsumere, from Latin sub- + sumere to take up -- > more at CONSUME > : to include or place within something larger or more comprehensive : > encompass as a subordinate or component element <red, green, and > yellow are subsumed under the term "color"> > > -Al > > On 12/12/06, Ean Schuessler <[hidden email]> wrote: > > On Tuesday 12 December 2006 12:08, Yoav Shapira wrote: > > > Hi, > > > Talking about JavaScript toolkits is becoming like talking about > > > programming languages: it's an endless debate about religious > > > zealotry, really ;) > > > > > > Dojo is good, it works. Prototype is good, it works. Dojo is being > > > adopted as a standard by some Java libraries, like Struts 2 IIRC. > > > Prototype is a de-facto standard in the Ruby on Rails world. Hence my > > > first sentence above. > > > > > > As long as you're considering options for OFBiz, I'd throw another > > > candidate in the ring: jQuery (http://jquery.com/). It's a fantastic > > > little library that also works well, but importantly for me, solves my > > > biggest complaints about Dojo and prototype: size. Both Dojo and > > > prototype end up adding hundreds of KBs to the size of your web page. > > > Sure they might get cached on the client or elsewhere along the way, > > > but still, the software engineer in me hates the thought of all that > > > baggage. > > > > <trolling> > > We need something thin, like OFBiz! ;-) > > > > From a strategic point of view I think that Dojo has a lot of inertia > > developing in the Java community and that is going to pay off for us. > > Everyone with any sense knows that Ruby is doomed to be subsumed by the > > unstoppable Linux+Java stack since no one seriously believes that Linux+Ruby > > is a viable adversary against Windows+.NET. > > </trolling> > > > > Actually, this JQuery stuff looks intruiging. > > > > -- > > Ean Schuessler, CTO > > [hidden email] > > 214-720-0700 x 315 > > Brainfood, Inc. > > http://www.brainfood.com > > |
In reply to this post by byersa
On Tuesday 12 December 2006 13:27, Al Byers wrote:
> subsumed? I had never heard that word before. Thanks for the vocabulary > lesson. > > Main Entry: sub·sume > Pronunciation: s&b-'süm > Function: transitive verb > Inflected Form(s): sub·sumed; sub·sum·ing > Etymology: New Latin subsumere, from Latin sub- + sumere to take up -- > more at CONSUME > > : to include or place within something larger or more comprehensive : > > encompass as a subordinate or component element <red, green, and > yellow are subsumed under the term "color"> Just so: http://jruby.sourceforge.net/ ;-) -- Ean Schuessler, CTO [hidden email] 214-720-0700 x 315 Brainfood, Inc. http://www.brainfood.com |
In reply to this post by Yoav Shapira-2
Here's an interesting conclusion from this article - http://
www.informit.com/guides/content.asp?g=webdesign&seqNum=281&rl=1: Conclusion All three scripts have their pros and cons that make them compete quite directly with each other. In the end, what script is best for you truly depends on your needs and preferences. If you’re looking for a massive feature set, go with Dojo. If you’re looking for optimizing your JavaScript writing techniques and cutting down on development time, try out Prototype. And lastly, if you want to have the best of both worlds and aren’t afraid to write a decent amount of functionality yourself, jQuery is worth a look. Cheers, Tim -- Tim Ruppert HotWax Media http://www.hotwaxmedia.com o:801.649.6594 f:801.649.6594 On Dec 12, 2006, at 11:08 AM, Yoav Shapira wrote: > Hi, > Talking about JavaScript toolkits is becoming like talking about > programming languages: it's an endless debate about religious > zealotry, really ;) > > Dojo is good, it works. Prototype is good, it works. Dojo is being > adopted as a standard by some Java libraries, like Struts 2 IIRC. > Prototype is a de-facto standard in the Ruby on Rails world. Hence my > first sentence above. > > As long as you're considering options for OFBiz, I'd throw another > candidate in the ring: jQuery (http://jquery.com/). It's a fantastic > little library that also works well, but importantly for me, solves my > biggest complaints about Dojo and prototype: size. Both Dojo and > prototype end up adding hundreds of KBs to the size of your web page. > Sure they might get cached on the client or elsewhere along the way, > but still, the software engineer in me hates the thought of all that > baggage. > > Yoav > > On 12/12/06, Anil Patel <[hidden email]> wrote: >> Has anybody tried Dojo toolkit for Ajax? >> If it was then What are the its cons over prototype.js. >> If we know more on this will help us to make better decisions in >> future on, >> How to pick third party library that can be proposed to Ofbiz >> community. >> >> Regards >> Anil Patel >> >> >> >> On 12/12/06, Si Chen <[hidden email]> wrote: >> > >> > Hi Andy - >> > >> > Just saw your commits last night. What are you planning to >> implement >> > with JSON and Ajax? >> > >> > We were thinking about doing an auto-complete for the form widget >> > lookup with prototype.js this week, by the way. >> > >> > Best Regards, >> > >> > Si >> > [hidden email] >> > >> > >> > >> > >> > >> >> |
Hi all, two thoughts about all this:
It's better that we implement something independent of toolkit. I just finished the ajax autocomplete stuff Si mentioned and I think that a toolkit-agnostic approach is quite feasible. If not, then we can write an interface and let people write the binding libraries for their favorite kit. I think this can be accomplished by comparing several approaches to the same problem. With such data, we can better see how a toolkit agnostic solution would work and start taking steps to implement it. So without further ado, I propose we implement autocomplete in the form widget using our favorite toolkits and submit the patches and code examples to Jira. With that in mind, I'd like to introduce our implementation of autocomplete using form widget, prototype and the CRMSFA application. It took me awhile to perfect the search and validation features, and they work quite well. Hopefully, this can be used as a basis for other toolkit implementations. Unfortunately, my day is over, so please keep an eye on Jira tomorrow and we'll have the patches, code and demo sites to play with. Cheers, - Leon My implementation is a little bit rough, but it should provide an interesting Tim Ruppert wrote: > Here's an interesting conclusion from this article - > http://www.informit.com/guides/content.asp?g=webdesign&seqNum=281&rl=1: > > Conclusion > > All three scripts have their pros and cons that make them compete quite > directly with each other. In the end, what script is best for you truly > depends on your needs and preferences. If you’re looking for a massive > feature set, go with Dojo. If you’re looking for optimizing your > JavaScript writing techniques and cutting down on development time, try > out Prototype. And lastly, if you want to have the best of both worlds > and aren’t afraid to write a decent amount of functionality yourself, > jQuery is worth a look. > > Cheers, > Tim > > -- > Tim Ruppert > HotWax Media > http://www.hotwaxmedia.com > > o:801.649.6594 > f:801.649.6594 > > > On Dec 12, 2006, at 11:08 AM, Yoav Shapira wrote: > >> Hi, >> Talking about JavaScript toolkits is becoming like talking about >> programming languages: it's an endless debate about religious >> zealotry, really ;) >> >> Dojo is good, it works. Prototype is good, it works. Dojo is being >> adopted as a standard by some Java libraries, like Struts 2 IIRC. >> Prototype is a de-facto standard in the Ruby on Rails world. Hence my >> first sentence above. >> >> As long as you're considering options for OFBiz, I'd throw another >> candidate in the ring: jQuery (http://jquery.com/). It's a fantastic >> little library that also works well, but importantly for me, solves my >> biggest complaints about Dojo and prototype: size. Both Dojo and >> prototype end up adding hundreds of KBs to the size of your web page. >> Sure they might get cached on the client or elsewhere along the way, >> but still, the software engineer in me hates the thought of all that >> baggage. >> >> Yoav >> >> On 12/12/06, Anil Patel <[hidden email]> wrote: >>> Has anybody tried Dojo toolkit for Ajax? >>> If it was then What are the its cons over prototype.js. >>> If we know more on this will help us to make better decisions in >>> future on, >>> How to pick third party library that can be proposed to Ofbiz >>> community. >>> >>> Regards >>> Anil Patel >>> >>> >>> >>> On 12/12/06, Si Chen <[hidden email]> wrote: >>> > >>> > Hi Andy - >>> > >>> > Just saw your commits last night. What are you planning to implement >>> > with JSON and Ajax? >>> > >>> > We were thinking about doing an auto-complete for the form widget >>> > lookup with prototype.js this week, by the way. >>> > >>> > Best Regards, >>> > >>> > Si >>> > [hidden email] >>> > >>> > >>> > >>> > >>> > >>> >>> > > |
In reply to this post by Si Chen-2
Si (& all),
I am in process of doing a lot of custom AJAX stuff for a new client. I intended on using prototype.js but based on conversations with other people decided to go with dojo instead. The main part of what I did was a JSON wrapper around the service event handler. What this does is allows you to define (controller) requests for ajax calls and have the results return in a lightweight (JSON) format. This will work with any front end toolkit (Yahoo, Prototype, Dojo, etc). The main point is to define a standard pattern for AJAX requests in OFBiz. Deciding on a toolkit for the javascript is very important and based on what I have researched and discussed with other people, Dojo seems to be the way to go. Of course, I am open for discussion with this, but we really should decide on a standard for contributions back to OFBiz. The last thing I want to see is several different ways of communication and different toolkits being used. Prototype.js has been removed from SVN for the time being. As soon as there is code which uses one of the toolkits it can be added back in. Let's start a community vote for the default AJAX toolkit to use in OFBiz. Based on the work I did, I have already setup the back end pattern, services using JSON for the return. Now let's decide on a front end toolkit. First lets, define the candidates: 1) Dojo 2) Prototype Andy Si Chen wrote: > Hi Andy - > > Just saw your commits last night. What are you planning to implement > with JSON and Ajax? > > We were thinking about doing an auto-complete for the form widget lookup > with prototype.js this week, by the way. > > Best Regards, > > Si > [hidden email] > > > > smime.p7s (4K) Download Attachment |
We're using Dojo with Ofbiz. I like it.
Regards Anil Patel On 12/13/06, A. Zeneski <[hidden email]> wrote: > > Si (& all), > > I am in process of doing a lot of custom AJAX stuff for a new client. I > intended on using prototype.js but based on conversations with other > people decided to go with dojo instead. > > The main part of what I did was a JSON wrapper around the service event > handler. What this does is allows you to define (controller) requests > for ajax calls and have the results return in a lightweight (JSON) format. > > This will work with any front end toolkit (Yahoo, Prototype, Dojo, etc). > The main point is to define a standard pattern for AJAX requests in OFBiz. > > Deciding on a toolkit for the javascript is very important and based on > what I have researched and discussed with other people, Dojo seems to be > the way to go. > > Of course, I am open for discussion with this, but we really should > decide on a standard for contributions back to OFBiz. The last thing I > want to see is several different ways of communication and different > toolkits being used. > > Prototype.js has been removed from SVN for the time being. As soon as > there is code which uses one of the toolkits it can be added back in. > > Let's start a community vote for the default AJAX toolkit to use in > OFBiz. Based on the work I did, I have already setup the back end > pattern, services using JSON for the return. Now let's decide on a front > end toolkit. > > First lets, define the candidates: > > 1) Dojo > 2) Prototype > > Andy > > Si Chen wrote: > > Hi Andy - > > > > Just saw your commits last night. What are you planning to implement > > with JSON and Ajax? > > > > We were thinking about doing an auto-complete for the form widget lookup > > with prototype.js this week, by the way. > > > > Best Regards, > > > > Si > > [hidden email] > > > > > > > > > > > |
In reply to this post by Andrew Zeneski
Hi,
Ooops Dojo is supported by IBM & AOL ....so I will prefer Dojo. http://dojotoolkit.org/foundation/ On 12/14/06, A. Zeneski <[hidden email]> wrote: > > Si (& all), > > I am in process of doing a lot of custom AJAX stuff for a new client. I > intended on using prototype.js but based on conversations with other > people decided to go with dojo instead. > > The main part of what I did was a JSON wrapper around the service event > handler. What this does is allows you to define (controller) requests > for ajax calls and have the results return in a lightweight (JSON) format. > > This will work with any front end toolkit (Yahoo, Prototype, Dojo, etc). > The main point is to define a standard pattern for AJAX requests in OFBiz. > > Deciding on a toolkit for the javascript is very important and based on > what I have researched and discussed with other people, Dojo seems to be > the way to go. > > Of course, I am open for discussion with this, but we really should > decide on a standard for contributions back to OFBiz. The last thing I > want to see is several different ways of communication and different > toolkits being used. > > Prototype.js has been removed from SVN for the time being. As soon as > there is code which uses one of the toolkits it can be added back in. > > Let's start a community vote for the default AJAX toolkit to use in > OFBiz. Based on the work I did, I have already setup the back end > pattern, services using JSON for the return. Now let's decide on a front > end toolkit. > > First lets, define the candidates: > > 1) Dojo > 2) Prototype > > Andy > Regards Alex D. Fleming |
I used prototype for my initial test and found it very easy to work
with. Dojo on the other hand seemed to have a much broader learning curve. It too me a while to get everything working, but I think it is due to the ajax part being more verbose. The extra features such as DND and other widgets is very nice as well. The fact that DOJO is available under the BSD license is a plus as well. I think there should be no license issues with this library. Should we just say DOJO is the way to go for future Ajax based tools in OFBiz or do we need a formal vote? Andrew Alex D. Fleming wrote: > Hi, > > Ooops Dojo is supported by IBM & AOL ....so I will prefer Dojo. > > http://dojotoolkit.org/foundation/ > > > On 12/14/06, A. Zeneski <[hidden email]> wrote: >> >> Si (& all), >> >> I am in process of doing a lot of custom AJAX stuff for a new client. I >> intended on using prototype.js but based on conversations with other >> people decided to go with dojo instead. >> >> The main part of what I did was a JSON wrapper around the service event >> handler. What this does is allows you to define (controller) requests >> for ajax calls and have the results return in a lightweight (JSON) >> format. >> >> This will work with any front end toolkit (Yahoo, Prototype, Dojo, etc). >> The main point is to define a standard pattern for AJAX requests in >> OFBiz. >> >> Deciding on a toolkit for the javascript is very important and based on >> what I have researched and discussed with other people, Dojo seems to be >> the way to go. >> >> Of course, I am open for discussion with this, but we really should >> decide on a standard for contributions back to OFBiz. The last thing I >> want to see is several different ways of communication and different >> toolkits being used. >> >> Prototype.js has been removed from SVN for the time being. As soon as >> there is code which uses one of the toolkits it can be added back in. >> >> Let's start a community vote for the default AJAX toolkit to use in >> OFBiz. Based on the work I did, I have already setup the back end >> pattern, services using JSON for the return. Now let's decide on a front >> end toolkit. >> >> First lets, define the candidates: >> >> 1) Dojo >> 2) Prototype >> >> Andy >> smime.p7s (4K) Download Attachment |
Andy,
>> Should we just say DOJO is the way to go for future Ajax based tools in >> OFBiz or do we need a formal vote? Yeah I will like to go with DOJO. Voting on this is a good idea :-) Now a days your active participation on mailing list makes me Happy :-). Thanks for it. On 12/14/06, A. Zeneski <[hidden email]> wrote: > > I used prototype for my initial test and found it very easy to work > with. Dojo on the other hand seemed to have a much broader learning > curve. It too me a while to get everything working, but I think it is > due to the ajax part being more verbose. > > The extra features such as DND and other widgets is very nice as well. > > The fact that DOJO is available under the BSD license is a plus as well. > I think there should be no license issues with this library. > > Should we just say DOJO is the way to go for future Ajax based tools in > OFBiz or do we need a formal vote? > > Andrew > > Alex D. Fleming wrote: > > Hi, > > > > Ooops Dojo is supported by IBM & AOL ....so I will prefer Dojo. > > > > http://dojotoolkit.org/foundation/ > > > > > > On 12/14/06, A. Zeneski <[hidden email]> wrote: > >> > >> Si (& all), > >> > >> I am in process of doing a lot of custom AJAX stuff for a new client. I > >> intended on using prototype.js but based on conversations with other > >> people decided to go with dojo instead. > >> > >> The main part of what I did was a JSON wrapper around the service event > >> handler. What this does is allows you to define (controller) requests > >> for ajax calls and have the results return in a lightweight (JSON) > >> format. > >> > >> This will work with any front end toolkit (Yahoo, Prototype, Dojo, > etc). > >> The main point is to define a standard pattern for AJAX requests in > >> OFBiz. > >> > >> Deciding on a toolkit for the javascript is very important and based on > >> what I have researched and discussed with other people, Dojo seems to > be > >> the way to go. > >> > >> Of course, I am open for discussion with this, but we really should > >> decide on a standard for contributions back to OFBiz. The last thing I > >> want to see is several different ways of communication and different > >> toolkits being used. > >> > >> Prototype.js has been removed from SVN for the time being. As soon as > >> there is code which uses one of the toolkits it can be added back in. > >> > >> Let's start a community vote for the default AJAX toolkit to use in > >> OFBiz. Based on the work I did, I have already setup the back end > >> pattern, services using JSON for the return. Now let's decide on a > front > >> end toolkit. > >> > >> First lets, define the candidates: > >> > >> 1) Dojo > >> 2) Prototype > >> > >> Andy > >> > > > -- Regards Alex D. Fleming |
In reply to this post by Andrew Zeneski
Just to continue the push towards Dojo, I am about to submit a new
Anonymous Checkout process for https://issues.apache.org/jira/browse/ OFBIZ-510 which is based upon Dojo. You guys will like it - 3 steps and working towards my 2 step process goal. Cheers, Tim -- Tim Ruppert HotWax Media http://www.hotwaxmedia.com o:801.649.6594 f:801.649.6594 On Dec 13, 2006, at 4:36 PM, A. Zeneski wrote: > I used prototype for my initial test and found it very easy to work > with. Dojo on the other hand seemed to have a much broader learning > curve. It too me a while to get everything working, but I think it is > due to the ajax part being more verbose. > > The extra features such as DND and other widgets is very nice as well. > > The fact that DOJO is available under the BSD license is a plus as > well. > I think there should be no license issues with this library. > > Should we just say DOJO is the way to go for future Ajax based > tools in > OFBiz or do we need a formal vote? > > Andrew > > Alex D. Fleming wrote: >> Hi, >> >> Ooops Dojo is supported by IBM & AOL ....so I will prefer Dojo. >> >> http://dojotoolkit.org/foundation/ >> >> >> On 12/14/06, A. Zeneski <[hidden email]> wrote: >>> >>> Si (& all), >>> >>> I am in process of doing a lot of custom AJAX stuff for a new >>> client. I >>> intended on using prototype.js but based on conversations with other >>> people decided to go with dojo instead. >>> >>> The main part of what I did was a JSON wrapper around the service >>> event >>> handler. What this does is allows you to define (controller) >>> requests >>> for ajax calls and have the results return in a lightweight (JSON) >>> format. >>> >>> This will work with any front end toolkit (Yahoo, Prototype, >>> Dojo, etc). >>> The main point is to define a standard pattern for AJAX requests in >>> OFBiz. >>> >>> Deciding on a toolkit for the javascript is very important and >>> based on >>> what I have researched and discussed with other people, Dojo >>> seems to be >>> the way to go. >>> >>> Of course, I am open for discussion with this, but we really should >>> decide on a standard for contributions back to OFBiz. The last >>> thing I >>> want to see is several different ways of communication and different >>> toolkits being used. >>> >>> Prototype.js has been removed from SVN for the time being. As >>> soon as >>> there is code which uses one of the toolkits it can be added back >>> in. >>> >>> Let's start a community vote for the default AJAX toolkit to use in >>> OFBiz. Based on the work I did, I have already setup the back end >>> pattern, services using JSON for the return. Now let's decide on >>> a front >>> end toolkit. >>> >>> First lets, define the candidates: >>> >>> 1) Dojo >>> 2) Prototype >>> >>> Andy >>> |
I am curious as to the pattern used to make the async calls, what method
of return is used here? I see two possible patterns which would be useful: 1) JSON compressed objects. This will require more processing on the front end to pull the data and format the HTML. I like leaving this in the front end code personally. This is currently implemented using the JSONServiceEventHandler request handler. 2) Screen Widget based HTML return. The Ajax request makes a simple call which returns a HTML fragment (developed using screen widgets). The return is then just plugged in by updating the element content (innerHTML). Either of these patterns is fine by me, and I believe that for most applications a combination of the two would be necessary. I am sure there are many other ways to accomplish the same thing, but since there is so much effort about to begin around 'Ajaxing' OFBiz making sure things are consistent is #1 priority. I'm curious as to what other 'patterns' people have come up with (if any). Andrew Tim Ruppert wrote: > Just to continue the push towards Dojo, I am about to submit a new > Anonymous Checkout process for > https://issues.apache.org/jira/browse/OFBIZ-510 which is based upon > Dojo. You guys will like it - 3 steps and working towards my 2 step > process goal. > > Cheers, > Tim > -- > Tim Ruppert > HotWax Media > http://www.hotwaxmedia.com > > o:801.649.6594 > f:801.649.6594 > > > On Dec 13, 2006, at 4:36 PM, A. Zeneski wrote: > >> I used prototype for my initial test and found it very easy to work >> with. Dojo on the other hand seemed to have a much broader learning >> curve. It too me a while to get everything working, but I think it is >> due to the ajax part being more verbose. >> >> The extra features such as DND and other widgets is very nice as well. >> >> The fact that DOJO is available under the BSD license is a plus as well. >> I think there should be no license issues with this library. >> >> Should we just say DOJO is the way to go for future Ajax based tools in >> OFBiz or do we need a formal vote? >> >> Andrew >> >> Alex D. Fleming wrote: >>> Hi, >>> >>> Ooops Dojo is supported by IBM & AOL ....so I will prefer Dojo. >>> >>> http://dojotoolkit.org/foundation/ >>> >>> >>> On 12/14/06, A. Zeneski <[hidden email]> wrote: >>>> >>>> Si (& all), >>>> >>>> I am in process of doing a lot of custom AJAX stuff for a new client. I >>>> intended on using prototype.js but based on conversations with other >>>> people decided to go with dojo instead. >>>> >>>> The main part of what I did was a JSON wrapper around the service event >>>> handler. What this does is allows you to define (controller) requests >>>> for ajax calls and have the results return in a lightweight (JSON) >>>> format. >>>> >>>> This will work with any front end toolkit (Yahoo, Prototype, Dojo, >>>> etc). >>>> The main point is to define a standard pattern for AJAX requests in >>>> OFBiz. >>>> >>>> Deciding on a toolkit for the javascript is very important and based on >>>> what I have researched and discussed with other people, Dojo seems >>>> to be >>>> the way to go. >>>> >>>> Of course, I am open for discussion with this, but we really should >>>> decide on a standard for contributions back to OFBiz. The last thing I >>>> want to see is several different ways of communication and different >>>> toolkits being used. >>>> >>>> Prototype.js has been removed from SVN for the time being. As soon as >>>> there is code which uses one of the toolkits it can be added back in. >>>> >>>> Let's start a community vote for the default AJAX toolkit to use in >>>> OFBiz. Based on the work I did, I have already setup the back end >>>> pattern, services using JSON for the return. Now let's decide on a >>>> front >>>> end toolkit. >>>> >>>> First lets, define the candidates: >>>> >>>> 1) Dojo >>>> 2) Prototype >>>> >>>> Andy >>>> > > smime.p7s (4K) Download Attachment |
In reply to this post by Alex D. Fleming-2
I'll let this thread run a little while longer before we say to have a
full official vote. As of right now, it appears most people are looking at Dojo, and that is fine with me. It seems that most of these toolkits do the same thing, so to me its just a matter of making a decision so I can push forward with my work. As for being more active on the lists, sorry I have been MIA for so long. I've been involved in a lot of custom (non open source) work as of late and apologize for not being around. I will do my best to be here as much as possible. Thanks! Andrew Alex D. Fleming wrote: > Andy, > >>> Should we just say DOJO is the way to go for future Ajax based tools in >>> OFBiz or do we need a formal vote? > > Yeah I will like to go with DOJO. > Voting on this is a good idea :-) > > Now a days your active participation on mailing list makes me Happy :-). > Thanks for it. > > > On 12/14/06, A. Zeneski <[hidden email]> wrote: >> >> I used prototype for my initial test and found it very easy to work >> with. Dojo on the other hand seemed to have a much broader learning >> curve. It too me a while to get everything working, but I think it is >> due to the ajax part being more verbose. >> >> The extra features such as DND and other widgets is very nice as well. >> >> The fact that DOJO is available under the BSD license is a plus as well. >> I think there should be no license issues with this library. >> >> Should we just say DOJO is the way to go for future Ajax based tools in >> OFBiz or do we need a formal vote? >> >> Andrew >> >> Alex D. Fleming wrote: >> > Hi, >> > >> > Ooops Dojo is supported by IBM & AOL ....so I will prefer Dojo. >> > >> > http://dojotoolkit.org/foundation/ >> > >> > >> > On 12/14/06, A. Zeneski <[hidden email]> wrote: >> >> >> >> Si (& all), >> >> >> >> I am in process of doing a lot of custom AJAX stuff for a new >> client. I >> >> intended on using prototype.js but based on conversations with other >> >> people decided to go with dojo instead. >> >> >> >> The main part of what I did was a JSON wrapper around the service >> event >> >> handler. What this does is allows you to define (controller) requests >> >> for ajax calls and have the results return in a lightweight (JSON) >> >> format. >> >> >> >> This will work with any front end toolkit (Yahoo, Prototype, Dojo, >> etc). >> >> The main point is to define a standard pattern for AJAX requests in >> >> OFBiz. >> >> >> >> Deciding on a toolkit for the javascript is very important and >> based on >> >> what I have researched and discussed with other people, Dojo seems to >> be >> >> the way to go. >> >> >> >> Of course, I am open for discussion with this, but we really should >> >> decide on a standard for contributions back to OFBiz. The last thing I >> >> want to see is several different ways of communication and different >> >> toolkits being used. >> >> >> >> Prototype.js has been removed from SVN for the time being. As soon as >> >> there is code which uses one of the toolkits it can be added back in. >> >> >> >> Let's start a community vote for the default AJAX toolkit to use in >> >> OFBiz. Based on the work I did, I have already setup the back end >> >> pattern, services using JSON for the return. Now let's decide on a >> front >> >> end toolkit. >> >> >> >> First lets, define the candidates: >> >> >> >> 1) Dojo >> >> 2) Prototype >> >> >> >> Andy >> >> >> >> >> > > smime.p7s (4K) Download Attachment |
I'm not sure about the other toolkits, but when I
looked around for some implementation ideas, I like the fact that one of Dojo's precepts is to degrade when not JS is turned off. This may be true of other toolkits as well, but Dojo states it specifically. |
In reply to this post by Andrew Zeneski
2) Screen Widget based HTML return. The Ajax request makes a simple call
which returns a HTML fragment (developed using screen widgets). The return is then just plugged in by updating the element content (innerHTML). I have used this pattern with screen/ftl for generating html on demand. Regards On 12/13/06, A. Zeneski <[hidden email]> wrote: > > I am curious as to the pattern used to make the async calls, what method > of return is used here? > > I see two possible patterns which would be useful: > > 1) JSON compressed objects. This will require more processing on the > front end to pull the data and format the HTML. I like leaving this in > the front end code personally. This is currently implemented using the > JSONServiceEventHandler request handler. > > 2) Screen Widget based HTML return. The Ajax request makes a simple call > which returns a HTML fragment (developed using screen widgets). The > return is then just plugged in by updating the element content > (innerHTML). > > Either of these patterns is fine by me, and I believe that for most > applications a combination of the two would be necessary. > > I am sure there are many other ways to accomplish the same thing, but > since there is so much effort about to begin around 'Ajaxing' OFBiz > making sure things are consistent is #1 priority. > > I'm curious as to what other 'patterns' people have come up with (if any). > > Andrew > > > Tim Ruppert wrote: > > Just to continue the push towards Dojo, I am about to submit a new > > Anonymous Checkout process for > > https://issues.apache.org/jira/browse/OFBIZ-510 which is based upon > > Dojo. You guys will like it - 3 steps and working towards my 2 step > > process goal. > > > > Cheers, > > Tim > > -- > > Tim Ruppert > > HotWax Media > > http://www.hotwaxmedia.com > > > > o:801.649.6594 > > f:801.649.6594 > > > > > > On Dec 13, 2006, at 4:36 PM, A. Zeneski wrote: > > > >> I used prototype for my initial test and found it very easy to work > >> with. Dojo on the other hand seemed to have a much broader learning > >> curve. It too me a while to get everything working, but I think it is > >> due to the ajax part being more verbose. > >> > >> The extra features such as DND and other widgets is very nice as well. > >> > >> The fact that DOJO is available under the BSD license is a plus as > well. > >> I think there should be no license issues with this library. > >> > >> Should we just say DOJO is the way to go for future Ajax based tools in > >> OFBiz or do we need a formal vote? > >> > >> Andrew > >> > >> Alex D. Fleming wrote: > >>> Hi, > >>> > >>> Ooops Dojo is supported by IBM & AOL ....so I will prefer Dojo. > >>> > >>> http://dojotoolkit.org/foundation/ > >>> > >>> > >>> On 12/14/06, A. Zeneski <[hidden email]> wrote: > >>>> > >>>> Si (& all), > >>>> > >>>> I am in process of doing a lot of custom AJAX stuff for a new client. > I > >>>> intended on using prototype.js but based on conversations with other > >>>> people decided to go with dojo instead. > >>>> > >>>> The main part of what I did was a JSON wrapper around the service > event > >>>> handler. What this does is allows you to define (controller) requests > >>>> for ajax calls and have the results return in a lightweight (JSON) > >>>> format. > >>>> > >>>> This will work with any front end toolkit (Yahoo, Prototype, Dojo, > >>>> etc). > >>>> The main point is to define a standard pattern for AJAX requests in > >>>> OFBiz. > >>>> > >>>> Deciding on a toolkit for the javascript is very important and based > on > >>>> what I have researched and discussed with other people, Dojo seems > >>>> to be > >>>> the way to go. > >>>> > >>>> Of course, I am open for discussion with this, but we really should > >>>> decide on a standard for contributions back to OFBiz. The last thing > I > >>>> want to see is several different ways of communication and different > >>>> toolkits being used. > >>>> > >>>> Prototype.js has been removed from SVN for the time being. As soon as > >>>> there is code which uses one of the toolkits it can be added back in. > >>>> > >>>> Let's start a community vote for the default AJAX toolkit to use in > >>>> OFBiz. Based on the work I did, I have already setup the back end > >>>> pattern, services using JSON for the return. Now let's decide on a > >>>> front > >>>> end toolkit. > >>>> > >>>> First lets, define the candidates: > >>>> > >>>> 1) Dojo > >>>> 2) Prototype > >>>> > >>>> Andy > >>>> > > > > > > > |
Free forum by Nabble | Edit this page |