even the simplest of the ideas you listed below would be super neat!
as far as page navigation goes, i have a few comments...
if it helps any, i believe this is not going to be any /long term/ trouble. right now, i would not base a million dollar large-scale web app on wicket... but i believe we've got the basic building blocks we need to make this sort of thing a reality in 1.1. we chose to ship 1.0 without full enterprise support simply because our time and resources are limited and not because we're ignorant or lazy (uh, i think... ;-)). among the navigation ideas we've got going for 1.1:
- client-side models. we could enable gigantic wicket web sites by serializing model state for a page into the client such that the page can be reconstructed for a future request without any server side state at all. by using this feature with wicket detachable models, one could have nice client side models without serializing megabytes of information into the client! ;-)
- zero state pages via detached listeners. to make zero-state pages that use client-side models, we will provide listeners that are "detached" from the session entirely. the exact implementation of this is still being discussed.
- session searching links. would like to introduce a new kind of bookmarkable page link that will search your session and only instantiate a bookmarkable page if it doesn't already exist. the code for this is very easy to write, but we're feature complete now for 1.0 and i don't want to open a can of worms. we need more time to think about, implement and test navigation features like this. we want to end up with the best feature, not a kitchen sink of features... and i'm still thinking about navigation in general. i think the features we've got are fine. we just need to add the right stuff to our baseline for 1.1.
- navigation stacks. in 1.1, i'd like to add a feature that keeps track of your browser window's page stack (sounds a little tricky, but it's not very hard... and with PageMaps it will work for popups and frames). this feature will let you get the previous page with some method like getPreviousPage(). you would be able to navigate back in, for example, a cancel button handler by just saying "back()" which would setResponsePage(getPreviousPage()). don't worry if this doesn't make total sense...
- a really nice, multi-level navigation component (i'm working on this mentally right now... it will probably have something to do with the experimental PageSet code (which are in 1.0... but don't attempt to understand or use them!))
- some kind of session size profiling feature. i'd like some kind of wicket "dashboard" where you can get a quick handle on how much stuff you have in your session. ideally this dashboard might even make some heuristic recommendations for how to reduce the size of your session. wicket lint? this might make a really nifty feature for an eclipse plugin... also, we've got a component hierarchy viewing panel... maybe we should add some size information to that too... i think we've even got size profiling code in wicket already... hmmm... just to keep people aware.
hope this helps
jon
Kristof Jozsa wrote:
Juergen Donnerstag wrote:
a
Some.. I delivered 3 swt apps to production at my old company, bootstrapped the
Hibernator eclipse plugin (ages ago) and eg. did some initial work for the JDocs
plugin for the Javalobby guys but we lost contact with them months ago too (I
guess they lost interest in that project).
Cool, you are the right one to kick off such a plug-in for Wicket. What do we need to do to convince you?
Geeez, lots I guess.. First of all, I need to get proved that wicket is the One :) I'm on track already, but all I did is to play with my own helloworlds.. so I definetely need time to get familiar with wicket. Knowing some internals (like page-instantiation logic ;)) could help too.. and as I see the current cvs head, it definetely needs some work to get it stabilized (eg. tests fail atm).
Seriously, do you have any plans or at least a bunch of ideas of what such a plugin could do? For a start, matching parsing templates for wicket markups with component names could help I think. Adding wizards and such funky almost-useless stuff could be relatively easy too. For a distant vision, parallel source and WYSIWYG html editing with a Wicket component palette on the side would be pretty impressive.. but right as I said, even to kick off with these, I need to dig into Wicket at least to see how to retrieve component trees built for pages from java code, etcetc.
At last, I have a daily work to do (guess we all have, nah?) and while I *am* looking for a hobby project, I'd rather start hacking away on the ideas which come up (if any :) and see what I can come up with than officially volunteer for anything..
Kristof
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
