"Class" are too abstract for xTalk. You dont see a class. "Template" are more easy if you can see your template and edit it as any other object. In metacard you can edit the templates of standard objects, but - you can not see them before you create a new object - you can not create your own templates The xtalk way must remains as visual as possible. My suggestion : 1) to store templates as objects or groups on the cards of some templateStack 2) be allowed to create, edit and delete templates in the templateStack 3) when you create a new object, it is a perfect copy of the template ; some of its properties are set (the id, the layer ...) all other properties are empty ie inherited from the the template. If you edit some property of the object (for example move it), the property has a value and is no longer inherited from the template. Metacard works already like that with colors and fonts... The main problem is what happens if you delete a template ? But that's the same when you delete a group ... ---------------------------- Claude Lemmel / Opus species email : [EMAIL PROTECTED] website : www.opus-species.com ------------------------------
