September 2014 - Pharo-dev - lists.pharo.org

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

by kilon alios

ah yes I manage to load it successfully, I viewed the Gofer class comment, it seems it cant handle pillar tables , but still is really nice :) On Sun, Sep 7, 2014 at 6:07 PM, Ben Coman <btc(a)openinworld.com> wrote: > kilon alios wrote: > > yeaaaahhh thank you thank you thank you :) I always wanted documentation > inside Pharo you make my dream come true :) if I get latest moose 5 image > with pharolauncher will i also get this ? > > > > After using PharoLauncher to get the Moose 5.0 image, I presume you should > use the script from the humane-assessment link where it says... > "To get this behavior, load the following code" > cheers -ben > > > > On Sun, Sep 7, 2014 at 4:41 PM, Tudor Girba <tudor(a)tudorgirba.com> <tudor(a)tudorgirba.com> wrote: > > > > Hi, > > Documentation is important. To make it more likely and more enjoyable for > people to write more of it, I teamed up with Andrei and Jan to build up > support for Pillar in the GTInspector. > > The current solution brings the following: > - Pillar specific syntax highlighting including Shout highlighting for > code snippets > - Embedded files validation and preview possibility > - Quick browsing of Pillar book projects when inspecting the book folder > - Class comment rendering using Pillar syntax when inspecting the class > object > - Text editor support for custom highlighting in Glamour (using Rubric for > now) > - Island parsing for quick specification of incomplete parser > > You can learn more about it here: > http://www.humane-assessment.com/blog/writing-pillar-books-with-the-gtinspe… > > [image: Inline image 1] > > There is much more to do in this direction, and I would be happy to > inspire some of you to join forces. Please let us know what you think. > > Cheers, > Doru > > --www.tudorgirba.com > > "Every thing has its own flow" > > > > >

Sept. 7, 2014

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

by Ben Coman

Sept. 7, 2014

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

by Ben Coman

Sept. 7, 2014

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

by kilon alios

yeaaaahhh thank you thank you thank you :) I always wanted documentation inside Pharo you make my dream come true :) if I get latest moose 5 image with pharolauncher will i also get this ? On Sun, Sep 7, 2014 at 4:41 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Documentation is important. To make it more likely and more enjoyable for > people to write more of it, I teamed up with Andrei and Jan to build up > support for Pillar in the GTInspector. > > The current solution brings the following: > - Pillar specific syntax highlighting including Shout highlighting for > code snippets > - Embedded files validation and preview possibility > - Quick browsing of Pillar book projects when inspecting the book folder > - Class comment rendering using Pillar syntax when inspecting the class > object > - Text editor support for custom highlighting in Glamour (using Rubric for > now) > - Island parsing for quick specification of incomplete parser > > You can learn more about it here: > > http://www.humane-assessment.com/blog/writing-pillar-books-with-the-gtinspe… > > [image: Inline image 1] > > There is much more to do in this direction, and I would be happy to > inspire some of you to join forces. Please let us know what you think. > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Sept. 7, 2014

[ann] pillar support in gtinspector

by Tudor Girba

Hi, Documentation is important. To make it more likely and more enjoyable for people to write more of it, I teamed up with Andrei and Jan to build up support for Pillar in the GTInspector. The current solution brings the following: - Pillar specific syntax highlighting including Shout highlighting for code snippets - Embedded files validation and preview possibility - Quick browsing of Pillar book projects when inspecting the book folder - Class comment rendering using Pillar syntax when inspecting the class object - Text editor support for custom highlighting in Glamour (using Rubric for now) - Island parsing for quick specification of incomplete parser You can learn more about it here: http://www.humane-assessment.com/blog/writing-pillar-books-with-the-gtinspe… [image: Inline image 1] There is much more to do in this direction, and I would be happy to inspire some of you to join forces. Please let us know what you think. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Sept. 7, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40211 Home: https://github.com/pharo-project/pharo-core

Sept. 7, 2014

[pharo-project/pharo-core] bf634e: 40211

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: bf634e701e124c3dc43d8dafc9915ede47626b11 https://github.com/pharo-project/pharo-core/commit/bf634e701e124c3dc43d8daf… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-07 (Sun, 07 Sep 2014) Changed paths: A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script211.st M ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40209.st M ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40210.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40211.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-MorphicAdapters.package/MorphicListAdapter.class/instance/widget API/menu_shifted_.st Log Message: ----------- 40211 13974 creating menus for ListModels is broken https://pharo.fogbugz.com/default.asp?13974 http://files.pharo.org/image/40/40211.zip

Sept. 7, 2014

Trying to scale and reposition the progress bar for PharoLauncher

by kilon alios

Hello pharoers it has been almost a year since the last time I commited to PharoLauncher so I decided to go for it once again. The first time I added a progress bar for people to see the progress of the download of the image . Now I want to scale and reposition the progress bar as I am not happy at all in the way it looks , its too small and hard to read. So I created a question at stackoverflow with all the details of my problem http://stackoverflow.com/questions/25708970/trying-to-find-the-progressbar-… I would not mind also some extra details on how I can fetch the Morphs used by UIManager or to even further customise UIManager. I tried to find the answer myself but after an hour of staring at the Pharo system browser I gave up.

Sept. 7, 2014

Re: [Pharo-dev] what were the changes to announcement?

by stepharo

Hi marcus and camille >> >> I tried to identify the changes in announcer byt comparing two images >> but I could not get it. >> Could you let me know what you change? > > Method announcements were not in a hierarchy and had duplicated APIs. > I made a hierarchy and removed a lot of useless ivs in each: protocol, > methodClass, selector (most of the time it can be retrieved from the > method). It permitted me to reduce the number of arguments needed and > remove many useless methods (see protocol triggering of > SystemAnnouncer). Senders of these triggering methods become a bit > simpler (usually big methods). Nice :) Thanks for the info. > BTW, for system announcements we discussed that all: > SystemAnnouncer uniqueInstance when: AnAnnouncement send: #something: > to: self > could be rewritten: > AnAnnouncement send: #something: to: self > well maybe with another name... > Announcements would just need to implement #announcer. > Ok I see now :)

Sept. 6, 2014

Re: [Pharo-dev] what were the changes to announcement?

by Camille Teruel

On 6 sept. 2014, at 14:15, stepharo <stepharo(a)free.fr> wrote: > Hi marcus and camille > > I tried to identify the changes in announcer byt comparing two images but I could not get it. > Could you let me know what you change? Method announcements were not in a hierarchy and had duplicated APIs. I made a hierarchy and removed a lot of useless ivs in each: protocol, methodClass, selector (most of the time it can be retrieved from the method). It permitted me to reduce the number of arguments needed and remove many useless methods (see protocol triggering of SystemAnnouncer). Senders of these triggering methods become a bit simpler (usually big methods). BTW, for system announcements we discussed that all: SystemAnnouncer uniqueInstance when: AnAnnouncement send: #something: to: self could be rewritten: AnAnnouncement send: #something: to: self well maybe with another name... Announcements would just need to implement #announcer. Camille > > Stef >

Sept. 6, 2014