October 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] default monospaced code font

by Goubier Thierry

Excellent, I like the comparison a lot! Thanks! My take is: - Unable to like Source Code Pro 9 (and it's so wide); - Source Sans Pro 9 has spacing issues (16r, the r is too close) and reading issues (it's the worse for the lL|i characters) - Source sans Pro 10 is better than 9 (but what with the 2x space?) Overall, I'd stay with DejaVu Sans 9 based on this sample. In my opinion, the best compromise density / readability. Thierry Le 16/10/2013 19:56, btc(a)openinworld.com a Ã©crit : > Goubier Thierry wrote: >> I'd be more impressed if the argument was helping me distinguish >> between | and l. > > Yes. It is designed to do that. Some common failings of monospaced fonts > are noted [1] and dealt with. There comment section is also interesting. > > The attached PDFs are the result of getting the urge to compare a broad > coverage of code examples (taken from "Terse Guide to Squeak") against > three fonts: > * DejaVu Sans 9 point > * Source Code Pro [1] [2] 9 point > * Source Sans Pro [3] [4] 9 point & 10 point, since the width of 10 was > the same as the others at 9. > Also attached is the source excel file. > > cheers -ben > > [1] http://blogs.adobe.com/typblography/2012/09/source-code-pro.html > [2] http://sourceforge.net/projects/sourcecodepro.adobe/files/ > [3] http://blogs.adobe.com/typblography/2012/08/source-sans-pro.html > [4] > http://sourceforge.net/projects/sourcesans.adobe/postdownload?source=dlp >> >> I'l let you try, then :) >> >> Thierry > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Oct. 17, 2013

Re: [Pharo-dev] TxText status (was Re: bug: [4993] Typing cmd+L cancel all typing and we can't undo it [Terminated] )

by Goubier Thierry

Le 16/10/2013 14:00, StÃ©phane Ducasse a Ã©crit : > >>> thierry >>> >>> the one of alain is a simple do/undo now Epicea is a new changes model developed by martin and >>> you raised a good point, we should look if Epicea could be used for RB undo. >> >> My point is: undo/redo is one API (Alain's), EPICEA would specialize that for code changes, and RB is also for code changes (is EPICEA able to represent RB operations?). > > We should check that. > >> >> Also, would EPICEA come with a merge capability? It would beat any versionning system out there by providing better history understanding. > > This is exactly the goal of the phd of martin. > - better supporting merging Cool. > - I want a way to get the complete history of pharo and even do senders/implementors in the past :) This one is easy if you have a git repo below :) Partly implemented already, Stef... Just waiting for the rest of the system to catch up. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Oct. 17, 2013

[pharo-project/pharo-core]

by GitHub

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

Oct. 17, 2013

[pharo-project/pharo-core] bd843d: 30494

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: bd843d375dd7c24ea5af9158193fd5e567e98413 https://github.com/pharo-project/pharo-core/commit/bd843d375dd7c24ea5af9158… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-17 (Thu, 17 Oct 2013) Changed paths: M CollectionsTests-Support.package/WideCharacterSetTest.class/instance/testing/testAddingToCharacterSet.st M NewList-Example.package/NewListExample.class/instance/initialize/buildMorphWithOld.st M NewList-Example.package/NewListExample.class/instance/initialize/openInWindow.st M NewList-Example.package/NewListExample.class/instance/initialize/openInWorld.st M NewList-Example.package/NewListExample.class/instance/morphic/setIndex_.st M NewList.package/NewList.class/instance/events - keyboard/basicKeyPressed_.st M NewList.package/NewList.class/instance/updating - private/updateHeaderHeight.st M NewList.package/NewListAdapter.class/instance/list protocol/getMenu_.st M SUnit-Core-Kernel.package/TAssertable.class/instance/asserting/shouldnt_raise_.st M SUnit-Core-Kernel.package/TAssertable.class/instance/asserting/shouldnt_raise_description_.st M SUnit-Core-Kernel.package/TAssertable.class/instance/asserting/shouldnt_raise_whoseDescriptionDoesNotInclude_description_.st M SUnit-Core-Kernel.package/TAssertable.class/instance/asserting/shouldnt_raise_whoseDescriptionIncludes_description_.st A SUnit-Core-Kernel.package/TAssertable.class/instance/asserting/validateShouldntException_.st M SUnit-Tests-Core.package/SUnitExtensionsTest.class/instance/tests/testExceptionWithoutMatchingString.st M SUnit-Tests-Core.package/SUnitExtensionsTest.class/instance/tests/testNoExceptionWithMatchingString.st M SUnit-Tests-Core.package/SUnitExtensionsTest.class/instance/tests/testNoExceptionWithNoMatchingString.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script149.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30494.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M SmartSuggestions-Menu.package/SugsAbstractContext.class/definition.st A SmartSuggestions-Menu.package/SugsAbstractContext.class/instance/accesing/isMethodSelected.st A SmartSuggestions-Menu.package/SugsAbstractContext.class/instance/private/selectedStatements.st A SmartSuggestions-Menu.package/SugsAbstractContext.class/instance/private/selectedTemporaryVariables.st M SmartSuggestions-Menu.package/SugsAbstractContext.class/instance/selection/selectTheTextForTheNode.st A SmartSuggestions-Menu.package/SugsAbstractContext.class/instance/selection/selectedStatementsAsSequence.st A SmartSuggestions-Menu.package/SugsAbstractContext.class/instance/selection/selectedStatementsAsText.st Log Message: ----------- 30494 11913 Trivial critic clean NewList https://pharo.fogbugz.com/f/cases/11913 11876 Do not allow shouldnt:raise: Error https://pharo.fogbugz.com/f/cases/11876 11879 Obtain selected statements for suggestions https://pharo.fogbugz.com/f/cases/11879 http://files.pharo.org/image/30/30494.zip

Oct. 17, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation-M-Z/labe… 1 regressions found. Zinc.Tests.ZnServerTests.testEntityTooLarge

Oct. 17, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation-A-L/labe… 1 regressions found. KernelTests.Exception.ExceptionTests.testNoTimeout

Oct. 17, 2013

[pharo-project/pharo-core]

by GitHub

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

Oct. 17, 2013

[pharo-project/pharo-core] 4d6fe6: 30493

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 4d6fe600f69e350d0a75d2710dd896e8e844fc83 https://github.com/pharo-project/pharo-core/commit/4d6fe600f69e350d0a75d271… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-16 (Wed, 16 Oct 2013) Changed paths: M Kernel-Methods.package/CompiledMethod.class/instance/accessing/category.st M Morphic-Base-MorphTreeWidget.package/MorphTreeModel.class/definition.st A Morphic-Base-MorphTreeWidget.package/MorphTreeModel.class/instance/accessing/disable.st A Morphic-Base-MorphTreeWidget.package/MorphTreeModel.class/instance/accessing/enable.st A Morphic-Base-MorphTreeWidget.package/MorphTreeModel.class/instance/accessing/enabled.st A Morphic-Base-MorphTreeWidget.package/MorphTreeModel.class/instance/accessing/enabled_.st M Morphic-Base-MorphTreeWidget.package/MorphTreeMorph.class/definition.st A Morphic-Base-MorphTreeWidget.package/MorphTreeMorph.class/instance/accessing/disable.st A Morphic-Base-MorphTreeWidget.package/MorphTreeMorph.class/instance/accessing/enable.st A Morphic-Base-MorphTreeWidget.package/MorphTreeMorph.class/instance/accessing/enabled.st A Morphic-Base-MorphTreeWidget.package/MorphTreeMorph.class/instance/accessing/enabled_.st A Morphic-Base-MorphTreeWidget.package/MorphTreeMorph.class/instance/accessing/fillStyleToUse.st M Morphic-Base-MorphTreeWidget.package/MorphTreeMorph.class/instance/events-processing/mouseDown_.st M Morphic-Base-MorphTreeWidget.package/MorphTreeMorph.class/instance/events-processing/mouseMove_.st M Morphic-Base-MorphTreeWidget.package/MorphTreeMorph.class/instance/events-processing/mouseUp_.st M Morphic-Base-MorphTreeWidget.package/MorphTreeMorph.class/instance/events-processing/takesKeyboardFocus.st M Morphic-Base-MorphTreeWidget.package/MorphTreeMorph.class/instance/selection/selectionColorToUse.st A Morphic-Base-MorphTreeWidget.package/MorphTreeMorph.class/instance/updating/enabledFromModel.st M Morphic-Base-MorphTreeWidget.package/MorphTreeMorph.class/instance/updating/update_.st M Morphic-Base-MorphTreeWidget.package/MorphTreeNodeMorph.class/instance/mouse events/handleMouseUp_.st M Morphic-Base-MorphTreeWidget.package/MorphTreeNodeMorph.class/instance/mouse events/mouseDown_.st M Morphic-Base-MorphTreeWidget.package/MorphTreeTransformMorph.class/instance/drawing/drawRawColorOn_forSubmorph_.st M Morphic-Base-MorphTreeWidget.package/MorphTreeTransformMorph.class/instance/drawing/drawSubmorphsOn_.st R Refactoring-Core-Refactorings.package/RBMoveMethodRefactoring.class/instance/transforming/compileDelagatorMethod.st A Refactoring-Core-Refactorings.package/RBMoveMethodRefactoring.class/instance/transforming/compileDelegatorMethod.st M Refactoring-Core-Refactorings.package/RBMoveMethodRefactoring.class/instance/transforming/transform.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script148.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30493.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A System-Support.package/SystemDictionary.class/instance/classes and traits/allBehaviors.st A System-Support.package/SystemNavigation.class/instance/query/allBehaviors.st M System-Support.package/SystemNavigation.class/instance/query/allMethods.st R Tests-Release.package/ReleaseTest.class/instance/testing/testKernelExtensions.st R Tools-Browser.package/extension/SystemNavigation/instance/browseAllUnimplementedCalls.st M Tools-FileList.package/FileList.class/class/file reader registration/allRegisteredServices.st Log Message: ----------- 30493 11912 faster #allMethods on SystemNavigation https://pharo.fogbugz.com/f/cases/11912 11894 Tests.Release.ReleaseTest.testKernelExtensions fails https://pharo.fogbugz.com/f/cases/11894 11909 MorphTreeMorph lacks enable/disable https://pharo.fogbugz.com/f/cases/11909 11886 Typo at method name: RBMoveMethodRefactor>>compileDelagatorMethod https://pharo.fogbugz.com/f/cases/11886 http://files.pharo.org/image/30/30493.zip

Oct. 17, 2013

Re: [Pharo-dev] Old Compiler is now unload able!

by Marcus Denker

On Oct 17, 2013, at 7:49 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Now have a look at Opal and help us making better because there are still edge corners and little bugs. > The most important thing to understand is that Opal is not perfectâ¦ it's just a little bit better than the old compiler. The idea is not perfection (because is does not exist), but to just have some infrastructure that allows us to build on top. (e.g. reviving the old Reflectivity stuff, as one example). For bugs, we have - temps defined in ifTrue: are compiled with the wrong offset in some case (I think when there are other blocks defining a temp with the same name) - Christoph saw some case with problems in to:do: but I have not yet been able to even find an example to re-create the problem - when stepping in the debugger, temp vars are sometimes looked up in the wrong scope. I think this has to do with #stepToSendOrReturn when you are entering a block will run until the first send of the new block, which is too far. For improvements: -> IR instruction should store *range* of the bc offset they generate, as they can generate more than one (this would simplify finding an IR instruction for a pc offset when doing bc->text mapping for the debugger) -> IRIntepreter should be an IRVisitor, clean up the dual visiting/interpreting interface -> Semantic analysis: TempVars should not have index (it is left over from pre-closure times and only used for sorting the variables at the end), Sub=case: Decide which implementation of a sorted dictionary to integrate in Pharo3 Big picture (unlikely to happen) --------------- -> move all optimzations to the IR level (Controll Flow Graph) -> same for some of the analysis related to blocks (e.g. detecting escaping writes in loops should much more beautiful of a CFG than the AST). But then, it works even if is a bit convoluted now. After getting rid of old Compiler ------------------------------------------ -> remove #failBlock: -> compiler should not care about #category, it only compiles. -> all users of RBScanner and RBParser should use the OpalCompiler facade or APIs on CompiledMethod (#ast). (this will allow us to replace the RBParser as we like, e.g. to experiment with PetitParser)

Oct. 17, 2013

Re: [Pharo-dev] Old Compiler is now unload able!

by StÃ©phane Ducasse

Now have a look at Opal and help us making better because there are still edge corners and little bugs. Stef On Oct 16, 2013, at 10:21 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > And for the curious my favourite brainfuck was code:type: and its senders. > > Because the first time you read (code: index type: type), you wonder > * why you pass a parameter index (that overrides inst var index, but most caller invoke with index inst. var.) > * with the key code: > * since there is also an inst var named code that's really troubling... > Also because there is a cryptic use of negated type on return > And once you start analyzing senders, and inst var refs, you're puzzled... > > To decipher, code:type: answers an encoded bytecode, made from an index (temp index, inst var index etc..) and a type (load inst var, load temp var, etc...) thus its name code... > Now, I've contemplated this code too much, and it almost sounds familiar, I can hardly remember how impenetrable it was. But make you a pleasure, put a newbie in front of it. > > To me, this a a very clever factorisation of bytecode encoding - much too clever - much too obfuscated - and I bet we can do much much clearer with not much more code. > But I don't have to prove anything, there is Opal already... > > > > 2013/10/16 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > Too bad :( > > One of the most brilliant anti-pattern onto which I burnt so many brain cells is gone, > > how are we going to teach good coding practices by counter examples. > > ;) > > :) > We should continue to build the new generation it is more exciting and now I can start to invest in reading > the compiler code. > > Stef >

Oct. 17, 2013