I'd also be quite careful about going through with this project. The 
trouble point to me is 'large' and 'features will be changing until the 
final publish'. Unless you're paid by the hour, this is the road to 
hell. Feature creep is fine, but the bigger a project the more you 
should plan ahead. No framework is going to save you from 'client 
wobble'. Extreme programming is fine for hobby projects but with clients 
and money and deadlines, it seems like recipe for disaster.

Just my two cents,

Patrick

[EMAIL PROTECTED] wrote:

>Hello List,
>
>I'm starting off with a bunch of info, and I'll get to some real questions at
>the end of this post.
>
>I'm getting started on an offline (disk-based) project.  I'd like whatever
>advice you might be able to give, to point me in the right direction.
>
>Here are some aspects of the project:
> - offline
> - keyboard-driven (no mouse)
> - buttons highlight, scroll, move as you arrow around the screen
> - most screens will have independent functionality
>   - slideshow, music player, video selector (several different ways)
> - nearly every place in this project will have multiple routes of access.
>   example:
>   - mainmenu -> watch last movie
>   - mainmenu -> movie features -> watch last movie
> - lots of sub-sub-sub menus.
>Keyboard shortcuts
> - available for various things
> - will change depending on what is currently visible
> - some will be global
>
>I think that I would like to load a lot of this at runtime, since the main SWF
>could get quite large, and compile times pretty long.  My thought on that is to
>listen for the onLoad event of loaded swfs, and set up the objects and 
>listeners
>at that time.
>
>The exact features, menu items, screens, and functionality on the screens will
>probably be changing up until the final publish of this project.  Actually, the
>end result of this project should be modular enough to add and remove screens
>and items at any time.  I'm looking at ARP, because it's supposed to so
>flexible.
>
>I have studied through the Birthday Organizer application, and built a small
>beginning application of my own to make sure I would be able to hook everything
>together.  I'm moving along slowly, but so far, it's making sense.
>
>I'm having a hard time figuring out how to merge key listeners with the ARP
>listener scheme.
>
>MY ACTUAL QUESTIONS:
>Do you think ARP is the right framework for me on this project?  (If I really
>use ARP, I'm going to need some guidance)
>Could you provide me any pointers so that I avoid the brick wall halfway 
>through
>the project?
>
>
>Many many thanks in advance!
>David Lanier
>
>_______________________________________________
>osflash mailing list
>[email protected]
>http://osflash.org/mailman/listinfo/osflash_osflash.org
>
>  
>


_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to