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

Projects are slowly getting to live... and

by stepharo

they will change our lifes. In latest Pharo50 when you load a configuration from versionner or from the catalog and that you say to the system to create a group in nautilus (we should add a commandline handler too) you get a project (group) with all your packages together ready to work ;) Here I loaded the ConfigurationOfMetaBoardBoard and I got the following... There are certainly improvements to do but this is a nice rethinking of groups (in fact I always wanted them like that but nautilus got them differently). So when you are a nice guy using configuration you will automatically get your nice projects at the top and you can work fast. We can imagine that the groups could also get smarter and do a lot of automatic things for us. Stef

Aug. 16, 2015

Re: [Pharo-dev] 16216 Default values in NECPreferences are not initilized right

by Nicolai Hess

2015-08-16 15:38 GMT+02:00 Merwan Ouddane <merwanouddane(a)gmail.com>: > Was the NECPreferences>>defaultPopupDelay in the post script ? > > > No, but your class initialization uses the default popup delay, it should work if we now just call the postcript. (better solution would be to add the enable/smart char/..../ settings in the class init. > On 16/08/2015 14:25, Merwan Ouddane wrote: > >> This is really weird, in the initialization the NEC was disabled by >> default, I did not changed that .... >> >> And even if the default value for the pop-up to appear was 200, in a >> fresh image it was at 500, coming from hell U.u >> >> Merwan >> >> On 16/08/2015 10:55, stepharo wrote: >> >>> Thanks. Can you open a new issue? >>> Merwan you will have to revisit your code. >>> >>> Stef >>> >>> Le 15/8/15 22:53, Nicolai Hess a Ã©crit : >>> >>>> This is not good. Somehow this disables NEC. >>>> And resets many other NEC settings, for example >>>> if you just enables code complation again, you still don't have >>>> the smart characters (-> inserting matchin "or ) or } ...) >>>> >>>> >>> >>> >> > >

Aug. 16, 2015

Re: [Pharo-dev] 16216 Default values in NECPreferences are not initilized right

by Merwan Ouddane

Was the NECPreferences>>defaultPopupDelay in the post script ? On 16/08/2015 14:25, Merwan Ouddane wrote: > This is really weird, in the initialization the NEC was disabled by > default, I did not changed that .... > > And even if the default value for the pop-up to appear was 200, in a > fresh image it was at 500, coming from hell U.u > > Merwan > > On 16/08/2015 10:55, stepharo wrote: >> Thanks. Can you open a new issue? >> Merwan you will have to revisit your code. >> >> Stef >> >> Le 15/8/15 22:53, Nicolai Hess a Ã©crit : >>> This is not good. Somehow this disables NEC. >>> And resets many other NEC settings, for example >>> if you just enables code complation again, you still don't have >>> the smart characters (-> inserting matchin "or ) or } ...) >>> >> >> >

Aug. 16, 2015

Re: [Pharo-dev] 16216 Default values in NECPreferences are not initilized right

by Merwan Ouddane

This is really weird, in the initialization the NEC was disabled by default, I did not changed that .... And even if the default value for the pop-up to appear was 200, in a fresh image it was at 500, coming from hell U.u Merwan On 16/08/2015 10:55, stepharo wrote: > Thanks. Can you open a new issue? > Merwan you will have to revisit your code. > > Stef > > Le 15/8/15 22:53, Nicolai Hess a Ã©crit : >> This is not good. Somehow this disables NEC. >> And resets many other NEC settings, for example >> if you just enables code complation again, you still don't have >> the smart characters (-> inserting matchin "or ) or } ...) >> > >

Aug. 16, 2015

[pharo-project/pharo-core] 1234a1: 50235

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 1234a1f9d0fa4cbdf8d10c2659056230ded115d6 https://github.com/pharo-project/pharo-core/commit/1234a1f9d0fa4cbdf8d10c26… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-08-16 (Sun, 16 Aug 2015) Changed paths: M BaselineOfQualityAssistant.package/BaselineOfQualityAssistant.class/instance/api projectSpec/baseline_.st M ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/symbolic versions/stable_.st A ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v1%5F2%5F2_.st M ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/symbolic versions/stable_.st A ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F4%5F1_.st M Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - variables/testSetLinkOnClassVariable.st M Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - variables/testSetLinkOnClassVariableAndUninstall.st M Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - variables/testSetLinkOnGlobalVariable.st M Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - variables/testSetLinkOnGlobalVariableAndUninstall.st R Reflectivity.package/LinkWrapperClassVariable.class/README.md R Reflectivity.package/LinkWrapperClassVariable.class/definition.st R Reflectivity.package/LinkWrapperClassVariable.class/instance/accessing/links.st R Reflectivity.package/LinkWrapperClassVariable.class/instance/accessing/setLink_.st R Reflectivity.package/LinkWrapperClassVariable.class/instance/accessing/wrappedVariable.st R Reflectivity.package/LinkWrapperClassVariable.class/instance/accessing/wrappedVariable_.st R Reflectivity.package/LinkWrapperClassVariable.class/instance/installing/removeLink_.st R Reflectivity.package/LinkWrapperClassVariable.class/instance/installing/uninstall.st R Reflectivity.package/LinkWrapperClassVariable.class/instance/reflective operations/doesNotUnderstand_.st R Reflectivity.package/LinkWrapperGlobal.class/README.md R Reflectivity.package/LinkWrapperGlobal.class/definition.st R Reflectivity.package/LinkWrapperGlobal.class/instance/accessing/links.st R Reflectivity.package/LinkWrapperGlobal.class/instance/accessing/setLink_.st R Reflectivity.package/LinkWrapperGlobal.class/instance/accessing/wrappedVariable.st R Reflectivity.package/LinkWrapperGlobal.class/instance/accessing/wrappedVariable_.st R Reflectivity.package/LinkWrapperGlobal.class/instance/installing/removeLink_.st R Reflectivity.package/LinkWrapperGlobal.class/instance/installing/uninstall.st R Reflectivity.package/LinkWrapperGlobal.class/instance/reflective operations/doesNotUnderstand_.st R Reflectivity.package/extension/ClassVariable/instance/asWrapperFor_.st R Reflectivity.package/extension/ClassVariable/instance/link_.st R Reflectivity.package/extension/GlobalVariable/instance/asWrapperFor_.st R Reflectivity.package/extension/GlobalVariable/instance/link_.st A Reflectivity.package/extension/LiteralVariable/instance/clearReflectivityAnnotations.st M Reflectivity.package/extension/LiteralVariable/instance/link_.st A Reflectivity.package/extension/LiteralVariable/instance/links.st A Reflectivity.package/extension/LiteralVariable/instance/removeLink_.st A Renraku.package/ReEngine.class/class/actions/reset.st A Renraku.package/ReEngine.class/class/cleanup/cleanUp.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50234.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50235.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50234.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50235.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Slot-Tests.package/SlotTest.class/README.md A Slot-Tests.package/SlotTest.class/definition.st A Slot-Tests.package/SlotTest.class/instance/testing - properties/testPropertyAtPut.st A Slot-Tests.package/SlotTest.class/instance/testing - properties/testRemoveProperty.st A Slot.package/LiteralVariable.class/instance/properties/propertyAt_ifAbsentPut_.st M Slot.package/LiteralVariable.class/instance/properties/propertyAt_put_.st M Slot.package/LiteralVariable.class/instance/properties/removePropertiesIfEmpty.st A Slot.package/Slot.class/class/class initialization/initialize.st A Slot.package/Slot.class/class/class initialization/initializeProperties.st M Slot.package/Slot.class/definition.st A Slot.package/Slot.class/instance/properties/ensureProperties.st A Slot.package/Slot.class/instance/properties/properties.st A Slot.package/Slot.class/instance/properties/propertyAt_.st A Slot.package/Slot.class/instance/properties/propertyAt_ifAbsent_.st A Slot.package/Slot.class/instance/properties/propertyAt_put_.st A Slot.package/Slot.class/instance/properties/removePropertiesIfEmpty.st A Slot.package/Slot.class/instance/properties/removeProperty_.st A Slot.package/Slot.class/instance/properties/removeProperty_ifAbsent_.st Log Message: ----------- 50235 16221 ReEngine needs a #reset and #cleanUp method https://pharo.fogbugz.com/f/cases/16221 16224 Property API for Slots https://pharo.fogbugz.com/f/cases/16224 16226 Use the new property API on Globals when setting a link: https://pharo.fogbugz.com/f/cases/16226 http://files.pharo.org/image/50/50235.zip

Aug. 16, 2015

[pharo-project/pharo-core]

by GitHub

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

Aug. 16, 2015

Re: [Pharo-dev] some questions about bloc

by Andrei Chis

Feedback is always welcomed :) Still in the brick repo there are, at the moment, quite some sub-projects/experiments. We are working now on making a better description for what is already in a more advanced state. For example the logic for skin, styes and theme modules is in a good state. Cheers, Andrei On Sat, Aug 15, 2015 at 11:59 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > Are you interested in some feedback for brick, or is it in a too early > stage? > > 2015-08-10 12:36 GMT+02:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: > >> Hi Nicolai, >> >> Thanks for looking into this :) Hierarchy will be optimised. Basically >> EnclosedView will gone - ProtoView will be a composition, this will remove >> code duplication and simplify addition of new functionality. After that >> rounded rectangle and rectangle will be merged. So in the end hierarchy >> will be BlProtoView -> BlView -> BlRectangle -> BrStringView -> >> BrButtonView which is simple enough. >> >> As Stephan said theme just provides default values and also skin for >> morph. Skin provides view and different styles for states like hovered, >> pressed, active, focused, disabled and others. >> >> Summarizing, with event listener any arbitrary morph can get dynamic >> behaviour on events, with skins any arbitrary morph can be deeply styled. >> >> Maybe it makes sense to move theme from BlProtoView to BlMorph. >> >> Cheers, >> Alex >> On Aug 9, 2015 9:57 PM, "Nicolai Hess" <nicolaihess(a)web.de> wrote: >> >>> >>> >>> 2015-08-09 20:17 GMT+02:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: >>> >>>> Hi >>>> >>> Thanks for your response. >>> >>> >>>> Animation was copied from other project and has nothing to do with >>>> Bloc. However, it is still there for a moment. BTW, example on the class >>>> side is still morphic. >>>> >>> >>> Yes, but it only works in a bloc world >>> >>> >>>> Yes, it does not make any sense to theme CircleView and ImageView, but >>>> it makes sense to theme their subclasses, like BrButtonView. Theming >>>> mechanism is not integrated in Bloc for now. >>>> >>> >>> But why dont we put this into a BlThemeableView ? >>> All subclasses of BlProtoView that want to support color or fillstyles, >>> now have a theme property too. >>> Why do they need a color property if the color is theme-dependent. >>> >>> Btw. what is that strange hierarchy for BrButtonView: >>> BlProtoView -> BlView -> BlEnclosedView -> BlRectangleView -> >>> BlRoundedRectangleView -> BrRectangleView -> BrStringView -> BrButtonView >>> A BlRectangleView, a RoundedRectangleView and a BrRectangleView? >>> >>> I think I don't understand bloc >>> >>> >>> Cheers, >>>> Alex >>>> On Aug 9, 2015 7:29 PM, "Nicolai Hess" <nicolaihess(a)web.de> wrote: >>>> >>>>> BlAlarmQueue >>>>> - split into two classes? >>>>> Queue : managing the add/remove/sort >>>>> Scheduler : process the Alarms >>>>> - alarm/alarmqueue both accessing and check the time "Time now" >>>>> I would put both checks to, either the alarm OR the queue/scheduler. >>>>> And don't use "Time now" explicit, if we put this behind a method >>>>> call, we >>>>> can easily create alarm queue mocs for unit tests. >>>>> - readding periodic alarms: shouldn't this be done by the alarm itself >>>>> - the queue should not care, whether a alarm is periodic. >>>>> >>>>> Some alarm examples put the queue into the morphs property dictionary. >>>>> I could find out why >>>>> this is necessary. >>>>> >>>>> >>>>> Layout: >>>>> Box/Column/Row Layout and corresponding cells define a double linked >>>>> list, we already >>>>> have a DoubleLinkedList, can we use the DoubleLinkedList instead of >>>>> reimplmenting this >>>>> on the layout/cells? >>>>> >>>>> Tablelayout: is this "work in progress" or abandoned? Currently it >>>>> shares much code with >>>>> the BoxLayout, but it does not look like it is working. >>>>> >>>>> Theming: >>>>> #theme is a property of BlProtoView - isn't this to low level for >>>>> defining theming support? >>>>> How would you theme a CircleView or an ImageView? >>>>> >>>>> >>>>> Animation: >>>>> what are all these "Logics"? >>>>> animationLogic >>>>> toLogic >>>>> stepLogic and steppedLogic(!?) >>>>> ifLogic .... >>>>> >>>>> Is this a software pattern ? I have never seen this before. >>>>> (For example we use "sortBlock" but not "sortLogic"). >>>>> How about ValueHolder or good old "Block". >>>>> >>>>> And "ifLogic" sounds like a condition, why don't we name it. ... >>>>> condition? >>>>> And putting all this "logic" into one animation class scares me. >>>>> >>>>> >>>>> About the class comment syntax: >>>>> - is this pillar syntax? I think this is difficult to read. Do you use >>>>> that syntax, because we >>>>> want to use a pillar as comment text and build a renderer for this or >>>>> is it to share comments between class comments and the bloc doc book, >>>>> easily? >>>>> >>>>> I can help with documenting the classes but I find it difficult to see >>>>> which parts of bloc >>>>> are just tests/proof of concept or are supposed to be in the final >>>>> version. Maybe I miss the big picture? >>>>> >>>>> >>>>> nicolai >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>> >

Aug. 16, 2015

Re: [Pharo-dev] some questions about bloc

by Aliaksei Syrel

Yes, shoot :) On Sun, Aug 16, 2015 at 10:54 AM, stepharo <stepharo(a)free.fr> wrote: > > > > Are you interested in some feedback for brick, or is it in a too early > stage? > > > please. > > > 2015-08-10 12:36 GMT+02:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: > >> Hi Nicolai, >> >> Thanks for looking into this :) Hierarchy will be optimised. Basically >> EnclosedView will gone - ProtoView will be a composition, this will remove >> code duplication and simplify addition of new functionality. After that >> rounded rectangle and rectangle will be merged. So in the end hierarchy >> will be BlProtoView -> BlView -> BlRectangle -> BrStringView -> >> BrButtonView which is simple enough. >> >> As Stephan said theme just provides default values and also skin for >> morph. Skin provides view and different styles for states like hovered, >> pressed, active, focused, disabled and others. >> >> Summarizing, with event listener any arbitrary morph can get dynamic >> behaviour on events, with skins any arbitrary morph can be deeply styled. >> >> Maybe it makes sense to move theme from BlProtoView to BlMorph. >> >> Cheers, >> Alex >> On Aug 9, 2015 9:57 PM, "Nicolai Hess" <nicolaihess(a)web.de> wrote: >> >>> >>> >>> 2015-08-09 20:17 GMT+02:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: >>> >>>> Hi >>>> >>> Thanks for your response. >>> >>> >>>> Animation was copied from other project and has nothing to do with >>>> Bloc. However, it is still there for a moment. BTW, example on the class >>>> side is still morphic. >>>> >>> >>> Yes, but it only works in a bloc world >>> >>> >>>> Yes, it does not make any sense to theme CircleView and ImageView, but >>>> it makes sense to theme their subclasses, like BrButtonView. Theming >>>> mechanism is not integrated in Bloc for now. >>>> >>> >>> But why dont we put this into a BlThemeableView ? >>> All subclasses of BlProtoView that want to support color or fillstyles, >>> now have a theme property too. >>> Why do they need a color property if the color is theme-dependent. >>> >>> Btw. what is that strange hierarchy for BrButtonView: >>> BlProtoView -> BlView -> BlEnclosedView -> BlRectangleView -> >>> BlRoundedRectangleView -> BrRectangleView -> BrStringView -> BrButtonView >>> A BlRectangleView, a RoundedRectangleView and a BrRectangleView? >>> >>> I think I don't understand bloc >>> >>> >>> Cheers, >>>> Alex >>>> On Aug 9, 2015 7:29 PM, "Nicolai Hess" <nicolaihess(a)web.de> wrote: >>>> >>>>> BlAlarmQueue >>>>> - split into two classes? >>>>> Queue : managing the add/remove/sort >>>>> Scheduler : process the Alarms >>>>> - alarm/alarmqueue both accessing and check the time "Time now" >>>>> I would put both checks to, either the alarm OR the queue/scheduler. >>>>> And don't use "Time now" explicit, if we put this behind a method >>>>> call, we >>>>> can easily create alarm queue mocs for unit tests. >>>>> - readding periodic alarms: shouldn't this be done by the alarm itself >>>>> - the queue should not care, whether a alarm is periodic. >>>>> >>>>> Some alarm examples put the queue into the morphs property dictionary. >>>>> I could find out why >>>>> this is necessary. >>>>> >>>>> >>>>> Layout: >>>>> Box/Column/Row Layout and corresponding cells define a double linked >>>>> list, we already >>>>> have a DoubleLinkedList, can we use the DoubleLinkedList instead of >>>>> reimplmenting this >>>>> on the layout/cells? >>>>> >>>>> Tablelayout: is this "work in progress" or abandoned? Currently it >>>>> shares much code with >>>>> the BoxLayout, but it does not look like it is working. >>>>> >>>>> Theming: >>>>> #theme is a property of BlProtoView - isn't this to low level for >>>>> defining theming support? >>>>> How would you theme a CircleView or an ImageView? >>>>> >>>>> >>>>> Animation: >>>>> what are all these "Logics"? >>>>> animationLogic >>>>> toLogic >>>>> stepLogic and steppedLogic(!?) >>>>> ifLogic .... >>>>> >>>>> Is this a software pattern ? I have never seen this before. >>>>> (For example we use "sortBlock" but not "sortLogic"). >>>>> How about ValueHolder or good old "Block". >>>>> >>>>> And "ifLogic" sounds like a condition, why don't we name it. ... >>>>> condition? >>>>> And putting all this "logic" into one animation class scares me. >>>>> >>>>> >>>>> About the class comment syntax: >>>>> - is this pillar syntax? I think this is difficult to read. Do you use >>>>> that syntax, because we >>>>> want to use a pillar as comment text and build a renderer for this or >>>>> is it to share comments between class comments and the bloc doc book, >>>>> easily? >>>>> >>>>> I can help with documenting the classes but I find it difficult to see >>>>> which parts of bloc >>>>> are just tests/proof of concept or are supposed to be in the final >>>>> version. Maybe I miss the big picture? >>>>> >>>>> >>>>> nicolai >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>> > >

Aug. 16, 2015

Removing default OK/CANCEL buttons from PluggableDialogWindow

by Jigyasa Grover

Hi ! I am using *PluggableDialogWindow* to display search results for my first Pharo application namely *sQuick* (github.com/jig08/sQuick_new) I wish to remove the default OK/CANCEL buttons. Further details at https://github.com/jig08/sQuick_new/issues/24. Help appreciated :) Thanks Jigyasa

Aug. 16, 2015

Re: [Pharo-dev] 16216 Default values in NECPreferences are not initilized right

by stepharo

Thanks. Can you open a new issue? Merwane you will have to revisit your code. Stef Le 15/8/15 22:53, Nicolai Hess a Ã©crit : > This is not good. Somehow this disables NEC. > And resets many other NEC settings, for example > if you just enables code complation again, you still don't have > the smart characters (-> inserting matchin "or ) or } ...) >

Aug. 16, 2015