On 12 Jan 2013, at 10:16, Hal Murray <hmur...@megapathdsl.net> wrote:
> > walter.ben...@gmail.com said: >>> Or may be ask the user (while exiting), that whether the user >>> wishes to save the game? > >> Not a very Sugary approach. > > What is the right way for Sugar to handle that problem? It should auto save as much state as possible so a resume is as seamless as possible. > I get annoyed when I start an activity and it pops up in some strange state > rather than the new-game I expect. That is a different and long standing design issue. We were hoping to land an improvement for build 13.1.0, Sugar 0.98, but time was too tight with all the other GTK3 and touch UI work needed. The enhancement was to make start new/resume an explicit choice for the user when pressing an icon in the home view. An intermediate, full screen UI would open prior to the activity launch pulse icon with large thumbnails for either start new, some resume choices, or cancel. It would contain similar functionality as per the right click activity palette (that it would be replacing) but we have the full screen available for thumbnails, titles, a clear layout, and large button hit targets for novice trackpad or touch screen users. Regards, Gary > On the other hand, if I was working on > something when the system shut down due to battery running low or such, > starting over where I left off might be a wonderful idea. > > I think Sugar needs either/both of: > Exit/Discard vs Exit/Save > Start/New vs Start/Resume > > > > -- > These are my opinions. I hate spam. > > > > _______________________________________________ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
