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

Re: [Pharo-dev] [CI] is integrator actually integrating?

by Marcus Denker

> On 05 Feb 2015, at 15:08, Max Leske <maxleske(a)gmail.com> wrote: > > Iâm subscribed to a couple of resolved (and validated) issues on fogbugz which donât seem to get integrated, although the integrator runs once a day. Is something going wrong there? > > Issues to integrate: > > https://pharo.fogbugz.com/f/cases/14669/Delay-refactoring-part-2a-avoid-UI-… <https://pharo.fogbugz.com/f/cases/14669/Delay-refactoring-part-2a-avoid-UI-…> > https://pharo.fogbugz.com/f/cases/14064/Improvements-to-checking-terminatio… <https://pharo.fogbugz.com/f/cases/14064/Improvements-to-checking-terminatio…> > It is not an automatic process. 1) that a change passes the monkey does not mean that it is good. It always needs human review â> if that happens, we put it on âfix to includeâ 2) even issues on âfix to includedâ are integrated by a human. The tool is quite good, though (just a couple of kicks) Keep in mind that not many people review issuesâ¦ Marcus

Feb. 5, 2015

[CI] is integrator actually integrating?

by Max Leske

Iâm subscribed to a couple of resolved (and validated) issues on fogbugz which donât seem to get integrated, although the integrator runs once a day. Is something going wrong there? Issues to integrate: https://pharo.fogbugz.com/f/cases/14669/Delay-refactoring-part-2a-avoid-UI-… <https://pharo.fogbugz.com/f/cases/14669/Delay-refactoring-part-2a-avoid-UI-…> https://pharo.fogbugz.com/f/cases/14064/Improvements-to-checking-terminatio… <https://pharo.fogbugz.com/f/cases/14064/Improvements-to-checking-terminatio…> Cheers, Max

Feb. 5, 2015

Re: [Pharo-dev] GT + Dark Theme

by Mariano Martinez Peck

Nice. And I have just added: PolymorphSystemSettings desktopImageFileName: '/Library/Desktop Pictures/Yosemite 3.jpg'. It looks nicer! On Thu, Feb 5, 2015 at 7:56 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > > Le 5 fÃ©vr. 2015 11:52, "Sven Van Caekenberghe" <sven(a)stfx.eu> a Ã©crit : > > > > > >> 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 ! > > Yeah, super! > > I'll start using Pharo4 now :-) > > Phil > > > > > > -- > > Sven Van Caekenberghe > > Proudly supporting Pharo > > http://pharo.org > > http://association.pharo.org > > http://consortium.pharo.org > > > > > > > > > -- Mariano http://marianopeck.wordpress.com

Feb. 5, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40476 Home: https://github.com/pharo-project/pharo-core

Feb. 5, 2015

[pharo-project/pharo-core] abf9e7: 40476

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: abf9e7101c0106e93e50b605501671ad1362dd27 https://github.com/pharo-project/pharo-core/commit/abf9e7101c0106e93e50b605… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-02-05 (Thu, 05 Feb 2015) Changed paths: M Morphic-Base.package/TextAnchor.class/README.md A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script476.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40476.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Caching.package/AbtractCache.class/instance/accessing/at_.st A System-CachingTests.package/LRUCacheTests.class/instance/testing/testAt.st M Tool-FilePackageBrowser.package/FileContentsBrowser.class/instance/other/browseVersions.st Log Message: ----------- 40476 12597 Update TextAnchor class comment https://pharo.fogbugz.com/f/cases/12597 14853 Improve AbstractCache plain access https://pharo.fogbugz.com/f/cases/14853 14814 NewVersionBrowser api not updated in all the client packages https://pharo.fogbugz.com/f/cases/14814 http://files.pharo.org/image/40/40476.zip

Feb. 5, 2015

Re: [Pharo-dev] Spotter & exact match

by Tudor Girba

Indeed, the matching has to be significantly improved. This is a work in progress, but we will likely get to it only in a couple of months. Doru On Thu, Feb 5, 2015 at 1:48 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > +1 > > > On Thu, Feb 5, 2015 at 2:46 PM, Ben Coman <btc(a)openinworld.com> wrote: > >> Some feedback on spotter. >> >> I want to search for #doIt. It shows me five methods starting with >> "doIt" but it would be nicer if exact matches took priority. Alternatively, >> it would be okay if typing "doit<space> did an exact match. >> >> cheers -ben >> > > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 5, 2015

Re: [Pharo-dev] ||

by Marcus Denker

> On 05 Feb 2015, at 10:12, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On 05 Feb 2015, at 10:04, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >>> On 04 Feb 2015, at 22:04, Levente Uzonyi <leves(a)elte.hu> wrote: >>> >>> A single parser is a nice goal, but performance is top priority for Shout, because it should do it's job real-time. When it starts lagging behind, then people just turn it off, because it doesn't help them. >>> Can those parsers (SHRBTextStyler and a Smalltalk parser written using PetitParser) parse an average method in less than 20ms on an average machine? >> >> I have not yet benchmarked itâ¦ PetitParser as it is is too slow, but we will soon have a faster version (factor 10). >> >> We should do some benchmarks. For using, it seems ok. With a fast machine + JIT, which does not say much of course. >> (there is a setting 'AST based coloringâ in Pharo3 and Pharo4, but it is turned off by default). >> >> One thing that is nice with the AST is that it can be used for other things, too. e.g. in Pharo we have a menu that is defined >> by the AST nodes and structural navigation in the editor. >> > > Another way to see it: How would the original Smalltalk be designed if they would have had 4GB RAM in 1978? > > What fascinates me still is that Smalltalk used the existing resources (even building their own machines) to an > extreme, while today we are obsessed to find reasons why we can not do anything that makes the system > slower or use more memory than yesterday. And that even with resources growing every yearâ¦ > > This is why we e.g. now have a meta object describing every instance variable in Pharo. I am sure there are people > who will see these ~7000 objects as pure wasteâ¦ while I would say that we have already *now* the resources to be > even more radical. > Seemingly I still can not explain what I mean in away that people get it, so please just ignore this mail. Marcus

Feb. 5, 2015

Re: [Pharo-dev] Spotter & exact match

by kilon alios

+1 On Thu, Feb 5, 2015 at 2:46 PM, Ben Coman <btc(a)openinworld.com> wrote: > Some feedback on spotter. > > I want to search for #doIt. It shows me five methods starting with "doIt" > but it would be nicer if exact matches took priority. Alternatively, it > would be okay if typing "doit<space> did an exact match. > > cheers -ben >

Feb. 5, 2015

Spotter & exact match

by Ben Coman

Some feedback on spotter. I want to search for #doIt. It shows me five methods starting with "doIt" but it would be nicer if exact matches took priority. Alternatively, it would be okay if typing "doit<space> did an exact match. cheers -ben

Feb. 5, 2015

Re: [Pharo-dev] Metacello + Filetree

by Thierry Goubier

2015-02-05 13:26 GMT+01:00 Sebastian Tleye <sebastian.tleye(a)gmail.com>: > Ok, great, I'll try GitFileTree, we are using the standard port. > Please ask if you need any help. Criticism on the lack of documentation and missing features accepted :) Thierry > > Thanks! > > 2015-02-05 12:53 GMT+01:00 Serge Stinckwich <serge.stinckwich(a)gmail.com>: > >> Why not launching a kickstarter thing to have someone (you !) paid to >> have a clean integration of git/pharo with documentation ? I guess people, >> companies and associations like ESUG can give money for that. >> >> >> Sent from my iPhone >> >> On 5 fÃ©vr. 2015, at 12:38, Thierry Goubier <thierry.goubier(a)gmail.com> >> wrote: >> >> >> >> 2015-02-05 11:27 GMT+01:00 Sebastian Tleye <sebastian.tleye(a)gmail.com>: >> >>> 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! >>> >> >> If you are on a private server, then GitFileTree will work (except if the >> git server is on a non-standard port: I will add support for that in the >> near future). >> >> Look for baselines and branches support to make your life (and your >> configurations) simpler. >> >> As I said during PharoDays: we now have a good chunk of the necessary >> infrastructure and we (the Pharo community) can develop additional support >> if needed. Asking (funding) the consortium for that could be a real cool >> way of contributing :) >> >> Thierry >> >> >>> >>> 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