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

Re: [Pharo-dev] Odd Commits to Soup Repo

by stepharo

then this is good because esteban told me that it was not some time ago :). Stef Le 2/8/16 Ã 20:05, monty a Ã©crit : > It's worked for me in the past. For example, when I migrated projects from a shared repo to separate repos. But the files don't always disappear immediately. > >> Sent: Tuesday, August 02, 2016 at 3:03 AM >> From: stepharo <stepharo(a)free.fr> >> To: pharo-dev(a)lists.pharo.org >> Subject: Re: [Pharo-dev] Odd Commits to Soup Repo >> >> Hi Paul >> >> It never works with me. Did you check that the file is really not there >> after. >> >> Stef >> >> Le 28/7/16 Ã 22:26, Paul DeBruicker a Ã©crit : >>> Sure you can delete mcz from Smalltalkhub. Or at least the Web UI offers a >>> 'Delete .mcz' button, which appears to work. >>> >>> Sign in >>> Navigate to the project >>> Click on Commits >>> Find the MCZ you want to delete >>> Click the name of the MCZ >>> Click the "Delete .mcz" button >>> >>> >>> It should then be deleted. >>> >>> As a test I deleted >>> ConfigurationOfAutomaticMethodCategorizer-StephaneDucasse.4, >>> Pharo-Launcher-Core-DamienCassou.21, and >>> ConfigurationOfPharoLauncher-DamienCassou.9 from the PharoExtras/Soup repo >>> >>> Or did you mean something else? >>> >>> >>> >>> >>> Hope this helps >>> >>> >>> Paul >>> >>> >>> >>> >>> >>> stepharo wrote >>>> Yes but we cannot remove file in Smalltalkhub repo. >>>> >>>> >>>> Stef >>>> >>>> >>>> Le 28/7/16 Ã 18:47, Sean P. DeNigris a Ã©crit : >>>>> I found ConfigurationOfPharoLauncher-DamienCassou.9 & >>>>> Pharo-Launcher-Core-DamienCassou.21 there. I assume they were uploaded by >>>>> mistake... >>>>> >>>>> >>>>> >>>>> ----- >>>>> Cheers, >>>>> Sean >>>>> -- >>>>> View this message in context: >>>>> http://forum.world.st/Odd-Commits-to-Soup-Repo-tp4908492.html >>>>> Sent from the Pharo Smalltalk Developers mailing list archive at >>>>> Nabble.com. >>>>> >>>>> >>> >>> >>> >>> -- >>> View this message in context: http://forum.world.st/Odd-Commits-to-Soup-Repo-tp4908492p4908538.html >>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >>> >>> >> >> >

Aug. 2, 2016

Re: [Pharo-dev] Bloc, Bloc 2 and Brick

by stepharo

Le 2/8/16 Ã 15:47, Ben Coman a Ã©crit : > On Tue, Aug 2, 2016 at 6:58 PM, Torsten Bergmann <astares(a)gmx.de> wrote: >> Hi Stef, >> >> from past discussions/threads I know "Bloc" as Pharo's possible future UI, watched the video [1] and have played with the premade >> image from the CI Server. Also the Brick layer (which is on top of Bloc) was announced as a preview once [2]. >> >> >> Now in some of the mails it was mentioned that there will be or already is a "Bloc 2" (see [3]). Can you or the person >> working on it summarize: >> >> - who works on it >> - what are the goals, what will be included (like the CSS styling) >> - where it is hosted >> - what the status is >> - if there is already a CI build or preview >> - how Brick will relate to "Bloc 2", will there be a "Brick 2" as well? >> - if it will work with Spec >> >> Even if not all could be answered (yet) more informations on "Bloc 2" would really be nice, ideally as a >> status summary to the community. >> >> Thanks >> T. >> >> [1] https://vimeo.com/115336678 >> [2] http://gtoolkit.org/brick/ >> [3] http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2016-August/1231… >> You see as I mention in my other mail: Glenn was not happy with the move inside Bloc1+ and he took all his experience and discussions on Bloc1+ and build a new one. > You read my thoughts Torsten. It would seem something has been learnt > from Bloc 1 to necessitate a change in direction. This would be > interesting to know, as well as the plan for the new architecture. The plans (as far as Alain, Glenn and Thales are concerned) is that we will have a roadmap soon :) > > I don't know what is the funding arrangements are to develop Bloc 2. There are none. Glenn is doing it instead of working on his PhD but he needs it also for his PhD. and I hope part of it will be able to be part of his PhD. My plan is to help Glenn for his PhD. > If its mostly someone's free time then maybe we can't put too much > demands on status report. However since Bloc will become a core part > of Pharo, perhaps it is worthwhile for the Pharo Association (or other > body) to fund such a status report for the community. A detailed > forward plan may have the side effect to encourage participation. Glenn and Alain were a bit secret because it was not clear how Bloc contributors would react. I was involved since I push Bloc since its early genesis. Since now this is going in the right direction, the project is now public, you can load it and it works. I do not know if the discussions are public on pharo slack channels now (they should be in Pharo and not in a private slack). Now what is important to understand is that Glenn is busy and Alain has some family problems. Now the plan is to have a presentation at ESUG between aliak and glenn. So we should get something. Stef > > cheers -ben > >

Aug. 2, 2016

Re: [Pharo-dev] Bloc, Bloc 2 and Brick

by stepharo

Hi Torsten Thanks for your interest. Yes Bloc is important to me (I'm waiting for it since Miro and Miro2 and all the work I asked igor to do around Athens and SDL) Glenn sent me a teaser (see attachement) last week Le 2/8/16 Ã 12:58, Torsten Bergmann a Ã©crit : > Hi Stef, > > from past discussions/threads I know "Bloc" as Pharo's possible future UI, watched the video [1] and have played with the premade > image from the CI Server. Also the Brick layer (which is on top of Bloc) was announced as a preview once [2]. > > > Now in some of the mails it was mentioned that there will be or already is a "Bloc 2" (see [3]). Can you or the person > working on it summarize: > > - who works on it Glenn Cavarle with Alain Plantec (and me from far and too little time) and Doru but I do not know much from that part. > - what are the goals, what will be included (like the CSS styling) Glenn implemented a new version of Bloc because he needed one for his job The flux in Bloc from October did not match with his requirements so without telling it to Alain and me he built one until he could show us something working and it works. I should say that I was also frustrated by the results of the discussions since October. Especially since before presenting Bloc to ESUG we got 4 versions and I tried to follow alain and help him documenting Bloc and while my stupid questions helped him it was difficult for me. So I really appreciate the effort of Glenn. In June we spent three days to understand if we should merge Bloc2 into Bloc and we decided the inverse because his implementation is based on SDL and a separate window) it does not suffer from the morphic plague. So for example the event bubbling is nice and clean. The idea is to be able to use one window (morphic) to develop all the widgets and displayed in the SDL window needed up to the point where we can remove morphic. So Bloc2 can benefit from the work of Aliak on Sparta and the mozzD backend. The idea is also to integrate the work on aliak on layouts. > - where it is hosted For the moment you can find it in GlennCavarle repo on smalltalkhub. Glenn is working for a company for ihs PhD and a week on two he is working on Bloc2. Bloc2 is key for Glenn and Alain since Thales wants to use it. MCHttpRepository location: 'http://smalltalkhub.com/mc/GlennCavarle/Bloc2/main' user: '' password: '' Now with the name removal we got some trouble to load it in Pharo 60. You can load it in Pharo 50. Say yes to all the warnings. Doru told me that he is talking with Glenn and that Bloc2 will be moved to the Bloc repo (by the end of this week). Esteban is following the discussions and will help for the SDL part and FFI. The SDL is fragile and the system freezes from time to time. But 64 bits first :) > - what the status is The core design looks stable to me. We can import SVG, create first buttons and style them (the skins in Bloc2 are so far not a theme) and the CSS is not for Skins but for style. Widgets can start to be built on top. The problem is that Brick took a glitch in Bloc1 and uses it against the expectation of Alain. So I do not think that we can port easily Brick to Bloc2. I started to read everything. And I will start to improve the class comments. Bloc2 - nice core - SDL based - nice bubbling of event - Bloc1+ Sparta and MozzD back end - Bloc1+ aliak layout - Bloc1 event handler - CSS styling Here is what glenn sent me last week (I translated it but thunderbird crashed!) Concernant Bloc, Ã§a devient assez stable mais il reste encore des sujets Ã valider/amÃ©liorer/stabiliser: - styles&themes -> 1Ã¨re Ã©bauche rÃ©alisÃ©e - Path (Shapes custom) -> voir ce que l'on peut reprendre de Athens-SVG - KeyBinding -> 1Ã¨re version trÃ¨s simple rÃ©alisÃ©e mais sans la gestion des sÃ©quences (ctrl A+B) - Animation -> premiÃ¨re version plutÃ´t concluante - ParentÃ© des fenÃªtres ou sous-fenÃªtres - AmÃ©lioration des performances de dessin par crÃ©ation de surfaces au niveau de BlElement -> premier rÃ©sultats concluant mais non-intÃ©grÃ©. - Gestion des Gestures (MultiTouch) -> migration des gestures d'OSWindow au niveau de Bloc sous forme d'EventListener (pas de gestures globales) - Gestion du Focus keyboard -> la base y est mais il reste encore pas mal de boulot - Mise en relation DnD et Clipboard -> l'instructure est lÃ mais il reste Ã faire le "cablage" - ... J'essaie de mettre ma roadmap au propre pour dÃ©but de semaine prochaine. Les prochains widgets sur ma liste sont: scrollbar & liste Now Doru told me that he should discuss with Glenn of certain design point. My wish is that such discussions do not kill Bloc2 because else I will leave this community :). Now I'm confident that something good will happen because Glenn needs it for his future. > - if there is already a CI build or preview There are examples. During holiday I tried to set up a jenkins but the network was too bad. This is on my todo but I'm busy since I'm back to work. > - how Brick will relate to "Bloc 2", will there be a "Brick 2" as well? I think that Brick should be rewritten on top of Bloc2 because the design of Brick was the thing that made Bloc get changed in October and after it changed too much. > - if it will work with Spec Spec is orthogonal. As soon as we will have widgets we will do a Spec binding for them. In the long term we will see if another framework wants to replace Spec to compose widgets (I know that alain has some ideas) but for now we want to be able to move our tool fast to new Brick and it should be possible and it should also simplify Spec because some of the design points of Spec are ugly because the old widget relay on change/update and what is needed is a notification (announcement). > Even if not all could be answered (yet) more informations on "Bloc 2" would really be nice, ideally as a > status summary to the community. > > Thanks > T. > > [1]https://vimeo.com/115336678 > [2]http://gtoolkit.org/brick/ > [3]http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2016-August/12… > >

Aug. 2, 2016

Re: [Pharo-dev] Bloc, Bloc 2 and Brick

by stepharo

Glenn sent me this teaser but I was waiting :) > Hi Stef, > > from past discussions/threads I know "Bloc" as Pharo's possible future UI, watched the video [1] yes it was cool :) > and have played with the premade > image from the CI Server. Also the Brick layer (which is on top of Bloc) was announced as a preview once [2]. > > > Now in some of the mails it was mentioned that there will be or already is a "Bloc 2" (see [3]). Can you or the person > working on it summarize: > > - who works on it Glenn Cavarle with Alain Plantec (and me from far and too little time) and Doru but I do not know much from that part. There was a separate slack team and since I did not like this idea I did not ask to join it. May be now this is folded back in the Pharo slack channel which to me would be better. > - what are the goals, what will be included (like the CSS styling) Glenn implemented a new version of Bloc because he needed one for his job The flux in Bloc from October did not match with his requirements so without telling it to Alain and me he built one until he could show us something working and it works. I should say that I was also frustrated by the results of the discussions since October. Especially since before presenting Bloc to ESUG we got 4 versions and I tried to follow alain and help him documenting Bloc and while my stupid questions helped him it was difficult for me. So I really appreciate the effort of Glenn. In June we spent three days to understand if we should merge Bloc2 into Bloc and we decided the inverse because his implementation is based on SDL and a separate window) it does not suffer from the morphic plague. So for example the event bubbling is nice and clean. The idea is to be able to use one window (morphic) to develop all the widgets and displayed in the SDL window needed up to the point where we can remove morphic. So Bloc2 can benefit from the work of Aliak on Sparta and the mozzD backend. The idea is also to integrate the work on aliak on layouts. Bloc2 SDL2 nice bubbling Bloc layout Sparta or MozzD back-end Nice core without the problem mention back in feb CSS styling here is what Gellen two me the 25 of July Concernant Bloc, Ã§a devient assez stable mais il reste encore des sujets Ã valider/amÃ©liorer/stabiliser: - styles&themes -> 1Ã¨re Ã©bauche rÃ©alisÃ©e - Path (Shapes custom) -> voir ce que l'on peut reprendre de Athens-SVG - KeyBinding -> 1Ã¨re version trÃ¨s simple rÃ©alisÃ©e mais sans la gestion des sÃ©quences (ctrl A+B) - Animation -> premiÃ¨re version plutÃ´t concluante - ParentÃ© des fenÃªtres ou sous-fenÃªtres - AmÃ©lioration des performances de dessin par crÃ©ation de surfaces au niveau de BlElement -> premier rÃ©sultats concluant mais non-intÃ©grÃ©. - Gestion des Gestures (MultiTouch) -> migration des gestures d'OSWindow au niveau de Bloc sous forme d'EventListener (pas de gestures globales) - Gestion du Focus keyboard -> la base y est mais il reste encore pas mal de boulot - Mise en relation DnD et Clipboard -> l'instructure est lÃ mais il reste Ã faire le "cablage" - ... J'essaie de mettre ma roadmap au propre pour dÃ©but de semaine prochaine. Les prochains widgets sur ma liste sont: scrollbar & liste, > - where it is hosted For the moment you can find it in GlennCavarle repo on smalltalkhub. Glenn is working for a company for ihs PhD and a week on two he is working on Bloc2. Bloc2 is key for Glenn and Alain since Thales wants to use it. MCHttpRepository location: 'http://smalltalkhub.com/mc/GlennCavarle/Bloc2/main' user: '' password: '' Now with the name removal we got some trouble to load it in Pharo 60. You can load it in Pharo 50. Say yes to all the warnings. Doru told me that he is talking with Glenn and that Bloc2 will be moved to the Bloc repo (by the end of this week). Esteban is following the discussions and will help for the SDL part and FFI. The SDL is fragile and the system freezes from time to time. But 64 bits first :) > - what the status is The core design looks stable to me. We can import SVG, create first buttons and style them (the skins in Bloc2 are so far not a theme) and the CSS is not for Skins but for style. Widgets can start to be built on top. The problem is that Brick took a glitch in Bloc1 and uses it against the expectation of Alain. So I do not think that we can port easily Brick to Bloc2. I started to read everything. And I will start to improve the class comments. > - if there is already a CI build or preview You can load it from Glenn's repo There are examples. During holiday I tried to set up a jenkins but the network was too bad. This is on my todo but I'm busy since I'm back to work. > - how Brick will relate to "Bloc 2", will there be a "Brick 2" as well? I think that Brick should be rewritten on top of Bloc2 because the design of Brick was the thing that made Bloc get changed in October and after it changed too much. > - if it will work with Spec Spec is orthogonal. As soon as we will have widgets we will do a Spec binding for them. In the long term we will see if another framework wants to replace Spec to compose widgets (I know that alain has some ideas) but for now we want to be able to move our tool fast to new Brick and it should be possible and it should also simplify Spec because some of the design points of Spec are ugly because the old widget relay on change/update and what is needed is a notification (announcement). > Even if not all could be answered (yet) more informations on "Bloc 2" would really be nice, ideally as a > status summary to the community. > > Thanks > T. > > [1] https://vimeo.com/115336678 > [2] http://gtoolkit.org/brick/ > [3] http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2016-August/1231… > >

Aug. 2, 2016

Re: [Pharo-dev] Odd Commits to Soup Repo

by monty

It's worked for me in the past. For example, when I migrated projects from a shared repo to separate repos. But the files don't always disappear immediately. > Sent: Tuesday, August 02, 2016 at 3:03 AM > From: stepharo <stepharo(a)free.fr> > To: pharo-dev(a)lists.pharo.org > Subject: Re: [Pharo-dev] Odd Commits to Soup Repo > > Hi Paul > > It never works with me. Did you check that the file is really not there > after. > > Stef > > Le 28/7/16 Ã 22:26, Paul DeBruicker a Ã©crit : > > Sure you can delete mcz from Smalltalkhub. Or at least the Web UI offers a > > 'Delete .mcz' button, which appears to work. > > > > Sign in > > Navigate to the project > > Click on Commits > > Find the MCZ you want to delete > > Click the name of the MCZ > > Click the "Delete .mcz" button > > > > > > It should then be deleted. > > > > As a test I deleted > > ConfigurationOfAutomaticMethodCategorizer-StephaneDucasse.4, > > Pharo-Launcher-Core-DamienCassou.21, and > > ConfigurationOfPharoLauncher-DamienCassou.9 from the PharoExtras/Soup repo > > > > Or did you mean something else? > > > > > > > > > > Hope this helps > > > > > > Paul > > > > > > > > > > > > stepharo wrote > >> Yes but we cannot remove file in Smalltalkhub repo. > >> > >> > >> Stef > >> > >> > >> Le 28/7/16 Ã 18:47, Sean P. DeNigris a Ã©crit : > >>> I found ConfigurationOfPharoLauncher-DamienCassou.9 & > >>> Pharo-Launcher-Core-DamienCassou.21 there. I assume they were uploaded by > >>> mistake... > >>> > >>> > >>> > >>> ----- > >>> Cheers, > >>> Sean > >>> -- > >>> View this message in context: > >>> http://forum.world.st/Odd-Commits-to-Soup-Repo-tp4908492.html > >>> Sent from the Pharo Smalltalk Developers mailing list archive at > >>> Nabble.com. > >>> > >>> > > > > > > > > > > -- > > View this message in context: http://forum.world.st/Odd-Commits-to-Soup-Repo-tp4908492p4908538.html > > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > > > > > >

Aug. 2, 2016

Re: [Pharo-dev] Bloc, Bloc 2 and Brick

by Ben Coman

On Tue, Aug 2, 2016 at 6:58 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi Stef, > > from past discussions/threads I know "Bloc" as Pharo's possible future UI, watched the video [1] and have played with the premade > image from the CI Server. Also the Brick layer (which is on top of Bloc) was announced as a preview once [2]. > > > Now in some of the mails it was mentioned that there will be or already is a "Bloc 2" (see [3]). Can you or the person > working on it summarize: > > - who works on it > - what are the goals, what will be included (like the CSS styling) > - where it is hosted > - what the status is > - if there is already a CI build or preview > - how Brick will relate to "Bloc 2", will there be a "Brick 2" as well? > - if it will work with Spec > > Even if not all could be answered (yet) more informations on "Bloc 2" would really be nice, ideally as a > status summary to the community. > > Thanks > T. > > [1] https://vimeo.com/115336678 > [2] http://gtoolkit.org/brick/ > [3] http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2016-August/1231… > You read my thoughts Torsten. It would seem something has been learnt from Bloc 1 to necessitate a change in direction. This would be interesting to know, as well as the plan for the new architecture. I don't know what is the funding arrangements are to develop Bloc 2. If its mostly someone's free time then maybe we can't put too much demands on status report. However since Bloc will become a core part of Pharo, perhaps it is worthwhile for the Pharo Association (or other body) to fund such a status report for the community. A detailed forward plan may have the side effect to encourage participation. cheers -ben

Aug. 2, 2016

Re: [Pharo-dev] let's talk about themes (and GLMBrickThemer)

by Tudor Girba

Hi, I will take a look at this tomorrow and get back to you. Cheers, Doru > On Aug 2, 2016, at 12:06 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > >> On 02 Aug 2016, at 08:59, stepharo <stepharo(a)free.fr> wrote: >> >> Hi esteban >> >> It looks cool. For the error could you use a different one because I cannot read it. >> Else when I tried to use the same way than Setting to manage skins it did not work >> > because theming is a lot of things: > > - a skin > - a color palette > - etc. > > for now, I would be happy with extract the color palette into a âStyleSheetâ objectâ¦ this could be modified in settings (while a complete skin not). > > Esteban > >> because a skin is not just color it can be behavior and you have to attach it somewhere. >> Now in bloc 2 :) >> >> you can the look (that can be expressed with CSS) >> >> and you have skins (the behavior: a date can be displayed as a calendar vs. a roller). >> In this model a theme (color) will just be similar to applying a new CSS. >> Stef >> >> Le 1/8/16 Ã 11:13, Esteban Lorenzano a Ã©crit : >>> Hi, >>> >>> For one of my side-projects, I made a new theme for Pharo (still no name, I was planing to call it âDark Metalâ or something like that. Is a variation on the Dark Theme but âourâ dark theme is more brown and this one is more blue (see attached)â¦ I wanted to publish it to push it but then I arrived to an unexpected problem: For Spotter and GTTools in general, theming is not done following current theming approach. Instead, they made a full hierarchy of objects. >>> >>> IMO this is plain bad. I understand the attempt to decouple, but now that means if I want to create a new theme, I need to create my theme object with colors I want and then also I need to create an undetermined number of classes (at least one for each tool, but there is also a hierarchy of things there)â¦ anyway, this DOES NOT scale. Because each tool will have to have a âtheme classâ for each existing themeâ¦ >>> How themes (skins, bah) work in all word is to have a color palette and then tools takes them (they can âplayâ a bit with this palette, but need to always respect the palette). >>> >>> Then, I will commit a SLICE modifying the âthemerâ classes to take colors from the current theme (instead of have them hardcoded). >>> But of course, how theme work now is not good because they mix âthemeâ (how they display) and âskinâ (color palette). I will also extract the palette to where should have always been (some kind of a style sheet object)â¦ who also should have been editable in settings so people can tweak their configuration. >>> >>> I didnât wanted to touch this before, because this will supposedly change with brick, but honestly this will not be ready for Pharo 6 and this is annoying (also, I want to publish my theme and I do not want to add overrides all around :P) >>> >>> cheers, >>> Esteban >>> >>> >>> <Mail Attachment.png> >> > -- www.tudorgirba.com www.feenk.com "Things happen when they happen, not when you talk about them happening."

Aug. 2, 2016

Re: [Pharo-dev] Bloc, Bloc 2 and Brick

by Tudor Girba

Hi, We are still in exploration mode with respect to design and this is why you see several internal names. We expect to have a clear structure within a couple of weeks, and there will be an announcement on that. In the end, there will be exactly one single Bloc and one single Brick. Cheers, Doru > On Aug 2, 2016, at 12:58 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi Stef, > > from past discussions/threads I know "Bloc" as Pharo's possible future UI, watched the video [1] and have played with the premade > image from the CI Server. Also the Brick layer (which is on top of Bloc) was announced as a preview once [2]. > > > Now in some of the mails it was mentioned that there will be or already is a "Bloc 2" (see [3]). Can you or the person > working on it summarize: > > - who works on it > - what are the goals, what will be included (like the CSS styling) > - where it is hosted > - what the status is > - if there is already a CI build or preview > - how Brick will relate to "Bloc 2", will there be a "Brick 2" as well? > - if it will work with Spec > > Even if not all could be answered (yet) more informations on "Bloc 2" would really be nice, ideally as a > status summary to the community. > > Thanks > T. > > [1] https://vimeo.com/115336678 > [2] http://gtoolkit.org/brick/ > [3] http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2016-August/1231… > -- www.tudorgirba.com www.feenk.com "Presenting is storytelling."

Aug. 2, 2016

[pharo-project/pharo-core]

by GitHub

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

Aug. 2, 2016

[pharo-project/pharo-core] 024ef4: 60162

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 024ef4c9ddab9f907611339a771d666b6928b2e3 https://github.com/pharo-project/pharo-core/commit/024ef4c9ddab9f907611339a… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-08-02 (Tue, 02 Aug 2016) Changed paths: R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60161.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60162.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60161.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60162.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-PolyWidgets.package/DateModel.class/class/example/example.st A Spec-PolyWidgets.package/DateModel.class/class/example/exampleModal.st M Spec-PolyWidgets.package/DateModel.class/instance/private/iconMorph.st M Spec-PolyWidgets.package/MethodToolbar.class/README.md A Spec-PolyWidgets.package/MethodToolbar.class/class/example/example.st M Spec-PolyWidgets.package/MethodToolbar.class/definition.st M Spec-PolyWidgets.package/PickListModel.class/README.md M Spec-PolyWidgets.package/PickListModel.class/class/example/example.st A Spec-PolyWidgets.package/SearchableTree.class/class/examples/example.st A Spec-Tests.package/DateModelTest.class/README.md A Spec-Tests.package/DateModelTest.class/definition.st A Spec-Tests.package/DateModelTest.class/instance/running/classToTest.st A Spec-Tests.package/DateModelTest.class/instance/running/tearDown.st A Spec-Tests.package/DateModelTest.class/instance/tests/testOnDateChosen.st A Spec-Tests.package/EditableListTest.class/README.md A Spec-Tests.package/EditableListTest.class/definition.st A Spec-Tests.package/EditableListTest.class/instance/running/classToTest.st A Spec-Tests.package/EditableListTest.class/instance/tests/testMoveElementAtTo.st A Spec-Tests.package/MethodToolbarTest.class/README.md A Spec-Tests.package/MethodToolbarTest.class/definition.st A Spec-Tests.package/MethodToolbarTest.class/instance/running/classToTest.st A Spec-Tests.package/PickListModelTest.class/README.md A Spec-Tests.package/PickListModelTest.class/definition.st A Spec-Tests.package/PickListModelTest.class/instance/running/classToTest.st M Spec-Tests.package/RadioButtonGroupModelTest.class/README.md M Spec-Tests.package/RadioButtonGroupModelTest.class/definition.st A Spec-Tests.package/RadioButtonGroupModelTest.class/instance/running/classToTest.st M Spec-Tests.package/RadioButtonGroupModelTest.class/instance/running/setUp.st M Spec-Tests.package/RadioButtonGroupModelTest.class/instance/tests/testAddRadioButton.st M Spec-Tests.package/RadioButtonGroupModelTest.class/instance/tests/testAddingFocusOrder.st M Spec-Tests.package/RadioButtonGroupModelTest.class/instance/tests/testCurrentActivated.st M Spec-Tests.package/RadioButtonGroupModelTest.class/instance/tests/testDefault.st M Spec-Tests.package/RadioButtonGroupModelTest.class/instance/tests/testLinkRadioButton.st R Spec-Tests.package/RadioButtonGroupModelTest.class/instance/tests/testOpenAndClose.st M Spec-Tests.package/RadioButtonGroupModelTest.class/instance/tests/testRebuildWidget.st A Spec-Tests.package/SearchableListTest.class/README.md A Spec-Tests.package/SearchableListTest.class/definition.st A Spec-Tests.package/SearchableListTest.class/instance/running/classToTest.st A Spec-Tests.package/SearchableListTest.class/instance/tests/testFiltering.st A Spec-Tests.package/SearchableTreeTest.class/README.md A Spec-Tests.package/SearchableTreeTest.class/definition.st A Spec-Tests.package/SearchableTreeTest.class/instance/running/classToTest.st M Spec-Tests.package/SpecFocusOrderTest.class/definition.st M Spec-Tests.package/SpecTestCase.class/README.md M Spec-Tests.package/SpecTestCase.class/definition.st A Spec-Tests.package/SpecTestCase.class/instance/running/openInstance_.st M Spec-Tests.package/TestAutoFractionComputation.class/definition.st M Spec-Tests.package/TestingComposableModel.class/README.md M Spec-Tests.package/TestingComposableModel.class/definition.st A Spec-Tests.package/TextInputFieldModelTest.class/README.md A Spec-Tests.package/TextInputFieldModelTest.class/definition.st A Spec-Tests.package/TextInputFieldModelTest.class/instance/running/classToTest.st R Spec-Tests.package/TextModelTest.class/instance/running/initText.st A Spec-Tests.package/TextModelTest.class/instance/running/initializationText.st M Spec-Tests.package/TextModelTest.class/instance/tests/testSelectAll.st Log Message: ----------- 60162 18836 Second cleaning of Spec-Polywidgets and adding test https://pharo.fogbugz.com/f/cases/18836 18845 Move MIMEHeaderValue from Mail to MIME package https://pharo.fogbugz.com/f/cases/18845 18749 QA v3.2.1 https://pharo.fogbugz.com/f/cases/18749 http://files.pharo.org/image/60/60162.zip

Aug. 2, 2016