Menu
▾
▴
Re: [Tm4j-developers] TMNav and TM4Web
|
From: Martin S. <hu...@we...> - 2003-02-26 08:47:08
|
Hi, Kal Ahmed wrote: > Hi Cristoph, > > I think I can see where you are coming from. However, I think that the > current division between tm4web and tmnav is about right (I'll come on > to the possible changes later). Currently tmnav and tm4j follow > different release schedules. This works because tmnav can make use of a > particular TM4J release and it allows the two projects to continue at > their own pace without one project having to wait for the other. While > it is (I think) possible to branch part of a CVS module, I think it is > generally much nicer to have separate modules for the separate > deliverables so that each can be labelled when it reaches a release > milestone. I think that it will be the case that tm4web will initially > develop slower than tmnav is currently developing (that is inevitable > because tm4web is in earlier stages at the moment) and I don't want > tm4web development to become a drag factor on tmnav. > > To me, there is a nice logical distinction between the client-oriented > presentational features of panckoucke and the tmnav application and the > web publishing/web application features of tm4web. I can see them as > being separate SourceForge downloads - tmnav for client-side developers, > tm4web for server-side developers. I agree with you Kal. At the current state of the two applications I think it makes no sense to put them together in one project. > > The one overlap is with kamal. Perhaps kamal should move into tm4web (or > we should think about creating a tm4ws module perhaps) - but I guess > that this depends upon how tightly tied kamal is to the panckoucke > libraries and whether or not we could achieve a degree of independence > like exists between tmnav and tm4j. Kamal is/will be a webservice-representation of a subset of the panckoucke-Interface. So it depends on panckoucke at the moment. I'm working on the internal interfaces at the time and it will be more independent of the navigation backend. But I'm not sure if it makes really sense to decouple the two completely. It think the only overlap of tm4web and kamal is that both are server side applications and both use a servlet engine to provide it's services. But the goals of both are different: tm4web provides a web-based interface for 'users', kamal provides a webservice based programming interface for 'user-applications'. So what is the benefit, if we put tm4web and kamal together in one project? > Those are just my thoughts - I would be interested to hear what the > other tmnav developers think too. > > Cheers, > > Kal Greetings Martin > > On Tue, 2003-02-25 at 13:41, Christoph Fröhlich wrote: > >>Hi kal >> >>some thoughts about the tm4web - project. >> >> >>I like the idea. And I think it would be good for the tmnav-project >>to be part of the tm4web-thing. (I have not spoken with the other >>developers about this, so we should hear what they think.) But to me, >>it would be fine to be part of a subproject which works on all >>aspects of the accessibilty of topicmaps. >> >>Naturally, working on all aspects of accesibilty means more, than >>working on web-related technologies. >>Therefor I would prefer a name, which is "more open" to other >>directions, perhaps tmAccess or tmGate or something like this. >> >> >> >>Some words on TMNav >> >>TMNav consists currently of three parts. >>One is the Panckoucke-Library, which offers services for frontend-applications. >>You may use panckoucke to obtain a view on a fragment of a topicmap. >>This view reduces the complexitivity of topicmaps down to a model, >>which is easy to understand and suitable for ui-purposes . >>Furthermore the version which is currently under developement wil >>contain code to load topicmaps assynchroniously and maintan a >>repository of all loaded maps. >>We plan to add authentication and restricted access features and yes >>- i hope we will get there to support editing. >>Panckoucke is currently the heart of the tmnav-project and I think >>other projects / applications / services could benefit from it as >>well. >> >> >>Second, TMnav contains Kamal, a webservice which settles on >>panckoucke and delivers the panckoucke generated model to the world. >> >>Third TMNav contains an Application, which is unfortunately usually >>referred to as TMNav as well. Using one single name for the package >>and for one part of the package, is defintely confusing. It does not >>make it easy to understand separate things separetly. >> >>The App is swing based . In its current state it is nothing more tham >>a playground. To me, developing the Swing-App will lead into a >>dead-end-street, since we have to reinvent several wheels, in order >>to provide something which could be really suitable to work with. I >>hope tmnav will be ported to more powerful editing enviroments, as >>eclipse or jedit, where it could live on some time. >> >>This is what we are currently developing. I think at least panckoucke >>and kamal could be valuable input to the so-called tm4web-project and >>I would love to bring theese efforts together with all what is >>elsewhere under developement. And I feel, the target should be >>broader than web.... >> >> >>Regards >>c >> >> >> >> >> >> >> >> >> >> >> >> >> >>------------------------------------------------------- >>This sf.net email is sponsored by:ThinkGeek >>Welcome to geek heaven. >>http://thinkgeek.com/sf >>_______________________________________________ >>Tm4j-developers mailing list >>Tm4...@li... >>https://lists.sourceforge.net/lists/listinfo/tm4j-developers >> > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Tm4j-developers mailing list > Tm4...@li... > https://lists.sourceforge.net/lists/listinfo/tm4j-developers |
