Sticky is where we will likely be going :). I do not like embedding the printout as a comment because this implies that the editor gets changed. And you almost never want that. At most, you want to compare, and for that we can find other solutions. In the meantime, you can still copy the result of the printout (Cmd+a , Cmd+c) and paste it in the editor manually. Cheers, Doru On Mon, Aug 4, 2014 at 12:15 PM, Werner Kassens <wkassens@libello.com> wrote:
of course werner
On 08/04/2014 12:09 PM, Yuriy Tymchuk wrote:
On 04 Aug 2014, at 12:06, Werner Kassens <wkassens@libello.com> wrote:
Hi,
makes a lot of sense to me. btw i dont like the printit thing too much: there was a a thread about scientists using programming languages with a notebook interface somewhere. in order to document what i do, i often use print it and then press '"' to make a comment out of the result. iow this printit version would need a 'make it a comment' command additionally to the inspectit command.
Or make is a sticky ;). I think that non-text solutions still have greater possibilities
Uko
werner
On 08/03/2014 10:09 PM, Tudor Girba wrote:
Hi,
The next stop in our little tour around code actions was the compilation notifications. Again, we used a popper interface to show the error without affecting the underlying text editor:
http://www.humane-assessment.com/blog/rethinking- compilation-notifications-in-pharo/
Please let us know what you think.
-- www.tudorgirba.com "Every thing has its own flow"