Benjamin wrote:
On 04 Mar 2014, at 11:15, Sven Van Caekenberghe
wrote:
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.
Sounds more like a hack than a solution :)
On 04 Mar 2014, at 11:15, Sven Van Caekenberghe wrote:
> 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.
Sounds more like a hack than a solution :)
Ben
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 wrote:
> Hi Max,
>
> thanks, I already found it, remembering that the same UX flaw for
> "File out" is there eve
On 04.03.2014, at 10:36, Jan Vrany 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 sa
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 t
If there’s no file then there was probably an exception. Try again with the
latest Fuel version (hasn’t been integrated into 3.0 yet).
Files are saved to the image directory as “Debugger…”
Cheers,
Max
On 04.03.2014, at 00:49, Jan Vrany wrote:
> Hi,
>
> Just a comment on user interface:
> I f
+1 (for Nautilus fileout)
Esteban A. Maringolo
2014-03-03 20:49 GMT-03:00 Jan Vrany :
> 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, an
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 a