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

Re: [Pharo-project] Help on collaborator Active book

by StÃ©phane Ducasse

On Apr 19, 2010, at 8:45 AM, laurent laffont wrote: > > List of Plugins @ > http://book.pharo-project.org/book/Virtual-Machine/VMPlugins/VMPluginsList > * "GeniePlugin : This plugin implements the functionality of" ??? > * "SurfacePlugin : This plugin is a fake" uh, what, lol > > > Thanks for your help Sean. > > For list of Plugins I've just extracted the first sentence of each Plugin's comment for start.... to be continued :) > > I would like to add for each plugin whether it's safe to built it internal or external. > > A section on how to write its own plugin would be cool. there is a chapter in the new blue book on my free books web page that explains that. We could get inspired. > And how to interface to an existing library. (QT, GTK, Webkit, ...) too. > > Can someone write the Mac OSX / Windows way to build the VM ? Yes jean-baptiste has that on his todo. > > Cheers, > > Laurent Laffont > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 19, 2010

[Pharo-project] Help on collaborator Active book

by Michael Roberts

On Sunday, April 18, 2010, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Fixed. > > Doru thanks! Mike

April 19, 2010

Re: [Pharo-project] we need help for rome

by StÃ©phane Ducasse

probably :) one coming from sophie and one coming from the repository. We will fix that as soon as we can make it run on mac (ok we just have to add the inst var) but would be nice to have a clean plugin but I imagine that john is stressed with the Scratch problem. Stef On Apr 19, 2010, at 8:44 AM, Alain Plantec wrote: > StÃ©phane Ducasse a Ã©crit : >> Thanks john oops I learned something. >> Now the problem is that I did not touch them. I just loaded code. So I wonder where they got lost or changed. >> >> Alain do you have the same in your image? >> > Hi all, > Just back from a cool week-end, with a lot of sun... > Yes, my RomePluginCanvas is the same as yours and it runs well on linux. > But I've not removed any inst var myself. > My version comes from the www.squeaksource.com/Rome. > I've checked, and the RomePluginCanvas from squeaksource is still the same as mine: > > RomeCanvas subclass: #RomePluginCanvas > instanceVariableNames: 'handle target flags strokeColor stack font fontSize fontMatrix' > classVariableNames: 'FlagFill FlagStroke Registry' > poolDictionaries: '' > category: 'Rome-PluginCanvas' > > so, does it means that there are also two version of the plugin ? > > Cheers > Alain >> Stef >> >> On Apr 17, 2010, at 4:09 AM, John M McIntosh wrote: >> >> >>> (a) In Sophie RomeCanvas subclass: #RomePluginCanvas >>> instanceVariableNames: 'handle target flags strokeColor stack font fontSize fontMatrix currentFillColor currentBackColor glyphAccuracy cachedGlyphBlt cachedClearBlt drawRunPositions drawRunGlyph drawRunPointY' >>> classVariableNames: 'CachedTarget FlagFill FlagStro >>> >>> (b) In Pharo >>> RomeCanvas subclass: #RomePluginCanvas >>> instanceVariableNames: 'handle target flags strokeColor stack font fontSize fontMatrix' >>> classVariableNames: 'FlagFill FlagStroke Registry' >>> poolDictionaries: '' >>> category: 'Rome-PluginCanvas' >>> >>> Comment warning: >>> INST VAR ORDER IS KNOWN TO PLUGIN! DO NOT REARRANGE! >>> >>> >>> So in the plugin we have... >>> if (interpreterProxy->slotSizeOf(canvasOop)) < CanvasInstSize) >>> fail(). >>> >>> >>> where CanvasInstSize is 13 >>> >>> but as you see in (b) the number of instance slots for the canvas Oops is 8. >>> 8 < 13, oops you fail. >>> So where did the instance vars currentFillColor currentBackColor glyphAccuracy cachedGlyphBlt cachedClearBlt >>> go? On purpose gone, refactored, old code. etc.... >>> >>> On 2010-04-16, at 1:37 PM, StÃ©phane Ducasse wrote: >>> >>> >>>> On Apr 16, 2010, at 10:30 PM, John McIntosh wrote: >>>> >>>> >>>>> Well I'm just as puzzled as you since the primitive gets executed and you are using the same binary that was shipped with Sophie years back. >>>> I like to hear that because I feel less idiot. :) >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> -- >>> =========================================================================== >>> John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 >>> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com >>> =========================================================================== >>> >>> >>> >>> >>> _______________________________________________ >>> 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

April 19, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Pharo 1.0 released!

by StÃ©phane Ducasse

On Apr 19, 2010, at 1:56 AM, Stephen Taylor wrote: > Henrik Johansen wrote: > >> Gotta love reddit... > [...] >> - "I don't know what Smalltalk is, and the site doesn't tell me, not even the about page!" > > That one I think is legitimate - and not just for Pharo but for almost every Open Source project out there. I think every project's home page should keep first time in visitors in mind. (My very least favourite thing for the first page of a site is to see the project commit log - talk about unwelcoming!). Good remark. Thanks. Does anybody have some text we could reuse? > And to say something positive - Pharo 1.0 looks great - solid and serious and workable. A couple of my co-workers have called my bluff and asked for a Smalltalk tutorial, and I'll be happy to show them Pharo. Excellent. :) Now I hope that in the future we will be able to amazed smalltalkers themselves... because this is the key point. If we succeed to have so a cool (I mean really cool) system then we will have done a good job Stef

April 19, 2010

Re: [Pharo-project] Help on collaborator Active book

by laurent laffont

> > > List of Plugins @ > http://book.pharo-project.org/book/Virtual-Machine/VMPlugins/VMPluginsList > * "GeniePlugin : This plugin implements the functionality of" ??? > * "SurfacePlugin : This plugin is a fake" uh, what, lol > > Thanks for your help Sean. For list of Plugins I've just extracted the first sentence of each Plugin's comment for start.... to be continued :) I would like to add for each plugin whether it's safe to built it internal or external. A section on how to write its own plugin would be cool. And how to interface to an existing library. (QT, GTK, Webkit, ...) too. Can someone write the Mac OSX / Windows way to build the VM ? Cheers, Laurent Laffont

April 19, 2010

Re: [Pharo-project] we need help for rome

by Alain Plantec

StÃ©phane Ducasse a Ã©crit : > Thanks john oops I learned something. > Now the problem is that I did not touch them. I just loaded code. So I wonder where they got lost or changed. > > Alain do you have the same in your image? > Hi all, Just back from a cool week-end, with a lot of sun... Yes, my RomePluginCanvas is the same as yours and it runs well on linux. But I've not removed any inst var myself. My version comes from the www.squeaksource.com/Rome. I've checked, and the RomePluginCanvas from squeaksource is still the same as mine: RomeCanvas subclass: #RomePluginCanvas instanceVariableNames: 'handle target flags strokeColor stack font fontSize fontMatrix' classVariableNames: 'FlagFill FlagStroke Registry' poolDictionaries: '' category: 'Rome-PluginCanvas' so, does it means that there are also two version of the plugin ? Cheers Alain > Stef > > On Apr 17, 2010, at 4:09 AM, John M McIntosh wrote: > > >> (a) In Sophie >> RomeCanvas subclass: #RomePluginCanvas >> instanceVariableNames: 'handle target flags strokeColor stack font fontSize fontMatrix currentFillColor currentBackColor glyphAccuracy cachedGlyphBlt cachedClearBlt drawRunPositions drawRunGlyph drawRunPointY' >> classVariableNames: 'CachedTarget FlagFill FlagStro >> >> (b) In Pharo >> >> RomeCanvas subclass: #RomePluginCanvas >> instanceVariableNames: 'handle target flags strokeColor stack font fontSize fontMatrix' >> classVariableNames: 'FlagFill FlagStroke Registry' >> poolDictionaries: '' >> category: 'Rome-PluginCanvas' >> >> Comment warning: >> >> INST VAR ORDER IS KNOWN TO PLUGIN! DO NOT REARRANGE! >> >> >> So in the plugin we have... >> >> if (interpreterProxy->slotSizeOf(canvasOop)) < CanvasInstSize) >> fail(). >> >> >> where CanvasInstSize is 13 >> >> but as you see in (b) the number of instance slots for the canvas Oops is 8. >> >> 8 < 13, oops you fail. >> >> So where did the instance vars currentFillColor currentBackColor glyphAccuracy cachedGlyphBlt cachedClearBlt >> go? On purpose gone, refactored, old code. etc.... >> >> >> On 2010-04-16, at 1:37 PM, StÃ©phane Ducasse wrote: >> >> >>> On Apr 16, 2010, at 10:30 PM, John McIntosh wrote: >>> >>> >>>> Well I'm just as puzzled as you since the primitive gets executed and you are using the same binary that was shipped with Sophie years back. >>>> >>> I like to hear that because I feel less idiot. :) >>> >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> -- >> =========================================================================== >> John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 >> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com >> =========================================================================== >> >> >> >> >> _______________________________________________ >> 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 > >

April 19, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Pharo 1.0 released!

by Igor Stasenko

On 16 April 2010 13:10, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > On Apr 15, 2010, at 10:33 31PM, Adrian Lienhard wrote: > >> Thanks, Daniel, for posting on reddit! We currently are almost at the top of the list... >> >> >> Cheers, >> Adrian > > Gotta love reddit... > 3 most repeated/discussed topics in comments: > Â - "I don't know what Smalltalk is, and the site doesn't tell me, not even the about page!" > Â - "SUCKS, I can't use my favourite text-editor and git!" > Â - "1 + 2 * 3 = 9 WTF SMALLTALK" > Oh yeah.. there are two guys battling to the death, each defending own point.. The guy who claims that precedence rules is a must, must be forgot, how much pain it was took to learn them in a childhood :) > :D > > Cheers, > Henry > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

April 19, 2010

Re: [Pharo-project] Help on collaborator Active book

by Sean P. DeNigris

I made a slew of minor edits. Here were some impressions that I didn't have enough information to fix: Announcements @ http://book.pharo-project.org/book/announcements * I'd like to see a short explanation of the trade-offs involved in announcements vs. simple message sends. The page speaks vaguely to this, but I think it would be very valuable to have a "Smalltalk Best Practice Patterns"-style description of the pros and cons of each so people can make informed decisions in their projects. Fixing underscores @ http://book.pharo-project.org/book/TipsAndTricks/FixingUnderscores * I wasn't sure whether this was an instruction, a suggestion, or merely an option. Is this necessary? personal preference? Again, some background would help. List of Plugins @ http://book.pharo-project.org/book/Virtual-Machine/VMPlugins/VMPluginsList * "GeniePlugin : This plugin implements the functionality of" ??? * "SurfacePlugin : This plugin is a fake" uh, what, lol Traits @ http://book.pharo-project.org/book/Traits: * This one I found very tough. Especially the initial part of the BulletinBoard example. I wasn't sure how I would play with the example in my own image. For instance, what should the subclass of BulletinBoard be? * "BoardListener new listenAndReact makes sure that each time the method announceNewAddedItem is executed on the created bulletinBoard, the event is received by the listener." Does it? It seems to just write to the Transcript, and not be connected to the listener at all. * "Open an inspector on the expression above" - which expression? * "! Going deeper When applying a trait to a class it may face different situations." * "!!Using Alias to access a hidden method" This section (the beginning anyway), seemed to describe something different than the title here. It's great to have a resource like this - let's squeeze all the juice out of it. Sean -- View this message in context: http://n4.nabble.com/Help-on-collaborator-Active-book-tp2014707p2015363.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 19, 2010

Re: [Pharo-project] Help on collaborator Active book

by Javier PimÃ¡s

Hi!! When reading the book I feel a bit lost, "out of context", I'd like to be able to see what part of the book I'm reading. I think it would be reeeaaally nice to have the navigation section to the right show more of this context, not just the next and previous pages. Something more like a small table of contents relative to the page being read. What do you think? Do you think it'd be possible/reasonable? Regards, Javier. On Sun, Apr 18, 2010 at 2:51 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > this is really cool to see this collaborative space taking shape. > I should start to write other chapters directly there too > > > Fixed. > > > > Doru > > > > > > On 18 Apr 2010, at 19:15, Lukas Renggli wrote: > > > >>> cheers Lukas, can you check how it has rendered, i am not sure the > >>> copy/paste has quite worked? > >> > >> Looks good, except for the part on keywords. Probably the mail messed > >> up some line wrappings. > >> > >> Lukas > >> > >> > >> > >> > >>> > >>> Mike > >>> > >>> On Sun, Apr 18, 2010 at 10:57 AM, Lukas Renggli <renggli(a)gmail.com> > wrote: > >>>>> yes i was going to copy it into the new help section. Can someone > with > >>>>> access to book.seaside.st send me the original markup? or tell me > how > >>>>> I can view the pier source. I have added a link for now. > >>>> > >>>> +value:toc+ > >>>> > >>>> !Parts, Chapters, Sections, Subsections > >>>> > >>>> Do not use the heading markup !, it cannot be properly converted to > >>>> Latex. Instead add a new structure for every section using the ==Add== > >>>> command. Name the section according to their latex label, only use > >>>> lowercase characters and no spaces. This is the name that will appear > >>>> in the URL. For the title capitalize the individual words. > >>>> > >>>> Chapters, sections and subsections are displayed in the order they are > >>>> created. They can be rearranged using the ==Order== command. > >>>> > >>>> !Figures > >>>> > >>>> To embed a figure create a link of the form > >>>> > >>>> =+foo.png|width=100%+ > >>>> > >>>> The line embeds the figure and sets the width of the image. For the > >>>> width use a percentage between 50% and 100%. Only upload PNG files > >>>> without transparency, no JPEG or GIF files. Do not upload files that > >>>> have spaces in their name. As the name property use the name of the > >>>> file you upload. Edit the title property, it will become the caption > >>>> of the image and show up in the index of figures. > >>>> > >>>> If the figure does not exist yet, it will show as a red link. Clicking > >>>> on it allows you to create it. Chose "Book Figure" as the structure > >>>> type to create. Then on the next page edit the title (caption) and > >>>> upload the image. > >>>> > >>>> !Keyword Index > >>>> To add a keyword to the index use ==\+index:WAComponent\+==. To add a > >>>> two level keyword use the syntax > >>>> ==\+index:WAComponent!renderContentOn:\+==. Note that this markup does > >>>> not generate any output. Preferably put it at the beginning of the > >>>> paragraph. > >>>> > >>>> !Source Code > >>>> For inlined source code use the syntax ==\==100 factorial\== ==. For > >>>> blocks of code that should be highlighted using the Smalltalk parser > >>>> begin each line with == \== ==. Use 4 spaces to indent the code, no > >>>> tabs. > >>>> > >>>> ==Integer>>factorial > >>>> == ^ self < 2 > >>>> == ifTrue: [ 1 ] > >>>> == ifFalse: [ self * (self - 1) factorial ] > >>>> > >>>> To have non highlighted code begin each line with a single =====. > >>>> > >>>> =squeak -headless seaside.image > >>>> > >>>> !References > >>>> > >>>> To create references to chapters, sections or figures use the normal > >>>> link-syntax but prepend it with ==ref:==, for example: > >>>> > >>>> =*ref:foo.png* > >>>> =*ref:../components* > >>>> > >>>> @here > >>>> This will create a link of the form *Form 123>.@here* and *Section > 4>.@here*. > >>>> > >>>> !Paragraph > >>>> Avoid unnecessary line breaks in paragraphs. Don't use wrapped text, > >>>> that is clumsy and almost impossible to edit afterwards from the web > >>>> browser. In TextMate use the command ''Unwrap Paragraph > >>>> (Ctrl\+Alt\+Q)'' to properly format the paragraph before pasting into > >>>> Pier. > >>>> > >>>> Use the syntax ==\@@important This is the paragraph text.== to > >>>> annotate a paragraph. > >>>> > >>>> @@important This is an ==\@@important== paragraph. > >>>> > >>>> @@blockquote This is a ==\@@blockquote== paragraph. > >>>> > >>>> @@note This is a ==\@@note== paragraph. > >>>> > >>>> @@advanced This is an ==\@@advanced== paragraph. > >>>> > >>>> @@todo This is a ==\@@todo== paragraph. > >>>> > >>>> !Navigation > >>>> | j | Previous Page > >>>> | k | Next Page > >>>> | p | Parent Page > >>>> | i | Table of Contents > >>>> > >>>> -- > >>>> Lukas Renggli > >>>> www.lukas-renggli.ch > >>>> > >>>> _______________________________________________ > >>>> 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 > >>> > >> > >> > >> > >> -- > >> Lukas Renggli > >> www.lukas-renggli.ch > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > > www.tudorgirba.com > > > > "Not knowing how to do something is not an argument for how it cannot be > done." > > > > > > _______________________________________________ > > 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 > -- Javier PimÃ¡s Ciudad de Buenos Aires

April 19, 2010

Re: [Pharo-project] Setup package fixes

by Levente Uzonyi

On Sun, 18 Apr 2010, Sean P. DeNigris wrote: > > I sent some fixes to the package owner, but also posted a link to the mcz > file http://seandenigris.com/files/Setup-SeanDeNigris.47.mcz here , in case > anyone wants it. Why did't you upload it to the squeaksource repository directly? (http://squeaksource.com/setup.html ) > > * Fix - Setup>>installDevelopment - changed from Installer (which is not > pre-installed in Pharo 1.0) to Gopher. > * Fix - Setup>>installSpecificUser - Changed "Author initials" (depreciated > in Pharo 1.0) to "author fullName". > - changed all author initials to full names, except jre because I didn't > know what it stood for. Probably Jorge Ressia. Levente > > I tested it against Pharo-Core 1.0 & PharoCore-1.1-11312-UNSTABLE. I tried > to port it to Squeak 4.1, but got various errors, so I backed out the > changes. But if you are interested, I can send them to you. > > Sean > -- > View this message in context: http://n4.nabble.com/Setup-package-fixes-tp2015309p2015309.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 19, 2010