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

Re: [Pharo-project] Pharo changing the game

by Eagle Offshore

It is not a code problem. It is a social/political problem. On Feb 13, 2010, at 1:52 AM, StÃ©phane Ducasse wrote: > Send code and it will be fixed in one hour. > > Stef > >> I think the really tragic thing is that nothing in Smalltalk remains stable. >> >> It would seem to me that in a language that has been around thirty years or so that core data types like numbers, dates, times, and (hopefully, although adoption of unicode was disruptive) strings would be the same across all the dialects. >> >> By now, there should be some chunks of the system that we can deem fully mature and then learn to LEAVE ALONE. >> >> The 16rff issue is a fine example of an absolutely stupid incompatibility. >> >> Just my $.04 >> >> -Todd Blanchard >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 14, 2010

[Pharo-project] GoferApiTest failing (WinXP)

by Ch Lamprecht

Hello to everybody, running the tests in latest images PharoCore-1.1 and 1.0 on WinXP I see GoferApiTest>>#testSubDirectoryRepository failing. It could be fixed by changing MCSubDirectoryRepository>>#description + ^ directory pathName, FileDirectory slash , '*' - ^ directory pathName, '/*' The current implementation works because '/' and '\' both are valid path separators on windows. Assuming '/' as path delimiter would cause trouble with MacFileDirectory - but that might be obsolete anyway. So may be the test is too strict? I just started to follow this list and the Pharo project ('Recreational programmer' btw. - thanks for the kind welcome message ;) ). Should I report this? And if so: It is a MC issue, should it be reported using the Pharo tracker or somewere else? Cheers, Christoph

Feb. 13, 2010

[Pharo-project] [ANN] HelpSystem (was ProfStef)

by Torsten Bergmann

>I have implemented some authoring capabilities in ProfStefBrowser >to create new tutorials Yes, authoring capabilities would be cool to have. But first we have to find out what the content really should be and how it should be represented (simple text, markup, active morphs, ...) >Some kind of simple markup language to have for example links to other pages >or books, or to execute code snippets with a single mouse click Do you know the Squeak welcome workspace? It provided something like this - a Text could define "runs" to change style, color of text or even have clickable links with Smalltalk code behind - dont know if this is still possible in Pharo since parts of Morphic are removed. On the other hand it was Squeak only - hard to create from tyical documentation formats (text, HTML, ...) Maybe we could reactive code from "Scamper" (the Squeak web browser) for simple HTML like text styling. Using a subset of HTML as description would also allow us to publish the help contents on webpages later. I also remember a full webbrowser written in Smalltalk (VW). Meanwhile it is open source (MIT), see [1] ... so lets just reactivate it ;) We all have many ideas (like yours with the debugger) - but first I would like to see a minimal version for a help system: - provide help contents as simple ascii text (as it is now) - ability to jump from a tool to a specific page (like F1-help on Windows) we can use a simple unique key which is defined in HelpTopic already. - ability to define order of pages together with order of (sub)books With a minimal help tool (included in the dev-image) we can provide help to beginners and start documenting Pharo. As a second step we can work on better markup, authoring, active content ... However - the repo is open for any contribution... >Now....It is not clear for me the differences between HelpSystem and >ProfStef. "HelpSystem" is like a normal help system you know from Eclipse, KDE, Windows, ... It is more a reference/documentation kind of thing. "ProfStef" is an interactive tutorial usefull to teach things step by step. >Help system is new ? Yes, developed yesterday. >should they be merged? Hey, we just decoupled ... why merge again ;) Read [2] >when we should use one and when the other ? ProfStef is for an introduction (5min course) on Pharo or tools, an interactive tutorial to introduce Smalltalk or basic concepts. It is more "workspace" oriented. See Laurents comments. HelpSystem is more a general help system with a "browser" that should be available as a base framework so tools can provide help texts/contents to users. Bye T. [1] http://www.cincomsmalltalk.com/userblogs/rowanb/blogView?showComments=true&… [2] http://lists.gforge.inria.fr/pipermail/pharo-project/2010-February/021782.h… -- Sicherer, schneller und einfacher. Die aktuellen Internet-Browser - jetzt kostenlos herunterladen! http://portal.gmx.net/de/go/chbrowser

Feb. 13, 2010

[Pharo-project] [ANN 1.1] pre-built core 1.1 #11208

by Marcus Denker

http://gforge.inria.fr/frs/download.php/26404/PharoCore-1.1-11208-UNSTABLE.… -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 13, 2010

[Pharo-project] [update 1.1] #11208

by StÃ©phane Ducasse

11208 ----- - Issue 1960: ExtendedNumberParser and Friend in Squeak should probably be packaged as separate Pharo package - Issue 1957: Cleanings Utilities tx JB :) - more tests for WeakRegistry - remove all senders of or:or:, or:or:or:, or:or:or:or: and or:or:or:or:or:. Add a deprecated message in each one. Remove the method or:or:or:or:or: Tx Jannik :)

Feb. 13, 2010

Re: [Pharo-project] About String empty and others

by Marcus Denker

On Feb 13, 2010, at 8:03 PM, StÃ©phane Ducasse wrote: > the only think is that the #() and '' will not be created all the time but in the compile method literal frame. > Yes, right now it's created once per method... the compiler could easily make sure that it's shared globally. Marcus > Stef > > >> would the idea to be to rewrite every #() with Array empty? >> >> If that was the case could you get the compiler to do that as an >> optimization? I quite like the fact that #() is the empty array. it's >> nice and compact; quite aesthetic. >> >> cheers, >> Mike >> >> On Sat, Feb 13, 2010 at 11:06 AM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> Hi guys >>> >>> chris mueller proposed in squeak to have >>> >>> >>> Exception>>messageText >>> "Return an exception's message text." >>> + ^ messageText ifNil: [ String empty ]! >>> - >>> - ^messageText! >>> >>> - Added Array class>>#empty and String class>>#empty to provide applications with >>> canonicalized instances of these oft-used objects; since they are embedded as literals in the >>> CompiledMethod. >>> >>> =============== Diff against Collections-ar.304 =============== >>> >>> Item was added: >>> + ----- Method: Array class>>empty (in category 'instance creation') ----- >>> + empty >>> + "A canonicalized empty Array instance." >>> + ^ #()! >>> >>> Item was added: >>> + ----- Method: String class>>empty (in category 'instance creation') ----- >>> + empty >>> + "A canonicalized empty String instance." >>> + ^ ''! >>> >>> Item was removed: >>> - ----- Method: String>>asDefaultDecodedString (in category 'converting') ----- >>> - asDefaultDecodedString >>> - >>> - ^ self >>> >>> >>> http://code.google.com/p/pharo/issues/detail?id=1961 >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 13, 2010

Re: [Pharo-project] About String empty and others

by StÃ©phane Ducasse

the only think is that the #() and '' will not be created all the time but in the compile method literal frame. Stef > would the idea to be to rewrite every #() with Array empty? > > If that was the case could you get the compiler to do that as an > optimization? I quite like the fact that #() is the empty array. it's > nice and compact; quite aesthetic. > > cheers, > Mike > > On Sat, Feb 13, 2010 at 11:06 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Hi guys >> >> chris mueller proposed in squeak to have >> >> >> Exception>>messageText >> "Return an exception's message text." >> + ^ messageText ifNil: [ String empty ]! >> - >> - ^messageText! >> >> - Added Array class>>#empty and String class>>#empty to provide applications with >> canonicalized instances of these oft-used objects; since they are embedded as literals in the >> CompiledMethod. >> >> =============== Diff against Collections-ar.304 =============== >> >> Item was added: >> + ----- Method: Array class>>empty (in category 'instance creation') ----- >> + empty >> + "A canonicalized empty Array instance." >> + ^ #()! >> >> Item was added: >> + ----- Method: String class>>empty (in category 'instance creation') ----- >> + empty >> + "A canonicalized empty String instance." >> + ^ ''! >> >> Item was removed: >> - ----- Method: String>>asDefaultDecodedString (in category 'converting') ----- >> - asDefaultDecodedString >> - >> - ^ self >> >> >> http://code.google.com/p/pharo/issues/detail?id=1961 >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 13, 2010

Re: [Pharo-project] About String empty and others

by StÃ©phane Ducasse

On Feb 13, 2010, at 7:40 PM, Michael Roberts wrote: > would the idea to be to rewrite every #() with Array empty? no and this is a good question. For now I do not see what we learn. I'm not sure that these empty messages bring anything. besides one extra message. > If that was the case could you get the compiler to do that as an > optimization? I quite like the fact that #() is the empty array. it's > nice and compact; quite aesthetic. yes I will roll back some of the changes > > cheers, > Mike > > On Sat, Feb 13, 2010 at 11:06 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Hi guys >> >> chris mueller proposed in squeak to have >> >> >> Exception>>messageText >> "Return an exception's message text." >> + ^ messageText ifNil: [ String empty ]! >> - >> - ^messageText! >> >> - Added Array class>>#empty and String class>>#empty to provide applications with >> canonicalized instances of these oft-used objects; since they are embedded as literals in the >> CompiledMethod. >> >> =============== Diff against Collections-ar.304 =============== >> >> Item was added: >> + ----- Method: Array class>>empty (in category 'instance creation') ----- >> + empty >> + "A canonicalized empty Array instance." >> + ^ #()! >> >> Item was added: >> + ----- Method: String class>>empty (in category 'instance creation') ----- >> + empty >> + "A canonicalized empty String instance." >> + ^ ''! >> >> Item was removed: >> - ----- Method: String>>asDefaultDecodedString (in category 'converting') ----- >> - asDefaultDecodedString >> - >> - ^ self >> >> >> http://code.google.com/p/pharo/issues/detail?id=1961 >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 13, 2010

Re: [Pharo-project] About String empty and others

by Michael Roberts

would the idea to be to rewrite every #() with Array empty? If that was the case could you get the compiler to do that as an optimization? I quite like the fact that #() is the empty array. it's nice and compact; quite aesthetic. cheers, Mike On Sat, Feb 13, 2010 at 11:06 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > chris mueller proposed in squeak to have > > > Exception>>messageText > Â Â Â "Return an exception's message text." > + Â Â Â ^ messageText ifNil: [ String empty ]! > - > - Â Â Â ^messageText! > > - Added Array class>>#empty and String class>>#empty to provide applications with > canonicalized instances of these oft-used objects; since they are embedded as literals in the > CompiledMethod. > > =============== Diff against Collections-ar.304 =============== > > Item was added: > + ----- Method: Array class>>empty (in category 'instance creation') ----- > + empty > + Â Â Â "A canonicalized empty Array instance." > + Â Â Â ^ #()! > > Item was added: > + ----- Method: String class>>empty (in category 'instance creation') ----- > + empty > + Â Â Â "A canonicalized empty String instance." > + Â Â Â ^ ''! > > Item was removed: > - ----- Method: String>>asDefaultDecodedString (in category 'converting') ----- > - asDefaultDecodedString > - > - Â Â Â ^ self > > > http://code.google.com/p/pharo/issues/detail?id=1961 > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 13, 2010

[Pharo-project] [update 1.1] #11207

by StÃ©phane Ducasse

11207 ----- - Issue 1959: Replace isSomething by is: # (starting) - Fix of parser 16rff now works - Deprecate digitValue: to use digitValueOf:

Feb. 13, 2010