January 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3436 in pharo: #copyFrom: is broken

by pharo＠googlecode.com

Comment #16 on issue 3436 by step...(a)stack.nl: #copyFrom: is broken http://code.google.com/p/pharo/issues/detail?id=3436 5.7.8.7 does not adequately explain why copy should be part of the method name. To me it looks like accidental complexity, and I would like to avoid spreading it.

Jan. 7, 2011

Re: [Pharo-project] Origins [poll]

by Stanislav Paskalev

Jan. 7, 2011

Re: [Pharo-project] Including Zinc HTTP Components in Pharo 1.2 Dev ?

by StÃ©phane Ducasse

Another one :) We were looking at the users of ZnUtils and I have the impression that it would be good to split it so that we get several groups of coherent users. there are the groups for - networking + constants - http ... so this way people could reuse the networking + constants parts for others protocols. Stef

Jan. 7, 2011

Re: [Pharo-project] Issue 3508 in pharo: cleanUpForProduction should really unload 'Graphics-Resources'

by pharo＠googlecode.com

Updates: Status: Closed Comment #6 on issue 3508 by marcus.denker: cleanUpForProduction should really unload 'Graphics-Resources' http://code.google.com/p/pharo/issues/detail?id=3508 12293

Jan. 7, 2011

Re: [Pharo-project] Origins [poll]

by Noury Bouraqadi

Jan. 7, 2011

Re: [Pharo-project] Issue 3510 in pharo: HistoryNode problem with two consecutives closeGroup

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3510 by marcus.denker: HistoryNode problem with two consecutives closeGroup http://code.google.com/p/pharo/issues/detail?id=3510 12293

Jan. 7, 2011

[Pharo-project] Issues in mailinglist

by Torsten Bergmann

works again, sorry for this post -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

Jan. 7, 2011

[Pharo-project] Issues in mailinglist

by Torsten Bergmann

New issues dont seem to appear in the mailinglist/archive anymore: http://lists.gforge.inria.fr/pipermail/pharo-project/2011-January/date.html Bye T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

Jan. 7, 2011

Re: [Pharo-project] Issue 3511 in pharo: Possibility to register own help in system help

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3511 by marcus.denker: Possibility to register own help in system help http://code.google.com/p/pharo/issues/detail?id=3511 12293

Jan. 7, 2011

[Pharo-project] wiki style help

by Torsten Bergmann

Hi, Nice idea, I like the "wiki help description" for three reasons: - its pragma based AND allows for definition of structured books (so Lukas should be satisfied since he can define content without dependency on help system) - it allows us to reuse existing swiki contents (if the full syntax is supported we can query existing swikis!) So it is a nice idea and would be a good addition. I reworked Alains code to better fit the pluggable architecture of the HelpSystem framework (now using a builder): Use an updated 1.2 core image, code is attached 1. File in "Foo.st" (which defines a simple help description) => no dependency on any help system 2. First I added a registration mechanism (pragma <systemHelp> so one can add own help types to the system help (the one that appears when you open the default help browser) => load "AddToSystemHelpFix.1.cs" => at least this fix should go into Core 1.2, so no ugly hacks are necessary to appear in the default help browser I added a now fixed issue for core 1.2 on: http://code.google.com/p/pharo/issues/detail?id=3511 3. I reworked Alains code so it uses a WikiStyleHelpBuilder (similar to the other builders) and a WikiStyleHelp as a new help type => see WikiStyleHelp.5.cs => if we agree on this we can integrated it into core too, currently it is in an own class category/package => "HelpBrowser openOn: WikiStyleHelp" will show all contents defined using the wiki style syntax, so only the one defined in class Foo appears => "HelpBrowser open" will show all help in the system (including the ones defined in Foo) => since it uses the new registration mechanism (see 2. above) all these topics will also appear in the help browser that is accessible from the menu I would vote for adding this to core 1.2 too. It's additional, nothing should break. What do you all think... And thanks Alain for the idea and initial code!!! Have fun T. -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail

Jan. 7, 2011