On 04 Aug 2014, at 12:06, Werner Kassens <wkass...@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. >
