Re: [GD-General] Game data editor

[Sylvain G. V. <vi...@ii...>]

Hi,

Usually Maya will do quite a good level editor.

Good things with Maya:
 * 80% of the work is already done,
 * quite sable, * artists and designers already know the tool,
 * one call create custom tools and interfaces using MEL,
 * one can have a realtime game-like rendering using CgFx/ColladaFx and
shaders.

The bad points being:
 * no immediate level testing, data has to be exported to game format (I
like using Collada + custom tools there) before being usable.
 * the rendering isn't exactly the same (no shadows for example),

From: Ola Olsson <ola...@gm...>
> [...]
> I've whipped up with a short list of desirable features (fairly 
> random):* Interface to supply/get data base (.csv or XML or SQL or 
> whatever)* Interface to supply/get meta data (for example 
> constraints, tool tips, 
> whatever).
> * Commands with Undo/Redo (preferably with a transaction mechanism, 
> grouping 
> commands that should be undone/redone together).
> * Ability to connect version control system.
> * Extensible menus.
> * Extensible views of the data (this includes 3D views).
> * Message pipe or other convenient way to communicate between 
> different 
> views/components/things.
> * Ability to script both GUI and behaviour (preferably C# or 
> something sensible like that).
> * Docking windows framework.
> * Typed ID/Reference support, for linking  data fields to other 
> things, bit 
> special case perhaps, but it keeps cropping up.
> * Modular design, e.g. a set of libraries that can be used more or 
> less 
> independently.
> * Library of nifty widgets.