Great..lets do it!!! How we start!? On 7/5/05, Todd O'Bryan <[EMAIL PROTECTED]> wrote: > On Jul 5, 2005, at 12:14 PM, Ron Piterman wrote: > > > ציטוט Pablo Ruggia: > > > >> This is not a Tapestry problem. It's the community (me included) > >> the one that should contribute with those components. I've created > >> several components and never upload them anywhere. I think you > >> guys are in the same. > >> I think what we need is a more "official" site where to upload > >> components, and not personal attemps like tassel or tdelli. > >> Perhaps a Tapestry subproject or something like that. > >> > > > > Since sourceforge is there, this should not be the problem. I think > > the problem is *doing* it. Its fine when Howard organizes, but this > > one - I think we have to do "on our self"... > > I have to agree with Pablo. What we need is a site that contains > Components that people express a need for, along with, over time, a > reasonably worked out API. (For example, a Menu component takes a > List of MenuBar components, each of which contains a link. The HTML > class for the menu as a whole is "menu", each menuBar is "menuBar" > and each item is "menuBarItem". Included are CSS examples which show > the menu vertically, horizontally, under JavaScript control, and as > plain old HTML links.) In the beginning, of course, we would just > have names and short descriptions. > > When I need a component for a Tapestry project I can go to this site. > If it isn't already specified, I fire off an email saying "I need > this component. Should I add it to the list or is it too special > purpose?" If there is a specification but no implementation, I can > start implementing using the API that people have come up with as a > guide. When I finish, I upload the .jwc, the Java class(es), and > provide links to any required libraries. > > If someone wants to improve on a component, they can, and if people > think additional functionality would be a good idea, they can lobby > for that. If people agree, they add it back to the repository. If > not, they just subclass/modify the component that's there. > > TapestryPalette seems to be able to access component libraries and > install needed components into Eclipse projects, so just making sure > that the component project is compatible with that functionality > would make life easy for lots of people. > > Todd > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
-- "The passion for destruction is also a creative passion!"
