[Pharo-project] Suggestion Note:

Stéphane Ducasse stephane.ducasse at inria.fr
Sat Jan 7 12:45:55 EST 2012

On Jan 4, 2012, at 10:22 AM, S Krish wrote:

> Should raise this as a separate artifact and probably send out my fixes ( currently these are hacks).
> Many of the other logics do not work as per standard practices... from other comp usage.. windows/ linux..
> * FileOut is silent and saves to the resources folder ... no chance of intervention while it goes out.. also overwrites silently..
>      Simple save/ saveas popup menu would help .. when reqd.
> * Image saveAs : only image name is taken.. no folder selection... though one can give a full path in the text editor.
> * remember the last navigated path in file open/ save dialogs
> * Monticello save is incremental and quickly builds up a huge stack of files.. need to optimize this.. autosave packages marked to a given default single file overwriting it.. reduce multiple mc saves to the minimum when you really need to version a new base.

sign the license
send code
and we will discuss


More information about the Pharo-dev mailing list