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

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

by Lukas Renggli

> 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

April 18, 2010

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

by StÃ©phane Ducasse

John how can I know the order and the iv that are used by the plugin? 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

April 18, 2010

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

by StÃ©phane Ducasse

Like that :) I will send you the information for your account. Stef On Apr 18, 2010, at 4:24 PM, Sean P. DeNigris wrote: > > I would love to contribute to the book (I'm great at catching grammatical > mistakes as I read). It seems like a login is needed - how do I get one? > > Thanks. > - Sean > -- > View this message in context: http://n4.nabble.com/Help-on-collaborator-Active-book-tp2014707p2014882.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 18, 2010

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

by Michael Roberts

cheers Lukas, can you check how it has rendered, i am not sure the copy/paste has quite worked? 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 >

April 18, 2010

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

by Sean P. DeNigris

I would love to contribute to the book (I'm great at catching grammatical mistakes as I read). It seems like a login is needed - how do I get one? Thanks. - Sean -- View this message in context: http://n4.nabble.com/Help-on-collaborator-Active-book-tp2014707p2014882.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 18, 2010

Re: [Pharo-project] Iliad 0.8 released!

by Nicolas Petton

Le dimanche 18 avril 2010 Ã 12:49 +0100, Ramiro Diaz Trepat a Ã©crit : > Thanks for the announcement but, what is iliad? Oops, I guess I should have explained it... Iliad is a new web framework. It is made around the following features: - standalone stateful widgets - automatic AJAX with degradation to normal requests if javascript is not available - RESTful applications - simple and concise API - easy to setup and deploy It reuses pieces of code from other frameworks: the dispatch pattern from HttpView2, the composite element hierarachy for building HTML from Aida/Web, and the stateful widgets from Seaside, however without using continuations. You can learn more at: http://www.iliadproject.org Cheers! Nicolas > > > > > 2010/4/18 Nicolas Petton <petton.nicolas(a)gmail.com> > Le dimanche 18 avril 2010 Ã 00:05 +0100, Julian Fitzell a > Ã©crit : > > Cool stuff, Nicolas. > > Thanks Julian :) > > > I'm happy to see Grease getting use in the wild... I'm > curious to what > > degree it met your needs? > > > Once Paolo and I ported it to GNU Smalltalk, it *really* met > my needs! > Of course it's a bit Seaside oriented but almost everything I > needed was > there. > > It allowed me to remove non portable code (like code for > encoding, > remove all #asString/#printString, etc), use useful classes > provided by > Grease like GRSmallDictionary. In the future I will probably > use > GRDelaySend too. > > As a direct consequence, I was also able to serve files from > the image > without adding dialect specific code :) > > And of course Unit tests were really helpful. > > Now I'm not really happy with the codec stuff, as from a GNU > Smalltalker > point of view it seems too Squeak/Pharo oriented, but I can > leave with > that for now. > > Cheers! > > Nicolas > > _______________________________________________ > 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 18, 2010

Re: [Pharo-project] Iliad 0.8 released!

by Ramiro Diaz Trepat

Thanks for the announcement but, what is iliad? 2010/4/18 Nicolas Petton <petton.nicolas(a)gmail.com> > Le dimanche 18 avril 2010 Ã 00:05 +0100, Julian Fitzell a Ã©crit : > > Cool stuff, Nicolas. > > Thanks Julian :) > > > I'm happy to see Grease getting use in the wild... I'm curious to what > > degree it met your needs? > > Once Paolo and I ported it to GNU Smalltalk, it *really* met my needs! > Of course it's a bit Seaside oriented but almost everything I needed was > there. > > It allowed me to remove non portable code (like code for encoding, > remove all #asString/#printString, etc), use useful classes provided by > Grease like GRSmallDictionary. In the future I will probably use > GRDelaySend too. > > As a direct consequence, I was also able to serve files from the image > without adding dialect specific code :) > > And of course Unit tests were really helpful. > > Now I'm not really happy with the codec stuff, as from a GNU Smalltalker > point of view it seems too Squeak/Pharo oriented, but I can leave with > that for now. > > Cheers! > > Nicolas > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 18, 2010

Re: [Pharo-project] Iliad 0.8 released!

by Nicolas Petton

Le dimanche 18 avril 2010 Ã 00:05 +0100, Julian Fitzell a Ã©crit : > Cool stuff, Nicolas. Thanks Julian :) > I'm happy to see Grease getting use in the wild... I'm curious to what > degree it met your needs? Once Paolo and I ported it to GNU Smalltalk, it *really* met my needs! Of course it's a bit Seaside oriented but almost everything I needed was there. It allowed me to remove non portable code (like code for encoding, remove all #asString/#printString, etc), use useful classes provided by Grease like GRSmallDictionary. In the future I will probably use GRDelaySend too. As a direct consequence, I was also able to serve files from the image without adding dialect specific code :) And of course Unit tests were really helpful. Now I'm not really happy with the codec stuff, as from a GNU Smalltalker point of view it seems too Squeak/Pharo oriented, but I can leave with that for now. Cheers! Nicolas

April 18, 2010

Re: [Pharo-project] About the collaborative pier

by StÃ©phane Ducasse

I like not to be the only guy not understanding :) On Apr 18, 2010, at 10:23 AM, Michael Roberts wrote: > Stef, Doru i have got confused as well with where pages get added. It > makes sense once you understand what Pier is doing, but i have put too > many pages in the wrong place. > > Anyway i have created a help chapter, with some tips. Please feel > free to correct or add more. > > cheers, > Mike > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 18, 2010

Re: [Pharo-project] Canvas transform bug when rendering text?

by StÃ©phane Ducasse

On Apr 18, 2010, at 10:32 AM, Michael Roberts wrote: > On Sun, Apr 18, 2010 at 8:21 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> we should release 1.1 much faster :) >> like that people will be able to get all the fixes.... > > yes ;) > > for tagging fixes for 1.0 maintenance, should we use a milestone 1.0.1 > in the tracker? - is this code candidate for 1.0.1? 1.0.1 would be better because we really want to not spend too much time on this one since far too many fixes were made in 1.1 Stef > > cheers, > Mike > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 18, 2010