Smalltalk › Pharo › Pharo Smalltalk Users

New pretty printer Blue Ink

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

5 messages Options

Franck Warlouzet

New pretty printer Blue Ink

Hello everyone,

We just integrated Blue Ink, the new pretty printer, in the latest Pharo 5 image ! Basically what was working still is and what was not well now is.

It is not yet enabled by default, we will wait for feedbacks first. If you want to try it, just type :

RBProgramNode formatterClass: BIConfigurableFormatter. BIConfigurableFormatter formatAsYouReadPolicy: true

Feel free to contact me via the mailing list or personnal mail if you experience a strange behavior. I tried to improve all of them but with you I am sure all the cases will be treated in an exhaustive way.

Thanks for testing it, I hope it will convince you to use format as you read in Nautilus or just automatically format your code.

Franck

Sven Van Caekenberghe-2

Re: New pretty printer Blue Ink

Nice.

All this new stuff (decompiler, formatter), what's next (new changes log ? ;-).

> On 22 Jul 2015, at 10:44, Franck Warlouzet <[hidden email]> wrote:
>
> Hello everyone,
>
> We just integrated Blue Ink, the new pretty printer, in the latest Pharo 5 image ! Basically what was working still is and what was not well now is.
>
> It is not yet enabled by default, we will wait for feedbacks first. If you want to try it, just type :
>
> RBProgramNode formatterClass: BIConfigurableFormatter.
>
> BIConfigurableFormatter formatAsYouReadPolicy: true
>
> Feel free to contact me via the mailing list or personnal mail if you experience a strange behavior. I tried to improve all of them but with you I am sure all the cases will be treated in an exhaustive way.
>
> Thanks for testing it, I hope it will convince you to use format as you read in Nautilus or just automatically format your code.
>
> Franck

NorbertHartl

Re: New pretty printer Blue Ink

> Am 22.07.2015 um 11:27 schrieb Sven Van Caekenberghe <[hidden email]>:
>
> Nice.
>
> All this new stuff (decompiler, formatter), what's next (new changes log ? ;-).
>
That is a very good question. When will Epicea be integrated? The current stuff is broken anyway so less chance to worsen things :)

Norbert

>> On 22 Jul 2015, at 10:44, Franck Warlouzet <[hidden email]> wrote:
>>
>> Hello everyone,
>>
>> We just integrated Blue Ink, the new pretty printer, in the latest Pharo 5 image ! Basically what was working still is and what was not well now is.
>>
>> It is not yet enabled by default, we will wait for feedbacks first. If you want to try it, just type :
>>
>> RBProgramNode formatterClass: BIConfigurableFormatter.
>>
>> BIConfigurableFormatter formatAsYouReadPolicy: true
>>
>> Feel free to contact me via the mailing list or personnal mail if you experience a strange behavior. I tried to improve all of them but with you I am sure all the cases will be treated in an exhaustive way.
>>
>> Thanks for testing it, I hope it will convince you to use format as you read in Nautilus or just automatically format your code.
>>
>> Franck
>
>

Franck Warlouzet

Re: New pretty printer Blue Ink

In reply to this post by Sven Van Caekenberghe-2

> From: [hidden email]
> Date: Wed, 22 Jul 2015 11:27:46 +0200
> To: [hidden email]
> Subject: Re: [Pharo-users] New pretty printer Blue Ink
>
> Nice.
>
> All this new stuff (decompiler, formatter), what's next (new changes log ? ;-).

New groups in Nautilus too, currently they are full of bugs and strange things. I am cleaning them up, I hope I will soon be done so you can use them.

Franck

> > On 22 Jul 2015, at 10:44, Franck Warlouzet <[hidden email]> wrote:
> >
> > Hello everyone,
> >
> > We just integrated Blue Ink, the new pretty printer, in the latest Pharo 5 image ! Basically what was working still is and what was not well now is.
> >
> > It is not yet enabled by default, we will wait for feedbacks first. If you want to try it, just type :
> >
> > RBProgramNode formatterClass: BIConfigurableFormatter.
> >
> > BIConfigurableFormatter formatAsYouReadPolicy: true
> >
> > Feel free to contact me via the mailing list or personnal mail if you experience a strange behavior. I tried to improve all of them but with you I am sure all the cases will be treated in an exhaustive way.
> >
> > Thanks for testing it, I hope it will convince you to use format as you read in Nautilus or just automatically format your code.
> >
> > Franck
>
>

tinchodias

Re: New pretty printer Blue Ink

In reply to this post by NorbertHartl

On Wed, Jul 22, 2015 at 11:41 AM, Norbert Hartl <[hidden email]> wrote:

> Am 22.07.2015 um 11:27 schrieb Sven Van Caekenberghe <[hidden email]>:
>
> Nice.
>
> All this new stuff (decompiler, formatter), what's next (new changes log ? ;-).
>
That is a very good question. When will Epicea be integrated? The current stuff is broken anyway so less chance to worsen things :)

I hope we can integrate it soon. One of the points that delayed the integration is that we shouldn't have two overlapping mechanisms to log changes in the 5.0 release (traditional .changes/.sources file + Epicea). Then, I have made many small refactorings in Pharo 5.0 towards making the whole .changes thing removable. In particular, I tried to encapsulate reads/writes to the changes files, the uses of RemoteString, and others, into SourceFileArray (as a kind of façade). A more clear and concentrated API in SourceFileArray is helping to understand how this thing works and how it could be removed and replaced. For example, SourceFileArray was a subclass of collection and there were many "SourceFiles at: 2" spread in the image to access the .changes file. Currently those are fixed but there is still some work to do. But I do believe we can have a removable .changes thing for Pharo 5 :-)

Martín