I am referring to a general workflow that will ensure a user has a uniform experience GUI wise. For example a gui tool will have to use the tab system if it can be spanned in multiple instances, have a shortcut dialog that will appear in a specific way, tools that come with their own code editors respect general editor shortcuts etc etc . It will form the basis upon which GUIs that are integrated to pharo are based on and then also allow for freedom of expression on implementation details. A general agreement on how Pharo should behave GUI wise since GUI is such a huge deal for Pharo.
On Mon, Mar 23, 2015 at 4:58 PM, Peter Uhnák <i.uh...@gmail.com> wrote: > On Mon, Mar 23, 2015 at 3:15 PM, kilon alios <kilon.al...@gmail.com> > wrote: > >> It would be nice if there was a general guideline of GUI design that all >> tools would have to obey instead of giving complete freedom in creating a >> very fragmented experience. >> > Could you elaborate on this a little? Are you refering to Spec vs Glamour > (Brick)? Or issues inside of Spec, and/or Morphic? > > Peter > >
