Smalltalk › Pharo › Pharo Smalltalk Developers

[ann] pillar support in gtinspector

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

8 messages Options

Tudor Girba-2

[ann] pillar support in gtinspector

Hi,

I updated the Pillar support in GTInspector. Some of the extensions already exist in the default Pillar #development version. If you want to play with the full support, you can load it like this:

Gofer new
smalltalkhubUser: 'Moose' project: 'PetitParser';
package: 'PetitAnalyzer';
package: 'PetitIndent';
package: 'PetitIslands';
smalltalkhubUser: 'Moose' project: 'GToolkit';
package: 'GT-InspectorExtensions-Pillar';
load

Then you can just inspect a book folder and you get this:

I did not integrate this in the main Pillar yet because this is an older implementation based on a limited island parser. As now Pillar has a full parser based on PetitParser, the next step is to move the highlighting logic to use this parser instead of the island parser. From my measurements, the speed of the two parsers is about the same, so from a user perspective there will be not much changes.

It pains me that we are editing Pillar in outside tools, and now we should no longer have to do that. Of course, this is not the most ideal tool support for Pillar but I think it is a reasonable start.

Cheers,

Doru

--
www.tudorgirba.com
www.feenk.com

"Problem solving should be focused on describing
the problem in a way that makes the solution obvious."

Uko2

Re: [Moose-dev] [ann] pillar support in gtinspector

On 29 Aug 2016, at 21:41, Tudor Girba <[hidden email]> wrote:

Hi,

I updated the Pillar support in GTInspector. Some of the extensions already exist in the default Pillar #development version. If you want to play with the full support, you can load it like this:

Gofer new
smalltalkhubUser: 'Moose' project: 'PetitParser';
package: 'PetitAnalyzer';
package: 'PetitIndent';
package: 'PetitIslands';
smalltalkhubUser: 'Moose' project: 'GToolkit';
package: 'GT-InspectorExtensions-Pillar';
load

Then you can just inspect a book folder and you get this:

<inspector-pillar.png>

Cool!

I did not integrate this in the main Pillar yet because this is an older implementation based on a limited island parser. As now Pillar has a full parser based on PetitParser, the next step is to move the highlighting logic to use this parser instead of the island parser. From my measurements, the speed of the two parsers is about the same, so from a user perspective there will be not much changes.

It pains me that we are editing Pillar in outside tools, and now we should no longer have to do that. Of course, this is not the most ideal tool support for Pillar but I think it is a reasonable start.

To make things sadder: when I need to write some short “richish" I’m using markdown instead for pillar because in ATOM I can open the rendered version of my document that will update while i type (and will display images and so on). It could be nice to have the same functionality in Pharo, but I’m really busy with improving other parts. Additionally I’m not sure that it makes sense to reimplement rich text editor in Pharo.

Uko

Cheers,
Doru

--
www.tudorgirba.com
www.feenk.com

"Problem solving should be focused on describing
the problem in a way that makes the solution obvious."

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.list.inf.unibe.ch/listinfo/moose-dev

stepharo

Re: [Moose-dev] [ann] pillar support in gtinspector

Le 29/8/16 à 21:47, Yuriy Tymchuk a écrit :

On 29 Aug 2016, at 21:41, Tudor Girba <[hidden email]> wrote:

Hi,

I updated the Pillar support in GTInspector. Some of the extensions already exist in the default Pillar #development version. If you want to play with the full support, you can load it like this:

Gofer new
smalltalkhubUser: 'Moose' project: 'PetitParser';
package: 'PetitAnalyzer';
package: 'PetitIndent';
package: 'PetitIslands';
smalltalkhubUser: 'Moose' project: 'GToolkit';
package: 'GT-InspectorExtensions-Pillar';
load

Then you can just inspect a book folder and you get this:

<inspector-pillar.png>

Cool!

I did not integrate this in the main Pillar yet because this is an older implementation based on a limited island parser. As now Pillar has a full parser based on PetitParser, the next step is to move the highlighting logic to use this parser instead of the island parser. From my measurements, the speed of the two parsers is about the same, so from a user perspective there will be not much changes.

It pains me that we are editing Pillar in outside tools, and now we should no longer have to do that. Of course, this is not the most ideal tool support for Pillar but I think it is a reasonable start.

To make things sadder: when I need to write some short “richish" I’m using markdown instead for pillar because in ATOM I can open the rendered version of my document that will update while i type (and will display images and so on). It could be nice to have the same functionality in Pharo, but I’m really busy with improving other parts. Additionally I’m not sure that it makes sense to reimplement rich text editor in Pharo.

It does. We want a real editor in Pharo.

Uko

Cheers,

Doru

--
www.tudorgirba.com
www.feenk.com

"Problem solving should be focused on describing
the problem in a way that makes the solution obvious."

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.list.inf.unibe.ch/listinfo/moose-dev

abergel

Re: [ann] pillar support in gtinspector

In reply to this post by Tudor Girba-2

Hi!

Having a spell checker would be fantastic… Any chance to have this?

Alexandre

On Aug 29, 2016, at 4:41 PM, Tudor Girba <[hidden email]> wrote:

Hi,

I updated the Pillar support in GTInspector. Some of the extensions already exist in the default Pillar #development version. If you want to play with the full support, you can load it like this:

Gofer new
smalltalkhubUser: 'Moose' project: 'PetitParser';
package: 'PetitAnalyzer';
package: 'PetitIndent';
package: 'PetitIslands';
smalltalkhubUser: 'Moose' project: 'GToolkit';
package: 'GT-InspectorExtensions-Pillar';
load

Then you can just inspect a book folder and you get this:

<inspector-pillar.png>

I did not integrate this in the main Pillar yet because this is an older implementation based on a limited island parser. As now Pillar has a full parser based on PetitParser, the next step is to move the highlighting logic to use this parser instead of the island parser. From my measurements, the speed of the two parsers is about the same, so from a user perspective there will be not much changes.

It pains me that we are editing Pillar in outside tools, and now we should no longer have to do that. Of course, this is not the most ideal tool support for Pillar but I think it is a reasonable start.

Cheers,
Doru

--
www.tudorgirba.com
www.feenk.com

"Problem solving should be focused on describing
the problem in a way that makes the solution obvious."

Sean P. DeNigris

Re: [Moose-dev] [ann] pillar support in gtinspector

Administrator

In reply to this post by stepharo

stepharo wrote

It does. We want a real editor in Pharo.

+10 :)

Cheers,
Sean

Nicolai Hess-3-2

Re: [Pharo-users] [ann] pillar support in gtinspector

In reply to this post by Tudor Girba-2

2016-08-29 21:41 GMT+02:00 Tudor Girba <[hidden email]>:

Hi,

I updated the Pillar support in GTInspector. Some of the extensions already exist in the default Pillar #development version. If you want to play with the full support, you can load it like this:

Gofer new
smalltalkhubUser: 'Moose' project: 'PetitParser';
package: 'PetitAnalyzer';
package: 'PetitIndent';
package: 'PetitIslands';
smalltalkhubUser: 'Moose' project: 'GToolkit';
package: 'GT-InspectorExtensions-Pillar';
load

Then you can just inspect a book folder and you get this:

I did not integrate this in the main Pillar yet because this is an older implementation based on a limited island parser. As now Pillar has a full parser based on PetitParser, the next step is to move the highlighting logic to use this parser instead of the island parser. From my measurements, the speed of the two parsers is about the same, so from a user perspective there will be not much changes.

It pains me that we are editing Pillar in outside tools, and now we should no longer have to do that. Of course, this is not the most ideal tool support for Pillar but I think it is a reasonable start.

Cheers,
Doru

nice!

I just played a bit with the code to apply larger different font sizes for the headings and

use the code styler for inlined code ("==").

Maybe we should use a different code styler or add a way to instruct the styler to ignore unknown classes or uknown selectors :)

--
www.tudorgirba.com
www.feenk.com

"Problem solving should be focused on describing
the problem in a way that makes the solution obvious."

Tudor Girba-2

Re: [Moose-dev] [Pharo-users] [ann] pillar support in gtinspector

Hi Nicolai,

Did you commit your changes with the highlight of == code?

Cheers,
Doru

> On Sep 6, 2016, at 4:56 PM, Nicolai Hess <[hidden email]> wrote:
>
>
>
> 2016-08-29 21:41 GMT+02:00 Tudor Girba <[hidden email]>:
> Hi,
>
> I updated the Pillar support in GTInspector. Some of the extensions already exist in the default Pillar #development version. If you want to play with the full support, you can load it like this:
>
> Gofer new
> smalltalkhubUser: 'Moose' project: 'PetitParser';
> package: 'PetitAnalyzer';
> package: 'PetitIndent';
> package: 'PetitIslands';
> smalltalkhubUser: 'Moose' project: 'GToolkit';
> package: 'GT-InspectorExtensions-Pillar';
> load
>
> Then you can just inspect a book folder and you get this:
>
> <inspector-pillar.png>
>
> I did not integrate this in the main Pillar yet because this is an older implementation based on a limited island parser. As now Pillar has a full parser based on PetitParser, the next step is to move the highlighting logic to use this parser instead of the island parser. From my measurements, the speed of the two parsers is about the same, so from a user perspective there will be not much changes.
>
> It pains me that we are editing Pillar in outside tools, and now we should no longer have to do that. Of course, this is not the most ideal tool support for Pillar but I think it is a reasonable start.
>
> Cheers,
> Doru
>
>
> nice!
>
> I just played a bit with the code to apply larger different font sizes for the headings and
> use the code styler for inlined code ("==").
>
> Maybe we should use a different code styler or add a way to instruct the styler to ignore unknown classes or uknown selectors :)
>
>
>
>
> --
> www.tudorgirba.com
> www.feenk.com
>
> "Problem solving should be focused on describing
> the problem in a way that makes the solution obvious."
>
>
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.list.inf.unibe.ch/listinfo/moose-dev

--
www.tudorgirba.com
www.feenk.com

"Obvious things are difficult to teach."

Nicolai Hess-3-2

Re: [Pharo-users] [Moose-dev] [ann] pillar support in gtinspector

2016-09-14 22:47 GMT+02:00 Tudor Girba <[hidden email]>:

Hi Nicolai,

Did you commit your changes with the highlight of == code?

Cheers,
Doru

No, but I just saw that I misinterpreted the "==", first I thought this is for "inline code" as it was used in some class comment like that.

But it is actually a more general formatting tag for "monospaced font" - we actually don't need to do code highlighting for this text, just use a monospace font resp. code font.

> On Sep 6, 2016, at 4:56 PM, Nicolai Hess <[hidden email]> wrote:
>
>
>
> 2016-08-29 21:41 GMT+02:00 Tudor Girba <[hidden email]>:
> Hi,
>
> I updated the Pillar support in GTInspector. Some of the extensions already exist in the default Pillar #development version. If you want to play with the full support, you can load it like this:
>
> Gofer new
> smalltalkhubUser: 'Moose' project: 'PetitParser';
> package: 'PetitAnalyzer';
> package: 'PetitIndent';
> package: 'PetitIslands';
> smalltalkhubUser: 'Moose' project: 'GToolkit';
> package: 'GT-InspectorExtensions-Pillar';
> load
>
> Then you can just inspect a book folder and you get this:
>
> <inspector-pillar.png>
>
> I did not integrate this in the main Pillar yet because this is an older implementation based on a limited island parser. As now Pillar has a full parser based on PetitParser, the next step is to move the highlighting logic to use this parser instead of the island parser. From my measurements, the speed of the two parsers is about the same, so from a user perspective there will be not much changes.
>
> It pains me that we are editing Pillar in outside tools, and now we should no longer have to do that. Of course, this is not the most ideal tool support for Pillar but I think it is a reasonable start.
>
> Cheers,
> Doru
>
>
> nice!
>
> I just played a bit with the code to apply larger different font sizes for the headings and
> use the code styler for inlined code ("==").
>
> Maybe we should use a different code styler or add a way to instruct the styler to ignore unknown classes or uknown selectors :)
>
>
>
>
> --
> www.tudorgirba.com
> www.feenk.com
>
> "Problem solving should be focused on describing
> the problem in a way that makes the solution obvious."
>
>
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.list.inf.unibe.ch/listinfo/moose-dev

--
www.tudorgirba.com
www.feenk.com

"Obvious things are difficult to teach."