A simple, quick solution would be to do an #inform: telling what was written where. In Pharo this then becomes a growl like non-obstrusive thing.
On 04 Mar 2014, at 10:36, Jan Vrany <[email protected]> wrote: > Hi Max, > > thanks, I already found it, remembering that the same UX flaw for > "File out" is there ever since Squeak days. > > > Files are saved to the image directory as “Debugger…” > > The real question here is: How should I know? I was merely saying > that usability/UX of tools is, say, poor (this is not the only > issue I run into in first 10 minutes of work :-) That's all :-) > > Jan > > >> >> Cheers, >> Max >> >> >> On 04.03.2014, at 00:49, Jan Vrany <[email protected]> wrote: >> >>> Hi, >>> >>> Just a comment on user interface: >>> I found a bug (#13035) and wanted to attach fueled stacktrace to report. >>> So I selected "Fuel out Stack". Oops, nothing happened. My first reaction >>> was "aha, another bug". >>> >>> What one would expect is a file dialog asking where do I want to save the >>> file. Or at least info where the file has be saved would be much much >>> better :-) Same for file out in browser... >>> >>> Best, Jan >>> >> >> >> > >
