ok, one more time... > -----Oorspronkelijk bericht----- > Van: Michiel Meeuwissen [mailto:[EMAIL PROTECTED] > Verzonden: woensdag 12 mei 2004 13:32 > Aan: [EMAIL PROTECTED] > Onderwerp: Re: CALL EXTENDED: : HACK: HugeNodeListIterator > > > Ernst Bunders <[EMAIL PROTECTED]> wrote: > > That's not what i meant. To understand my remarks you have > to realize that > > though i am a commiter now i stil a 'user' of mmbase for > the gratest part > > (allthough this is steadily changing). Therefore i know > that one of the > > weaknesses of mmbase is that the best way to get to know > the software is to > > study the apidocs and the sourcecode. > > Studying the apidocs of the bridge and bridge.util is the > best way to get > to know them, and i think that is ok if you are wanting to > use them (i.e. > _are_ programmer) >
> > I really beleve that mmbase should > > become more accassible which means that first there must be > a real notion of > > what mmbase is. Constantly adding all kinds of nice bells > and wistles dous > > not make this dream come any closer. > > I do agree. Though I remain at my standpoint that my proposal > was not a > 'bell' or a 'wistle'; it is a very dry utility class which > adds completely > nothing besides an implemetnation for an existing interface > and is targeted > completely to peoply using the bridge to implement stuff in > java for mmbase. > > > Personnaly i am learning about all kinds of functionality > currently in > > mmbase by accidently stumbling upon them. I think this is bad. > > I do not necessary think that this is bad. Imagine that you > need what I > proposed? I would not know where to look for it in the > documetation besides > in the api-doc. Just what I do if I need a certain collection > implemtnation. > Then I browse to apidocs of java.util.Collection and see what > the available > implementations are. In that way I acquired a pretty good > idea of what is > possible with java.util and what not, and I don't see how > otherwise I could > have gotten it. > > > > But i think this is slightly political > > Yes, I think it is. I don't mind that you use an anyway lost > vote for it, > but I think it must be clear what you are actually saying. > You are right. I hope i expressed myselfe clearly now, adding that indead my objections are more of a general natuere than specifically concerning your proposal. Yet i quess developing this kind of stuff outside the mmbase packages has some merites. for one, you yoursef admit that you wouldn't know where else to look for it besides the apidocs. It has no effect on mmbase and mmbase will not use it. So it dousn't have to be in the mmbase packages. It would rather belong to an application on mmbase, like (heY!) the taglib? by for instance adding it to bridge.jsp.taglib.util and allowing the list tags to make use of it it suddenly gets a focus. Everybody can use it (even without being aware of its existence). allso the responsibility would be primarily with those who maintain the taglib app. then if it turns out after a while everybody likes to use it, and they tire of having to install the taglib in order to have access to it you could move it, and would have plenty support. Roundabout? yes. The question is what you want: lots of featuers (with more added all the time) or small, clear and logical api that is easy to understand and use (like the mmci (still) is). Ernst > > > > > I for me, would like a nice library of 'bridge utils' where I > > > could find > > > these kind of things. > > > > > > Michiel > > > > > > > If there would be a nl.meeuwissen.mmbase.bridge.util > package available i > > would probably be an avid user of it :) > > Hff. That would be folly, I'd much rather see a org.mmbase.bridge.util > collection of classes. > > > Michiel > > > > -- > Michiel Meeuwissen > Mediacentrum 140 H'sum > +31 (0)35 6772979 > nl_NL eo_XX en_US > mihxil' > [] () >
