Re: [K-3D dev] K-3D future

[Peter Balon]

bondpaper wrote:
> Romain Behar wrote:

> One of things I *still* find impressive is the way that NaN built and 
> maintained the Blender community. If an objective of the k3d project is 
> to build a community of interested users, it might be of value to look 
> at NaN's m.o. as a model. Wings3D is also experiencing some success in 
> this area. The one thing that I think sets these community-oriented 
> efforts apart is that they have community facilities: a dedicated web 
> site with galleries, discussion areas, news, etc. The discussion areas, 
> galleries, a mechanism for highlighting exceptional work from users, and 
> regular participation on the part of the developer(s) are probably the 
> most important of these.

A galery would most certainly attract some audience. I had a look at some
PHP tools which provide such communication facilities, is it posible to
set up such thing on sourceforge?

> >  Another matter is splitting completely the 3D engine
> > from the GUI (P. Christeas), to have a commandline
> > application creating or modifying 3D scenes using
> > scripts. This might be useful to make automatically
> > generated animations, but I wonder how many people
> > would need such product or whether this already
> > exists. Some changes went toward separating tool
> > algorithms from the tools themselves, since the same
> > modifiers works for the tool and its animated
> > counterpart. A stand-alone engine might be a good
> > thing.
>
>
> It is my feeling that the more you separate the engine is from the 
> actual interface, the more options you have in terms of being able to 
> interact with it.

I can only agree with that. The more code you can put to a separate, gui
independend, business layer the more flexible you can build your gui on top of 
that.
With that in mind you could code easily more than one client in your favourite
language/toolkit like Qt or gnome, or have no gui at all, e.g. only a perl 
package
to manipulate the k3d objects.
Moreover cutting the code in even smaller functional chunks would improve
maintainability. It would be easier to track down bugs and eliminate them.
The code of this modules could be improved over time without affecting the rest
of the entire application.

Greetings,

Peter

> Regards,
> Tom
>
> >  Cheers,
> >
> >   Romain
> >
> >
> > __________________________________________________
> > Do you Yahoo!?
> > New DSL Internet Access from SBC & Yahoo!
> > http://sbc.yahoo.com
> >
> >
> > _______________________________________________
> > K3D-dev mailing list
> > address@hidden
> > http://mail.freesoftware.fsf.org/mailman/listinfo/k3d-dev
>
> _______________________________________________
> K3D-dev mailing list
> address@hidden
> http://mail.freesoftware.fsf.org/mailman/listinfo/k3d-dev