September 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Primitives lookupEntryIn:index: fails on mac with the latest vm

by StÃ©phane Ducasse

Hi andrei I never saw it and I could not reproduce it I tried 20 times on NB-win32 with the latest image and my vm is Smalltalk vm version 'NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 git://gitorious.org/cogvm/blessed.git Commit: 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 ' Stef > Hi, > > I was trying to merge a slice into the latest Pharo 3 image when I got a FileSystemError in MacStore(DiskStore)>>basicEntry:path:nodesDo:. This happens as 'Primitives lookupEntryIn:index:' returns #badDirectoryPath. The bad part is that it goes into an infinite loop and blocks the image. The same scenario works ok with the stable pharo vm. > > I can reproduce this by going to the PharoInbox choosing a package that is not merged (let's say NativeBoost-Win32-CamilloBruni.42) and hit merge. If no error appears the first time, close the merge window and select merge again. For almost all packages, after a few time I get the previous error. > > Has anyone encountered this before? Might it be related to https://pharo.fogbugz.com/f/cases/7559 ? > > Cheers, > Andrei

Sept. 30, 2013

Re: [Pharo-dev] ConfigurationOfGhost: Where?

by StÃ©phane Ducasse

On Sep 30, 2013, at 2:37 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Yes, it is still in SS3. > Some weeks ago I think someone reported that the #cannotInterpert: trick was not working anymore in latest Pharo (so proxies won't work). who? Because why it would not work? > I didn't have the time yet to try different images/VMs and see if it works, but if I can give it a try today or tomorrow. I can migrate the repo if you want. > > Cheers > > > On Sun, Sep 29, 2013 at 11:04 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > It is probably still on SS3 > > http://ss3.gemstone.com/ss/Ghost/ > > Stef > > On Sep 24, 2013, at 7:58 PM, phil(a)highoctane.be wrote: > >> I am preparing my environment for development and am updating my webstack configuration to match the new moves to SmalltalkHub. >> >> Now, I am trying to get my ConfigurationOfOak working. >> >> Fuel has moved to SmalltalkHub and it is fine. >> >> Now, where is Ghost .? >> >> I want to update this: >> >> spec >> project: 'GhostProxies' with: [ >> spec >> className: 'ConfigurationOfGhost'; >> loads: #('Core'); >> versionString: #stable; >> file: 'ConfigurationOfGhost'; >> repository: 'http://ss3.gemstone.com/ss/Ghost' ]. >> >> spec project: 'GhostProxiesTests' copyFrom: 'GhostProxies' with: [ >> spec loads: #('Tests' ) ]. >> >> The search function on STH isn't helping much... >> >> Thanks for the help! >> >> Phil > > > > > -- > Mariano > http://marianopeck.wordpress.com

Sept. 30, 2013

Re: [Pharo-dev] State of SVG importer

by StÃ©phane Ducasse

> > Ok I will update the stable setting because it was just loading the development version so breaking the point of stable > Igor such information should not be only in your head!!!! > > > it is work to do.. > but i am not sure it is worth doing. Pharo 2.0 officially not supported by Athens, so why we should worry about staying compatible? > Yes, in perfect case , configuration baseline should contain branch to load different versions for 2.0 image, and for 3.0. > > But to do that , first i need to learn (again) how to do it :) > We certainly need a UI tool for configurations, because keeping all those "how to-s" in head > becomes tedious and counterproductive task. yes and it is coming, versioner will help us for that. But to me it looks like you did not write enough configurations. I hate writing them but I do not it because there is no other ways to manage quality and reproducibility. If this is the price to pay, I pay it because this is what I want. a ONE CLICK loading system. I take a reference one and I copy. So now this is done. Have a look and see if it loads what you think it should. Stef

Sept. 30, 2013

Re: [Pharo-dev] State of SVG importer

by StÃ©phane Ducasse

Igor I'm adding development: spec <symbolicVersion: #development> spec for: #common version: '2.5' stable: spec <symbolicVersion: #stable> spec for: #'pharo2.x' version: '2.1'. "after some modification in NB made it incompatible with 3.0" spec for: #'pharo3.x' version: '2.3' and you should probably merged the version in 3.0/main so that everything loads clean. Stef > > > On 30 September 2013 13:27, hilaire <hilaire.fernandes(a)gmail.com> wrote: > Got it working on 3.0. > > Indeed gradient is not handled. However I can see a ASGradient hierarchy. > > > yes, i don't remember all the details, but it should be easy to fix. > i stopped working on it, when realized that the missing elliptical segment type > prevents me to display correctly many svg content, so i started working on it > but this still not there. > it needs some overhaul in path creation, and calculating path geometry.. > i wanted to extend functionality , so you can use own parametric functions > for path segments (elliptical curves is just simple case of this). > The problem is that Cairo don't have direct support of elliptical curves, > so they need to be approximated either by bezier curves or by straight line segments > (a tiny ones, of course). > > This is where i stopped in May, because i had to focus on text rendering & text editor, > and as you may know i still working on it.. > > Hilaire > > > > -- > View this message in context: http://forum.world.st/State-of-SVG-importer-tp4710870p4711359.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > > > > -- > Best regards, > Igor Stasenko.

Sept. 30, 2013

Re: [Pharo-dev] State of SVG importer

by Igor Stasenko

On 30 September 2013 21:52, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > > On Sep 30, 2013, at 9:44 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > > > On 29 September 2013 21:40, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > >> >> On Sep 29, 2013, at 9:30 PM, Hilaire Fernandes < >> hilaire.fernandes(a)gmail.com> wrote: >> >> > Le 29/09/2013 21:17, Hilaire Fernandes a Ã©crit : >> >> You may want to fix it for earlier tester. >> > >> > I manage to load the needed package by hand. >> > But there is a missing class AthensCairoSurface. >> > Please could you check on a fresh pharo 2.0 the configuration and fix >> it? >> >> I think that we should work on pharo 30. We do not have the resource to >> maintain it on 20. >> First it should work on 30. >> >> > yes , there are multiple important updates which made to NB which making > current version of Athens incompatible with pharo 2.0. > The last version of Athens, compatible with 2.0 image is 2.1. > > > Ok I will update the stable setting because it was just loading the > development version so breaking the point of stable > Igor such information should not be only in your head!!!! > > it is work to do.. but i am not sure it is worth doing. Pharo 2.0 officially not supported by Athens, so why we should worry about staying compatible? Yes, in perfect case , configuration baseline should contain branch to load different versions for 2.0 image, and for 3.0. But to do that , first i need to learn (again) how to do it :) We certainly need a UI tool for configurations, because keeping all those "how to-s" in head becomes tedious and counterproductive task. > > ConfigurationOfAthens loadVersion: '2.1'. > > and to load svg package use: > (ConfigurationOfAthens project version: '2.1') load: 'SVG' > > (but you need to load XML support first). > > And since you planning to work on SVG, i recommend you to > pick up the latest pharo 3.0 image where athens already installed > and work there, on development version of Athens. > > > -- Best regards, Igor Stasenko.

Sept. 30, 2013

Re: [Pharo-dev] State of SVG importer

by Igor Stasenko

On 30 September 2013 21:46, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Hilaire > > I published > > > a new baseline > - to address SVG needing XMLParser > - added version 24 to use the new baseline > (no change) > - added version 25 to load all the more recent versions from the > repository. > > So let me know if this is helping you. Normally 24 should load ok I'm > testing. > > > â¦. > > It looks some packages were changed in the image and should be merged and > published. > thanks for help. Yes, i need to create a new configuration version, since there's some most recent work which committed but not yet adopted inside of config. > Igor should do that but he is lying sick in his bed. > > Stef > > > On Sep 30, 2013, at 1:27 PM, hilaire <hilaire.fernandes(a)gmail.com> wrote: > > > Got it working on 3.0. > > > > Indeed gradient is not handled. However I can see a ASGradient hierarchy. > > > > Hilaire > > > > > > > > -- > > View this message in context: > http://forum.world.st/State-of-SVG-importer-tp4710870p4711359.html > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > > -- Best regards, Igor Stasenko.

Sept. 30, 2013

Re: [Pharo-dev] State of SVG importer

by StÃ©phane Ducasse

On Sep 30, 2013, at 9:44 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > > On 29 September 2013 21:40, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Sep 29, 2013, at 9:30 PM, Hilaire Fernandes <hilaire.fernandes(a)gmail.com> wrote: > > > Le 29/09/2013 21:17, Hilaire Fernandes a Ã©crit : > >> You may want to fix it for earlier tester. > > > > I manage to load the needed package by hand. > > But there is a missing class AthensCairoSurface. > > Please could you check on a fresh pharo 2.0 the configuration and fix it? > > I think that we should work on pharo 30. We do not have the resource to maintain it on 20. > First it should work on 30. > > > yes , there are multiple important updates which made to NB which making current version of Athens incompatible with pharo 2.0. > The last version of Athens, compatible with 2.0 image is 2.1. Ok I will update the stable setting because it was just loading the development version so breaking the point of stable Igor such information should not be only in your head!!!! > ConfigurationOfAthens loadVersion: '2.1'. > > and to load svg package use: > (ConfigurationOfAthens project version: '2.1') load: 'SVG' > > (but you need to load XML support first). > > And since you planning to work on SVG, i recommend you to > pick up the latest pharo 3.0 image where athens already installed > and work there, on development version of Athens.

Sept. 30, 2013

Re: [Pharo-dev] State of SVG importer

by Igor Stasenko

On 30 September 2013 13:27, hilaire <hilaire.fernandes(a)gmail.com> wrote: > Got it working on 3.0. > > Indeed gradient is not handled. However I can see a ASGradient hierarchy. > > yes, i don't remember all the details, but it should be easy to fix. i stopped working on it, when realized that the missing elliptical segment type prevents me to display correctly many svg content, so i started working on it but this still not there. it needs some overhaul in path creation, and calculating path geometry.. i wanted to extend functionality , so you can use own parametric functions for path segments (elliptical curves is just simple case of this). The problem is that Cairo don't have direct support of elliptical curves, so they need to be approximated either by bezier curves or by straight line segments (a tiny ones, of course). This is where i stopped in May, because i had to focus on text rendering & text editor, and as you may know i still working on it.. > Hilaire > > > > -- > View this message in context: > http://forum.world.st/State-of-SVG-importer-tp4710870p4711359.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- Best regards, Igor Stasenko.

Sept. 30, 2013

Re: [Pharo-dev] About Soup and XML

by StÃ©phane Ducasse

I published a new configuration with - new baseline with XMLParser dependencies - a new version using this new baseline - all tests green Now it would be good that you take the time to see what is needed to get pushed in the XMLParser project. I do not want to have project that I maintained under PharoExtras to get in strange shape. Stef > Hi paul > > I do not think that it is wise in the long term to have split repository. For example it does not really make > sense to me to have a part of XMLSupport in your private project and another part in squeaksource. > So we should > - update soup to use XMLReader in SmalltalkHub > - and publish gemstone package in their corresponding base project > > Managing conifguration is complex enough to make things as simple as we can. > So are you interested in helping? > > Stef > > > baseline14: spec > <version: '1.4-baseline'> > spec > for: #squeakCommon > do: [ > spec blessing: #baseline. > spec description: 'Migrated to SmalltalkHub'. > spec author: 'StephaneDucasse'. > spec timestamp: '21/02/2013'. > spec repository: 'http://www.smalltalkhub.com/mc/PharoExtras/Soup/main'. > spec > package: 'Soup-Core' with: [ spec requires: 'XMLSupport' ]; > package: 'Soup-Tests-Core' with: [ spec requires: 'Soup-Core' ]; > package: 'Soup-Help' with: [ spec requires: 'Soup-Core' ]; > package: 'Soup-XPath' with: [ spec requires: 'Soup-Core' ]; > package: 'Soup-Zinc' with: [ spec requires: 'Soup-Core' ]. > spec > project: 'XMLSupport' > with: [ spec > className: 'ConfigurationOfXMLSupport'; > versionString: #stable; > repository: 'http://www.squeaksource.com/XMLSupport' ]. > spec > group: 'default' with: #('Core' 'Tests'); > group: 'Core' with: #('Soup-Core' 'Soup-XPath'); > group: 'Tests' with: #('Soup-Tests-Core') ]. > spec > for: #gemstone > do: [ > spec repository: 'http://www.smalltalkhub.com/mc/PharoExtras/Soup/main'. > spec > project: 'XMLSupport' > with: [ spec > className: 'ConfigurationOfXMLSupport'; > versionString: #stable; > repository: 'http://www.smalltalkhub.com/mc/pdebruic/XMLSupport/main' ]. > spec > package: 'SoupGemstone-Core' with: [ spec requires: 'XMLSupport' ]; > package: 'Soup-Tests-Core' with: [ spec requires: 'SoupGemstone-Core' ]; > package: 'Soup-Help' with: [ spec requires: 'SoupGemstone-Core' ]; > package: 'Soup-XPath' with: [ spec requires: 'SoupGemstone-Core' ]; > package: 'Soup-Zinc' with: [ spec requires: 'SoupGemstone-Core' ]. > > spec > group: 'default' with: #('Core' 'Tests'); > group: 'Core' with: #('SoupGemstone-Core'); > group: 'Tests' with: #('Soup-Tests-Core') ]. > >

Sept. 30, 2013

Re: [Pharo-dev] State of SVG importer

by StÃ©phane Ducasse

Hilaire I published a new baseline - to address SVG needing XMLParser - added version 24 to use the new baseline (no change) - added version 25 to load all the more recent versions from the repository. So let me know if this is helping you. Normally 24 should load ok I'm testing. â¦. It looks some packages were changed in the image and should be merged and published. Igor should do that but he is lying sick in his bed. Stef On Sep 30, 2013, at 1:27 PM, hilaire <hilaire.fernandes(a)gmail.com> wrote: > Got it working on 3.0. > > Indeed gradient is not handled. However I can see a ASGradient hierarchy. > > Hilaire > > > > -- > View this message in context: http://forum.world.st/State-of-SVG-importer-tp4710870p4711359.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Sept. 30, 2013