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 <lind...@visionet.de> 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 <schae...@thomas-daily.de>: >> 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
