Re: [Pharo-users] rethinking compilation notifications

2014-08-04 Thread Tudor Girba
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

Re: [Pharo-users] rethinking compilation notifications

2014-08-04 Thread Werner Kassens
of course werner On 08/04/2014 12:09 PM, Yuriy Tymchuk wrote: On 04 Aug 2014, at 12:06, Werner Kassens 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. i

Re: [Pharo-users] rethinking compilation notifications

2014-08-04 Thread Yuriy Tymchuk
On 04 Aug 2014, at 12:06, Werner Kassens 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 >

Re: [Pharo-users] rethinking compilation notifications

2014-08-04 Thread Werner Kassens
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 th

Re: [Pharo-users] rethinking compilation notifications

2014-08-03 Thread Sven Van Caekenberghe
On 04 Aug 2014, at 00:07, Sean P. DeNigris wrote: > Tudor Girba-2 wrote >> compilation notifications... we used a popper interface to show the error >> without >> affecting the underlying text editor: > > Thank god! At least it used to be highlighted so you could delete it easily, > but now we

Re: [Pharo-users] rethinking compilation notifications

2014-08-03 Thread Sean P. DeNigris
Tudor Girba-2 wrote > compilation notifications... we used a popper interface to show the error > without > affecting the underlying text editor: Thank god! At least it used to be highlighted so you could delete it easily, but now we don't even have that. Any chance this could be ported easily to