Just tossing in a few words I'd like to see well supported:

Distribution
Deployment
Installation
Integration
Upgrade (data/state migration, transition between dependencies, consistency
guarantees, deployment of)
History (cross cuts most things)
Dependencies, Entanglement
Version Control
Merge
Data persistence (e.g. schema, tables)
Discussions (e.g. something like talk pages, user pages on wikis)
Tasks, Priorities, Bug tracker

I'm sure I've missed many.


On Dec 8, 2012 8:10 AM, "John Carlson" <yottz...@gmail.com> 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
> fonc@vpri.org
> http://vpri.org/mailman/listinfo/fonc
>
_______________________________________________
fonc mailing list
fonc@vpri.org
http://vpri.org/mailman/listinfo/fonc

Reply via email to