Michael Sammut spoke the following wise words on 20/06/2004 10:16 PM EST:
I like your thoughts there.  A formal mechanism would be great.  Sounds like
a pretty big task though?!  I am game assist once a game plan is enacted!

Well we can start on the core requirements and add the rest as we go.

We have some rules and some custom types too.  I guess I have taken for
granted the ease of developing some of these custom types or rules and
thought that they would not be useful to others.  On the other hand, there
are some things that do not require code, rather explanations/walkthroughs.

I guess my company can get on the ball and start sending more of this over.

Yeah although I'm not sure what extra explanations/walkthroughs are needed?

I guess if everybody does custom work then this idea may not be that useful.

Personally I'd prefer to be able to package modules like this to allow sharing and code updating between farcry projects and servers. Also this might smoothen the staging->live transition. Being able to host them for free download on the community site would be an added bonus.

-- tim lucas

http://www.toolmantim.com


My original suggestion:
For a more formal install & packaging I think we should devise a FarCry
module description XML schema. This would have:
  * name
  * description
  * author
  * url
  * email
  * list of custom types
  * list of custom rules
  * list of custom sec policies
  * list of custom configs
  * custom install file url
  * custom uninstall file url
  * dummy table data (WDDX?) url

All this and the files could be pacakaged as a zip.

For the community website you could then autoextract this information
from the zip (which would mean it would be mega-easy for authors to keep
the info fresh as well).

For the core install procedure we could deploy all the types, rules,
secpols and configs and forward the user to the custom install file (if
anything else needs to be done). Also in later iterations we could have
it check for naming conflicts and deal with updates.

Also I think a way to group publishing rules would be very handy because
the publishing rule list starts to get a bit big for that tiny little
box (so all of a modules publishing rules would be grouped together).

--- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/

Reply via email to