For me it is still the little things that are missing which I'd like to see integrated into Wicket, like "pretty URL" support. To my recollection, the current state of events is that we expect developers to use a servlet filter to hack something together themselves. It would be nice if this feature was better integrated directly into Wicket in the spirit of what Eelco mentioned a long time back.

Gili

Johan Compagner wrote:
For me (after i finished the most part of the OGNL replacement) it is Form aware links/submits

For example the Selection Listener on the choice objects that are doing that now through normal get request should be done by form submits. But then these form submits shouldn't do anything for the models or call form.onSubmit or button.onSubmit. The form should just be there to store the values for that request.

And i thought that even better ajax intergration in wicket was the core feature of 1.2?

johan


On 11/2/05, *Martijn Dashorst* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    And how could I forget 'SECURITY' as a main focus area.

    Martijn



    On 11/1/05, *Martijn Dashorst* <[EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>> wrote:

        All,

        As we just have release 1.1 I'd like to start a feature
        discussion on Wicket 1.2, and on what timeframe we wish to ship it.

        What are our major concerns for Wicket 1.2?

        I just list a few things I think could be on the feature list:

         - reference documentation
         - database integration
         - session size/state management
         - single component markup generation
         - portal support
         - testing

        I also think we should aim for some release date. I would like
        us to focus on smaller releases, and maybe strive for 4 releases
        per year. Currently we are at 2.1 releases per year. My proposal
        is to do time-boxed, feature driven development, aiming for high
        quality and less focus on more features per release. Having a
        schedule of 4 releases, means releasing each 3 months. Currently
        a typical release candidate is out there for about 3 weeks, and
        we usually have 2 release candidates. This means the last 6
        weeks are RC time. This is half of a 3 month release, and seems
        too much IMO.

        Your thoughts please?

        Martijn

-- Living a wicket life...

        Martijn Dashorst - http://www.jroller.com/page/dashorst
        <http://www.jroller.com/page/dashorst>

Wicket 1.1 is out: http://wicket.sourceforge.net/wicket-1.1



-- Living a wicket life...

    Martijn Dashorst - http://www.jroller.com/page/dashorst

Wicket 1.1 is out: http://wicket.sourceforge.net/wicket-1.1


--
http://www.desktopbeautifier.com/


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to