search

ronaldwang / avatarcore

Automatically exported from code.google.com/p/avatarcore
0 stars 0 forks source link

Feature references in Library objects #2

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What would you like to see changed/added?

Support for Feature objects in Libraries.

How will this help you accomplish your goals?

Self-contained, full Feature definitions for Avatars rather than using
stitched together pieces spread out in FeatureDefinition sets.

What version of the product are you using now?

0.5.5

Please provide any additional information below.

I think this was part of the original design but must have been lost.  Some
investigation should first be made to identify any code that may already be
in place to facilitate all or part of this.

Original issue reported on code.google.com by senocu...@gmail.com on 10 Feb 2010 at 5:16

GoogleCodeExporter commented 9 years ago

Original comment by senocu...@gmail.com on 17 Feb 2010 at 5:21

GoogleCodeExporter commented 9 years ago 
i'm glad you brought this up as the current library doesn't have this. Could 
you 
remind us what a Feature does or is and how it differs from FeatureDefiniton 
exactly

Original comment by mediamou...@gmail.com on 21 Feb 2010 at 10:54

GoogleCodeExporter commented 9 years ago 
Features describe different interchangeable parts of an avatar.  
FeatureDefinitions
represent the different variations available for a feature.
http://www.myavatareditor.com/avatarcore/docs/com/myavatareditor/avatarcore/Feat
ure.html
http://www.myavatareditor.com/avatarcore/docs/com/myavatareditor/avatarcore/Feat
ureDefinition.html
http://code.google.com/p/avatarcore/wiki/AboutFeatures
http://code.google.com/p/avatarcore/wiki/AboutLibraries

My Avatar Editor demonstrates the usage well.  Things like eyes, noses, hair -
they're all features.  The different variations of those features are defined in
FeatureDefinition objects.  Pick a new hair style, and the art for the hair 
feature
is grabbed from the available variations in the respective hair 
FeatureDefinition.

FeatureDefinition's also contain variations of color and adjustments 
(transforms).
With that, any combination of art, color, and adjust within a definition can be 
used
for a single feature.

Feature's aren't necessary in Libraries. In fact, they'll be redundant with
FeatureDefinitions, and more restrictive since each Feature can only contain 
one art,
color, and adjust.  The purpose of supporting them is simply to provide a 
simple use
case that may be easier to pick up by beginners.

Original comment by senocu...@gmail.com on 21 Feb 2010 at 3:12