May 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pillar 0.56 : New features, new syntax

by Norbert Hartl

Cyril, > Am 22.05.2015 um 23:12 schrieb Cyril Ferlicot <cyril.ferlicot(a)gmail.com>: > > The second main change is the Internal Links. > Now when you want to reefer to an anchor, a figure or a script you'll > need to use *@anchor* instead of *anchor*. > I'm sorry for that but that's the easiest way to implement the > inter-files links. why @? It is about links and how to point to a fragment inside a resource. This already exists and is called fragment identifier http://en.wikipedia.org/wiki/Fragment_identifier <http://en.wikipedia.org/wiki/Fragment_identifier> You do it by using # the separate the resource and the fragment in an URI. '../chapters/chapter1.pillar#section1' is complete valid URI and the way to go. Can you change that? Norbert

May 23, 2015

Re: [Pharo-dev] Main pillar web site?

by H. Hirzel

Hello Cyril I just saw your announcement about Pillar 0.56 : New features, new syntax My suggestion is to the main pillar web site the information which version of Pillar you describe there? https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… And that you post the news about updates somewhere and refer to them from the main pillar documentation website. --Hannes On 5/18/15, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > Luc, > > Thanks for the nice diagram showing Pillar in action. > > I suggest to include it on the pillar web site. > > And maybe you have some additional documentation. For example about the > parser. > > --Hannes > > On 5/18/15, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: >> Hi all, >> >> As a teacher, I wrote a little Lab subject to introduce the Visitor >> design >> pattern to students using Pillar. >> And I used the following fig to describe it. >> >> HIH, >> >> #Luc >> >> 2015-05-18 20:16 GMT+02:00 H. Hirzel <hannes.hirzel(a)gmail.com>: >> >>> Thank you. >>> >>> Is it possible to add a short paragraph about the >>> >>> Rational >>> >>> for Pillar? >>> >>> It seems to be a text format for the PRnnn classes which is easy to >>> parse. >>> >>> Which formats does the Pillar documentation tool chain read and which >>> ones are generated? >>> >>> --Hannes >>> >>> On 5/4/15, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: >>> > Hi. >>> > The documentation is now here: >>> > >>> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >>> > >>> > We're still updating the documentation so that still can change. >>> > >>> > On 4 May 2015 at 16:14, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>> >> Thank you! >>> >> >>> >> Here is the summary >>> >> >>> >> >>> >> >>> >> Pillar documentation >>> >> ==================== >>> >> >>> >> Start page >>> >> http://www.smalltalkhub.com/#!/~Pier/Pillar >>> >> >>> >> >>> >> Documentation >>> >> https://github.com/pillar-markup/pillar-documentation >>> >> >>> >> >>> >> >>> >> First Google hit >>> >> >>> https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/HTML_Report/… >>> >> >>> >> Leads to Pharo contribution CI server (Confirm security exception, >>> >> it >>> is >>> >> safe). >>> >> >>> >> >>> >> >>> >> Pillar tool chain repositories >>> >> ------------------------------- >>> >> >>> >> https://github.com/pillar-markup >>> >> >>> > >>> > >>> > >>> > -- >>> > Cheers >>> > Cyril Ferlicot >>> > >>> > >>> >>> >> >

May 23, 2015

Re: [Pharo-dev] Cross platform key modifiers

by Nicolai Hess

Hi ben, 2015-05-22 17:28 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > Not sure what past history we inherited, but I am questioning the > semantics of our key modifiers. My understanding is that the following is > industry standard... > OSX Windows Linux > option alt alt > cmd ctrl ctrl > Yes, this is what I expected too. And I thought this is for what KMCommandModifier is used for. With that, I would expect "Character arrowLeft command" maps to Ctrl+Left for windows/linux Meta+Left for Mac (If Meta is the Command-Key on a Mac keyboard). > > with Copy being the simplest example of this... > cmd-c ctrl-c ctrl-c > > Supporting this view: > * "option" and "alternative" are synonyms > * "command" and "control" have similar meaning (e.g. in the army if you > command someone, you control them) > * Microsoft say so (https://support.microsoft.com/en-us/kb/970299) > * Apple say so (https://support.apple.com/kb/PH18812?locale=en_US) and > indeed marks its keyboards with "alt" and "option" on the same key ( > http://www.apple.com/au/keyboard/) > > So examining this with > KMLog setDebug.Transcript open. > > On OSX Pharo 50044 I get... > option+arrowLeft --> [keystroke '<Opt-left>'] > cmd+arrowLeft --> [keystroke '<Cmd-left>'] > ctrl+arrowLeft --> OS changes screens > > but I am told that Windows gives... > alt+arrowLeft --> [keystroke '<Cmd-left>'] > ctrl+arrowLeft --> [keystroke '<Ctrl-left>'] > > when I believe Windows should be... > alt+arrowLeft --> [keystroke '<Opt-left>'] > ctrl+arrowLeft --> [keystroke '<Cmd-left>'] > > > Part of the issue I think is that our keystroke mapping should be more > abstract. > > When I was using Pharo on Windows, sometimes it felt like a second class > citizen wrt key mappings, mapping ctrl-c to an apple-named <cmd-c>. > Perhaps what we should see is: > > OSX... > option+arrowLeft --> [keystroke '<Meta-left>'] > cmd+arrowLeft --> [keystroke '<Hotkey-left>'] > > Windows... > alt+arrowLeft --> [keystroke '<Meta-left>'] > ctrl+arrowLeft --> [keystroke '<Hotkey-left>'] > > Otherwise there will always be the tension on windows that ctrl-c should > generate [<keystroke '<Ctrl-c>] and we end up with definitions repetitively > formed like... > PharoShortcuts>>acceptShortcut > ^ $s ctrl win | $s ctrl unix | $s command mac > > which opens the door for inconsistencies. We should only need to do > something like... > PharoShortcuts>>acceptShortcut > ^ $s hotkey > Isn't OSXs Command-key like MS-Windows "Window" or Linux "Meta" -key? > > and leave it to the platform default or user preference the define what > the hotkey actually is. A status line in the Keymap Browser could display > which actual real keys map to <Hotkey> and <Meta>. > > > What are you thoughts? > cheers -ben > >

May 22, 2015

Fwd: FogBugz (Case [Issue]13315) Morphic - NewList without icons

by Nicolai Hess

Is there some more information about this? I opened that issue and I asks quesions about the NewList implementation on the mailing list and commented on some other issues about NewList (for example 13554 <https://pharo.fogbugz.com/default.asp?13554> Red cross in EyeDateAndTimeInspector). (With not so much feedback). And making NewListRender working with athens caused quite some headache to me. But this is the first time I hear someone is working on a new list. I would like to encourage people to make more comments on the bugtracker. And, as we have already quite some mess in our widget libraries, because we have all kinds of list/tree-morph-nomorph-pluggable-or-simple-with-or-without-icons-things, I would like some more discussion/background info about this. Especially how we prevent to not have "just-another-list" in the image, but a way/plan to migrate or exchange the current list class to use the new/better one. thanks nicolai ---------- Forwarded message ---------- From: Pharo Issue Tracker <do-not-reply(a)pharo.fogbugz.com> Date: 2015-05-22 11:23 GMT+02:00 Subject: FogBugz (Case [Issue]13315) Morphic - NewList without icons To: "nicolaihess(a)web.de" <nicolaihess(a)web.de> [image: avatar] *Marcus Denker* resolved *Case 13315*: NewList without icons <https://pharo.fogbugz.com/default.asp?13315> and assigned it to you: *Bug* in [image: Project:] Morphic: 1. Pharo Image We have a better list done by esteban soon *Status* changed: Work Needed [image: changed to] Resolved (Invalid) *Assigned To* changed: Everyone [image: changed to] Nicolai Hess [image: Priority] *Priority*: 3 â Must Fix [image: Status] *Status*: Resolved (Invalid) [image: Assigned To] *Assigned to*: Nicolai Hess [image: Milestone] *Milestone*: Pharo5.0 Go to Case <https://pharo.fogbugz.com/default.asp?13315> Don't want FogBugz notifications anymore? Update your preferences. <https://pharo.fogbugz.com/f/userPrefs> [image: FogBugz] A case which you opened has been resolved ( Resolved (Invalid) ) by Marcus Denker in FogBugz. It is your responsibility to verify the resolution and close or reactivate the case. Case ID: 13315 Title: NewList without icons Status: Resolved (Invalid) Category: Bug Project: Morphic Area: 1. Pharo Image Priority: 3 - Must Fix Milestone: Pharo5.0: 4/1/2016 Assigned To: Nicolai Hess URL: https://pharo.fogbugz.com/default.asp?13315 Changes: Status changed from 'Work Needed' to 'Resolved (Invalid)'. Last message: We have a better list done by esteban soon If you do not want to receive automatic notifications anymore, change your preferences in the Options screen. (https://pharo.fogbugz.com/f/userPrefs)

May 22, 2015

Pillar 0.56 : New features, new syntax

by Cyril Ferlicot

Hello, today I created the version 0.56 of Pillar and with this version we'll need to do some changes, sorry. The first change is the numerator. The old numerator was too limited, so i changed it. Now if you put different files into the pillar.conf the numerator will not be reset at each files. The parameters 'startNumberingAtHeaderLevel:' and 'stopNumberingAtHeaderLevel:' are replace by 'level1:', 'level2:', 'level3:', 'level4:', 'level5:'. For now they can take 3 sub-parameters: 'numbering', 'size' and 'renderAs'. numbering: a boolean that say if this header level need to be take in account by the numerator. size: the number of level we want to render. You can put numbering at true and size at 0 if you want your numerator to be reset at a level without rendering the number of this level. renderAs: can be number, roman, letter or upperLetter. Example: pillar.conf: { 'level1': { 'numbering': true, 'size': 1, 'renderAs': 'roman' }, 'level2': { 'numbering': true, 'size': 2, 'renderAs': 'number' }, 'level3': { 'numbering': true, 'size': 1, 'renderAs': 'upperLetter' }, 'level4': { 'numbering': true, 'size': 2, 'renderAs': letter }, 'level5': { 'numbering': false }, } document.pillar: ! Example !! Introduction !!! Beginning !!! Example - Intro !!!! Example 1 !!!! Example 2 !!!!! With X !!!!! With Y !! Explanation Result: I. Example I.1. Introduction A. Beginning B. Example - Intro B.a. Example 1 B.b. Example 2 With X With Y I.2. Explanation In the future we could also add feature like 'delimiter'. The second main change is the Internal Links. Now when you want to reefer to an anchor, a figure or a script you'll need to use *@anchor* instead of *anchor*. I'm sorry for that but that's the easiest way to implement the inter-files links. And so the last main change is the Inter-files links ! Imagine you're writing a book. You have a directory 'Chapter1' which contains the file 'chapter1.pillar' and a directory 'Chapter2' with a file 'chapter2.pillar'. If you want to make a reference to the chapter 1 in the chapter 2 you can create an interfile link you can now use the syntax: *../Chapter1/chapter1.pillar* But be careful ! Remember that pillar can export in different format. And you can export a group of file as separate output files or as one file. So if you don't use an Alias your link will not be render if you export as one output file in LaTeX. And if you export in LaTeX or HTML or Markdown as one output file and you don't have an anchor on your link, the link will be vanish. So I recommend to use inter file links like this: *Chapter 1>../Chapter1/chapter1.pillar@cha:chapter1* when cha:chapter1 is an anchor you need to create at the beginning of the chapter 1. I already changed the links on Enterprise Pharo (you can find a table with the list of the inter-files links on the README.md) On last thing for the people who write book for SquareBracketAssociates: It would be good to have some conventions, so if you create anchors use this form : @sec:nameOfSection for a section @cha:nameOfTheChapter for a title of chapter @fig:nameOfFigure for a figure @spt:nameOfTheScript for a script -- Cheers Cyril Ferlicot

May 22, 2015

Re: [Pharo-dev] [Reflectivity] Progress for Breakpoints

by stepharo

Marcus with franck and alain we worked on using Rubric instead of pluggableTextMorph in Nautilus. so you will be able to display icons or other for the breakpoints. Stef Le 22/5/15 11:53, Marcus Denker a Ã©crit : >>> >>> https://pharo.fogbugz.com/f/cases/15516/add-suggestion-for-breakpoint >>> >>> this is of course completely untestedâ¦ it works only when there is >>> no unaccepted >>> text in the editor and maybe only within Nautilus. >>> >>> And of course existing breakpoints are not yet in any form >>> visualised in the editor. >> >> This is in 50041. Please use with careâ¦ still needs work to be really >> usable. >> > > I now finished to add everything from Claraâs original > SmartBreakpoints project. > > There are still lots of things that need to be done > > -> Something goes wrong when re-adding a one-shot breakpoint again. > -> Adding should be disabled when the editor has non-submitted code. > -> The experience in the debugger is not that nice > (need to think about using the <debuggerCompleteToSender> trick and > explore the filtering capabilities of the debugger) > > I am now continuing to flesh out the Reflectivity features: > > -> hook AST generation is now done by HookGenerator > -> correct hooks are already generated for the case that a link passes > arguments to the meta object (see the RFReification hierarchy, for now > we have only #object *and* actual compiling does not yet work due > to missing > semantic analysis of the AST snippets for the hooks) > -> We have support for âvirtualâ meta objects. Any valid reification > can be the metaObject > (this is fun for #node). > > TODO > - add all reifications for all nodes (#arguments, #node, #context, > #value #name, #arg1â¦) > - do semantic analysis correctly and add test for links with arguments > - add conditions with parameters (e.g. for object specific links: > [:object | object == myObject]) > - handle primitives: when putting a link on a primitive method, wrap > the compiledMethod instead > of AST manipulation. > - â¦. > > I will continue to flesh it out and send examples to the list as these > things start to work for real. > > > Marcus >

May 22, 2015

Re: [Pharo-dev] Opportunity to steal good ideas from dad ;)

by stepharo

http://www.smalltalkhub.com/#!/~emaringolo/SortFunctions I use them extensively. Esteban A. Maringolo > I had a look. > > Apart from the fact that for some reason, the extensions on MAElement are in the Core package, hence loading just Core gave errors, things looked OK. > > This is generally useful, small and a very good example of super cool OO design. > > I would vote to integrate this (<=> and all). Why? Can we rewrite a large part of the system with it? If not why people cannot just load a package? We should stop to think monolithic. Stef

May 22, 2015

Re: [Pharo-dev] Opportunity to steal good ideas from dad ;)

by stepharo

What is <=> because I found it quite not intention revealing. Le 22/5/15 11:19, phil(a)highoctane.be a Ã©crit : > Thinking of the <=> operator, this can be useful for things like this: > > dataset := #(1 3 4 5 7 8 5 2 3 0). > mean := dataset average. > dataset collect: [ :each | mean <=> each ] > > --> #(1 1 -1 -1 -1 -1 -1 1 1 1) > > This we can also do with > > coll := #(1 3 4 5 7 8 5 2 3 0). > mean := coll average. > coll collect: [ :each | (mean - each) sign ] > > but still. > > Other use cases for <=> ? > > Phil > > > On Fri, May 22, 2015 at 11:43 AM, Sven Van Caekenberghe <sven(a)stfx.eu > <mailto:sven@stfx.eu>> wrote: > > > > On 21 May 2015, at 16:50, Esteban A. Maringolo > <emaringolo(a)gmail.com <mailto:emaringolo@gmail.com>> wrote: > > > > 2015-05-21 10:01 GMT-03:00 phil(a)highoctane.be > <mailto:phil@highoctane.be> <phil(a)highoctane.be > <mailto:phil@highoctane.be>>: > >> > >> > >> On Thu, May 21, 2015 at 2:19 PM, Sean P. DeNigris > <sean(a)clipperadams.com <mailto:sean@clipperadams.com>> > >> wrote: > >>> > >>> Squeak 4.6 "Spur" Release Notes > >>> http://wiki.squeak.org/squeak/6192 > >> > >> > >> Tag sort functions looks great to have around. > >> > >> About the spaceship operator (<=>), is this something we'd > like to have > >> around? (I like it). > http://en.wikipedia.org/wiki/Three-way_comparison > > > > http://www.smalltalkhub.com/#!/~emaringolo/SortFunctions > <http://www.smalltalkhub.com/#%21/%7Eemaringolo/SortFunctions> > > > > I use them extensively. > > > > Esteban A. Maringolo > > I had a look. > > Apart from the fact that for some reason, the extensions on > MAElement are in the Core package, hence loading just Core gave > errors, things looked OK. > > This is generally useful, small and a very good example of super > cool OO design. > > I would vote to integrate this (<=> and all). > > Sven > > > > >

May 22, 2015

Re: [Pharo-dev] Format shortcut.

by Damien Cassou

Cyril Ferlicot <cyril.ferlicot(a)gmail.com> writes: > I propose to keep ctrl + shift + f (like in Eclipse). makes sense -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

May 22, 2015

[pharo-project/pharo-core]

by GitHub

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

May 22, 2015