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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
> [EMAIL PROTECTED]
>
>
>
>
>
