This is line with I said earlier. We should instead use jquery. And
to some extend we need to be ready to help those community to build
and maintain tools that help us.
I will prefer jquery over dojo.
Sent from my iPhone
On Jun 8, 2010, at 10:12 AM, Sascha Rodekamp <sascha.rodekamp.lynx...@googlemail.com
> wrote:
Hey guys,
i started the work to update the Dojo libary to the current version
1.4.
And i have to say that it didn't satisfy me to work on every Dojo
based
JaveScript for a little version update. It will coast a lot of time
to test
and update all the JavaScript Code. And what we have at the end a
new heavy
Dojo libary which brings a lot of widget but it's hard to extend :-)
So i have another (maybe better idea). Why we didn't set Dojo and
Prototype
as depricated
and starting to use jQuerry. In my optinion jQuerry is a better
invest in
the future. There are a lot of Widget/ Plugin's too and it's much
lighter
than Dojo.
Instead of spending my time with updating all the Dojo stuff, i
could spend
my time to migrate all Prototype / Dojo based Code to jQuerry.
What do you think?
Cheers
Sascha
2010/6/5 Anil Patel <anil.pa...@hotwaxmedia.com>
Looks like good plan. Overtime people might choose to replace
prototype
framework with similar thing from Dojo.
Thanks and Regards
Anil Patel
HotWax Media Inc
Find us on the web at www.hotwaxmedia.com or Google Keyword "ofbiz"
On Jun 5, 2010, at 1:13 PM, Jacques Le Roux wrote:
So far I have mostly used Dojo for its tree in a CMS tool, and some
Prototype functions notably for layered lookups.
I still see them as complementary (Dojo coming more complete but
heavier,
Prototype being mostly an API).
I does do think it's necessary to make a choice.
Jacques
From: "Adrian Crum" <adrian.c...@yahoo.com>
From what I recall, the two libraries were included in the
project with
the idea that the most popular one would get used. At the
time, Dojo was a very heavy library and the first attempts to
use it
resulted in very slow page loads. I used Prototype in some
initial Ajax work - mainly because it was pretty easy to use.
Today, I
have no preference for either one.
-Adrian
--- On Sat, 6/5/10, Anil Patel <anil.pa...@hotwaxmedia.com> wrote:
From: Anil Patel <anil.pa...@hotwaxmedia.com>
Subject: Re: Dojo tree 1.4
To: dev@ofbiz.apache.org
Cc: "Anil Patel" <anil.pa...@hotwaxmedia.com>
Date: Saturday, June 5, 2010, 7:00 AM
I started using Dojo in Ofbiz long
back and in six months because of issues faced we switched
to using prototype. At that time there were few others in
comunity who liked prototype better. But I really don't
remember the reasons.
Since then new checkout process was added that uses
prototype for all javascript needs. But did not remove Dojo
because i did not want to upset anybody in community.
Thanks and Regards
Anil Patel
HotWax Media Inc
Find us on the web at www.hotwaxmedia.com or Google Keyword
"ofbiz"
On Jun 5, 2010, at 9:47 AM, Jacques Le Roux wrote:
I have created a branch
http://svn.apache.org/repos/asf/ofbiz/branches/dojo1.4
Nothing else for now
Jacques
From: "Sascha Rodekamp" <sascha.rodekamp.lynx...@googlemail.com>
Hi Jacques ...
jep it's a lot of work but not impossible :)
A brunch is a good idea to start working on this
project. I think the reason
for Antil was, that he isn't use to Dojo. But that
shouldn't be a problem
the syntax isn't complicated.
And by the way, if this will work the new Dojo
will bring us a big benefit
(in my opinion).
Cheers
Sascha
2010/6/5 Jacques Le Roux <jacques.le.r...@les7arts.com>
Sascha,
We should rather use the dev ML for this
thread.
Maybe it's the reason why Anil was reluctant
to use Dojo?
Jacques
Jacques Le Roux wrote:
Sascha Rodekamp wrote:
Hey,
so i started upgrading to dojo 1.4.
The good point is ... Dojo 1.4 has
many really cool new Features which
can
help us to improve the UI.
The Bad thing is, some parts of the
syntax had changed. That effects many
parts in OFBiz (OnePageCheckout,
Trees, all Dojo features Scripts :-)).
Arg, I did not thought it will be so much
trouble :/
So that's a lot of work and i can't do it
on my own ... who volunteer to
help me ;) ??
I could help
First Step is to collect all depending
issues and than to fix them step
by
step.
So if we do that we need a branch I
guess...
Jacques
Have a nice day
Sascha
-- >> http://www.lynx.de
--
http://www.lynx.de
