I like the idea! But that could be my bad English ;)
I think it is wise to use extensions as our project name, though wickets could be our external name of others like that as well.
Eelco
[EMAIL PROTECTED] wrote:
Hello Guys,
What about if we called the polished components simply wickets. They have been designed with wicket library, and so they are simply wickets.
Les
--------------------------
I agree that wicket-components is too restrictive a name. I certainly agree with having a new module holding polished additional functionality. Some other suggestions for names:
wicket-extras wicket-addons wicket-extensions wicket-additions
I personally like wicket-extensions - classes and components that extend the wicket core. That way we are keeping it very open as to what this module can contain but we are making it very clear that these are things closely related to wicket.
regards, Chris ---------------------
-------------------------------------------------------
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-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
------------------------------------------------------- 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-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
