that's fine, except that "contrib" and "library" have exactly the opposite meanings to me.
"library" is something stable and supported and reliable. "contrib" is normally the dumping
grounds.
Juergen Donnerstag wrote:
Why not use something like http://eclipse-plugins.2y.net/eclipse/index.jsp to maintain a library of wicket contribution? We could leave wicket-contrib for project related, but non-core, components. And everyone who would like to contribute his component may add it to to the "library".
Juergen
On Fri, 11 Feb 2005 07:51:27 -0800, Jonathan Locke <[EMAIL PROTECTED]> wrote:
okay, i can agree with you guys about signin panel leaving the core. but i disagree completely about password text field, which is a core component as well as the list view extensions.
where these things should go is another matter. the problem i have with contrib is that in every project i've ever seen, it's /not/ filled with high quality components. so, i tend to avoid looking at contrib right away because that's usually very uneven or in the worst case, just a dumping ground for whatever. also, i think beginners and those with less time or talent should have a place where they can contribute stuff that's fairly half-baked and which someone else might touch up. so i tend to think contrib is the right place for this kind of stuff.
anyway, what i'd like to see is some "third place" then that's not a dumping ground and is not the core. something like "wicket-components" maybe.
so i'm suggesting:
wicket - core wicket-examples - polished examples wicket-components - polished components wicket-contrib - not so polished stuff wicket-contrib/examples - not so polished examples wicket-contrib/components - not so polished components
that would give us enough places to put everything and not have to reject anyone's contribution or pollute the polished stuff
Eelco Hillenius wrote:
I agree with Martijn. -1 for moving some of the examples to contrib. Also, - but I've argues this before - I would be +1 for moving the sign in panel to contrib, just like password text field and some of the ListView extensions. ListView/ PageableListView are absolutely core components however. The tree could be argued on, though we had that argument, and decided it should stay in core.
Contrib should be filled with high quality reusable components, not will all kinds of experiments.
Now about the examples... I would prefer to keep most of the examples, but just have the best ones visible from the index page. A lot of project work like this, and as a framework user, I like it when there are a lot of code examples, even when some of them are not that good/ not finished.
The few examples that are in the project that hardly do anything, or that most of us agree on are not good practice, should be removed (and not put back in any project). If we have different opinions on how to solve certain problems, there will allways be that Wiki (or your own blogs?) for that.
Eelco
Martijn Dashorst wrote:
-1
Contrib is a component contributions project. Examples just feature examples. I agree that those should be pristine examples with the best design.
Rule of thumb: anything you can create by composing or extending core components should be in the contrib project. Anything that is a showcase of how something might be done should be in the examples project.
I think I would move the SignInPanel to the contrib package, because as you mention, it will become a beast of a component. I also noticed that some on this list would never use the component, which is also a signal to move it into contrib. In my opinion, the core should consist of only the basic components which don't aggregate multiple components:
core: - form stuff (inputs, form, buttons, but no composite components) - markup stuff (panel, border, page, links, but no panels containing components)
giving benefit of the doubt: - listview (and its pageable variants) - treeview - menu (is it even there?) - basic validation (Number taking a numberformat? Date, ...)
contrib: - signin panel - datetime field picker - etc.
Jonathan Locke wrote:
i'd like to move SignInPanel and friends into a subfolder of panel called signin and FeedbackPanel into a subfolder called feedback. this will give us room to grow and stay orderly if we add more stock panels to the core. already sign-in panel has a bunch of localization files and probably ought to have a ton.
also, want to move a few of the examples out of wicket.examples to contrib since we want wicket.examples to really show polished examples that demonstrate best-practices. some examples have no description on the index page. we need to at least explain what it demonstrates...
-------------------------------------------------------
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
------------------------------------------------------- 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
------------------------------------------------------- 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
