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

Re: [Pharo-dev] GT + Dark Theme

by Sven Van Caekenberghe

> On 05 Feb 2015, at 10:32, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > 40 475 now integrates the fixes for making GT work nicer with the Dark Theme. > > Thanks to all the contributors! > > Marcus Ah, just beautiful: Great work, thank you ! -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

Feb. 5, 2015

Re: [Pharo-dev] Metacello + Filetree

by Sebastian Tleye

hahah ok! 2015-02-05 11:33 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Let us know about your solution, it can be interesting. > > Uko > > > On 05 Feb 2015, at 11:27, Sebastian Tleye <sebastian.tleye(a)gmail.com> > wrote: > > Thanks Yuriy and Thierry, > > I see what I can do, I was using Bitbucket until some time ago but now we > moved our project to a private git server! > > 2015-02-05 11:13 GMT+01:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > >> Hi Sebastian, >> >> filetree only gives you access to the latest version of your packages, >> and you can't access the history without access to the underlying version >> control system you are using. >> >> This access for Metacello is available in two ways: via Metacello >> github:// and bitbucket:// urls and tags or branches (but you need to be >> using either github or bitbucket), or via GitFileTree if you are using git. >> >> Thierry >> >> 2015-02-05 11:03 GMT+01:00 Sebastian Tleye <sebastian.tleye(a)gmail.com>: >> >>> Hi, >>> >>> I am using a filetree repository for my project, also I have created a >>> first stable version using the versioner tool. >>> Everything was working fine until I commited more changes, now when I >>> want to install the stable version is throwing an error saying that cannot >>> resolve the package that it needs, however if I load the development >>> version it works perfectly. >>> >>> To clarify a little, >>> >>> The development version tries to load >>> Phadeo-ImporterExporters-SebastianTleye.12 and it works perfectly. The >>> stable version tries to load Phadeo-ImporterExporters-SebastianTleye.10 and >>> it throws an error saying that it cannot be resolve. >>> >>> Any Idea of what is happening? >>> I read that filetree and Metacello are compatibles so I don't know >>> what's the problem >>> >> >> Hi sebastian >> >> >>> >>> Thanks in advance >>> >>> SebastiÃ¡n Tleye >>> >> >> > > > -- > SebastiÃ¡n Tleye > > > -- SebastiÃ¡n Tleye

Feb. 5, 2015

Re: [Pharo-dev] Switching to Pharo from Visualworks

by Serge Stinckwich

- Glamour : https://ci.inria.fr/pharo-contribution/view/Books/job/DeepIntoPharo/lastSuc… - Zinc : https://github.com/SquareBracketAssociates/EnterprisePharo/tree/master/Zinc… On Thu, Feb 5, 2015 at 11:37 AM, Markus Fritsche <mfritsche(a)reauktion.de> wrote: > On Wed, 4 Feb 2015 19:30:38 -0600 > Stephen Travis Pope <stephen(a)heaveneverywhere.com> wrote: > >> How does a newbie learn what all the new packages are for? Glamour, Ring, >> AsmJit, Zinc, etc. are neat names, but if they're not part of higher-level >> packages it makes navigating the system (and even figuring out what they're >> for) pretty difficult. > > +1 to that one. > > -- > Markus Fritsche <mfritsche(a)reauktion.de> > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Feb. 5, 2015

Re: [Pharo-dev] Switching to Pharo from Visualworks

by Markus Fritsche

On Wed, 4 Feb 2015 19:30:38 -0600 Stephen Travis Pope <stephen(a)heaveneverywhere.com> wrote: > How does a newbie learn what all the new packages are for? Glamour, Ring, > AsmJit, Zinc, etc. are neat names, but if they're not part of higher-level > packages it makes navigating the system (and even figuring out what they're > for) pretty difficult. +1 to that one. -- Markus Fritsche <mfritsche(a)reauktion.de>

Feb. 5, 2015

Re: [Pharo-dev] ||

by kilon alios

I am surely wont complain if you made code that I need to be faster, faster. Afterall languages like C/C++ are not popular by accident. Nor is accidental that many of python libraries are made in those two language that people love to hate. I am definitely not claiming that performance is not important. But slow speed definetly did not kill Python, it wont kill Pharo either. On the other hand recently I was distracted by the fact that people still code on old computers like Amstrads and Amigas and have beendoing some amazing stuff like GUIs OS with video playback , internet browsing, Business applications etc which is kinda insane if you take into account that these are machines that thousands times slow with cpu that barely reach 6-12mhz. So I think we need to be realistic about Pharo and let things evolve and people contribute the way they want and can. Both performace and efficiency are very important. But yes I am more orientated towards well designed workflow. Maybe this is why I still I love Amiga 500 :D On Thu, Feb 5, 2015 at 12:24 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > 2015-02-05 11:14 GMT+01:00 kilon alios <kilon.alios(a)gmail.com>: > >> And there is also the matter of hardware evolution. >> >> When I was running Pharo on my 2007 imac 20'' with dual core 2.GHZ , >> Morphic was slow. And by slow I mean that I could see it was struggling to >> move windows around. I could see windows flickering trying to render >> themselves moving around. >> >> But now with my 2014 imac even though the screen is double the size and >> the resolution much bigger (27'' retina) , Morphic is now quite fast. The >> reason is of course the fact that the CPU is a quad core at 3 Ghz thats >> almost a 3x times increase in speed and it really shows. >> >> Even when Pharo take full the huge area of 27'' Morphic is responsive and >> quite fast. >> > > Which means if I see you complaining of speed issues, then it must be > really bad :) > > Thierry >

Feb. 5, 2015

[CI] help needed: integration of Fuel changes with new version number

by Max Leske

Hi guys ClÃ©ment asked us a while ago to update Fuel for Spur support and we did (https://pharo.fogbugz.com/f/cases/14688/Change-CompiledMethod-header-serial… <https://pharo.fogbugz.com/f/cases/14688/Change-CompiledMethod-header-serial…>). The problem now: Fuel is an integral part of the integration process and the change to the Fuel version number means that the automatic integration will not work. Hereâs why: This slice can't be automatically integrated because I changed the Fuel version number. Now, when the image worker reads the result from the validation, Fuel raises an exception because of the different version numbers in the parent and child image. We should probably add a mechanism that ensures that the original Fuel version is reloaded after the validation, such that the Fuel file is written by the same version that then reads it in the parent. Can someone please manually integrate or (which would be way cooler) adapt the integration process such that future updates to Fuel can be automatically integrated? Cheers, Max

Feb. 5, 2015

Re: [Pharo-dev] Metacello + Filetree

by Yuriy Tymchuk

Let us know about your solution, it can be interesting. Uko > On 05 Feb 2015, at 11:27, Sebastian Tleye <sebastian.tleye(a)gmail.com> wrote: > > Thanks Yuriy and Thierry, > > I see what I can do, I was using Bitbucket until some time ago but now we moved our project to a private git server! > > 2015-02-05 11:13 GMT+01:00 Thierry Goubier <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>>: > Hi Sebastian, > > filetree only gives you access to the latest version of your packages, and you can't access the history without access to the underlying version control system you are using. > > This access for Metacello is available in two ways: via Metacello github:// and bitbucket:// urls and tags or branches (but you need to be using either github or bitbucket), or via GitFileTree if you are using git. > > Thierry > > 2015-02-05 11:03 GMT+01:00 Sebastian Tleye <sebastian.tleye(a)gmail.com <mailto:sebastian.tleye@gmail.com>>: > Hi, > > I am using a filetree repository for my project, also I have created a first stable version using the versioner tool. > Everything was working fine until I commited more changes, now when I want to install the stable version is throwing an error saying that cannot resolve the package that it needs, however if I load the development version it works perfectly. > > To clarify a little, > > The development version tries to load Phadeo-ImporterExporters-SebastianTleye.12 and it works perfectly. The stable version tries to load Phadeo-ImporterExporters-SebastianTleye.10 and it throws an error saying that it cannot be resolve. > > Any Idea of what is happening? > I read that filetree and Metacello are compatibles so I don't know what's the problem > > Hi sebastian > > > Thanks in advance > > SebastiÃ¡n Tleye > > > > > -- > SebastiÃ¡n Tleye

Feb. 5, 2015

Re: [Pharo-dev] ||

by Thierry Goubier

2015-02-05 10:55 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > It is obviously a compromise (or a continuum) between abstractions and > performance. > I agree. With a special view in that we are in a sub domain where simple things well designed (Smalltalk, that is) are amazingly good at supporting complex designs. > > But there should remain a focus on efficiency (not just speed but also > memory), it is hard to fix these things years later. > And I like the fact that efficient code and design is often a pleasure to read and learn from :) Now, being radical: could we get rid of pragmas ? The only reason I see to them is that they allow extension by external packages, because we can't have methods which belong to two protocols (*). Thierry (*) I tried to get rid of them in some of my stuff, where it is used in the same way GTInspector and GTSpooter uses pragmas, and I had to stop because of that feature. All other uses of pragmas are replaceable (and often, as in the gt stuff, redundant).

Feb. 5, 2015

ZnUrl>>#withRelativeReference:

by Sven Van Caekenberghe

Hi, I added ZnUrl>>#withRelativeReference: which implements the process described in section 5 of RFC 3986. https://pharo.fogbugz.com/f/cases/14855/Add-reference-resolution-to-ZnUrl Summary: In certain contexts (like links on a webpage) partial URLs are used that must be interpreted relative to a base URL (like the URL of the webpage itself). Example: 'http://www.site.com/static/html/home.html' asZnUrl withRelativeReference: '../js/menu.js' => http://www.site.com/static/js/menu.js This was previously not possible with ZnUrl. If you know this stuff, please have a look. Monty ? Peter ? Sven PS: this is in #bleedingEdge for now

Feb. 5, 2015

Re: [Pharo-dev] Metacello + Filetree

by Sebastian Tleye

Thanks Yuriy and Thierry, I see what I can do, I was using Bitbucket until some time ago but now we moved our project to a private git server! 2015-02-05 11:13 GMT+01:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > Hi Sebastian, > > filetree only gives you access to the latest version of your packages, and > you can't access the history without access to the underlying version > control system you are using. > > This access for Metacello is available in two ways: via Metacello > github:// and bitbucket:// urls and tags or branches (but you need to be > using either github or bitbucket), or via GitFileTree if you are using git. > > Thierry > > 2015-02-05 11:03 GMT+01:00 Sebastian Tleye <sebastian.tleye(a)gmail.com>: > >> Hi, >> >> I am using a filetree repository for my project, also I have created a >> first stable version using the versioner tool. >> Everything was working fine until I commited more changes, now when I >> want to install the stable version is throwing an error saying that cannot >> resolve the package that it needs, however if I load the development >> version it works perfectly. >> >> To clarify a little, >> >> The development version tries to load >> Phadeo-ImporterExporters-SebastianTleye.12 and it works perfectly. The >> stable version tries to load Phadeo-ImporterExporters-SebastianTleye.10 and >> it throws an error saying that it cannot be resolve. >> >> Any Idea of what is happening? >> I read that filetree and Metacello are compatibles so I don't know what's >> the problem >> > > Hi sebastian > > >> >> Thanks in advance >> >> SebastiÃ¡n Tleye >> > > -- SebastiÃ¡n Tleye

Feb. 5, 2015