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

[Pharo 3] Failing tests on Build Server

by Marcus Denker

Linux: ReleaseTest>>testUnknownProcesses BlockClosureTest>>testOnForkErrorTakesLessThanOneSecond Win: ZnHTTPSTests.>>testGetPharoVersion All: ReleaseTest>>#testObsoleteBehaviors

Dec. 9, 2013

Issue for Pharo2 needs review

by Marcus Denker

12300 #date:time: fix backport 2.0 https://pharo.fogbugz.com/f/cases/12300/

Dec. 9, 2013

Re: [Pharo-dev] Smalltalk in a C World

by StÃ©phane Ducasse

You should think that they use their smalltalk for their projects. Stef On Dec 9, 2013, at 9:21 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > How can people even know Smalltalk MT still exist with their website and their communication ? > > I looked at other Smalltalks a while ago, for Smalltalk MT I clicked on "what's new" on their website and I got that: > > <Screen Shot 2013-12-09 at 9.18.11 AM.png> > > Then I thought this Smalltalk was dead (nothing new in the past 4 years) and I didn't look any further. > > > 2013/12/8 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > > Yes - still alive and kicking. But I'm sure you did not notice since there > > are no "big" announcements or advertising for it. > > ObjectConnect follows the "time is better invested into technology" strategy. > > It is one of the most interesting Smalltalks ever implemented. > > http://www.objectconnect.com/stmt_overview.htm > I like the idea that you can get 50kb applications. > Now since this is a closed system and windows-centric. > But I like that it shows that Smalltalk does not have to be the image centric way. > > > > > The newest ST/MT 6.3 version (now 64 bit) is from end of November 2013 > > Now it is not a community thing. :) > And the web site stop and 5.6 in 2009. > > Last time I talk to tarrick he told me that he could control the "no gc in the next 250 frames on PS2" > but it was in 1998 :) > > > Stef >

Dec. 9, 2013

Re: [Pharo-dev] It would be too expensive to add a description for packages in Configuration Browser?

by StÃ©phane Ducasse

> Hi Hernan, > > the problem is not the button - but the missing standard and standardized descriptions > on the configs... > > For instance I also write markup docu on my configs (see ConfigurationOfINIFile) - it > is loadable as a usual config but adds two class side methods: #documentation > and #tutorialOn: using the <onlineTutorial> pragma. > > The documentation is stored as class comment in markdown format on the > ConfigurationOfINIFile class. I use the same description then for the STHub project page. > > If one loads additionally the "PharoOnlineHelp" package afterwards it will also appear > magically in my Pharo online help as a tutorial. This was my proposal - but so far it looks > like nobody is really interested. this is not that this is a question of time. And sorry but I will not use markdown. > Maybe because often this ends in "which syntax" discussions and due to the lack of > good in image default text display facilities for markup, pier-syntax, ... > > In general it can be done easily, but we have to agree on some kind of "common standard" > for configurations and documentation on > - how to describe a package (also the format, either markdown or pier syntax with http://smalltalkhub.com/#!/~Pier/Pillar) > - how to name the methods or pragmas that are used > > Stef also did something (with Catalog), the ConfigurationOfINIFile for instance has two supporting > methods: #catalogDescription and > #repositoryUrlString. this one is deprecated after discussing with versioner. > Still Catalog uses Pier and is not really visible - and STHub does support markdown by default. > > As of today I would like to see Pharo moving into the following direction: > - using the configs for describing the help/documentation/package descriptions > - also tagging with package categories (for instance there are packages/projects for "database access", others for "parsers", or "games") > - maybe use pier syntax for descriptions (it can be parsed by Pillar and other formats like HTML, markdown, Latex, ... be generated) > - generate pages like catalog https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/HTML_Report/? > but with a better design and visibility like "http://packages.pharo.org" The code is open. My time is really counted. Just merged your convention to mine and unify. > together with a loadable list for the config browser > - when one uploads such a ConfigurationOfMyKillerApp to STHub it should automagically update the > STHub description (which is currently only possible via the web interface) > - additional rankings (number of downloads like on STHub, successful CI builds, member rankings, ...) > - automated verfication > - ... <snip>lot of other ideas</snip> > > Bye > T. > > Gesendet: Sonntag, 08. Dezember 2013 um 22:12 Uhr > Von: "HernÃ¡n Morales Durand" <hernan.morales(a)gmail.com> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] It would be too expensive to add a description for packages in Configuration Browser? > Hi Torsten, > > 2013/12/8 Torsten Bergmann <astares(a)gmx.de> > The reason is simple: when I wrote the config browser > there was no such additional description on the configs itself > and one would have to load the config into the image first. > > Think of 2000 config's (note each is a package) loading in the future when > the config browser opens. This will take ages. I think this is not good > since the app should be responsive. > > Maybe a "show details" button helps when the package is selected. > > > > I agree (see attached screenshot). I have added the button but the thing is: Package can be fetched from the repository, but there is no package description. There are only textual descriptions of commits. > > So anyone see any workaround here? > > > > I would rather see: > 1. Either a simple hosted seaside app "Pharo Store" that one can use to > register a config for a specific pharo version (similar like squeakmap) > maybe directly from the STHub interface with description, ... > > This app can be queried by the config browser (JSON/XML/Fuel/...) > to display infos on the package, maybe also a rating about downloads, ... > > 2. Or a general mechanism that loads the configs, runs tests and if > OK provides them for the config browser as "yes these config really work" > > > Absolutely. Configurations should be certified. > > > HernÃ¡n >

Dec. 9, 2013

Re: [Pharo-dev] Smalltalk in a C World

by ClÃ©ment Bera

How can people even know Smalltalk MT still exist with their website and their communication ? I looked at other Smalltalks a while ago, for Smalltalk MT I clicked on "what's new" on their website and I got that: [image: Images intÃ©grÃ©es 1] Then I thought this Smalltalk was dead (nothing new in the past 4 years) and I didn't look any further. 2013/12/8 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > > Yes - still alive and kicking. But I'm sure you did not notice since > there > > are no "big" announcements or advertising for it. > > ObjectConnect follows the "time is better invested into technology" > strategy. > > It is one of the most interesting Smalltalks ever implemented. > > http://www.objectconnect.com/stmt_overview.htm > I like the idea that you can get 50kb applications. > Now since this is a closed system and windows-centric. > But I like that it shows that Smalltalk does not have to be the image > centric way. > > > > > The newest ST/MT 6.3 version (now 64 bit) is from end of November 2013 > > Now it is not a community thing. :) > And the web site stop and 5.6 in 2009. > > Last time I talk to tarrick he told me that he could control the "no gc in > the next 250 frames on PS2" > but it was in 1998 :) > > > Stef >

Dec. 9, 2013

[pharo-project/pharo-core]

by GitHub

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

Dec. 9, 2013

[pharo-project/pharo-core] 76bf0c: 30633

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 76bf0c7bf67d5ce70f6b704375f7fa37172061ef https://github.com/pharo-project/pharo-core/commit/76bf0c7bf67d5ce70f6b7043… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-12-08 (Sun, 08 Dec 2013) Changed paths: M Network-MIME.package/QuotedPrintableMimeConverter.class/README.md M Network-MIME.package/QuotedPrintableMimeConverter.class/definition.st M Network-MIME.package/QuotedPrintableMimeConverter.class/instance/conversion/mimeDecode.st A Network-MIME.package/QuotedPrintableMimeConverter.class/instance/conversion/mimeEncode.st A Network-MIME.package/QuotedPrintableMimeConverter.class/instance/initialize/initialize.st A Network-MIME.package/QuotedPrintableMimeConverter.class/instance/initialize/newline_.st A NetworkTests.package/QuotedPrintableMimeConverterTest.class/README.md A NetworkTests.package/QuotedPrintableMimeConverterTest.class/definition.st A NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/accesing/decode_.st A NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/accesing/encode_.st A NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/running/setUp.st A NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeCRLF.st A NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeCustomNewline.st A NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeDecodedStrings.st A NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeSimpleStrings.st A NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeSoftLinebreak.st A NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeSoftLinebreakCR.st A NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeSoftLinebreakCRLF.st A NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testDecodeSoftLinebreakLF.st A NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testEncodeCR.st A NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testEncodeCRLF.st A NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testEncodeEncodedStrings.st A NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testEncodeLF.st A NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testEncodeLongLine.st A NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testEncodeSimpleStrings.st A NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testEncodeSoftLinebreak.st A NetworkTests.package/QuotedPrintableMimeConverterTest.class/instance/testing/testLongLine.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script288.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30633.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30633 4825 Quoted-printable encoding incomplete https://pharo.fogbugz.com/f/cases/4825 http://files.pharo.org/image/30/30633.zip

Dec. 9, 2013

Re: [Pharo-dev] Commit right to Pharo30Inbox

by Marcus Denker

On 09 Dec 2013, at 01:11, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > Hi list. > I want to submit a SLICE to the pharo inbox, can you grant me commit rights? > > username: hernan > Done.

Dec. 9, 2013

Re: [Pharo-dev] access to MetaRepoForPharo30

by Marcus Denker

On 09 Dec 2013, at 08:05, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I would need access to: > http://www.smalltalkhub.com/#!/~Pharo/MetaRepoForPharo30 > > Actually, could I be added to the Pharo team? > Done. Marcus

Dec. 9, 2013

access to MetaRepoForPharo30

by Tudor Girba

Hi, I would need access to: http://www.smalltalkhub.com/#!/~Pharo/MetaRepoForPharo30 Actually, could I be added to the Pharo team? Doru -- www.tudorgirba.com "Every thing has its own flow"

Dec. 9, 2013