Hi!
If we remove the alternate macro function then we can have GetName for
celPcCommon returning hard references instead of assigning strings. Who
knows who could be using the alternate macro though? :))
CEL_IMPLEMENT_FACTORY_ALT (Blaa, "pcnew.blaa", "pcblaa")
so 1. can we remove this macro? 2. can we also add code to automatically
deal with pc prefix on property class names since they're basically
redundant? we can even declare a new macro.
another thing I've been thinking about is for the new system, to make
component objects with the idea to be glamourised property classes that will
eventually replace them. So entity will be storing components alongside
property classes. Then again entities are kind of redundant also if you can
chain a group of components (under a entity component).
cya!
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Cel-main mailing list
Cel-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cel-main
