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

Re: [Pharo-project] About using pragma for help like in setting

by laurent laffont

Cool ! Laurent. On Sun, Dec 12, 2010 at 10:25 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi, > > help system design is very open and using pragmas can be done. > I already showed an example - look in the archive. > > Will respond in detail this evening. > > Thx > T. > > > -- > GRATIS! Movie-FLAT mit Ã¼ber 300 Videos. > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome > >

Dec. 12, 2010

Re: [Pharo-project] About using pragma for help like in setting

by laurent laffont

> > > I think, the fact that there is no single external package with help > system documentation proves this, no? > Actually there's at least Help on HelpSystem ;) ProfStef, WebTester, Metacello, Mocketry, Mondrian. I've started one for Pier but on Seaside mailing-list nobody have answered :( So yes there's some help, it's slow. I agree 100% on what you said about dependencies, documentation close to code, tagging/pragma approach, .... but it seems to me that whatever system we adopt, growing documentation will be slow . So we need to push to write doc. even if the current or futures systems are not perfect. Laurent. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > >

Dec. 12, 2010

[Pharo-project] About using pragma for help like in setting

by Torsten Bergmann

Hi, help system design is very open and using pragmas can be done. I already showed an example - look in the archive. Will respond in detail this evening. Thx T. -- GRATIS! Movie-FLAT mit Ã¼ber 300 Videos. Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome

Dec. 12, 2010

Re: [Pharo-project] good news of the year

by laurent laffont

It's sooooo exciting. Congrats to INRIA, StÃ©phane and you Igor ! Laurent On Sat, Dec 11, 2010 at 6:40 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Thanks everyone. > > I had very warm and friendly greeting here in Lille. And atmosphere is > very cool (everyone around you using pharo). > I am a full of enthusiasm and energy to put in Pharo, as never before. ;) > > > -- > Best regards, > Igor Stasenko AKA sig. > >

Dec. 12, 2010

Re: [Pharo-project] Loading *some of* a MC snapshot into the image

by Lukas Renggli

1. From the merge dialog you individually pick and install the changes that work. In the old merge dialog this works nicely. 2. You manually fix your code, e.g. the variable changes that do not work. 3. You close the merge dialog (cancel). 4. You adopt the merged version. 5. You commit. Lukas On 12 December 2010 04:37, Damien Pollet <damien.pollet(a)gmail.com> wrote: > I have a snapshot compiled against an old version of PetitParser. > Unfortunately one of my classes now has a conflicting inst var with > the most recent PetitParser, so my code does not load, MC explodes > instead of giving me a chance to fix the problem on the fly. Of > course, there are quite a few changes I'd like to rescue in that > snapshot. Please don't tell me I have to copy-paste them allâ¦ > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > > -- Lukas Renggli www.lukas-renggli.ch

Dec. 12, 2010

Re: [Pharo-project] good news of the year

by GÃ¶ran Krampe

Hi Igor and all! My warmest congratulations to you Igor and the rest of the team over there in Lille, and I hope to see you again! regards, GÃ¶ran

Dec. 12, 2010

Re: [Pharo-project] Issue 3402 in pharo: SmalltalkEditor new raises an Error

by pharo＠googlecode.com

Comment #2 on issue 3402 by stephane.ducasse: SmalltalkEditor new raises an Error http://code.google.com/p/pharo/issues/detail?id=3402 (No comment was entered for this change.) Attachments: NewTextMorph-TextEditor-fixes.1.cs 1.6 KB

Dec. 12, 2010

Re: [Pharo-project] Issue 3402 in pharo: SmalltalkEditor new raises an Error

by pharo＠googlecode.com

Comment #1 on issue 3402 by stephane.ducasse: SmalltalkEditor new raises an Error http://code.google.com/p/pharo/issues/detail?id=3402 The #changeParagraph: is bogus: changeParagraph: aParagraph "Install aParagraph as the one to be edited by the receiver." self resetState TextEditor>>paragraph is following: paragraph ^ morph ifNotNil: [morph paragraph] I changed the TextEditor, for creating and initializing it not like: TextEditor new but like: TextEditor newForMorph: morph in that way, TextEditor>>paragraph always works. And for same reason, i removed the #changeParagraph: , because it useless. Also, the following test is now should be rewritten: CompilerEvaluationTest>>testEvaluationOfSelfSend SmalltalkEditorTest >> testCompilationOfUndefinedVar they using old SmalltalkEditor new, instead of (newForMorph:) as well as using #changeParagraph: So, creating SmalltalkEditor can be done like: morph := NewTextMorph new. morph paragraph: paragraph. editor := SmalltalkEditor newForMorph: morph.

Dec. 12, 2010

Re: [Pharo-project] Ideas for HelpSystem

by StÃ©phane Ducasse

let us start small but steady instead of having the full system only in dream. We should really improve on that level so I will allocate some time on that and integrate less fixes. Stef On Dec 12, 2010, at 6:04 AM, Damien Pollet wrote: > On Sat, Dec 11, 2010 at 00:18, Bernardo Ezequiel Contreras > <vonbecmann(a)gmail.com> wrote: >> here's a similar example >> >> http://soek.goodies.st.s3.amazonaws.com/index.html > > Indeed, but part of my point was the how polished Yard is (both > appearance and interaction). > It integrates API and manual/tutorial-type documentation. > Also it's extensible so a project that defines a DSL can also include > a Yard plugin to document that DSL nicely. There's an example with > Sinatra on their website. > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet >

Dec. 12, 2010

Re: [Pharo-project] About using pragma for help like in setting

by StÃ©phane Ducasse

Sean I understand 100% lukas's approach, somebody contacted me to know if we the core with a web server can be under a certain size and if this is needed then we must remove the doc on production. The setting tag is working well so we can just use the same pattern and we get an help system that does not depend on any external class of the package, that can be searched. It scales. Now I was thinking that torsten would reply to this mail but in 1.3 will take a decision because I want a really better help and documentation inside the right class and package. Stef

Dec. 12, 2010