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

[pharo-project/pharo-core] 9ee0e6: 60266

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 9ee0e6f6ac6ac784e27725b7f1e30794c6383f7e https://github.com/pharo-project/pharo-core/commit/9ee0e6f6ac6ac784e27725b7… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-10-21 (Fri, 21 Oct 2016) Changed paths: M Nautilus.package/AbstractNautilusUI.class/definition.st M Nautilus.package/AbstractNautilusUI.class/instance/build ui text/buildNewCommentText.st R Nautilus.package/AbstractNautilusUI.class/instance/class comment pane/acceptCommentFromView.st R Nautilus.package/AbstractNautilusUI.class/instance/class comment pane/classCommentTextModel.st R Nautilus.package/AbstractNautilusUI.class/instance/class comment pane/promptForCancel.st R Nautilus.package/AbstractNautilusUI.class/instance/class comment pane/whenExtendCommentSwitch_.st R Nautilus.package/AbstractNautilusUI.class/instance/class comment pane/whenTextUpdatedInCommentPane_.st M Nautilus.package/AbstractNautilusUI.class/instance/code panel/buildCodePanelWithoutComment.st A Nautilus.package/AbstractNautilusUI.class/instance/comment pane/acceptCommentFromView.st A Nautilus.package/AbstractNautilusUI.class/instance/comment pane/commentTextModel.st A Nautilus.package/AbstractNautilusUI.class/instance/comment pane/promptForCancel.st A Nautilus.package/AbstractNautilusUI.class/instance/comment pane/whenExtendCommentSwitch_.st A Nautilus.package/AbstractNautilusUI.class/instance/comment pane/whenTextUpdatedInCommentPane_.st M Nautilus.package/AbstractNautilusUI.class/instance/source code area/okToChangeComment.st M Nautilus.package/NautilusUI.class/instance/private/updateOnClassSelection.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60265.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60266.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60265.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60266.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60266 19223 rename nautilus class comment pane to just "comment pane" https://pharo.fogbugz.com/f/cases/19223 http://files.pharo.org/image/60/60266.zip

Oct. 21, 2016

Re: [Pharo-dev] [ANN] Sparta v1.1

by Sean P. DeNigris

Denis Kudriashov wrote > I look at code and it seems you implemented another one new text model? > Why > you not use TxText? Argh. I know it's bad form to complain about gifts, but at the rate we reinvent the wheel, I often fear that I will be retired from programming before we have a sane text model :/ ----- Cheers, Sean -- View this message in context: http://forum.world.st/ANN-Sparta-v1-1-tp4919394p4919570.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 21, 2016

Re: [Pharo-dev] [ANN] Sparta v1.1

by Aliaksei Syrel

Hi Denis Thanks for your questions! They are important. Unfortunately, I didn't have time today to perform a detailed comparison and stress test of txtext model. I will answer tomorrow :) Cheers, Alex On 20 October 2016 at 22:17, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > 2016-10-20 1:15 GMT+02:00 Glenn CavarlÃ© <glenn.cavarle(a)gmail.com>: > >> Good job Alex! >> Yes, the development version of Bloc is already based on Sparta. >> The stable version 0.10.1 is the last version with Athens support. >> > > What the repository for Bloc? >

Oct. 20, 2016

Re: [Pharo-dev] [ANN] Sparta v1.1

by Denis Kudriashov

2016-10-20 1:15 GMT+02:00 Glenn CavarlÃ© <glenn.cavarle(a)gmail.com>: > Good job Alex! > Yes, the development version of Bloc is already based on Sparta. > The stable version 0.10.1 is the last version with Athens support. > What the repository for Bloc?

Oct. 20, 2016

Re: [Pharo-dev] [Moose-dev] new themoosebook.org - work in progress

by Alexandre Bergel

Impressive!!!! Alexandre > On Oct 20, 2016, at 3:46 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > I am working on a new The Moose Book. You can see the current draft here: > http://themoosebook.org > > In the current form, it covers about 40% of what I want to have at the end. My target is to get a first complete version ready until Spring 2017. The book targets Moose 6.1, although most parts will work with Moose 6.0. > > The book is written in Pillar. A secondary goal for this book is to build a book editor with tools in Pharo. The current book was generated directly from Pharo without using the command line. The current code is in book GitHub repository, but the end goal is to have these tools working separately from the book. > > Please let me know what you think. > > The book repo is here: > https://github.com/girba/themoosebook > > Cheers, > Doru > > > -- > www.tudorgirba.com > www.feenk.com > > "Every thing has its own flow." > > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev

Oct. 20, 2016

Re: [Pharo-dev] [ANN] New release of iceberg

by Nicolas Passerini

Thank you Alex, a fix for that is in the way, but it needs some work yet, I will integrate it as soon as possible. A little clarification yet: we do not have a "three way diff"... or at least I am not aware of and a query in this list a few weeks ago raised no results. So using a 2-way diff there is no way to *really *show new code vs. old code. It will just show the differences between the two versions... in the case that one version is an ancestor of the other one, then the differences could be understood as "new code" vs. "old code" but that will not be allways the case. I will like to have a 3-way diff, but I am not sure that I will have time for that soon enough because we have defined other priorities. In the meantime we are working on making a bit more flexible the current 2-way diff, so that we can decide which side to paint red and which one to paint green. (Yes I could have just swap the versions, but I preferred to have allways "my" code in the left... I think that once we fix the color issue it will be more intuitive.) So the corrected version will work so: - left is allways "my code", right is "their" code. - red is old, green is new. (Another improvement would be to put labels on top of it, but it also needs improving the diff widget. Now we have only one title for the morph, the information is there but is not so clear as I would liket to.) Also we have problems with the highlihgting, because sometimes it is shifted one or two characters. I would like to fix it but... again, it takes time. So, to sum up, the diff needs a lot of work yet. 2016-10-17 11:48 GMT+02:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: > Diff has inverted colors (Red <-> Green) Almost every time have to stop > and think why new code I just wrote will be removed ;) > > GitHub: (new content is green) > [image: Inline images 1] > > Iceberg: (new content is red, note also that last E character in LINE is > not highlighted, but it should): > [image: Inline images 2] > > Cheers, > Alex > > On 16 October 2016 at 20:28, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > >> Hi >> >> I use Iceberg to load project in non-interactive mode and this is what I >> get with latest stable: >> >> RETRY->BaselineOfIceberg An attempt to use interactive tools detected, >> while in non-interactive mode >> >> Is there any reason that prevents Iceberg to be used in non-interactive >> mode, from command line for example? >> >> Cheers, >> Alex >> >> On 15 October 2016 at 13:59, stepharo <stepharo(a)free.fr> wrote: >> >>> + 1 >>> >>> This is on my todo :) >>> >>> >>> Le 13/10/16 Ã 20:37, Tudor Girba a Ã©crit : >>> >>> Hi Nicolas, >>>> >>>> Great work! >>>> >>>> I will test it again. I kindly ask everyone else to follow the call and >>>> test this release. Ideally, create a repository on GitHub and play with it. >>>> >>>> It is important to get this piece as stable as possible to make Git >>>> part of the default Pharo experience. >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> On Oct 13, 2016, at 2:25 PM, Nicolas Passerini <npasserini(a)gmail.com> >>>>> wrote: >>>>> >>>>> Hi, we are releasing a new version of Iceberg, with several new >>>>> features and bugfixes. I would't yet say that is 100% production ready, but >>>>> it is close, so I want to invite you to test it and provide feedback. >>>>> >>>>> You can install it by doing: >>>>> >>>>> Metacello new >>>>> baseline: 'Iceberg'; >>>>> repository: 'github://npasserini/iceberg'; >>>>> load. >>>>> >>>>> More installation instructions and documentation can be found at >>>>> https://github.com/npasserini/iceberg. >>>>> >>>>> Some of the new features in this version are: >>>>> - Allow to commit several packages together in the same commit. >>>>> - Show diffs for incoming and outgoing commits (i.e. before push/pull >>>>> you can browse the difference between the remote and the local versions). >>>>> - New History view allows to see any commit in any branch and compare >>>>> it to the current loaded version. >>>>> - Better support for interacting code loaded outside Iceberg >>>>> (smaltalkhub, filetree, gitfiletree, etc). >>>>> - From the diff view, revert changes or browse them (i.e. open a >>>>> Nautilus on the changed class/method). >>>>> - Automatically update presentations on code / repository changes. >>>>> - Integration with Metacello, i.e. after installing Iceberg you do >>>>> something like >>>>> >>>>> Metacello new >>>>> >>>>> baseline: 'TaskIt' >>>>> ; >>>>> repository: 'github://sbragagnolo/taskit' >>>>> ; >>>>> load. >>>>> >>>>> >>>>> (By default) it will be loaded using iceberg (there is a setting to >>>>> avoid it if you prefer traditional behavior. >>>>> >>>>> - Improved handling of git errors. >>>>> - Improved performance for several operations. >>>>> - Improved documentation. >>>>> - ... and several bug fixes and other minor improvements (please look >>>>> at https://github.com/npasserini/iceberg/milestone/7?closed=1 for >>>>> more details). >>>>> >>>>> >>>>> Please do not hesitate to contact me if you have any doubts. >>>>> >>>> -- >>>> www.tudorgirba.com >>>> www.feenk.com >>>> >>>> "Reasonable is what we are accustomed with." >>>> >>>> >>>> >>>> >>> >>> >> >

Oct. 20, 2016

Re: [Pharo-dev] [ANN] New release of iceberg

by Norbert Hartl

I would be interested how (or if) people use iceberg. I think it is an important tool for us so a lot of people should try. What makes me wonder is the fact that I usually need around 2-3 clicks until I get a debugger from iceberg. How are other people using it? - I cloned a repository myself and packages existed before hooking up iceberg. On "synchronize repositoryâ¦" I get a DNA IceForeignVersion>>#snapshot - I clone a remote repository and get - after that I can close and open iceberg and get the red square. No cure so far - I created the directory and tried again. Then I get So what is _the_ use case for iceberg that works? thanks, Norbert > Am 13.10.2016 um 14:25 schrieb Nicolas Passerini <npasserini(a)gmail.com>: > > Hi, we are releasing a new version of Iceberg, with several new features and bugfixes. I would't yet say that is 100% production ready, but it is close, so I want to invite you to test it and provide feedback. > > You can install it by doing: > > Metacello new > baseline: 'Iceberg'; > repository: 'github://npasserini/iceberg'; > load. > > More installation instructions and documentation can be found at https://github.com/npasserini/iceberg <https://github.com/npasserini/iceberg>. > > Some of the new features in this version are: > - Allow to commit several packages together in the same commit. > - Show diffs for incoming and outgoing commits (i.e. before push/pull you can browse the difference between the remote and the local versions). > - New History view allows to see any commit in any branch and compare it to the current loaded version. > - Better support for interacting code loaded outside Iceberg (smaltalkhub, filetree, gitfiletree, etc). > - From the diff view, revert changes or browse them (i.e. open a Nautilus on the changed class/method). > - Automatically update presentations on code / repository changes. > - Integration with Metacello, i.e. after installing Iceberg you do something like > > Metacello new > baseline: 'TaskIt'; > repository: 'github://sbragagnolo/taskit'; > load. > > (By default) it will be loaded using iceberg (there is a setting to avoid it if you prefer traditional behavior. > > - Improved handling of git errors. > - Improved performance for several operations. > - Improved documentation. > - ... and several bug fixes and other minor improvements (please look at https://github.com/npasserini/iceberg/milestone/7?closed=1 <https://github.com/npasserini/iceberg/milestone/7?closed=1> for more details). > > > Please do not hesitate to contact me if you have any doubts.

Oct. 20, 2016

[pharo-project/pharo-core]

by GitHub

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

Oct. 20, 2016

[pharo-project/pharo-core] ae8113: 60265

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: ae8113132bc2dbe240e6b4e1bff1cb64a9c88d01 https://github.com/pharo-project/pharo-core/commit/ae8113132bc2dbe240e6b4e1… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-10-20 (Thu, 20 Oct 2016) Changed paths: R Morphic-Widgets-Pluggable.package/PluggableTextEditorMorph.class/README.md R Morphic-Widgets-Pluggable.package/PluggableTextEditorMorph.class/class/as yet unclassified/stylingClass.st R Morphic-Widgets-Pluggable.package/PluggableTextEditorMorph.class/definition.st R Morphic-Widgets-Pluggable.package/PluggableTextEditorMorph.class/instance/as yet unclassified/textMorphClass.st R Polymorph-Widgets.package/TEasilyThemed.class/instance/controls/newAutoAcceptTextEditorFor_getText_setText_getEnabled_.st R Polymorph-Widgets.package/TEasilyThemed.class/instance/controls/newBasicTextEditorFor_getText_setText_.st R Polymorph-Widgets.package/TEasilyThemed.class/instance/controls/newBasicTextEditorFor_getText_setText_getEnabled_.st R Polymorph-Widgets.package/TEasilyThemed.class/instance/controls/newBasicTextEditorFor_getText_setText_getEnabled_menu_.st R Polymorph-Widgets.package/UITheme.class/instance/morph creation/newAutoAcceptTextEditorIn_for_getText_setText_getEnabled_.st R Polymorph-Widgets.package/UITheme.class/instance/morph creation/newBasicTextEditorIn_for_getText_setText_getEnabled_menu_.st R Rubric.package/RubFindReplaceService.class/instance/as yet unclassified/initialize.st A Rubric.package/RubFindReplaceService.class/instance/initialization/initialize.st A Rubric.package/RubFindReplaceService.class/instance/private/findAndSelect.st A Rubric.package/RubFindReplaceService.class/instance/private/findAndSelectRegex.st A Rubric.package/RubFindReplaceService.class/instance/private/setStartIndex.st M Rubric.package/RubFindReplaceService.class/instance/services/find.st M Rubric.package/RubFloatingEditorBuilder.class/instance/private/buildEditor.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60264.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60265.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60264.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60265.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60265 19220 MNU in Find and Replace on accepting empty input https://pharo.fogbugz.com/f/cases/19220 17194 users of PluggableTextEditorMorph should use Rubric https://pharo.fogbugz.com/f/cases/17194 18904 Opened Find And Replace dialog from fasttables search is uncloseable https://pharo.fogbugz.com/f/cases/18904 http://files.pharo.org/image/60/60265.zip

Oct. 20, 2016

Re: [Pharo-dev] [ANN] Sparta v1.1

by Denis Kudriashov

2016-10-20 9:07 GMT+02:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: > As I understand, Pharo for PC should not make any assumptions about user's > hardware. If gpu accelerated backend can not be used there should be still > a performant fallback backend which also needs a fallback that is > guaranteed to work even on Personal Calculators. (Taschenrechner). That is > why library is so big. For example for mac and windows Sparta is shipped > with 3 (!) backends that together build fallback chain, for instance on > windows: direct2d1.1, skia, cairo. Compiling library for mac without Skia > reduces binary size from 15mb to 10mb. Removing GL package and leaving only > software backends may reduce size even more. > > It is a bit different on embedded systems, since hardware configuration is > already known and there is no need to have so many fallback backends. > Library itself allows developers to add new exotic backends quite easily. > > Let's take Pharo6 for mac. It is shipped with the following libs: > Cairo (1.4mb) + Pixman (2.8mb) + Freetype (0.8mb) = 5mb > > Moz2D is self contained and does not require any additional libs. > Moz2D = 15mb, Moz2D without Skia = 10mb. Moz2D without Skia and GL = ? > (estimate around 6-7mb). > Also imaging that we will remove Cairo, Athens, Fonts from image, font plugin from VM. Also Morphic and old Canvas. I expect Morphic is much bigger then Bloc. And at some point bitblt stuff from image and VM. I am sure at the end new clean solutions will provide much lesser image and VM size.

Oct. 20, 2016