I Think there is some confusion between WHAT we want this new SDL to be and
HOW it will take form and be implemented. It is always prematurate to
answer the second question before aswering (more or less) the first. We
should focus on defining WHAT (and WHY) we want this or that feature.

Here are some questions/suggestions that could concern the 'WHAT' and that
pop up in my mind while typing, maybe some are nonsense:

Meta-features
    Would it be rather script-oriented, programming laguage-oriented, or a
whole development environement?
    Modularity/Reusability/Evolutivity
    Interoperability with other systems/formats
    Distributed render
    Collaborative scene development and repository (POV-forge?)
    Documentation
    Debugger
    Preview of object/textures being defined
    Related Tools?
    .../...

Features
    Keep current POV (+MegaPOV?) features
    Improve some (JIT-compiler for isosurface functions?)
    Add some object types (primitive/compound)?
        MegaPOV's (cloth, mechsim, glow, hdr ...)
        Sub-surface scattering
        Landscape-oriented: terrain, skyscape, clouds, sun, rain, snow, ...
        Vegetation-oriented (tree, ivy, flower, grass, ...)
        Characters/Animals/Organic (articulated=> IK?), skin, cloth, hair
        Fires/smokes/explosions
        Particle system (running liquids, ...)
        .../...
    Built-in object placement
        drop_on (Object),
        stick_on (Object),
        throw (Direction),
        .../...
    Animation features
        Paths
        Morphing (meshes)
        Timelines attached to objects
        Collision detection
        Object breaking/explosion
    .../...

Syntax
    Keep syntax for objects/pigments/... nor far from what it is now
    Rather object-oriented or rather functionnal-oriented?
    Get inspired by existing languages? (for me: yes)
    Compact yet readable
    Specialized 'editor' or only syntax-colored text editor?
    .../...


Perhaps we could imagine a way to collect and formalize ideas and
requirements from the community, and then organize/hierarchize, and then
submit/comment.

Some of us can volunteer to help on this task (like some did for TC-RTC).

A new-SDL comitee can be chosen.

Every one can contribute (stupids/newbies/advanced/gurus).

POV-team as main advisor and decision-maker.

I repeat here at the end of this post: WHAT do we want? The 'HOW' should be
answered later, taking into account technical aspects and feasibility,
development cost, time cost, money cost (we will probably have to provide
the
development team with new tools, docs, aspirin, coffee, therapists or
whatsoever :O))


    Bruno

Post a reply to this message