Hai, I do object !. Not to putting it in a jar but how we name these things, we can start calling everything a application but imho this is getting silly fast. We need a better naming system. For example applications for end user stuff (complete apps like a news website or a portal builder etc etc and for example a mmbase extention for extending the core api's of mmbase. In this case i would say taglibs are a extention and not a application.
If we don't think about naming and start moving all from the module name to the application name we will end up with nothing in the end because everything is called a application from the smallest example to important extentions like the taglibs, editwizards or Remote MMCI (don't even tell me Remote MMCI is a application). Sorry for forcing you all to think about this in this hot weather but imho its needed. Greetings, Daniel. > -----Oorspronkelijk bericht----- > Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Namens Rob Vermeulen > Verzonden: woensdag 13 augustus 2003 10:03 > Aan: [EMAIL PROTECTED] > Onderwerp: Re: mmbase-taglib.jar > > > >Perhaps it would be a nice idea to ship 1.7 with the taglib in a seperate > >jar. This will make it easier to upgrade only the taglib, or to remove it > >completely if you don't like it. > > > I agree, the taglibs are a nice example of an MMBase application and > should be placed in the application module. > So no objections from my side. > > greetings Rob > >
