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. On Wednesday, February 13, 2013 2:47:15 AM UTC, Jason Grout wrote: > > On 2/12/13 7:11 PM, Janil Garcia wrote: > > I just want to know: if someone become interested in creating a 'native' > (Qt, GTK) interface for Sage, how would the community would respond? > > People would like? > > I think it'd be great. As for Cantor---do whatever you think is best. > -- 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.
