- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Shout style table editor (Request for Feedback)

by Yuriy Tymchuk

Super cool! > On 11 Oct 2016, at 10:26, Guille Polito <guillermopolito(a)gmail.com> wrote: > > Nice! > > <3 > > -------- Original Message -------- >> Wow, that looks very nice ! >> >>> On 10 Oct 2016, at 18:42, Nicolai Hess <nicolaihess(a)gmail.com> wrote: >>> >>> I am working on a syntax style table editor, see issue for some background about this. >>> 18322 Settings for Syntax Highlighting a bit confusing >>> 15409 A more complete set of syntactic colors is needed >>> >>> >>> Load package >>> >>> ST-StylingPreview >>> ST-StylingPreviewShoutExtension >>> >>> from >>> >>> MCHttpRepository >>> location: 'http://smalltalkhub.com/mc/NicolaiHess/StylerTableEditor/main' >>> user: '' >>> password: '' >>> >>> And open the preview/editor with: >>> >>> STStylerPreview open. >>> >>> This is a prototype, you can view builtin style tables, create and edit new custom style tables. >>> This has some fake code styler methods to make the styling work for the >>> code preview pane, and it supports more styling attributes than the default styler. >>> >>> This is what I would like to have as a syntax style setting dialog instead of the current >>> confusing behavior. It may be helpful to actually see what syntax styling attributs are >>> actually available. >>> >>> >>> <PharoScreenshot.3.png> >> > >

Oct. 11, 2016

Re: [Pharo-dev] Fixing a problem with FastTable Context Menus

by tesonep＠gmail.com

Thanks! On Tue, Oct 11, 2016 at 11:37 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > now you have rights :) > > On 11 Oct 2016, at 11:13, tesonep(a)gmail.com wrote: > > Hello, > I have fixed a problem in the FastTable's context menus, but I don't > have access to the Moose/Glamour repository in SmalltalkHub. The package I > have modified is (Glamour-FastTable) > > How I can proceed, can I get access to the repository (my user is > pabloTesone)? or how I should publish the change? > > Thanks a lot. > > -- > Pablo Tesone. > tesonep(a)gmail.com > > > -- Pablo Tesone. tesonep(a)gmail.com

Oct. 11, 2016

Re: [Pharo-dev] Fixing a problem with FastTable Context Menus

by Esteban Lorenzano

now you have rights :) > On 11 Oct 2016, at 11:13, tesonep(a)gmail.com wrote: > > Hello, > I have fixed a problem in the FastTable's context menus, but I don't have access to the Moose/Glamour repository in SmalltalkHub. The package I have modified is (Glamour-FastTable) > > How I can proceed, can I get access to the repository (my user is pabloTesone)? or how I should publish the change? > > Thanks a lot. > > -- > Pablo Tesone. > tesonep(a)gmail.com <mailto:tesonep@gmail.com>

Oct. 11, 2016

Fixing a problem with FastTable Context Menus

by tesonep＠gmail.com

Hello, I have fixed a problem in the FastTable's context menus, but I don't have access to the Moose/Glamour repository in SmalltalkHub. The package I have modified is (Glamour-FastTable) How I can proceed, can I get access to the repository (my user is pabloTesone)? or how I should publish the change? Thanks a lot. -- Pablo Tesone. tesonep(a)gmail.com

Oct. 11, 2016

Re: [Pharo-dev] Shout style table editor (Request for Feedback)

by Guille Polito

Nice! <3 -------- Original Message -------- > Wow, that looks very nice ! > >> On 10 Oct 2016, at 18:42, Nicolai Hess <nicolaihess(a)gmail.com> wrote: >> >> I am working on a syntax style table editor, see issue for some background about this. >> 18322 Settings for Syntax Highlighting a bit confusing >> 15409 A more complete set of syntactic colors is needed >> >> >> Load package >> >> ST-StylingPreview >> ST-StylingPreviewShoutExtension >> >> from >> >> MCHttpRepository >> location: 'http://smalltalkhub.com/mc/NicolaiHess/StylerTableEditor/main' >> user: '' >> password: '' >> >> And open the preview/editor with: >> >> STStylerPreview open. >> >> This is a prototype, you can view builtin style tables, create and edit new custom style tables. >> This has some fake code styler methods to make the styling work for the >> code preview pane, and it supports more styling attributes than the default styler. >> >> This is what I would like to have as a syntax style setting dialog instead of the current >> confusing behavior. It may be helpful to actually see what syntax styling attributs are >> actually available. >> >> >> <PharoScreenshot.3.png> >

Oct. 11, 2016

Re: [Pharo-dev] Fwd: Call for design for a literal programming doc similar to PythonDocTest

by phil＠highoctane.be

Whatever would be better than what we have now. I like what you propose, makes sense and doesn't loads the UI with more stuff. I am willing to test your implementation for sure. Phil On Mon, Oct 10, 2016 at 6:56 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > ---------- Forwarded message ---------- > From: Nicolai Hess <nicolaihess(a)gmail.com> > Date: 2016-09-16 17:01 GMT+02:00 > Subject: Re: [Pharo-dev] Call for design for a literal programming doc > similar to PythonDocTest > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > > > 2016-09-16 0:19 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: > >> I'd be more interested with a package level doc than a class doc or test. >> >> Package level doc is quite useful to outline how some things are working >> together, something which is quite hard to figure out except by reading >> external doc or inferring things by walking through the code or a running >> test. >> > > > Why don't we have yet package comments ? > I see there is some support for it in PackageManifest, I remember there > was some work (people working) on support for Nautilus, no? > > maybe something like this, (see attached file) > Nautilus comment pane > on class selection -> show class comment > no class selection -> show package comment (class side #description of > package manifest of this package) > you can even add or change the (package) comment, it will compile a proper > #description method on the manifest class) > > > Anyone looked at this ? > Is this what we can use for supporting and editing package comments? I am > not sure if the > use of package manifests is how we wanted to implement package comments. > Any other ideas? > > I can open a fogbugzs issue and refine this implementation a little bit. > > > >> Having the ability to read about a package would be very useful. >> Basically, this is what Java provides. >> >> http://docs.oracle.com/javase/7/docs/technotes/tools/solaris >> /javadoc.html#packagecomment >> >> Phil >> >> >> On Thu, Sep 15, 2016 at 8:45 PM, stepharo <stepharo(a)free.fr> wrote: >> >>> Hi all >>> >>> I want something similar in the spirit to PythonDocTest >>> https://docs.python.org/2/library/doctest.html >>> >>> I'm talking about >>> >>> basename >>> "Returns the base of the basename, >>> i.e. >>> /foo/gloops.taz basename is 'gloops.taz' >>> / basename is '/'" >>> >>> Pragmas do not work well i.e., >>> basename >>> "Returns the base of the basename" >>> <expr: '''/foo/gloops.taz'' asFileReference basename' result: >>> 'gloops.taz'> >>> >>> >>> We should invent a syntax to be put inside comments and that we can >>> easily parse because we need to improve >>> the use and discovery of the library. >>> >>> I was thinking about >>> >>> basename >>> "Returns the base of the basename" >>> " >>> '/foo/gloops.taz' asFileReference basename >>> >>> 'gloops.taz' >>> " >>> >>> Do you have any idea? >>> >>> I cannot not do anything and just complain that our methods are not that >>> well documented. >>> We as a community should take this and build an super cool system. >>> >>> I tried and defined >>> on Object to see if it works! >>> >>> Object >>> aResultingObject >>> "If the method comment contains >>> then it is a pharo documentated >>> test. We can check that it is true." >>> >>> " >>> '/foo/gloops.taz' asFileReference basename >>> >>> 'gloops.taz' >>> " >>> >>> ^ self = aResultingObject >>> >>> >>> Stef >>> >>> >>> >> > >

Oct. 10, 2016

Re: [Pharo-dev] Shout style table editor (Request for Feedback)

by Sven Van Caekenberghe

Wow, that looks very nice ! > On 10 Oct 2016, at 18:42, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > I am working on a syntax style table editor, see issue for some background about this. > 18322 Settings for Syntax Highlighting a bit confusing > 15409 A more complete set of syntactic colors is needed > > > Load package > > ST-StylingPreview > ST-StylingPreviewShoutExtension > > from > > MCHttpRepository > location: 'http://smalltalkhub.com/mc/NicolaiHess/StylerTableEditor/main' > user: '' > password: '' > > And open the preview/editor with: > > STStylerPreview open. > > This is a prototype, you can view builtin style tables, create and edit new custom style tables. > This has some fake code styler methods to make the styling work for the > code preview pane, and it supports more styling attributes than the default styler. > > This is what I would like to have as a syntax style setting dialog instead of the current > confusing behavior. It may be helpful to actually see what syntax styling attributs are > actually available. > > > <PharoScreenshot.3.png>

Oct. 10, 2016

Fwd: Call for design for a literal programming doc similar to PythonDocTest

by Nicolai Hess

---------- Forwarded message ---------- From: Nicolai Hess <nicolaihess(a)gmail.com> Date: 2016-09-16 17:01 GMT+02:00 Subject: Re: [Pharo-dev] Call for design for a literal programming doc similar to PythonDocTest To: Pharo Development List <pharo-dev(a)lists.pharo.org> 2016-09-16 0:19 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: > I'd be more interested with a package level doc than a class doc or test. > > Package level doc is quite useful to outline how some things are working > together, something which is quite hard to figure out except by reading > external doc or inferring things by walking through the code or a running > test. > Why don't we have yet package comments ? I see there is some support for it in PackageManifest, I remember there was some work (people working) on support for Nautilus, no? maybe something like this, (see attached file) Nautilus comment pane on class selection -> show class comment no class selection -> show package comment (class side #description of package manifest of this package) you can even add or change the (package) comment, it will compile a proper #description method on the manifest class) Anyone looked at this ? Is this what we can use for supporting and editing package comments? I am not sure if the use of package manifests is how we wanted to implement package comments. Any other ideas? I can open a fogbugzs issue and refine this implementation a little bit. > Having the ability to read about a package would be very useful. > Basically, this is what Java provides. > > http://docs.oracle.com/javase/7/docs/technotes/tools/solaris > /javadoc.html#packagecomment > > Phil > > > On Thu, Sep 15, 2016 at 8:45 PM, stepharo <stepharo(a)free.fr> wrote: > >> Hi all >> >> I want something similar in the spirit to PythonDocTest >> https://docs.python.org/2/library/doctest.html >> >> I'm talking about >> >> basename >> "Returns the base of the basename, >> i.e. >> /foo/gloops.taz basename is 'gloops.taz' >> / basename is '/'" >> >> Pragmas do not work well i.e., >> basename >> "Returns the base of the basename" >> <expr: '''/foo/gloops.taz'' asFileReference basename' result: >> 'gloops.taz'> >> >> >> We should invent a syntax to be put inside comments and that we can >> easily parse because we need to improve >> the use and discovery of the library. >> >> I was thinking about >> >> basename >> "Returns the base of the basename" >> " >> '/foo/gloops.taz' asFileReference basename >> >>> 'gloops.taz' >> " >> >> Do you have any idea? >> >> I cannot not do anything and just complain that our methods are not that >> well documented. >> We as a community should take this and build an super cool system. >> >> I tried and defined >>> on Object to see if it works! >> >> Object >>> aResultingObject >> "If the method comment contains >>> then it is a pharo documentated >> test. We can check that it is true." >> >> " >> '/foo/gloops.taz' asFileReference basename >> >>> 'gloops.taz' >> " >> >> ^ self = aResultingObject >> >> >> Stef >> >> >> >

Oct. 10, 2016

Shout style table editor (Request for Feedback)

by Nicolai Hess

I am working on a syntax style table editor, see issue for some background about this. 18322 <https://pharo.fogbugz.com/f/cases/18322/Settings-for-Syntax-Highlighting-a-…> Settings for Syntax Highlighting a bit confusing 15409 <https://pharo.fogbugz.com/f/cases/15409/A-more-complete-set-of-syntactic-co…> A more complete set of syntactic colors is needed Load package ST-StylingPreview ST-StylingPreviewShoutExtension from MCHttpRepository location: 'http://smalltalkhub.com/mc/NicolaiHess/StylerTableEditor/main ' user: '' password: '' And open the preview/editor with: STStylerPreview open. This is a prototype, you can view builtin style tables, create and edit new custom style tables. This has some fake code styler methods to make the styling work for the code preview pane, and it supports more styling attributes than the default styler. This is what I would like to have as a syntax style setting dialog instead of the current confusing behavior. It may be helpful to actually see what syntax styling attributs are actually available.

Oct. 10, 2016

Re: [Pharo-dev] Pharo not working on Sierra OS

by Esteban Lorenzano

he has to copy it into /Applications because otherwise Sierra copy it into a sandbox (then it does not find sources). other problem, I did not noticed. Esteban > On 10 Oct 2016, at 18:06, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Hey Pharo vm developers (i.e. Esteban) we have one user who has problems. > > Though I guess we need more clarifications on how exactly it is "not working" > > Uko > > Sent from my iPhone > > Begin forwarded message: > >> From: Nevena Milojkovic <nevena(a)inf.unibe.ch <mailto:nevena@inf.unibe.ch>> >> Date: 10 October 2016 at 16:40:46 GMT+2 >> To: SCG staff <scg-staff(a)list.inf.unibe.ch <mailto:scg-staff@list.inf.unibe.ch>> >> Subject: [scg-staff] Pharo not working on Sierra OS >> >> Hi all, >> >> One of my students has problems with running Pharo on macOS Sierra. It is not working properly. >> >> Even the latest VM from today (https://dl.dropboxusercontent.com/u/7684634/pharo50-sierra-stable.zip <https://dl.dropboxusercontent.com/u/7684634/pharo50-sierra-stable.zip>) he says he can only open Nautilus. >> >> Any help? >> >> Cheers, >> Nevena >> >> >> >> >> >> >> >>

Oct. 10, 2016