Re: wicket-dojo wrappers (correction)
Hi David, Would it be possible to put up the jar that contains or the java file: org.smallmind.nutsnbolts.util.DotNotationComparator? I get a compile error with this and I don't understand what it does in terms of dot notation. Thanks, James. On 10/11/2011 3:15 AM, David Berkman wrote: Sorry for the repost, but this list doesn't take attachments I guess, so I've upload the code at https://github.com/zenbones/WicketDojo I've had a number of requests, so I'll upload this bit of code here so people can have a look. I know there's room for improvement in the code that exists, and a ton that needs to be done. There's a wicket-dojo project on GitHub https://github.com/vijaykiran/wicketstuff-dojo that's much cleaner, with many more advanced integrations. However, that project lacked implemented wrappers for Dojo Dijits, which is what I wanted most. The code there also seemed a bit daunting, so I began a project to make wrappers I could understand, and extend, and learn both Wicket and Dojo in the process. This is the results so far. The few advantages it has over the GitHub code I've linked to are... 1) A bunch of useful Dijits wrapped in a way I hope is fairly clear and extensible (it's getting better). 2) All the wrappers use fluent APIs 3) You can generally set a field, or your own model, interchangeably. For instance, if you want to set a Title, you can usually setTitle(String title) or setTitleModel(IModel titleModel). Being able to control the model is extremely useful. 4) You can generally set attributes in your HTML and these values will initialize the fields/models in the wrappers on a non-Ajax render. Values can then be dynamically altered from there via Ajax (as with user interaction). 5) Using setIntermediateChanges(true) will generally update the wrappers' fields/models upon user interactions with the Dijit, via Ajax (you can also add DojoAjaxUpdatingBehaviors to get your own callbacks). This extends to things like stack container updating its models for selected child index and id. There's still much to do. It's not the cleanest code yet. It doesn't handle animations or fx or anything but presenting widgets. It's part of a larger project so I haven't presented a real build, just the code. If people are interested, I can cleave this off and provide a true maven build. David - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket-dojo wrappers (correction)
Thanks David, I've just pulled down the code now to have a look. On 10/11/2011 3:15 AM, David Berkman wrote: Sorry for the repost, but this list doesn't take attachments I guess, so I've upload the code at https://github.com/zenbones/WicketDojo I've had a number of requests, so I'll upload this bit of code here so people can have a look. I know there's room for improvement in the code that exists, and a ton that needs to be done. There's a wicket-dojo project on GitHub https://github.com/vijaykiran/wicketstuff-dojo that's much cleaner, with many more advanced integrations. However, that project lacked implemented wrappers for Dojo Dijits, which is what I wanted most. The code there also seemed a bit daunting, so I began a project to make wrappers I could understand, and extend, and learn both Wicket and Dojo in the process. This is the results so far. The few advantages it has over the GitHub code I've linked to are... 1) A bunch of useful Dijits wrapped in a way I hope is fairly clear and extensible (it's getting better). 2) All the wrappers use fluent APIs 3) You can generally set a field, or your own model, interchangeably. For instance, if you want to set a Title, you can usually setTitle(String title) or setTitleModel(IModel titleModel). Being able to control the model is extremely useful. 4) You can generally set attributes in your HTML and these values will initialize the fields/models in the wrappers on a non-Ajax render. Values can then be dynamically altered from there via Ajax (as with user interaction). 5) Using setIntermediateChanges(true) will generally update the wrappers' fields/models upon user interactions with the Dijit, via Ajax (you can also add DojoAjaxUpdatingBehaviors to get your own callbacks). This extends to things like stack container updating its models for selected child index and id. There's still much to do. It's not the cleanest code yet. It doesn't handle animations or fx or anything but presenting widgets. It's part of a larger project so I haven't presented a real build, just the code. If people are interested, I can cleave this off and provide a true maven build. David - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Advice wanted about polished component set with Wicket
Hi Martin, Have you got a typical example of a destroy + create new in the wicket-ajax.onBeforeRender? This may make life easier with JQuery. Thanks, James. On 8/11/2011 9:26 PM, Martin Makundi wrote: Hi! When you render jquery components via ajax you often need to recreate them (destroy old + create new) with wicket-ajax.onBeforeRender It might seem bit tricky at start but simply make it part of onBeforeRender or similar in either a behavior or component itself. ** Martin 2011/11/8 James Stewart: Hi all, We have been using Wicket for some time now with our home grown html& some wicket components. However, there are some complaints that our components and pages look a bit bland. This has prompted us to look around at various alternatives. We tried using plain jQuery with wicket and found some odd behaviour here and there on Internet Explorer when using Ajax, which we never got to the bottom of. If I remember correctly it was the calendar appearing on first render which then disappeared and it would never reappear again. This has lead us to reassess our component situation. Having looked at the wiQuery demo site it doesn't fill me with confidence. Perhaps it is just the demo site that does not work well and is not an indication of the underlying library. The next library we are considering is Visural Wicket. It looks promising but it only seem to have one developer working on it. Otherwise we would probably look to something like YUI of which I have some experience but not with Wicket. It would take some investigating though to establish if it would have similar problems that we encountered with JQuery. Any advice or real world experience will be appreciated. Thanks, James. - 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: Advice wanted about polished component set with Wicket
That sounds encouraging. I am very interested in how you went about integrating Dojo into Wicket. On 9/11/2011 2:51 PM, Martin Grigorov wrote: Hi David, I'm interested in your work. Another guy also did something at https://github.com/vijaykiran/wicketstuff-dojo On Tue, Nov 8, 2011 at 8:36 PM, David Berkman wrote: I've had excellent success wrapping most of Dojo with Wicket, and it would not be hard to complete the rest. There's a wicket-dojo project out there, but it didn't seem to be active, so I just started in on my own. Dojo is a comprehensive, well laid out project (always had a good concept of namespace and packaging, unlike most other javascript frameworks), with decent documentation. Browsers have a tendency to fire events in different orders, and when you start adding your own 'onxxx' functions, you can get unexpected behavior. My first guess would be that this is the cause of your problems in IE, as it seems to be particularly random in this regard. Dojo has its own, extensive, event framework, that corrects for these issues. If you want to look at my code, let me know and I'll send it your way. David -----Original Message- From: James Stewart [mailto:james.stewart...@gmail.com] Sent: Tuesday, November 08, 2011 4:58 AM To: users@wicket.apache.org Subject: Advice wanted about polished component set with Wicket Hi all, We have been using Wicket for some time now with our home grown html& some wicket components. However, there are some complaints that our components and pages look a bit bland. This has prompted us to look around at various alternatives. We tried using plain jQuery with wicket and found some odd behaviour here and there on Internet Explorer when using Ajax, which we never got to the bottom of. If I remember correctly it was the calendar appearing on first render which then disappeared and it would never reappear again. This has lead us to reassess our component situation. Having looked at the wiQuery demo site it doesn't fill me with confidence. Perhaps it is just the demo site that does not work well and is not an indication of the underlying library. The next library we are considering is Visural Wicket. It looks promising but it only seem to have one developer working on it. Otherwise we would probably look to something like YUI of which I have some experience but not with Wicket. It would take some investigating though to establish if it would have similar problems that we encountered with JQuery. Any advice or real world experience will be appreciated. Thanks, James. - 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
Advice wanted about polished component set with Wicket
Hi all, We have been using Wicket for some time now with our home grown html & some wicket components. However, there are some complaints that our components and pages look a bit bland. This has prompted us to look around at various alternatives. We tried using plain jQuery with wicket and found some odd behaviour here and there on Internet Explorer when using Ajax, which we never got to the bottom of. If I remember correctly it was the calendar appearing on first render which then disappeared and it would never reappear again. This has lead us to reassess our component situation. Having looked at the wiQuery demo site it doesn't fill me with confidence. Perhaps it is just the demo site that does not work well and is not an indication of the underlying library. The next library we are considering is Visural Wicket. It looks promising but it only seem to have one developer working on it. Otherwise we would probably look to something like YUI of which I have some experience but not with Wicket. It would take some investigating though to establish if it would have similar problems that we encountered with JQuery. Any advice or real world experience will be appreciated. Thanks, James. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
problem with locating lightbox resources - images etc.
I created a subversion branch on my local machine of the lightbox wicket stuff and built the wicket-lightbox.jar using mvn install. I then put the jar in my war/WEB-INF/lib folder. It seems to work except for when I click on the thumbnail. It loads the image correctly and does the animation of loading the image and displays it. However, the decorative images are missing and I get the following error in the logs: 02/09/2009 12:07:57 PM com.google.appengine.tools.development.LocalResourceFileServlet doGet WARNING: No file found for: /resources/org.wicketstuff.lightbox.LightboxBehavior/resources/images/loading.gif ...and some other images like closelabel etc. I can see this image in the resouces/images/ folder within the jar. The resources folder is in org.wicketstuff.lightbox package within the jar. I'm a bit lost as to how it's supposed to work and find these images. Is there something I'm missing in the way that I built it or am using it. The docs within the lightbox are a bit light (excuse the pun). Thanks. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
