This one I would have to 100% disagree -integrate FourQ package directly into the Core code base
Rather than integrate a pretty solid package into the core, let's start building the core out in a package heavy format.
farcry.util.*
farcry.fourq.*
farcry.ntm.*
farcry.security.*
etc
Basically we envisaged doing exactly as you describe, and retaining FourQ as a distinct package, perhaps ../packages/farcry/fourq. The main reason for moving it into the farcry_core code base is to eliminate the added complication of having a package outside of farcry_core that doesn't have a particularly large following outside of the FarCry community -- though I'm certainly open contrary arguments.
-- geoff http://www.daemon.com.au/
--- 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/
