First of all, thank you Paolo for your thoughts. I will quickly comment some aspects you mention.
> For many of the point you listed, you wrote: > "It can be extracted like a plugin?: Is possible. Any case > there would be lot of dependency with it." > > What dependencies are you meaning here??? On other plugins or on > third party libraries??? We mean that they work so close to the core that they will depend on other basic plugins. SDL Symbolism will have render dependencies, or projections too. So if we make plugins of them they will be interrelated. > I didn't test Kosmo yet, but now I'll go download and give it a try!!! Great. We have just upload v:1 rc1. We wanted to do it next week because we still not finish writing the "What´s new" section and ordered the sources. Anycase we think much better if you try v.1 because there are lot of changes. Next week we will announce "officially" it and we will upload source code and first documents. Hope you, and everybody, like it. Regards, Manuel. Quoting "P.Rizzi Ag.Mobilità Ambiente" <[EMAIL PROTECTED]>: > This post is _very_ interesting. > > It clarifies the distinction between plugins and extensions. > In my mind they were the same, and I was always wondering > why there existed the two of them. > > Now you say plugins are present in the basic package while > extensions are third-party... > In my mind I imagined something more like Linux, with OJ Core > beeing like the Kernel and OJ versions like distributions, > made assembling the Core with any sensible combination of plugins. > So I can't see any distinction between a basic package and any other > distribution, but now I see other people see this distinction. > > For many of the point you listed, you wrote: > "It can be extracted like a plugin?: Is possible. Any case > there would be lot of dependency with it." > > What dependencies are you meaning here??? On other plugins or on > third party libraries??? > > For other listed points , you wrote: > "It can be extracted like a plugin?: Difficult" > > Here I have to trust you, because I obviously don't know your code, > but I suspect that it may indeed be difficult because the Core make it so. > Many functionalities may be difficult to implement as plugins > because the Core > has no support for them to be pluggable. But if it had, it should be > easy to do. > > So the question is: "...is it worth the effort to make to Core support > more pluggability???", and: "...is anyone available do that???". > If the answer to any of these question is "no", then functionalities > will go inside the Core. > > I'm _very_ happy reading that you are trying to develop not only > a desktop solution but a system also usable as a server, mobile, etc. > This is _great_!!! I always thought that it's the only reasonable way > it should be. And also in this respect I see a smaller Core > as an advantage on the way to creating such a modular platform. > > Reading your post it seems you are developing an impressive amount of > useful functionalities, that should have be present in OJ. > Also you are 9 people working full-time, and this is, > I believe, the strongest task-force in the OJ arena. > > Putting all together it's quite tempting to say: "...why don't we simply > adopt the Core from Kosmo as the OJ Core altogether...?!?". > > In the end I want to thank you very much for all your work!!! > I didn't test Kosmo yet, but now I'll go download and give it a try!!! > > > Bye > Paolo Rizzi ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
