- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] b1b738: 50715

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: b1b738b40653feebd993cef3f84c9f4556aca695 https://github.com/pharo-project/pharo-core/commit/b1b738b40653feebd993cef3… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-04-26 (Tue, 26 Apr 2016) Changed paths: M BlueInk-Extras.package/BIInspector.class/class/settings/settingsOn_.st M ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/symbolic versions/stable_.st A ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/versions/version2193_.st M ConfigurationOfVersionner.package/ConfigurationOfVersionner.class/instance/symbolic versions/stable_.st A ConfigurationOfVersionner.package/ConfigurationOfVersionner.class/instance/versions/version21312_.st M DebuggerModel.package/DebugSystemSettings.class/class/settings/debugSettingsOn_.st M FreeType.package/FreeTypeSystemSettings.class/class/settings/freeTypeSettingsOn_.st M Monticello.package/MCFileBasedRepository.class/class/settings/monticelloSettingsOn_.st M Morphic-Base.package/ShortcutReminder.class/class/settings/settingsOn_.st M Morphic-Base.package/SystemProgressMorph.class/class/settings/settingOn_.st R NodeNavigation.package/NNavNavigation.class/class/configuration/enableAstHighlightSetting_.st M OpalCompiler-Core.package/AbstractCompiler.class/class/settings/compilerSettingsOn_.st M Rubric.package/RubAbstractTextArea.class/class/settings/rubricSettingsOn_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50714.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50715.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50714.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50715.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Settings-Polymorph.package/PolymorphSystemSettings.class/class/morphic/morphicAnimationSettingsOn_.st M Settings-Polymorph.package/PolymorphSystemSettings.class/class/morphic/morphicMenuSettingsOn_.st M Settings-Polymorph.package/PolymorphSystemSettings.class/class/morphic/morphicSettingsOn_.st M Settings-Polymorph.package/PolymorphSystemSettings.class/class/morphic/morphicWindowsSettingsOn_.st M Settings-System.package/SystemSystemSettings.class/class/settings/systemSettingOn_.st M Text-Diff.package/TextDiffBuilder.class/class/settings/differatorSettingsOn_.st M Text-Edition.package/Editor.class/class/settings/editingSettingsOn_.st M Tool-Finder.package/DialogItemsChooserUI.class/class/settings/dialogItemsChooserSettingsOn_.st M UIManager.package/CommandLineUIManager.class/class/settings/uiSettingsOn_.st M Versionner-Spec-Browser.package/VersionnerSpecBrowser.class/class/settings/settingsOn_.st A WorldMenuHelp.package/WorldMenuHelp.class/README.md A WorldMenuHelp.package/WorldMenuHelp.class/class/as yet unclassified/bookName.st A WorldMenuHelp.package/WorldMenuHelp.class/class/as yet unclassified/overview.st A WorldMenuHelp.package/WorldMenuHelp.class/class/as yet unclassified/pages.st A WorldMenuHelp.package/WorldMenuHelp.class/definition.st Log Message: ----------- 50715 18080 New Help about adding World Menu Items https://pharo.fogbugz.com/f/cases/18080 18091 Comment some existing settings https://pharo.fogbugz.com/f/cases/18091 18089 Update Rubric 2.19.3 https://pharo.fogbugz.com/f/cases/18089 18090 Update Versionner 2.13.12 https://pharo.fogbugz.com/f/cases/18090 http://files.pharo.org/image/50/50715.zip

April 26, 2016

Re: [Pharo-dev] [Pharo 5] Some feedbacks

by Stephan Eggermont

On 25-04-16 12:16, Hilaire wrote: > While giving a try to Pharo5, I wrote some notes about how it fells. > It may be useful to share it. Of course it is also very opinionated and > may be rude. But no offense to consider, really. Thanks for the detailed feedback. Stephan

April 26, 2016

[pharo-project/pharo-core]

by GitHub

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

April 26, 2016

[pharo-project/pharo-core] 690d4c: 50714

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 690d4c587a8380a4489d030e3ed9f1796672b1f8 https://github.com/pharo-project/pharo-core/commit/690d4c587a8380a4489d030e… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-04-26 (Tue, 26 Apr 2016) Changed paths: M BlueInk-Core.package/BIPrettyPrinterContext.class/instance/initialization/initialize.st M ContributingToTheCatalogHelp.package/ContributingToTheCatalogHelp.class/class/accessing/bookName.st M HowToContributeHelp.package/HowToContributeHelp.class/class/accessing/bookName.st M OpalCompiler-Core.package/OCASTSemanticAnalyzer.class/instance/error handling/storeIntoReadOnlyVariable_.st M OpalCompiler-Core.package/OCASTSemanticAnalyzer.class/instance/error handling/storeIntoSpecialVariable_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50713.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50714.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50713.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50714.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Shout.package/SHRBTextStyler.class/instance/visiting/visitAssignmentNode_.st Log Message: ----------- 50714 18070 Syntax error: Cannot store into https://pharo.fogbugz.com/f/cases/18070 18082 Shorter help items https://pharo.fogbugz.com/f/cases/18082 18065 BIPrettyPrinterContext undeclared var in #initialize https://pharo.fogbugz.com/f/cases/18065 http://files.pharo.org/image/50/50714.zip

April 26, 2016

Please add me to the smalltalkhub Pharo group

by Alistair Grant

Hi, I have a proposed enhancement to the CatalogBrowser that I would like to submit via fogbugz. I'm following Stephan Eggermont's video which states: "Ask to be added to the smalltalkhub Pharo group on the mailing list" Is this the right place to make the request (and please add me)? Thanks, Alistair

April 25, 2016

Re: [Pharo-dev] [Pharo 5] Some feedbacks

by Peter UhnÃ¡k

> > I think it is more a question of usability based on the average wished > font size. So all in all the choice of font size can be done objectively > although font size wish is subjective. > Yes, that's why it is configurable. > > Some people will want 9, other 14 or 16. The average is likely in between. > It was 9 since at least Pharo 3, so I am not sure what's the complaint about, considering people were ok with the size for several years (so I am inferring 9/10 should be good for everyone). > > > > > >> Line numbers: where is it used, not in the system browser > > > > This is disabled by default, so it shouldn't be a problem. > > UI noise, but not a big deal. > Considering the L+ and W are literally the smallest elements in the UI I'd hardly call it noise; but this is subjective. > > >> Nautilis: where is the local senders tools? > > > > You need to scope your view (top left corner button "Scoped") > > Oh great to know what does "Scoped". > The tooltips of the "Scoped" button is therefore not helping as there is > no useful information: "Browse scoped the selected packages" > One can check at Dr. Geo what useful tips mean: Most of its tools come > with 3 or even 4 lines tips (see screenshot example) > > I guess professional software company have people to review it all. > A company that cares about first-time users. Once you know what it does, the current tooltip is often completely obvious. And since we don't really have much first-time users that would be willing to share (as often they are overwhelmed by so much different stuff) it can be quite difficult to improve. So if you can propose better tooltips (since you are a pair of fresh eyes), then it would be valuable for new users. > > > >> Spotter > > Why Ctrl+[->]? my intuition tells me [->] as indicated by the blue icon > > arrow, please fix it! > > > > Because -> and <- is already taken. Pretty much any shortcut in the > > system has ctrl/alt/command in it, so I don't see why this only thing in > > the entire system should be different. You can also hover over the > > button to see the shortcut. > > Indeed <- and -> is used to edit the text search but keyboard focus can > open the use of <- -> for navigation. Not being able to use -> is > counter intuitive. > > > Not to mention that you have two different right arrows (ctrl+right, > > ctrl+shift+right), so just because you immediately see one use case > > doesn't mean that it's the only one/best one. There was A LOT of > > discussion on the mailing list regarding Spotter's usability and > shortcuts. > > It is inconsistent: why no need of Ctrl for up and down, but a need for > it for left and right. > Because horizontal navigation in such a way is the same everywhere. But with control you are taking different action. But point above about new/accustomed users holds here as well. > > > > >> Playground > > Why Ctrl+shift+g to open a pane, looks like Ctrl+g is working. > > Nevertheless Ctrl+g is not very handy short cut, it hurts the fingers! > > Can it be changed? > > > > Because it's not the same. do-it-all-and-go (ctrl+shift+g) executes all > > the code and inspects it in the next pane, while ctrl+g (do-it-and-go) > > just the selected block/current line. > > ok. But Ctrl+g is really really not fingers friendly for a short cut you > will use very often. See screenshot, there is so much tension in the > three fingers when doing it. It is torture and I can tell you my hands > are large celtic ones. I guess you need two hands to use comfortably > this shortcut. > Interesting, I press the control with my thumb. As a proper touch-type user I should actually use the opposite shift than the key is on (so right shfit for G, left shift for H, etc.)â¦ I don't know why I type it with one hand. The default meta key on linux is ctrl, so such hand-braking shortcuts are not so uncommon (ctrl+shift+Debug, ctrl+shift+Format). Peter

April 25, 2016

Re: [Pharo-dev] XMLParser changes

by monty

+1 > Sent: Monday, April 25, 2016 at 6:23 AM > From: "Jan Vrany" <jan.vrany(a)fit.cvut.cz> > To: pharo-dev(a)lists.pharo.org > Subject: Re: [Pharo-dev] XMLParser changes > > Not sure whether this was an intention. but strictly speaking,Â > new behavior is correct.Â > See Extensible Markup Language (XML) 1.0 (Fifth Edition),Â > SectionÂ 2.10 White Space Handling: > > "An XML processor must always pass all characters in a document that > are not markup through to the application. A validating XML processor > must also inform the application which of these characters constitute > white space appearing in element content." > > Jan > > > > On Mon, 2016-04-25 at 12:14 +0200, Cyril Ferlicot Delbecque wrote: > > Hi, > > > > last week there was a new stable version of XMLParser and some tests > > broke in some tools. I think that there was a regression in this > > version. > > > > Snippet: > > > > (XMLDOMParser parse: '<?xml version="1.0" encoding="UTF-8"?> > >  > > <Clones> > > Â Â Â Â <ClonedFragment cloneName="test"> > > Â Â Â Â Â Â Â Â <Member fileName="ProgramA"/> > > Â Â Â Â Â Â Â Â <Member fileName="ProgramB"/> > > Â Â Â Â </ClonedFragment> > > Â Â Â Â <ClonedFragment cloneName="test2"> > > Â Â Â Â Â Â Â Â <Member fileName="ProgramA"/> > > Â Â Â Â Â Â Â Â <Member fileName="ProgramB"/> > > Â Â Â Â </ClonedFragment> > > </Clones>') elements first nodes > > > > With the release 2.7.4 we get 2 nodes but in release 2.7.6 we get 5 > > nodes. The 2 previous ones and 3 empty String nodes. > > > > I think this is not what we expect. Correct me if I am wrong :) > > > > > >

April 25, 2016

Re: [Pharo-dev] [Pharo 5] Some feedbacks

by Hilaire

Le 25/04/2016 13:58, Peter UhnÃ¡k a Ã©crit : > Some comments > >> Font size is ridiculous! Make it at minimum 12 for the permanent > visual elements > > This is subjectiveâ¦ I am even considering making the size smaller for > myself (after all, in Pharo 4 it was size 9). I think it is more a question of usability based on the average wished font size. So all in all the choice of font size can be done objectively although font size wish is subjective. Some people will want 9, other 14 or 16. The average is likely in between. > >> Line numbers: where is it used, not in the system browser > > This is disabled by default, so it shouldn't be a problem. UI noise, but not a big deal. > >> "Format as you read" -> what is tooltips good for? > > This is autoformatting without the need to reformat the code yourself, > very useful if you are reading some old/unformatted codebase. > > For example open Morph>>acceptDroppingMorph:event: and click on the > button â it will reformat the code without changing the code itself. => Tooltips needed. >> AST navigation: what is it? I don't understand its description. What > nodes? > > Do we really need a block of text of description for everything? If you > know what AST is then it is pretty self-explanatory. If you don't know > what AST is then the option has no value for you, because the navigation > would be random. > >> Nautilis: where is the local senders tools? > > You need to scope your view (top left corner button "Scoped") Oh great to know what does "Scoped". The tooltips of the "Scoped" button is therefore not helping as there is no useful information: "Browse scoped the selected packages" One can check at Dr. Geo what useful tips mean: Most of its tools come with 3 or even 4 lines tips (see screenshot example) When people add UI element, great care is need in the description. I guess professional software company have people to review it all. >> Spotter > Why Ctrl+[->]? my intuition tells me [->] as indicated by the blue icon > arrow, please fix it! > > Because -> and <- is already taken. Pretty much any shortcut in the > system has ctrl/alt/command in it, so I don't see why this only thing in > the entire system should be different. You can also hover over the > button to see the shortcut. Indeed <- and -> is used to edit the text search but keyboard focus can open the use of <- -> for navigation. Not being able to use -> is counter intuitive. > Not to mention that you have two different right arrows (ctrl+right, > ctrl+shift+right), so just because you immediately see one use case > doesn't mean that it's the only one/best one. There was A LOT of > discussion on the mailing list regarding Spotter's usability and shortcuts. It is inconsistent: why no need of Ctrl for up and down, but a need for it for left and right. > >> Playground > Why Ctrl+shift+g to open a pane, looks like Ctrl+g is working. > Nevertheless Ctrl+g is not very handy short cut, it hurts the fingers! > Can it be changed? > > Because it's not the same. do-it-all-and-go (ctrl+shift+g) executes all > the code and inspects it in the next pane, while ctrl+g (do-it-and-go) > just the selected block/current line. ok. But Ctrl+g is really really not fingers friendly for a short cut you will use very often. See screenshot, there is so much tension in the three fingers when doing it. It is torture and I can tell you my hands are large celtic ones. I guess you need two hands to use comfortably this shortcut. Hilaire -- Dr. Geo http://drgeo.eu

April 25, 2016

Re: [Pharo-dev] XMLParser changes

by monty

All preservesIgnorableWhitespace: does now is preserve whitespace as string nodes in elements of type element content as indicated by a DTD with ELEMENT declarations that restricts their content to elements. That's why toggling the setting didn't do anything for you when you parsed a doc with no DTD and ELEMENT declarations (I will adapt the #ignorableWhitespace: comment for #preservesIgnorableWhitespace: to explain this more). > Sent: Monday, April 25, 2016 at 6:55 AM > From: "Cyril Ferlicot Delbecque" <cyril.ferlicot(a)gmail.com> > To: pharo-dev(a)lists.pharo.org > Subject: Re: [Pharo-dev] XMLParser changes > > > > On 25/04/2016 12:30, Norbert Hartl wrote: > > > It is right. There is no characters to be skipped. These must all resolve to text nodes with the whitespace characters in it. The behaviour of the new version is correct. So if you indent XML documents you might change the structure. The property should give control over that behaviour is called PreserveWhiteSpace. > > > > Norbert > > > > Ok thank you. > Now I need to find how to disable it. :) > I tried > > ((XMLDOMParser on: '<?xml version="1.0" encoding="UTF-8"?> >  > <Clones> > <ClonedFragment cloneName="test"> > <Member fileName="ProgramA"/> > <Member fileName="ProgramB"/> > </ClonedFragment> > <ClonedFragment cloneName="test2"> > <Member fileName="ProgramA"/> > <Member fileName="ProgramB"/> > </ClonedFragment> > </Clones>') preservesIgnorableWhitespace: false; parseDocument) elements > first nodes > > but I still get the whitespaces. > > I did not do a lot of XML parsing, someone knows how to remove easily > all the whitespaces nodes in a document? > > -- > Cyril Ferlicot > > http://www.synectique.eu > > 165 Avenue Bretagne > Lille 59000 France > >

April 25, 2016

Re: [Pharo-dev] XMLParser changes

by monty

It's not a regression (see the changelog or the new comment in #ignorableWhitespace:). This is the correct behavior required by the spec, is long-overdue, and is also the way other parsers like libxml2 behave. >From Sec. 2.10: "An XML processor MUST always pass all characters in a document that are not markup through to the application. A validating XML processor MUST also inform the application which of these characters constitute white space appearing in element content." The "white space appearing in element content" is the only whitespace the spec treats as ignorable, but the definition of "element content" requires validation and a DTD with ELEMENT declarations that restrict its content to elements. >From sec. 3.2.1: "An element type has element content when elements of that type MUST contain only child elements (no character data), optionally separated by white space." so these are of type element content: <!ELEMENT a (b,c,d)> <!ELEMENT a (b|c)> <!ELEMENT a (b+,c*)> but these aren't: <!ELEMENT a (#PCDATA|b|c)*> <!ELEMENT a ANY> <!ELEMENT a EMPTY> And if the parser is non-validating (or in our case, if you disable it) or there's no DTD, then all whitespace must be assumed to be non-ignorable. > Sent: Monday, April 25, 2016 at 6:14 AM > From: "Cyril Ferlicot Delbecque" <cyril.ferlicot(a)gmail.com> > To: pharo-dev(a)lists.pharo.org, monty <monty2(a)programmer.net> > Subject: XMLParser changes > > Hi, > > last week there was a new stable version of XMLParser and some tests > broke in some tools. I think that there was a regression in this version. > > Snippet: > > (XMLDOMParser parse: '<?xml version="1.0" encoding="UTF-8"?> >  > <Clones> > <ClonedFragment cloneName="test"> > <Member fileName="ProgramA"/> > <Member fileName="ProgramB"/> > </ClonedFragment> > <ClonedFragment cloneName="test2"> > <Member fileName="ProgramA"/> > <Member fileName="ProgramB"/> > </ClonedFragment> > </Clones>') elements first nodes > > With the release 2.7.4 we get 2 nodes but in release 2.7.6 we get 5 > nodes. The 2 previous ones and 3 empty String nodes. > > I think this is not what we expect. Correct me if I am wrong :) > > > -- > Cyril Ferlicot > > http://www.synectique.eu > > 165 Avenue Bretagne > Lille 59000 France > >

April 25, 2016