Smalltalk › Pharo › Pharo Smalltalk Users

rethinking compilation notifications

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

9 messages Options

Tudor Girba-2

Aug 03, 2014; 8:09pm

rethinking compilation notifications

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:

You can find more details here:

http://www.humane-assessment.com/blog/rethinking-compilation-notifications-in-pharo/

Please let us know what you think.

Cheers,

Doru

www.tudorgirba.com

"Every thing has its own flow"

Sean P. DeNigris

Aug 03, 2014; 10:07pm

Re: rethinking compilation notifications

Administrator

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 Pharo core?

Cheers,
Sean

Guillermo Polito

Aug 04, 2014; 4:57am

Re: rethinking compilation notifications

In reply to this post by Tudor Girba-2

Just

Le 3 août 2014 22:09, "Tudor Girba" <[hidden email]> a écrit :

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:

You can find more details here:
http://www.humane-assessment.com/blog/rethinking-compilation-notifications-in-pharo/

Please let us know what you think.

Cheers,
Doru

--
www.tudorgirba.com

"Every thing has its own flow"

... [show rest of quote]

Sven Van Caekenberghe-2

Aug 04, 2014; 6:34am

Re: rethinking compilation notifications

In reply to this post by Sean P. DeNigris

On 04 Aug 2014, at 00:07, Sean P. DeNigris <[hidden email]> 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 don't even have that. Any chance this could be ported easily to
> Pharo core?

+1 Please

>
> -----
> Cheers,
> Sean
> --
> View this message in context: http://forum.world.st/rethinking-compilation-notifications-tp4771635p4771640.html
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>

Santiago Bragagnolo

Aug 04, 2014; 7:26am

Re: [Pharo-dev] rethinking compilation notifications

In reply to this post by Tudor Girba-2

So beautiful :)

2014-08-03 22:09 GMT+02:00 Tudor Girba <[hidden email]>:

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:

You can find more details here:
http://www.humane-assessment.com/blog/rethinking-compilation-notifications-in-pharo/

Please let us know what you think.

Cheers,
Doru

--
www.tudorgirba.com

"Every thing has its own flow"

... [show rest of quote]

wernerk

Aug 04, 2014; 10:06am

Re: rethinking compilation notifications

In reply to this post by Tudor Girba-2

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.
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.

Uko2

Aug 04, 2014; 10:09am

Re: rethinking compilation notifications

On 04 Aug 2014, at 12:06, Werner Kassens <[hidden email]> 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.
>

wernerk

Aug 04, 2014; 10:15am

Re: rethinking compilation notifications

of course
werner

On 08/04/2014 12:09 PM, Yuriy Tymchuk wrote:

>
> On 04 Aug 2014, at 12:06, Werner Kassens <[hidden email]> 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.
>>
>
>
>

... [show rest of quote]

Tudor Girba-2

Aug 04, 2014; 10:37am

Re: rethinking compilation notifications

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 <[hidden email]> wrote:

of course
werner

On 08/04/2014 12:09 PM, Yuriy Tymchuk wrote:

On 04 Aug 2014, at 12:06, Werner Kassens <[hidden email]> 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.

... [show rest of quote]

... [show rest of quote]

www.tudorgirba.com

"Every thing has its own flow"