There's no place like Home

Kay C Lan lan.kc.macmail at gmail.com
Thu Jun 7 22:49:27 EDT 2007


> Eric Chatonet wrote:
>  could be interesting to
>  list features that would be nice to have according to three levels:
>
>  1. Beginners
>  2. Hobbyists
>  3. Pros *
>
> Actually, pros don't need a home stack or are able to write their
> own tools (as you do and many among us) but this would help hobbyists to
> go to the next step.



IMO I'd make it solve the one problem that EVERY Rev user faces at one stage
or another whether they be a beginner in programming or a pro from another
language. Plus, I believe the Pros in Rev would find it handy too. It was
also not a problem in HC, which may be why it catches so many ex HC users.

I'd make the Home Stack a 'Splash Screen' where you'd be encouraged (not
forced) to place a graphic (company logo or just a photo of yourself) and
maybe some contact details (optional). The first time you ever opened Rev
you'd be guided through the process, but if you clicked the 'Not Now' button
the Home Stack would have an 'Update Spash Screen'  button in easy view.

The Home Stack (in the IDE) would then have one other button, a "Start New
Project" button, which when pressed would then clone the Home Stack, but
clean it so as to make it just a 'Spash Screen' stack (ie no Start New
Project button) and also make a 'Working' stack. The Splash Screen (and Home
stack) would disappear, leaving the Working stack as the logical place for
the beginner to start the next killer app.

For the beginner, how many 'my stack works fine in the IDE but when I create
a standalone I can't seem to save any data' questions would you avoid.

For the Rev Pro, their Home stack would look exactly like their company
splash screen. The option to hide the Home Stack would still be there, and
obviously you could 'Start New Project' from a Menu, but the result would be
the same, your Splash Screen and Working Stack would be cloned from your
Home Stack template. How much time would that save you?

Just my thoughts.



More information about the use-livecode mailing list