Re: Wicket JavaScript Library Integration - A Common Base
Cemal Bayramoglu schrieb: dear Cemal, > What I was proposing was not > as a solution to incompatibilities between such multiple > dependencies. fair enough. I am a believer in keeping the core as simple and light as possible whilst still open (and designed for) potential enhancement with extended functionality. agreed. it is just that - for quite some time - i feel an urgent need to solve this dependency problem with a broad level of acceptance in the community, so that component authors can choose a 'standard' way to express dependencies to external JS Libs that are then with on the page level. the scope of your project is different then, in the first instance, so i´ll take it to another thread. anyway, i am eager to keep an eye on your project and - as you said - maybe it can be extended accordingly. thanks, uwe - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket JavaScript Library Integration - A Common Base
Stefan, ... and encapsulating JavaScript statements; the two main concerns I'd imagine anyone making an integration between Wicket and a JavaScript library has. Regards - Cemal jWeekend OO & Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com On 26 March 2010 13:37, Stefan Lindner wrote: > This sounds exactly like the thing I'm looking for. A small and simple > framework for HeaderContribution. > > Stefan > > -Ursprüngliche Nachricht- > Von: ce...@jweekend.com [mailto:ce...@jweekend.com] Im Auftrag von Cemal > Bayramoglu > Gesendet: Freitag, 26. März 2010 14:26 > An: users > Betreff: Re: Wicket JavaScript Library Integration - A Common Base > > Uwe! > > I was thinking in terms of a simple core, of well defined and limited > scope. It would provide a clear and well trodden way for people to > integrate their favourite JavaScript libraries with Wicket in a > consistent and effective, tried and tested way. > > As you say, there are always going to be potential complications > whenever a single web page depends on more than one version of the > same JavaScript libraries, or sometimes even when some libraries clash > with other, (seemingly) unrelated ones. What I was proposing was not > as a solution to incompatibilities between such multiple > dependencies. On the other hand, once we had the common base (that > seems to have already attracted some interest and even potential > development support here), an extension, optional for people who > want/need it, could try to manage the versions and other causes of > conflict you talk of, if I understand you correctly. > > I am a believer in keeping the core as simple and light as possible > whilst still open (and designed for) potential enhancement with > extended functionality. > > Regards - Cemal > jWeekend > OO & Java Technologies, Wicket > Consulting, Development, Training > http://jWeekend.com > > 2010/3/26 Uwe Schäfer : >> Uwe Schäfer schrieb: >> >> Hi Cemal, >> >>>> I was thinking that it could possibly be sensible to have another >>>> project where we abstract out the mechanisms wiQuery provides for >>>> resources and JavaScript statements. >> >> to keep that topic alive: do you agree that providing a unified way for >> component authors to contribute standard libs to the page, as well as >> coordinating these dependencies on the page level is a primary goal of >> creating this lib? >> >> cu uwe >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: Wicket JavaScript Library Integration - A Common Base
This sounds exactly like the thing I'm looking for. A small and simple framework for HeaderContribution. Stefan -Ursprüngliche Nachricht- Von: ce...@jweekend.com [mailto:ce...@jweekend.com] Im Auftrag von Cemal Bayramoglu Gesendet: Freitag, 26. März 2010 14:26 An: users Betreff: Re: Wicket JavaScript Library Integration - A Common Base Uwe! I was thinking in terms of a simple core, of well defined and limited scope. It would provide a clear and well trodden way for people to integrate their favourite JavaScript libraries with Wicket in a consistent and effective, tried and tested way. As you say, there are always going to be potential complications whenever a single web page depends on more than one version of the same JavaScript libraries, or sometimes even when some libraries clash with other, (seemingly) unrelated ones. What I was proposing was not as a solution to incompatibilities between such multiple dependencies. On the other hand, once we had the common base (that seems to have already attracted some interest and even potential development support here), an extension, optional for people who want/need it, could try to manage the versions and other causes of conflict you talk of, if I understand you correctly. I am a believer in keeping the core as simple and light as possible whilst still open (and designed for) potential enhancement with extended functionality. Regards - Cemal jWeekend OO & Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com 2010/3/26 Uwe Schäfer : > Uwe Schäfer schrieb: > > Hi Cemal, > >>> I was thinking that it could possibly be sensible to have another >>> project where we abstract out the mechanisms wiQuery provides for >>> resources and JavaScript statements. > > to keep that topic alive: do you agree that providing a unified way for > component authors to contribute standard libs to the page, as well as > coordinating these dependencies on the page level is a primary goal of > creating this lib? > > cu uwe > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket JavaScript Library Integration - A Common Base
Uwe! I was thinking in terms of a simple core, of well defined and limited scope. It would provide a clear and well trodden way for people to integrate their favourite JavaScript libraries with Wicket in a consistent and effective, tried and tested way. As you say, there are always going to be potential complications whenever a single web page depends on more than one version of the same JavaScript libraries, or sometimes even when some libraries clash with other, (seemingly) unrelated ones. What I was proposing was not as a solution to incompatibilities between such multiple dependencies. On the other hand, once we had the common base (that seems to have already attracted some interest and even potential development support here), an extension, optional for people who want/need it, could try to manage the versions and other causes of conflict you talk of, if I understand you correctly. I am a believer in keeping the core as simple and light as possible whilst still open (and designed for) potential enhancement with extended functionality. Regards - Cemal jWeekend OO & Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com 2010/3/26 Uwe Schäfer : > Uwe Schäfer schrieb: > > Hi Cemal, > >>> I was thinking that it could possibly be sensible to have another >>> project where we abstract out the mechanisms wiQuery provides for >>> resources and JavaScript statements. > > to keep that topic alive: do you agree that providing a unified way for > component authors to contribute standard libs to the page, as well as > coordinating these dependencies on the page level is a primary goal of > creating this lib? > > cu uwe > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket JavaScript Library Integration - A Common Base
I like the idea as well :) 2010/3/19 Cemal Bayramoglu : > There's been plenty of encouraging feedback about wiQuery [1] and how > cleanly it integrates jQuery and makes it easy to use in a Wicket app. > We also get lots of questions, sometimes unrelated to wiQuery, about > how to integrate other JavaScript libraries. > > I was thinking that it could possibly be sensible to have another > project where we abstract out the mechanisms wiQuery provides for > resources and JavaScript statements. People could then build on this > base to integrate their preferred JavaScript libraries (eg YUI, extJS, > Prototype ...). I would even see wiQuery being potentially refactored > to use such a base framework. > > Any thoughts? > > Regards - Cemal > jWeekend > OO & Java Technologies, Wicket > Consulting, Development, Training > http://jWeekend.com > > [1] http://code.google.com/p/wiquery/ > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket JavaScript Library Integration - A Common Base
Uwe Schäfer schrieb: Hi Cemal, I was thinking that it could possibly be sensible to have another project where we abstract out the mechanisms wiQuery provides for resources and JavaScript statements. to keep that topic alive: do you agree that providing a unified way for component authors to contribute standard libs to the page, as well as coordinating these dependencies on the page level is a primary goal of creating this lib? cu uwe - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket JavaScript Library Integration - A Common Base
Hi, This would be great, but I think we can only provide an implementation to JavaScript frameworks designed in an unobtrusive way. When I tried to bind ExtJs within Wicket, I had some pain to adapt ExtJs components to Wicket. For the refactoring part, I don't see any problem to achieve this. Generated JavaScript is based on statements (we just need to abstract this a little bit) and on listening instantiation of components to render their associated resources. Lionel On Fri, Mar 19, 2010 at 4:45 PM, Cemal Bayramoglu < jweekend_for...@cabouge.com> wrote: > There's been plenty of encouraging feedback about wiQuery [1] and how > cleanly it integrates jQuery and makes it easy to use in a Wicket app. > We also get lots of questions, sometimes unrelated to wiQuery, about > how to integrate other JavaScript libraries. > > I was thinking that it could possibly be sensible to have another > project where we abstract out the mechanisms wiQuery provides for > resources and JavaScript statements. People could then build on this > base to integrate their preferred JavaScript libraries (eg YUI, extJS, > Prototype ...). I would even see wiQuery being potentially refactored > to use such a base framework. > > Any thoughts? > > Regards - Cemal > jWeekend > OO & Java Technologies, Wicket > Consulting, Development, Training > http://jWeekend.com > > [1] http://code.google.com/p/wiquery/ > -- __ Lionel Armanet WickeXt becomes WiQuery ! http://code.google.com/p/wiquery gmail: lionel.armanet*at*gmail.com
Re: Wicket JavaScript Library Integration - A Common Base
I like it! Where do I sign up? :) -- Jeremy Thomerson http://www.wickettraining.com On Fri, Mar 19, 2010 at 10:45 AM, Cemal Bayramoglu < jweekend_for...@cabouge.com> wrote: > There's been plenty of encouraging feedback about wiQuery [1] and how > cleanly it integrates jQuery and makes it easy to use in a Wicket app. > We also get lots of questions, sometimes unrelated to wiQuery, about > how to integrate other JavaScript libraries. > > I was thinking that it could possibly be sensible to have another > project where we abstract out the mechanisms wiQuery provides for > resources and JavaScript statements. People could then build on this > base to integrate their preferred JavaScript libraries (eg YUI, extJS, > Prototype ...). I would even see wiQuery being potentially refactored > to use such a base framework. > > Any thoughts? > > Regards - Cemal > jWeekend > OO & Java Technologies, Wicket > Consulting, Development, Training > http://jWeekend.com > > [1] http://code.google.com/p/wiquery/ > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: Wicket JavaScript Library Integration - A Common Base
Cemal Bayramoglu schrieb: dear Cemal, I was thinking that it could possibly be sensible to have another project where we abstract out the mechanisms wiQuery provides for resources and JavaScript statements. i have no idea of how wiQuery does it, but i strongly agree to the urgent need of a standard base for JS-lib integration. > People could then build on this > base to integrate their preferred JavaScript libraries (eg YUI, extJS, > Prototype ...). I would even see wiQuery being potentially refactored > to use such a base framework. > > Any thoughts? the problem arises quickly when you try to use two components using different (because of being bundled) versions of jquery (or anything else) on the same page. i think the responsibility of that lib would be to act as a mediator to which version of the javascript to use as well as making sure, there is only one reference within a page. there has to be a standard within wicket, that every component-author can agree on. from my pov wicketstuff-core/jslib could have been such a thing (even though it violates open/close principle as sven nicely put), but whatever approach reaches consensus, i´d be more than happy to help. cu uwe -- THOMAS DAILY GmbH Adlerstraße 19 79098 Freiburg Deutschland T + 49 761 3 85 59 0 F + 49 761 3 85 59 550 E schae...@thomas-daily.de www.thomas-daily.de Geschäftsführer/Managing Directors: Wendy Thomas, Susanne Larbig Handelsregister Freiburg i.Br., HRB 3947 Registrieren Sie sich unter http://www.signin.thomas-daily.de für die kostenfreien TD Morning News, eine Auswahl aktueller Themen des Tages morgens um 9:00 in Ihrer Mailbox. Hinweis: Der Redaktionsschluss für unsere TD Morning News ist täglich um 8:30 Uhr. Es werden vorrangig Informationen berücksichtigt, die nach 16:00 Uhr des Vortages eingegangen sind. Die Email-Adresse unserer Redaktion lautet redakt...@thomas-daily.de. To receive the free TD News International – a selection of the day’s top issues delivered to your mail box every day – please register at www.signin.thomas-daily.de Please note: Information received for our TD News International after 4 p.m. will be given priority for publication the following day. The daily editorial deadline is 8:30 a.m. You can reach our editorial staff at redakt...@thomas-daily.de. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Wicket JavaScript Library Integration - A Common Base
There's been plenty of encouraging feedback about wiQuery [1] and how cleanly it integrates jQuery and makes it easy to use in a Wicket app. We also get lots of questions, sometimes unrelated to wiQuery, about how to integrate other JavaScript libraries. I was thinking that it could possibly be sensible to have another project where we abstract out the mechanisms wiQuery provides for resources and JavaScript statements. People could then build on this base to integrate their preferred JavaScript libraries (eg YUI, extJS, Prototype ...). I would even see wiQuery being potentially refactored to use such a base framework. Any thoughts? Regards - Cemal jWeekend OO & Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com [1] http://code.google.com/p/wiquery/ - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
