I'm a bit confused - general architecture of what, exactly? Sorry if this is obvious. The organisation? The artefact that VPRI will eventually produce? or FoNC itself?
What is a "view" here? It appears to be inverted for your use. Surely REASON comes before PROCESS, doesn't it? (That is, rather than focus on the processes, or applications that a user will be focussing on, why not focus on the things that the people are trying to achieve). That is, in the process going to the bank to get some money out, the reason is surely king - it's the driver... and that's to get money out so I can go and buy food. Julian On 09/12/2012, at 3:09 AM, John Carlson <[email protected]> wrote: > So I was just designing a generic architecture presentation, and I came up > with 5 different types of views. Are there more? > > Editor (programmer, designer, scripter) > Debugger (programmer) > Browser (end user, player, sharing) > Configuration (setting property lists) > Administration (ACLs, grant, revoke, capabilities, upgrading schema) > > What are the FoNC thoughts on supporting all these views? What's the best > approach for children? On one of my projects, we combined the Editor, > Debugger and Browser into a single view , which we called the workbench (or > recorder), then we added views for various tools we wanted to incorporate. > If we would have had a GUI builder, we probably would have had Configuration. > What I don't know how to do is incorporate Administration, except by > providing capabilities to share behavior and structure. How does the user > interface for capabilities appear in FoNC? > > John > _______________________________________________ > fonc mailing list > [email protected] > http://vpri.org/mailman/listinfo/fonc _______________________________________________ fonc mailing list [email protected] http://vpri.org/mailman/listinfo/fonc
