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

Fwd: RE: [Pharo-users] Porting Voss to Pharo

by stepharo

Hi Stef, Please see http://voss.logicarts.com/licensing I'm not a lawyer, so I can't say anything about the interpretation of GPLv3, except to comment without prejudice: As it is a complex subject, my intention was that users may prefer to negotiate a commercial licence with technical support, which may well be cheaper than the alternative legal services. I'm open to suggestions and negotiation, but I do need to monetise my time and effort - nobody paid me to write VOSS. Regards, John >-----Original Message----- >From: stepharo [mailto:stepharo@free.fr] >Sent: Saturday, March 07, 2015 8:57 AM >To: Any question about pharo is welcome; jc(a)logicarts.com >Subject: Re: [Pharo-users] Porting Voss to Pharo > >I think that the author of voss should reply. > >Stef > >Le 6/3/15 23:07, Stephan Eggermont a crit : >> On 06/03/15 16:16, stepharo wrote: >>> Hi guys >>> >>> if some of you are interested to drive porting VOSS to Pharo, let me >>> know John sent me the code and I can give it to you. >>> There is a dual license >>> - LGPL >>> - commercial >> >> What does LGPL mean for VOSS? At FOSDEM I talked with Bradley Kuhn of >> the FSF. It is something that has been on their to do list for a while >> now. In the 'strict' interpretation it is as viral as GPL for >> smalltalk code. >> >> Stephan >> >> >> >> > > >______________________________________________ >This email has been scanned by Netintelligence >http://www.netintelligence.com/email

March 10, 2015

Fwd: RE: [Pharo-users] Porting Voss to Pharo

by stepharo

-------- Message transfÃ©rÃ© -------- Sujet : RE: [Pharo-users] Porting Voss to Pharo Date : Sat, 7 Mar 2015 17:05:35 -0000 De : John Clapperton <jc(a)logicarts.com> Pour : 'stepharo' <stepharo(a)free.fr> Hi Stef, Just to let you know, I'm going into hospital on Tuesday for another operation on my eye, and probably won't be able to reply to emails for a week or so afterwards. Regards, John

March 10, 2015

Re: [Pharo-dev] PLEASE DO NOT COMMIT NEW FEATURES

by stepharo

make them green because - this is a good to spot potential bugs in Pharo - this also a good sign for the project health. stef > Hi, > > What should we do with the non-green builds? > > Cheers, > Doru > > > > On Mon, Mar 9, 2015 at 7:59 PM, Stephan Eggermont <stephan(a)stack.nl > <mailto:stephan@stack.nl>> wrote: > > On 09/03/15 17:39, Esteban Lorenzano wrote: > > (every year same fightâ¦) > > Please, please, pleaseâ¦ just bugfixes. > Otherwise we will never release. > > > +1 > > Here are some non-green builds: > https://ci.inria.fr/pharo-contribution/ > > Stephan > > > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

March 10, 2015

[pharo-project/pharo-core]

by GitHub

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

March 9, 2015

[pharo-project/pharo-core] f9bfbf: 40545

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: f9bfbf4d506b70370fffb0c2d0cafbbba03ada59 https://github.com/pharo-project/pharo-core/commit/f9bfbf4d506b70370fffb0c2… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-03-10 (Tue, 10 Mar 2015) Changed paths: R Collections-Abstract.package/ArrayedCollection.class/instance/objects from disk/restoreEndianness.st R Collections-Abstract.package/ArrayedCollection.class/instance/objects from disk/swapHalves.st R Collections-Streams.package/PositionableStream.class/instance/accessing/nextWordsInto_.st R Collections-Strings.package/ByteString.class/instance/converting/convertFromSystemString.st M Collections-Strings.package/Symbol.class/instance/converting/asMutator.st A CollectionsTests.package/StringTest.class/instance/testing - converting/testSubStrings.st M CollectionsTests.package/SymbolTest.class/instance/tests/testAsMutator.st A Graphics-Primitives.package/extension/ArrayedCollection/instance/restoreEndianness.st A Graphics-Primitives.package/extension/ArrayedCollection/instance/swapHalves.st A Graphics-Primitives.package/extension/PositionableStream/instance/nextWordsInto_.st A Multilingual-Languages.package/extension/ByteString/instance/convertFromSystemString.st M RecentSubmissions.package/RecentMessageList.class/instance/actions/revertLastMethodSubmission.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script544.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script545.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40544.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40545.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Slot.package/extension/SmalltalkImage/instance/classBuilder.st A Slot.package/extension/SystemDictionary/instance/declare_from_.st M Spec-Core.package/LabelModel.class/instance/deprecated-api/text_.st R Spec-Core.package/extension/Array/instance/generateSpecFormatArray.st R Spec-Core.package/extension/String/instance/generateSpecFormatArray.st M Spec-Tools.package/NewVersionBrowser.class/instance/accessing/displayStringsFor_.st R Spec-Tools.package/extension/String/instance/firstWord.st M System-Changes.package/ChangeSet.class/class/services/fileIntoNewChangeSet_.st A System-Platforms.package/extension/SmalltalkImage/instance/os.st A System-Platforms.package/extension/SmalltalkImage/instance/platform.st A System-Sound.package/Beeper.class/README.md A System-Sound.package/Beeper.class/class/beeping/beep.st A System-Sound.package/Beeper.class/class/beeping/beepPrimitive.st A System-Sound.package/Beeper.class/class/customize/clearDefault.st A System-Sound.package/Beeper.class/class/customize/default.st A System-Sound.package/Beeper.class/class/customize/newDefault.st A System-Sound.package/Beeper.class/class/customize/setDefault_.st A System-Sound.package/Beeper.class/class/private/primitiveBeep.st A System-Sound.package/Beeper.class/definition.st A System-Sound.package/Beeper.class/instance/play interface/play.st R System-Support.package/Beeper.class/README.md R System-Support.package/Beeper.class/class/beeping/beep.st R System-Support.package/Beeper.class/class/beeping/beepPrimitive.st R System-Support.package/Beeper.class/class/customize/clearDefault.st R System-Support.package/Beeper.class/class/customize/default.st R System-Support.package/Beeper.class/class/customize/newDefault.st R System-Support.package/Beeper.class/class/customize/setDefault_.st R System-Support.package/Beeper.class/class/private/primitiveBeep.st R System-Support.package/Beeper.class/definition.st R System-Support.package/Beeper.class/instance/play interface/play.st R System-Support.package/SmalltalkImage.class/instance/accessing/classBuilder.st R System-Support.package/SmalltalkImage.class/instance/os/os.st R System-Support.package/SmalltalkImage.class/instance/os/platform.st M System-Support.package/SmalltalkImage.class/instance/special objects/newSpecialObjectsArray.st R System-Support.package/SystemDictionary.class/instance/dictionary access/declare_from_.st R System-Support.package/SystemNavigation.class/instance/private/createMethodNamed_realParent_.st A System-Support.package/SystemNavigation.class/instance/query/createMethodNamed_realParent_.st M System-Support.package/VirtualMachine.class/instance/accessing/path.st M Text-Edition.package/TextEditor.class/instance/menu messages/changeStyle.st Log Message: ----------- 40545 15049 Move endianess methods from collections to graphics package https://pharo.fogbugz.com/f/cases/15049 15051 Remove Spec extension methods from String https://pharo.fogbugz.com/f/cases/15051 15059 Cleaning up System-Support https://pharo.fogbugz.com/f/cases/15059 15052 Remove dependency String -> LanguageConverter https://pharo.fogbugz.com/f/cases/15052 15103 return unchanged argument in asMutator if argument is a mutator https://pharo.fogbugz.com/f/cases/15103 http://files.pharo.org/image/40/40545.zip

March 9, 2015

Re: [Pharo-dev] PLEASE DO NOT COMMIT NEW FEATURES

by Tudor Girba

Hi, What should we do with the non-green builds? Cheers, Doru On Mon, Mar 9, 2015 at 7:59 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > On 09/03/15 17:39, Esteban Lorenzano wrote: > >> (every year same fightâ¦) >> >> Please, please, pleaseâ¦ just bugfixes. >> Otherwise we will never release. >> > > +1 > > Here are some non-green builds: > https://ci.inria.fr/pharo-contribution/ > > Stephan > > > > > -- www.tudorgirba.com "Every thing has its own flow"

March 9, 2015

Re: [Pharo-dev] latest GTools settings

by Tudor Girba

I opened an issue: https://pharo.fogbugz.com/f/cases/15104/Spotter-settings-should-also-appear… Cheers, Doru On Mon, Mar 9, 2015 at 11:01 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > The settings will be in the Settings Browser. It's a bug that it's not > there yet and it will be fixed until the release. > > But, the same settings are also accessible from the Spotter UI as it > relates to data being uploaded and people should be able to learn quickly > if their data is being shared or not and not have to dig to find that > information out. > > Cheers, > Doru > > > > On Mon, Mar 9, 2015 at 9:28 PM, stepharo <stepharo(a)free.fr> wrote: > >> Why everything is not simple. There is nice setting browser. Why do we >> need to have other mechanisms. >> Why just spotter and not all the other tools. >> Can we do something simple and consistent? >> >> Stef >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

March 9, 2015

Re: [Pharo-dev] latest GTools settings

by Tudor Girba

Hi, The settings will be in the Settings Browser. It's a bug that it's not there yet and it will be fixed until the release. But, the same settings are also accessible from the Spotter UI as it relates to data being uploaded and people should be able to learn quickly if their data is being shared or not and not have to dig to find that information out. Cheers, Doru On Mon, Mar 9, 2015 at 9:28 PM, stepharo <stepharo(a)free.fr> wrote: > Why everything is not simple. There is nice setting browser. Why do we > need to have other mechanisms. > Why just spotter and not all the other tools. > Can we do something simple and consistent? > > Stef > > -- www.tudorgirba.com "Every thing has its own flow"

March 9, 2015

Re: [Pharo-dev] valid name for an instance variable?

by Sean P. DeNigris

Marcus Denker-4 wrote >> is x: (with colon) a valid inst var name ? > no. Why complicate the system by special-handling illegal variable names? Just let the incorrect x: become the just-as-incorrect x::, no? Or am I missing something? ----- Cheers, Sean -- View this message in context: http://forum.world.st/valid-name-for-an-instance-variable-tp4810632p4810780… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 9, 2015

Re: [Pharo-dev] [Pharo4] RBEnvironment-based search is broken

by stepharo

Thanks for the list. Stef PS: may be I'm doing too many things :) Which issues are we talking about? I can have a look. > > 14230 <https://pharo.fogbugz.com/default.asp?14230> > Some rules aren't applied on the classside anymore > 14621 <https://pharo.fogbugz.com/default.asp?14621> > Some RBBrowserEnvironments don't work well with Metaclasses > > closed but related: > 14228 <https://pharo.fogbugz.com/default.asp?14228> > critic rules running on all methods of a class extended by a package > (closed) > 15077 <https://pharo.fogbugz.com/default.asp?15077> > CriticBrowser MNU Trait>>methodClass (closed) > > closed, related and part of the problem: > 14096 <https://pharo.fogbugz.com/default.asp?14096> > Rewrite lint rules to check classes and methods > 14098 <https://pharo.fogbugz.com/default.asp?14098> > allClassesAndTraits significantly different from allClassesAndTraitsDo: > > > And mailing list "discussions" > http://forum.world.st/RBEnvironments-allClasses-Traits-Meta-tp4796370.html > http://forum.world.st/What-is-a-Behavior-are-Traits-behavior-too-tp4804691.… > > > > Of course, implementorsOf: is broken because allClasses > does not returns the metaclasses. > > I like it when people "normalize" things :( > > > He asked for feedback on this. And as far as I know no one > complained. > > > Fair enough. > > Really need to have more test cases to cover things like that :) > > > > RBEnvironments are so nice, small but really powerfull > (refactoring/searching/validation). > I would like to get this right. > > > > Thierry > >

March 9, 2015