Hi, Using mootools in the developpement of APE JSF saved us a lot of time (ajax request, Class, Events, array & object functions). As it use a special build of mootools for example the $ operator is not included in this build. MooTools build of APE JSF "only" contains Core, Browser, Array, Function, String, Hash, Event, Class, Request, it's 1680 lines of codes (MooTools full is about 4329 lines of code). So it's only include what i realy need in the JSF.
Writing the APE JSF was is something really complex, and i am working on a new development pattern for the future version of APE JSF. For now i still have many things to clarify before start talking about it. But i'll write an article and wait for feedback before starting to work on it. But i think for this future version I'll not use a framework and start by creating a "Request framework". I am always happy to hear some feedback about the JSF. Thanks. Regards. Lorren Biffin a écrit : > Primarily my reasoning is based on the added requirement of loading > mootools into the page. (i.e. making an additional resource call). > This worry is not so prevalent as I use a resource aggregation / cache > tool for JS / CSS anyhow. I use frameworks only when needed to save on > development time / resource load. I don't have a need to modify the > JSF at the moment and the size of the JSF feels trivial, so reading-in > mootools for this reason alone feels silly / awkward. > > Secondarily, I dislike giving the $ operator to mootools w/o a great > reason to do so, as jQuery is usually my framework of choice when I > use one. > > I have nothing against Mootools, it just feels unusual to require it > for an unrelated project to handle (what feels like) a trivial task. > > I also understand that my reasons for wanting a purely APE > implementation of the JSF are likely trivial in the wider scope of the > APE project as a whole, which is why I suggest crowd-sourcing the > development. :) > > All-in-all though, this won't stop me from using APE in it's current > state.. It's all preference and I'm happy to take things as they come. > You guys are doing a great job and I wouldn't want to ask more of you > than you're already generously giving to us. :) > > Lorren Biffin > (425) 522-2673 > http://twitter.com/lorrenbiffin > > > On Fri, Dec 11, 2009 at 6:37 PM, John Chavarria > <[email protected] <mailto:[email protected]>> wrote: > > Could you bring your reasons for such a thing? > > Thanks :) > -- > John Chavarria - CEO / Designer > Weelya - improve the Web > > +33 (0) 4.67.169.778 > +33 (0) 6.43.56.00.83 > > Twitter : @jchavarria / @weelya > > 32 Rue du Faubourg Boutonnet > 34090 Montpellier > > > http://www.ape-project.org/ > http://www.weelya.com/ > > > > On Sat, Dec 12, 2009 at 3:16 AM, Lorren <[email protected] > <mailto:[email protected]>> wrote: > > Ideally I would like to see an APE library independent of any > particular JS framework. > > Maybe this could be crowd-sourced to the APE community as a Weelya > backed initiative? I'm sure there would be much interest and could > potentially bring this idea to fruition much sooner than if > you did it > in-house. :) > > On Dec 11, 6:09 pm, Nicolas Trani <[email protected] > <mailto:[email protected]>> wrote: > > Hi, > > > > mootools is only used by the APE JSF Core that runs into an > iframe. It > > use a specific build of mootools to be more light. As it run > into an > > iframe you can use any framework on your website the APE JSF > Client > > communicate with the Core. > > > > A "[your framework name here]" Core is not planed by the APE > team (for > > now) as it will be verry hard to maintains two version of > the Core. > > Mayebe in the future APE JSF will use his own framework. > > > > Regards. > > > > Lorren wrote: > > > Is there a non-mootools version of the JSF planned? > > > > -- > > Nicolas Trani - D veloppeur web > > Weelya - Improve the web > > 32 rue du faubourg boutonnet > > 34090 Montpellier > > Tel : 04 67 169 778http://www.weelya.com > > -- > You received this message because you are subscribed to the Google > Groups "APE Project" group. > To post to this group, send email to > [email protected] <mailto:[email protected]> > To unsubscribe from this group, send email to > [email protected] > <mailto:ape-project%[email protected]> > For more options, visit this group at > http://groups.google.com/group/ape-project?hl=en > --- > APE Project (Ajax Push Engine) > Official website : http://www.ape-project.org/ > Git Hub : http://github.com/APE-Project/ > > > -- > You received this message because you are subscribed to the Google > Groups "APE Project" group. > To post to this group, send email to [email protected] > <mailto:[email protected]> > To unsubscribe from this group, send email to > [email protected] > <mailto:ape-project%[email protected]> > For more options, visit this group at > http://groups.google.com/group/ape-project?hl=en > --- > APE Project (Ajax Push Engine) > Official website : http://www.ape-project.org/ > Git Hub : http://github.com/APE-Project/ > > > -- > You received this message because you are subscribed to the Google > Groups "APE Project" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/ape-project?hl=en > --- > APE Project (Ajax Push Engine) > Official website : http://www.ape-project.org/ > Git Hub : http://github.com/APE-Project/ -- You received this message because you are subscribed to the Google Groups "APE Project" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/ape-project?hl=en --- APE Project (Ajax Push Engine) Official website : http://www.ape-project.org/ Git Hub : http://github.com/APE-Project/
