Le 15/05/2014 09:29, Hilaire Fernandes a écrit :
Thierry,
I was not aware it could be that short. Yes it will be nice. All in all: - one GUI tool to edit an existing script (so no visibility on the other methods of the class)
Hilaire, Would you need the script to hide the fact it is a method or not? I.e. make it DSL-Like and hide the method header and its parameters?
- one GUI tool to create a method (with visibility to the other method of the class, as possible examples)
Does it includes the ability to modify existing methods? I ask that to see if we need to hide much of what makes a system browser in Smalltalk, or, to the contrary, if it is a good idea to open up to the browser world so as to introduce the user (maybe advanced) to the underlying Pharo so as to allow for more powerfull extensions. If we need to hide, then it will be with a dedicated GUI. If we open up, then a restricted browser is best (and then, if we want to keep to standards in Pharo, it means Nautilus). Is DrGeo development open so that I may write it myself ? Thierry
Hilaire
Le 15/05/2014 09:18, Goubier Thierry a écrit :
Have you considered controlling the user experience directly to let him focus only on the method to create or edit?
Creating a text editor window in coding mode with the ability to edit or create a method in a preset class is not much work; I'd say around 20 lines with the default menu and an accept which compiles.
If you want complete control on the menu (i.e. a bit more polish than the default and control over which shortcuts are active), I can extract what I've done for mine: it's a minimal command objects API to couple menus and shortcuts inspired by the one of the OmniBrowser (of Pharo 1.4). In there, a typical command with its shortcut/label/icon/activation status is about five lines long.
-- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95