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

Re: [Pharo-dev] Adding a new catalog entry

by Nicolas Cellier

2014-03-17 10:15 GMT+01:00 Pharo4Stef <pharo4Stef(a)free.fr>: > > well we will have to clean and simplify all that in the future. >> This is why versionner should be good so that people use it and we can >> simplify the declarations. >> >> Stef >> >> > But I had the feeling that Versionner UI is currently very limited vs > Metacello options (especially w.r.t. cross dialect support) > > > > The problem is that metacello is too complex. :) > And the API could be better. > > Agree, see my other reply to Sven. An alternative is to - keep UI simple (mostly as it is now) by focusing onto single dialect/single dialect version - to automate the single dialect extract and cross dialect merge But maybe it's easier to say than do ;) > Or do you have a different POV, like only Pharo3.0 stuff should go to > MetaRepoForPharo3.0, and the ConfigurationOf... should be expunged from any > other dialect/version ? > > > For now this is ok to have multiple dialects in the metarepo because > people may want to have gemstone and squeak version. > Now for the core Pharo tool configruations should be as simple as possible > (RB, ...) > > Stef > > > >> >>> >>> Bye >>> T. >>> >>> *Gesendet:* Sonntag, 16. MÃ¤rz 2014 um 17:31 Uhr >>> *Von:* "Nicolas Cellier" <nicolas.cellier.aka.nice(a)gmail.com> >>> *An:* "Pharo Development List" <pharo-dev(a)lists.pharo.org> >>> *Betreff:* Re: [Pharo-dev] Adding a new catalog entry >>> >>> 2014-03-16 16:06 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>>> >>>> Nicolas, >>>> >>>> On 16 Mar 2014, at 10:08, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>> > To get access your StHub account, if you have any, should be part of >>>> the Pharo team, but I don't think I can do that. >>>> >>>> I now see that 'nice' is part of 'Pharo', so I think you should be able >>>> to save to MetaRepoForPharo30. >>>> >>> >>> >>> Thanks, I think I messed up when entering my credentials... >>> I have now published with a symbolic stable version. >>> >>> >>>> Sven >>> >>> >

March 17, 2014

Re: [Pharo-dev] Just a reminder

by Jan Vrany

On 17/03/14 09:45, Henrik Johansen wrote: >> >> Now how many do have to follow through all this? >> >> So well yes in the end it means not thinking about compatibility costs a >> lot thereafter.... >> > > Smalltalk os platformName -> works in Pharo 1.3, 1.4, 2.0, 3.0, Squeak 4.1 (in other words, the first new code release after relicensing effort). > > Smalltalk platformName -> works in all older version of Pharo/Squeak. > > While thereâs many places backwards compat could be better preserved, this is not one of themâ¦ > It is. There are other Smalltalks out there and most of them (maybe except GemStone?) have an object globally accessible under name #Smalltalk. So, Smalltalk platformName is the only sensible default as Friedrich pointed out. Best, Jan

March 17, 2014

Re: [Pharo-dev] Just a reminder

by Henrik Johansen

On 15 Mar 2014, at 8:05 , Friedrich Dominicus <frido(a)q-software-solutions.de> wrote: > That if you the developers of Phar change things many have to follow and > it comes to things like this: > "protocol: version dependent" > platformName > "After Squeak version 3.6, #platformName was moved to SmalltalkImage Some > versions of Pharo move this to OSPlatform and issue deprecation warnings > about the other usages. The original idiom (Squeak 3.6 and earlier) is the sensible > default, but here we attempt to support other implementations if the sensible > default is not available." > > "OSProcess platformName" > > (Smalltalk respondsTo: #platformName) > ifTrue: [^ Smalltalk platformName]. > self isPharo3AndLater > ifTrue: [ ^ (Smalltalk perform: #os) name ]. > ^ (((Smalltalk hasClassNamed: #OSPlatform) > and: [(Smalltalk at: #OSPlatform) > respondsTo: #platformName]) > ifTrue: [Smalltalk at: #OSPlatform] > ifFalse: [((Smalltalk classNamed: 'SmalltalkImage') > ifNil: [^ Smalltalk osVersion]) current]) platformName > > Now how many do have to follow through all this? > > So well yes in the end it means not thinking about compatibility costs a > lot thereafter.... > Smalltalk os platformName -> works in Pharo 1.3, 1.4, 2.0, 3.0, Squeak 4.1 (in other words, the first new code release after relicensing effort). Smalltalk platformName -> works in all older version of Pharo/Squeak. While thereâs many places backwards compat could be better preserved, this is not one of themâ¦ Cheers, Henry

March 17, 2014

Please add me to PharoExtras

by Stephan Eggermont

So I can save a working version of ConfigurationOfXMLSupport (it cannot load XMLWriter, due to a missing mc) Stephan

March 17, 2014

Re: [Pharo-dev] WhatsUp from: 2014-03-17 until: 2014-03-31

by Pharo4Stef

> > ### Here's what I've been up to since the last WhatsUp: - working on new book chapter - better catalog - working on finding money for engineers. > > ### What's next, until 2014-03-31 (*): - consortium more work. - working on finding money for engineers - unreloader

March 17, 2014

Re: [Pharo-dev] Adding a new catalog entry

by Pharo4Stef

> well we will have to clean and simplify all that in the future. > This is why versionner should be good so that people use it and we can simplify the declarations. > > Stef > > > But I had the feeling that Versionner UI is currently very limited vs Metacello options (especially w.r.t. cross dialect support) The problem is that metacello is too complex. :) And the API could be better. > Or do you have a different POV, like only Pharo3.0 stuff should go to MetaRepoForPharo3.0, and the ConfigurationOf... should be expunged from any other dialect/version ? For now this is ok to have multiple dialects in the metarepo because people may want to have gemstone and squeak version. Now for the core Pharo tool configruations should be as simple as possible (RB, â¦) Stef > >> >> >> Bye >> T. >> >> Gesendet: Sonntag, 16. MÃ¤rz 2014 um 17:31 Uhr >> Von: "Nicolas Cellier" <nicolas.cellier.aka.nice(a)gmail.com> >> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >> Betreff: Re: [Pharo-dev] Adding a new catalog entry >> >> 2014-03-16 16:06 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >> Nicolas, >> >> On 16 Mar 2014, at 10:08, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> > To get access your StHub account, if you have any, should be part of the Pharo team, but I don't think I can do that. >> >> I now see that 'nice' is part of 'Pharo', so I think you should be able to save to MetaRepoForPharo30. >> >> >> Thanks, I think I messed up when entering my credentials... >> I have now published with a symbolic stable version. >> >> Sven

March 17, 2014

Re: [Pharo-dev] EyeTreeInspector not ready for prime-time

by Sven Van Caekenberghe

On 13 Mar 2014, at 12:51, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > I'm glad we're re-inventing the tools! And, I'm struggling with this tool in > its current form... > > As others have mentioned, the "class" pseudo-variable is confusing, but here > are some that I find worse: > - The receiver does not change with the selection. For me, this was a key > feature of the explorer. > - It does not properly update e.g. if you are inspecting a class containing > a dictionary and add an item to the dictionary, collapsing and expanding the > dictionary node does not show the added item. It seems you must open an > entirely new inspector. > - If you toggle from EyeTreeInspector to EyeInspector, your code in the > bottom pane is lost With the following two cases integrated https://pharo.fogbugz.com/f/cases/13076/Optimize-the-information-displayed-… https://pharo.fogbugz.com/f/cases/13086/EyeTreeInspector-text-pane-doItRece… we're up to the next two open cases https://pharo.fogbugz.com/f/cases/13090/EyeTreeInspector-should-open-with-o… https://pharo.fogbugz.com/f/cases/13091/EyeInspector-switching-should-prese… which would leave the updating issue, which has to be described. Any help appreciated ! Sven

March 17, 2014

Re: [Pharo-dev] WhatsUp from: 2014-03-17 until: 2014-03-31

by Stephan Eggermont

Added Pier3 to MetaRepoForPharo30 Stephan

March 17, 2014

Re: [Pharo-dev] WhatsUp from: 2014-03-17 until: 2014-03-31

by Stefan Marr

Hi: On 17 Mar 2014, at 07:00, seaside(a)rmod.lille.inria.fr wrote: > ### Hereâs what I've been up to since the last WhatsUp: - Fixed the CogVM simulator and the related build setup for OSX. This means, you can go to: https://github.com/pharo-project/pharo-vm/pull/20 grab the source and build the VM on OSX with Bochs plugin and start debugging the VM in the simulator. The build still needs to be adapted to the other platforms as well. Best regards Stefan -- Stefan Marr INRIA Lille - Nord Europe http://stefan-marr.de/research/

March 17, 2014

Re: [Pharo-dev] Image's size in pillar

by Damien Cassou

Hi Natalia, On Sun, Mar 16, 2014 at 2:23 PM, Natalia Tymchuk <natalia.tymchuk(a)unikernel.net> wrote: > but with changing the value width I didn't get changes of my images sizes. How can I make my images take half of the page's width? I fixed this a month ago in the development version of Pillar but didn't release a stable version yet. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

March 17, 2014