For me it would be either core or extensions, or just keep it an
example; I don't want to support another stuff project myself.
Eelco
Martijn Dashorst wrote:
Eelco Hillenius wrote:
Btw, where should we put the DatePicker when it is done? Core or
extensions? Personally I feel that such a component will be very
commonly used, so I would argue for putting it in core.
The same question came to my mind... It would be /really/ cool to have
more 'complex' components out of the box. It would enlarge the
conceptual surface area though (quoted from the vision document).
I am not sure which option I'm favouring: adding such javascript
components to:
- core,
- extensions or
- stuff
Martijn
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit
http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
