- Pharo-dev - lists.pharo.org

Spec wiring

by Yuriy Tymchuk

Hi guys, I need a little help to understand how spec works. Iâve encountered a problem, that when all children nodes of a tree are checked, the parent node remains partially checked instead of going fully checked. Iâve tried to figure out how to work with that, but failed. Any suggestions? Uko

Aug. 29, 2014

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

by Sven Van Caekenberghe

Nice work, thanks Torsten ! On 29 Aug 2014, at 10:41, Torsten Bergmann <astares(a)gmx.de> wrote: > 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] Future of Spec

by stepharo

+ 1 :) We are planning to integrate GT tools but this is at another level and the future is bright and shinning :) Stef On 28/8/14 21:39, kilon alios wrote: > Well as the discussion was in another thread , Spec is licensed as MIT > inside Pharo , the new GPL license seems to affect any present and > future contributions from Ben. So I will say yes it looks like Spec is > here to stay, I may not be a fan of Spec design but they are many > Pharoers out there that they are and since Pharo community is quite > democratic looks like Spec is here to stay. The Pharo team wont be > able to add in Pharo any GPL affected contributions of Ben ( assuming > Ben continuous to develop Spec which I doubt) but Pharoers can > continue to contribute to the Pharo MIT Spec . So it looks like the > effect is minimum if you exclude the fact we lost the most major > contributor to Spec. > > So far the idea is to push forward both Spec and Morphic and > personally I really like this idea as it lets people more options on > the GUI front which can be only good thing since anyone this way can > use the right tool for his or her own needs. It would also be a lot of > shame if Ben's hard work goes to waste even though he decided to give > up pharo, we have to respect his choice but also his work make sure > his effort don't go wasted as he built a tool that many people find > useful. > > So yes you can keep using Spec and I am sure we will all appreciate > any contribution you make to Spec :) > > > On Thu, Aug 28, 2014 at 10:15 PM, Martin Saurer > <martin.saurer(a)bluewin.ch <mailto:martin.saurer@bluewin.ch>> wrote: > > Dear all, > > A few weeks ago, I read about the dispute on Spec, which has > escalated, and as a result of that, Ben has left the > Pharo/Smalltalk community. It's always sad when a long term member > leaves, but live is going on. > > >From my (somewhat business minded) point of view one question is > currently unanswered: > Is there a future of Spec (without Ben)? > > I'm asking this because I'm the author of a web frontend engine > which can be bound to a programming language (like Pharo) to > create desktop-like web applications. Currently there is an > implementation for the J programming language as well as a rough > (but working) implementation for Pharo. My plans for the (far) > future is to bind the frontend engine to Pharo in a more elegant > way probably by extending Spec. So one may write a desktop > application in Spec, and a corresponding web GUI is automatically > created as well. > > So I'm currently a little unsure whether to go with Spec or going > back to the good old Polymorph. > > Is somebody of the core team able to clarify the situation? > > Many thanks in advance. > > Martin > > > >

Aug. 29, 2014

Re: [Pharo-dev] Future of Spec

by stepharo

Hi martin > Dear all, > > A few weeks ago, I read about the dispute on Spec, which has escalated, and as a result of that, Ben has left the Pharo/Smalltalk community. It's always sad when a long term member leaves, but live is going on. Indeed. > > From my (somewhat business minded) point of view one question is currently unanswered: > Is there a future of Spec (without Ben)? Yes. Definitively. :) It will move slower but we will. I started to clean Spec double unnecessary interpretation loop Ben was not alone behind Spec. The idea is coming from my experience writing application in VW. Johan also helped. So we do not stress much. Esteban has a new Spec interpreter on hold since a long long time. We cleaned with igor many methods to improve the GC stress when we introduced new version of LayoutFrame. And Esteban always wanted to do a pass on Spec. So we will plan that. If you look we are continuously making sure that the system will evolve nicely. some issues are planned on fogzbugs https://pharo.fogbugz.com/default.asp?13888 https://pharo.fogbugz.com/default.asp?13479 https://pharo.fogbugz.com/default.asp?13851#107599 > I'm asking this because I'm the author of a web frontend engine which can be bound to a programming language (like Pharo) to create desktop-like web applications. Super can you tell us more? Did you look at Phobos? > Currently there is an implementation for the J programming language as well as a rough (but working) implementation for Pharo. My plans for the (far) future is to bind the frontend engine to Pharo in a more elegant way probably by extending Spec. Excellent. We need clients and we will pay attention to you. > So one may write a desktop application in Spec, and a corresponding web GUI is automatically created as well. We want the same for Cocoa Widgets :) Esteban has a first draft of a brigde so we could define our interface in Spec and run the with Mars (the bridge) and get Cocoa widgets. > So I'm currently a little unsure whether to go with Spec or going back to the good old Polymorph. In fact it depends of your needs. Glenn started to use spec and went directly to morphic because some aspects of widgets are not covered by Spec (we should improve the coverage of the Morph API - color, selection....). Now the API of polymorph is not really good because widget creation api should be widget class and not UITheme. So I started to see how we could improve the situation and the first step is that every widgets with labels should be font parametrized and access a theme. Then the API will be migrated from UI to the widgets. I will restart to work on that after 15 of october (or before if I finish my current proposal writing). > > Is somebody of the core team able to clarify the situation? Let me know if this is ok for you. > > Many thanks in advance. > > Martin > > > >

Aug. 29, 2014

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