Volker Braun <[email protected]> writes: > I've been thinking about a native interface for a while, and I think > the biggest misconception is that one should just write yet another > notebook. What we should develop is a better separation of UI and the > business logic (notebooks holding cells of code and output). I can't > really discern any UI design pattern in the current sagenb, its just > munching html everywhere. The classic MVC pattern would separate > > - model: the notebook as a list of different types of cells, read/ > write sws (doesn't know about html at all) > - view: this is the only part that speaks html > - controller: receives events from the view (user pressed button) and > updates model accordingly. > > Switching between a web and a native gui should just boil down to > replacing the view. There are refinements of this pattern like MVP > but the fundamental idea is always that view and model are strictly > separated.
I think that Samuel Ainsworth's new GUI for sagenb moves in this direction. See http://github.com/samuela/sagenb and various posts on the sage-notebook list. -Keshav -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-support?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
