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

Re: [Pharo-dev] Issue 13941 [FEATURE]: Configuration Browser: Switch to Any Repository

by Torsten Bergmann

Hi, no - there was only a context menu action to "Switch repository" so far (for instance when you are in Pharo 4 you may still like to access repository of Pharo 3 to load, etc). I fixed the issue by adding an "Add repository" functionality. Details and screenshot on https://pharo.fogbugz.com/f/cases/13941/FEATURE-Configuration-Browser-Switc… Have fun T. Â Â Gesendet:Â Freitag, 29. August 2014 um 08:50 Uhr Von:Â "phil(a)highoctane.be" <phil(a)highoctane.be> An:Â "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org> Betreff:Â Re: [Pharo-dev] Issue 13941 [FEATURE]: Configuration Browser: Switch to Any Repository +1 I remember that this can be done by some weird modified click on the configuration browser UI. Phil Le 29 aoÃ»t 2014 08:35, "Sven Van Caekenberghe" <sven(a)stfx.eu> a Ã©crit :+1 And maybe remember manually entered URLs. On 29 Aug 2014, at 02:56, Sean P. DeNigris <sean@clipperadams.com[sean@clipperadams.com]> wrote: > It would be great to use the Configuration Browser on one's own meta reposâ¦ > > https://pharo.fogbugz.com/default.asp?13941[https://pharo.fogbugz.com/defau… > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Issue-13941-FEATURE-Configuration-Browser-Switch-to-A… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > Â

Aug. 29, 2014

Re: [Pharo-dev] Spec license

by stepharo

Hi skri Glenn is also working for a company and building an alternative to Spec to support mobile and others. What is important is that - we should continue to clean and improve spec and its documentation. - understand and push alternative solutions - so I suggest that you should make sure that other people can use what you are doing and continue to push it. Nothing is curved on stones. I clean Morphic regularly but I will be happy to through away all my work if something better is coming (bloc for example). Stef On 28/8/14 15:21, S Krish wrote: > > Will there be any interest in alternative declarative framework, > mostly fleshed out, worked in Pharo 2.0 / with little fixes for > FileDirectory et als in 3.0 > > http://skrishnamachari.wordpress.com/2012/01/31/pharo-application-framework… > > I can push this in with the required MIT license sign off as reqd. > > More importantly, move this framework to a more refactored cleaner > state if there is a slight interest in alternatives. > > > > On Thu, Aug 28, 2014 at 5:51 PM, phil(a)highoctane.be > <mailto:phil@highoctane.be> <phil(a)highoctane.be > <mailto:phil@highoctane.be>> wrote: > > No, it doesn't. > > We can improve Spec in the core, why wouldn't we be able to? > We use it in a lot of the tools, so, there are plenty of samples > and documentation exists. > > One can make sense of what's going on under the hood. > > Have a look at: (this is for Pharo 3.0) > > SpecInterpreter>>interpretASpec:selector: and ComposableModel + > NewValueHolder. > WindowModel is interesting to look into as well. > > The "famous" NewValueHolder is of interest too. > > > then implementors of defaultSpec provide a lot of specs to give to > the SpecInterpreter. > > Then one wants to look into the Spec-MorphicAdapters to see how > Spec maps its view on things with underlying Morphs (e.g. check > the MorphicDiffAdapter). > > We can only benefit by caring about this piece on our side, as > there is tremendous potential in being able to change the > underlying system (e.g. from Morphic to Bloc for example) in a > piecemeal way, without breaking all of the tools. > > Phil > > > On Thu, Aug 28, 2014 at 1:19 PM, Henrik Johansen > <henrik.s.johansen(a)veloxit.no > <mailto:henrik.s.johansen@veloxit.no>> wrote: > > Does it really matter? > If the external repository gets successfully relicensed, or > Benjamin publishes new improvements as a separate, > GPL-licensed change set, the end result is the same; > no improvement he makes will make its way back into the > versions in Core. > > I may not know his reasons, but I can certainly respect his > wish that no further contributions are included in a core > distribution. > > Whether to maintain/improve the current, MIT-licensed versions > in Core without him, or unload it all and point potential > users to the external library, is a separate decision. > Though, from previous attempts, Iâd say the chances of success > of an external UI-builder framework seeing actual use are > rather slim. > > Cheers, > Henry > > On 28 Aug 2014, at 12:16 , Stephan Eggermont <stephan(a)stack.nl > <mailto:stephan@stack.nl>> wrote: > > > > https://github.com/spec-framework/spec/commit/07ea83ca50523b4a912e363ff2f39… > > > > I think the license might need further improvements. > > I've taken a look at the commit history, and it looks > > to me like there is a licensing problem there. > > I am no lawyer, so don't know what the > > exact consequences of that are. > > > > The (MIT licensed) Pharo code was copied > > to the repository without including the copyright > > notice, as is required by the MIT license. > > > > For new contributions, you now have the > > license agreements, and with git it is > > perfectly clear what is new, and under > > the new license, and what is old, and > > can therefore also be used under the > > old license. And AFAIK MIT license > > is compatible with GPL. > > > > I have no clue as to the license status of > > changes between the copying and the > > relicensing. > > > > Of course copyright holding contributors can > > decide to relicense. The contributors to the > > Spec-* packages in the Pharo/Pharo30 repo > > seem to be: > > > > AlainPlantec > > AndreiChis > > BenComan > > BenjaminVanRyseghem > > BernardoContreras > > CamilloBruni > > CamilleTeruel > > ChristopheDemarey > > ClementBera > > DamienCassou > > ErwanDouaille > > EstebanLorenzano > > GabrielOmarCotelli > > GuillermoPolito > > HernanMoralesDurand > > IgorStasenko > > LeoGassman > > MarcusDenker > > MartinDias > > NicolaiHess > > PabloHerrero > > PavelKrivanek > > PhilippeBack > > RobertoMinelli > > SeanDeNigris > > SebastianTleye > > StephaneDucasse > > SvenVanCaekenberghe > > TorstenBergmann > > TudorGirba > > YuriyTymchuk > > > > Stephan > > > > > > > > > > >

Aug. 29, 2014

Re: [Pharo-dev] Spec license

by stepharo

Hi phil I agree. I cleaned the MorphicAdapters during a recesss from project writing. I should finish the last two: menu and menu group. Stef On 28/8/14 14:21, phil(a)highoctane.be wrote: > No, it doesn't. > > We can improve Spec in the core, why wouldn't we be able to? > We use it in a lot of the tools, so, there are plenty of samples and > documentation exists. > > One can make sense of what's going on under the hood. > > Have a look at: (this is for Pharo 3.0) > > SpecInterpreter>>interpretASpec:selector: and ComposableModel + > NewValueHolder. > WindowModel is interesting to look into as well. > > The "famous" NewValueHolder is of interest too. > > > then implementors of defaultSpec provide a lot of specs to give to the > SpecInterpreter. > > Then one wants to look into the Spec-MorphicAdapters to see how Spec > maps its view on things with underlying Morphs (e.g. check the > MorphicDiffAdapter). > > We can only benefit by caring about this piece on our side, as there > is tremendous potential in being able to change the underlying system > (e.g. from Morphic to Bloc for example) in a piecemeal way, without > breaking all of the tools. > > Phil > > > On Thu, Aug 28, 2014 at 1:19 PM, Henrik Johansen > <henrik.s.johansen(a)veloxit.no <mailto:henrik.s.johansen@veloxit.no>> > wrote: > > Does it really matter? > If the external repository gets successfully relicensed, or > Benjamin publishes new improvements as a separate, GPL-licensed > change set, the end result is the same; > no improvement he makes will make its way back into the versions > in Core. > > I may not know his reasons, but I can certainly respect his wish > that no further contributions are included in a core distribution. > > Whether to maintain/improve the current, MIT-licensed versions in > Core without him, or unload it all and point potential users to > the external library, is a separate decision. > Though, from previous attempts, Iâd say the chances of success of > an external UI-builder framework seeing actual use are rather slim. > > Cheers, > Henry > > On 28 Aug 2014, at 12:16 , Stephan Eggermont <stephan(a)stack.nl > <mailto:stephan@stack.nl>> wrote: > > > > https://github.com/spec-framework/spec/commit/07ea83ca50523b4a912e363ff2f39… > > > > I think the license might need further improvements. > > I've taken a look at the commit history, and it looks > > to me like there is a licensing problem there. > > I am no lawyer, so don't know what the > > exact consequences of that are. > > > > The (MIT licensed) Pharo code was copied > > to the repository without including the copyright > > notice, as is required by the MIT license. > > > > For new contributions, you now have the > > license agreements, and with git it is > > perfectly clear what is new, and under > > the new license, and what is old, and > > can therefore also be used under the > > old license. And AFAIK MIT license > > is compatible with GPL. > > > > I have no clue as to the license status of > > changes between the copying and the > > relicensing. > > > > Of course copyright holding contributors can > > decide to relicense. The contributors to the > > Spec-* packages in the Pharo/Pharo30 repo > > seem to be: > > > > AlainPlantec > > AndreiChis > > BenComan > > BenjaminVanRyseghem > > BernardoContreras > > CamilloBruni > > CamilleTeruel > > ChristopheDemarey > > ClementBera > > DamienCassou > > ErwanDouaille > > EstebanLorenzano > > GabrielOmarCotelli > > GuillermoPolito > > HernanMoralesDurand > > IgorStasenko > > LeoGassman > > MarcusDenker > > MartinDias > > NicolaiHess > > PabloHerrero > > PavelKrivanek > > PhilippeBack > > RobertoMinelli > > SeanDeNigris > > SebastianTleye > > StephaneDucasse > > SvenVanCaekenberghe > > TorstenBergmann > > TudorGirba > > YuriyTymchuk > > > > Stephan > > > > > > > > > >

Aug. 29, 2014

Re: [Pharo-dev] Phexample: API Change Proposal (was Phexample: Image Destroying Bug)

by Stefan Marr

Hi Sean: On 29 Aug 2014, at 03:17, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Stefan Marr-3 wrote >>> It doesnât look like it has public write access. >> >> Guess the error is between chair and screen. I probably forgot to save the >> change or somethingâ¦ >> Now it should be enabled. > > It may have reverted during the recent sthub problems. Would you try one > more time, or add me as a developer? Thanks again. I added you. Best regards Stefan -- Stefan Marr INRIA Lille - Nord Europe http://stefan-marr.de/research/

Aug. 29, 2014

>>#next: SocketStream and other oddities

by Holger Hans Peter Freyther

Hi, while writing some SMS PDU parsing code I stumbled across an "oddity" I have not seen with GNU Smalltalk. When calling the >>#next: selector on a ReadStream and the number of elements I need are not available, Pharo will return less or an empty collection. This means I write code like this: | id len | id := stream next: 4 id size = 4 ifFalse: [^self reportError: 'Short read']. len := stream next: 4 len size = 4 ifFalse: [^self reportError: 'Len not available']. Besides the aesthetic issue it is getting worse when the SocketStream class is in use. So now >>#next: 4 can return nil as well. But naively I wrote code like this: [ | msg | msg := ThingParser parse: aSocketStream. ] on: ConnectionClosed do: [:e | self logStuff: e. self scheduleReconnect ] So to make the above code work with the SocketStream I need to write the following. I had a quick look at why the ConnectionClosed is swallowed and found the comment to allow partial reads out of a dead socket. | id len | id := stream next: 4. id ifNil: [^self reportError: 'Short read']. len := stream next: 4 len ifNil: [^self reportError: 'Short read']. len size = 4 ifFalse: [^self reportError: 'Len not available'] In GNU Smalltalk there is EndOfStream which is a subclass of Notification and the above code boils down to: [ | id len | id := stream next: 4. len := stream next: 4. ] on: EndOfStream do: [:e | self logStuff: e. self scheduleReconnect. ]. So couldn't the >>#readInto:startingAt:count: selector of SocketStream do something like GNU Smalltalk and give an EndOfStream notification? [self receiveData: anInteger] on: ConnectionClosed do:[:ex| EndOfStream signalOn: self. ex return ]. kind regards holger

Aug. 29, 2014

Re: [Pharo-dev] Issue 13941 [FEATURE]: Configuration Browser: Switch to Any Repository

by phil＠highoctane.be

+1 I remember that this can be done by some weird modified click on the configuration browser UI. Phil Le 29 aoÃ»t 2014 08:35, "Sven Van Caekenberghe" <sven(a)stfx.eu> a Ã©crit : > +1 > > And maybe remember manually entered URLs. > > On 29 Aug 2014, at 02:56, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > > It would be great to use the Configuration Browser on one's own meta > reposâ¦ > > > > https://pharo.fogbugz.com/default.asp?13941 > > > > > > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: > http://forum.world.st/Issue-13941-FEATURE-Configuration-Browser-Switch-to-A… > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > >

Aug. 29, 2014

Re: [Pharo-dev] Issue 13941 [FEATURE]: Configuration Browser: Switch to Any Repository

by Sven Van Caekenberghe

+1 And maybe remember manually entered URLs. On 29 Aug 2014, at 02:56, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > It would be great to use the Configuration Browser on one's own meta reposâ¦ > > https://pharo.fogbugz.com/default.asp?13941 > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Issue-13941-FEATURE-Configuration-Browser-Switch-to-A… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Aug. 29, 2014

Re: [Pharo-dev] Phexample: API Change Proposal (was Phexample: Image Destroying Bug)

by Sean P. DeNigris

Stefan Marr-3 wrote >> It doesnât look like it has public write access. > > Guess the error is between chair and screen. I probably forgot to save the > change or somethingâ¦ > Now it should be enabled. It may have reverted during the recent sthub problems. Would you try one more time, or add me as a developer? Thanks again. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Phexample-API-Change-Proposal-was-Phexample-Image-Des… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 29, 2014

Issue 13941 [FEATURE]: Configuration Browser: Switch to Any Repository

by Sean P. DeNigris

It would be great to use the Configuration Browser on one's own meta reposâ¦ https://pharo.fogbugz.com/default.asp?13941 ----- Cheers, Sean -- View this message in context: http://forum.world.st/Issue-13941-FEATURE-Configuration-Browser-Switch-to-A… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 29, 2014

Re: [Pharo-dev] Roadmap on tools?

by Craig Latta

> As far as I know no one has built anything more complex than a class > browser. I would say Spec was incapable of building a complex > interface of any kind. It's clumsy, developer-hostile, and counter- > intuitive. > > The whole Spec process of writing code in three different places is > the very definition of a /super pain in the asset/s. it is far less > intuitive to my mind than creating composite morphs. > > Progress on Spec is glacially slow - but that's not the problem. Spec > is profoundly misconceived and fundamentally flawed and offers > nothing over raw Morphic. The Spec model is simply not how anyone > would want to build an interface in 2014. I certainly would never use > it. Okay, but how do you really feel? :) I'm intrigued by the 2014 comment, though (which of course will look hilarious in 2015). How do people want to build interfaces in 2014? -C -- Craig Latta netjam.org +31 6 2757 7177 (SMS ok) + 1 415 287 3547 (no SMS)

Aug. 28, 2014