I was thinking yesterday there should be a standardized block of information.
BUILD:
SCIRRA PLGUINS:
THIRD PARTY PLUGINS:
BUILD: 153
SCIRRA PLGUINS: Function, Sprite, Array
THIRD PARTY PLUGINS: Lite.Tween, SVGCanvas
That way we can have an idea what in it and know ahead of time if we wan't to download the capx or if it's a waste of time because we dont' want X plugins.
Also I think there should be general guidelines.
* Documented
Un-documented code can be hard to work with. In fact undocumented code can lead to loss of productivity. This leads to searching for HOW X is done or why can't Y be done.
* Polished
The code should be easy to look at.
* Cleaned
If there are disabled code. List why. Is it a feature that can optionally be enabled or is it just prior debugging code.
* Good and meaningful description in the name.
Example
"foofongs Bejeweled kit"
now this sounds good for anyone wanting to get into making bejeweled clone. the capx is downloaded. and BOOM the CAPX requires 10 Plugins of RexRainbows work(dude makes great plugins). There is a problem here.
1. The developer likely doesn't now how much of it works.
2. There is likely to be a lot of work to modify the game enough
3. what plugins do what? no way to tell.
Instead foofong should have given a title like
"foofongs Bejewled kit using RexRainbows plugins"
BUILD: 153(beta)
SCIRRA PLGUINS: ?
THIRD PARTY PLUGINS: ?
The reason for this. Is because then other developers really know what they are looking at. Does foofong actually know how to do a Bejeweled game or is he just muddling his way through using many different plugins. The description can help out a lot to up and coming developers.
As an example. Someone may be trying to develope a matching engine for a game that isn't anything like Bejewelled as a whole. They don't want to install 4 plugins just for a little mini game inside there platformer. So instead they just want to find the match algorythim. because foofong copied his capx and did only a handful of changes. The capx is mostly unhelpful.