[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."
On 29 Aug 2016, at 21:41, Tudor Girba <tudor@tudorgirba.com> 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 <http://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 Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
Le 29/8/16 à 21:47, Yuriy Tymchuk a écrit :
On 29 Aug 2016, at 21:41, Tudor Girba <tudor@tudorgirba.com <mailto:tudor@tudorgirba.com>> 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 <http://www.tudorgirba.com/> www.feenk.com <http://www.feenk.com>
"Problem solving should be focused on describing the problem in a way that makes the solution obvious."
_______________________________________________ Moose-dev mailing list Moose-dev@list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch> https://www.list.inf.unibe.ch/listinfo/moose-dev
stepharo wrote
It does. We want a real editor in Pharo.
+10 :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/ann-pillar-support-in-gtinspector-tp4913115p4913691.ht... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Hi! Having a spell checker would be fantastic⦠Any chance to have this? Alexandre
On Aug 29, 2016, at 4:41 PM, Tudor Girba <tudor@tudorgirba.com> 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 <http://www.tudorgirba.com/> www.feenk.com
"Problem solving should be focused on describing the problem in a way that makes the solution obvious."
2016-08-29 21:41 GMT+02:00 Tudor Girba <tudor@tudorgirba.com>:
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."
Hi Nicolai, Did you commit your changes with the highlight of == code? Cheers, Doru
On Sep 6, 2016, at 4:56 PM, Nicolai Hess <nicolaihess@gmail.com> wrote:
2016-08-29 21:41 GMT+02:00 Tudor Girba <tudor@tudorgirba.com>: 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 Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
-- www.tudorgirba.com www.feenk.com "Obvious things are difficult to teach."
2016-09-14 22:47 GMT+02:00 Tudor Girba <tudor@tudorgirba.com>:
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 <nicolaihess@gmail.com> wrote:
2016-08-29 21:41 GMT+02:00 Tudor Girba <tudor@tudorgirba.com>: 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 Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
-- www.tudorgirba.com www.feenk.com
"Obvious things are difficult to teach."
participants (6)
-
Alexandre Bergel -
Nicolai Hess -
Sean P. DeNigris -
stepharo -
Tudor Girba -
Yuriy Tymchuk