I'll try to find some time to write an overview of the experimental branch. But the code is an order of magnitude simpler than current Wicket codes and about the same amount less tangled. It also does lot less though :) (some of that is intentional).
I have basically rewritten the most messy parts of Wicket (request cycle, url processing, page management). Some of it is done, some still needs work. It is however not a drop in replacement for current wicket internals. It will require substantial effort to integrate. So before I even consider doing that I'd really like for some people to take a look at it. Also I'm not sure if the architecture is flexible enough to support portlets without having to do various hacks like in current wicket. So it would be really nice if someone who has experience with building support for portlets took a look and told me what needs to be improved. -Matej On Thu, Aug 20, 2009 at 10:33 PM, Martijn Dashorst<martijn.dasho...@gmail.com> wrote: > It would be nice to get some guidance towards the goals, and > architecture of your new design before we commit to it. Just looking > at the code doesn't reveal intention or the bigger picture. > > Martijn > > On Thu, Aug 20, 2009 at 8:09 PM, Matej Knopp<matej.kn...@gmail.com> wrote: >> Hi, >> >> actually the changes in 1.5 might be quite drastic as far as wicket >> internals are concerned. I've already rewritten the request cycle, url >> processing and page management. I'm not sure how much of it will >> actually get to trunk though. You can take a look at the code here if >> you are interested: >> >> http://svn.apache.org/repos/asf/wicket/sandbox/knopp/experimental/wicket-ng/ >> >> Note that this is pretty much a prototype. While the request cycle, >> url processing and page management work, the rest of wicket is more or >> less mocked. >> >> Also right now it only covers regular request processing. I don't know >> enough about portlets to build in portlet support. I'm not even sure >> the architecture is flexible enough to allow seamless portlet >> integration. That said, it would be much probably lot easier and >> cleaner to refactor this code than to add add portlets to existing >> wicket trunk - which always feel like a hack to me. >> >> -Matej >> >> >> >> On Thu, Aug 20, 2009 at 8:03 PM, Antony Stubbs<antony.stu...@gmail.com> >> wrote: >>> There us already a working patch since early this year. I just need to >>> update it to trunk which shouldn't be a big deal. >>> >>> Regards, >>> Antony Stubbs >>> >>> website: sharca.com >>> >>> On 20/08/2009, at 7:58 PM, Igor Vaynberg <igor.vaynb...@gmail.com> wrote: >>> >>>> come up with a proposal we can discuss. when we hash out the idea then >>>> come up with a patch. >>>> >>>> proposal==patch is fine as far as you dont mind refactoring as we iterate. >>>> >>>> -igor >>>> >>>> On Thu, Aug 20, 2009 at 9:51 AM, Antony Stubbs<antony.stu...@gmail.com> >>>> wrote: >>>>> >>>>> Apologies if this is known, but is there anywhere noted the plan for 1.5? >>>>> >>>>> Also, I'd like to look back at the portal events work I did, and try and >>>>> get >>>>> that into 1.5. What would be the process for doing so? In terms of making >>>>> a >>>>> branch, or just re-patching, or do I just need to get the final OK from >>>>> Ate? >>>>> >>>>> Cheers, >>>>> Antony Stubbs, >>>>> >>>>> sharca.com >>>>> >>>>> On 20/08/2009, at 5:10 PM, Igor Vaynberg wrote: >>>>> >>>>>> Wicket 1.4.x has been branched and now lives in >>>>>> https://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.x >>>>>> Trunk is now what will become 1.5.0. >>>>>> >>>>>> Trunk may be broken in the early days of development and contain a lot >>>>>> of API breaks, so if you are following bleeding edge you may want to >>>>>> do so on the 1.4.x branch for a while. >>>>>> >>>>>> -igor >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>>>>> For additional commands, e-mail: users-h...@wicket.apache.org >>>>>> >>>>> >>>>> >>> >> > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.4 increases type safety for web applications > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0 >
