- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Who is maintaining the Grease configuration

by Dale Henrichs

I'm the editor for the Grease configuration, so I'll take this on ... Dale ----- Original Message ----- | From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> | To: "Pharo-project(a)lists.gforge.inria.fr Development" <Pharo-project(a)lists.gforge.inria.fr> | Sent: Wednesday, April 25, 2012 7:37:14 AM | Subject: [Pharo-project] Who is maintaining the Grease configuration | | Because we should create a symbolic version for 20 | | This package depends on the following classes: | BlockContext | You must resolve these dependencies before you will be able to load | these definitions: | fixCallbackTemps | tempVarRefs | valueWithPossibleArguments: | | |

April 25, 2012

Re: [Pharo-project] Artefact - a PDF framework

by Francois Stephany

I've adopted the poor man's solution: 1. Output my report in HTML/CSS. 2. Use wkhtmltopdf (http://code.google.com/p/wkhtmltopdf/) to convert it to PDF. The drawback is obviously the call to OSProcess but it gets the job done. On 25/04/12 06:06, Christoph Wysseier wrote: > For our web applications a PDF generator is a crucial part too. There > were AFAIK several attempts to build such a framework in Smalltalk > (SPDF, ...) but in the end none of these became feature-rich and/or > powerful. > > I really like the new effort. Due to the past experience I am skeptical > if such a framework really makes sense but I would love to be convinced > from the opposite. Powerful PDF generators such as Apache FOP (based on > standardised XSL:fo) face what a feature-complete framework would need > to implement (area model with relative text flow, image processing, > typography including font embedding, formatting, ...). > > Olivier, this would be my wish list BTW and very cool! ;) > > For those who cannot wait I propose to use Apache FOP > (http://xmlgraphics.apache.org/fop) for PDF generation. Although built > with Java (slow, requires a lot of ressources, etc.) it can be used as > black box (servlet) fed using XML and XSL:fo data over a Unix socket. > Most of our applications are using this solution at the moment as it > offers a powerful solution for professional pdf documents. Ugly but > works like a charm since years here... > > Cheers, > Chris > > Am 25.04.12 11:23, schrieb StÃ©phane Ducasse: >> We really want to generate report for Moose so we are really >> interested by this effort. >> >> Stef >> >> On Apr 25, 2012, at 10:18 AM, Damien Cassou wrote: >> >>> Hi Olivier, >>> >>> On Wed, Apr 25, 2012 at 10:15 AM, Olivier Auverlot >>> <olivier.auverlot(a)gmail.com> wrote: >>>> If you test it, thanks for your remarks and suggestions. >>> >>> such a framework makes a lot of sense. Could you please create a few >>> unit tests or a small web page with examples so everyone can get a >>> glimpse of the API rapidly? Some examples for the Common Lisp >>> equivalent are at: www.fractalconcept.com/asp/asdataQuQhZ0XhCuWs >>> >>> Best, >>> >>> -- >>> Damien Cassou >>> http://damiencassou.seasidehosting.st >>> >>> "Lambdas are relegated to relative obscurity until Java makes them >>> popular by not having them." James Iry > > > -- http://tulipemoutarde.be CA: +1 778 558 3225 BE: +32 65 709 131

April 25, 2012

Re: [Pharo-project] Editor focus & hotkeys

by Gary Chambers

Looks like stab/shift-tab is well broken at the moment. I'll investigate further when I get time. Regards, Gary ----- Original Message ----- From: "blake" <dsblakewatson(a)gmail.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, April 25, 2012 3:54 PM Subject: Re: [Pharo-project] Editor focus & hotkeys >>> No, don't change it! Now I know the secret! Others should have to >>> suffer as well! :-) >> >> Nice approach LOL That's why I do not comment my code :) It was hard to >> write, it should be hard to read ^^ > > Or, as I like to say before playing a song, "I've suffered for my > music, now it's your turn." > > >> Thank both of you for your feedback :) > > Thanks for listening! > > ===Blake=== >

April 25, 2012

Re: [Pharo-project] Polymorph (and a few other) changes/fixes

by Gary Chambers

And another... That'll have to do for now. The tab focus things will take quite some investigation... Regards, Gary ----- Original Message ----- From: "Gary Chambers" <gazzaguru2(a)btinternet.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, April 25, 2012 3:52 PM Subject: Re: [Pharo-project] Polymorph (and a few other) changes/fixes > Fixes for checkbox, Benjamin, please check as I had to revert the > CheckboxMorph>>initialize to not hook the click event. > > Also I notice that tabbing from lists (and shift-tabbing from multiline > text) appears to have been broken at some point > before these changes. > > Attached lastest cs > > Regards, Gary > > ----- Original Message ----- > From: "Gary Chambers" <gazzaguru2(a)btinternet.com> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Wednesday, April 25, 2012 3:36 PM > Subject: Re: [Pharo-project] Polymorph (and a few other) changes/fixes > > >> Indeed. >> >> Hold off on integration for a few mins, some last minute fixes... >> >> Regards, Gary >> >> ----- Original Message ----- >> From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> >> To: <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Wednesday, April 25, 2012 1:17 PM >> Subject: Re: [Pharo-project] Polymorph (and a few other) changes/fixes >> >> >> In the future we will have to look at respondsTo: >> and remove them because we should enforce for example that objects that >> are used have the right protocol >> >> |label| >> label := self checkboxLabelForText: aCheckbox label. >> (label respondsTo: #enabled:) ifTrue: [ >> label enabled: aCheckbox enabled]. >> label font: self labelFont. >> ^label >> >> >> On Apr 25, 2012, at 1:53 PM, StÃ©phane Ducasse wrote: >> >>> I see such idiom and I'm thinking that it would be good to fix such kind >>> of respondsTo: >>> >>> self allMorphsDo: [:m | >>> (m ~= self and: [m respondsTo: #font:]) >>> ifTrue: [m font: aFont]] >>> >>> >>> Stef >> >> >> >

April 25, 2012

Re: [Pharo-project] Editor focus & hotkeys

by blake

>> No, don't change it! Now I know the secret! Others should have to >> suffer as well! :-) > > Nice approach LOL That's why I do not comment my code :) It was hard to write, it should be hard to read ^^ Or, as I like to say before playing a song, "I've suffered for my music, now it's your turn." > Thank both of you for your feedback :) Thanks for listening! ===Blake===

April 25, 2012

Re: [Pharo-project] Polymorph (and a few other) changes/fixes

by Gary Chambers

Fixes for checkbox, Benjamin, please check as I had to revert the CheckboxMorph>>initialize to not hook the click event. Also I notice that tabbing from lists (and shift-tabbing from multiline text) appears to have been broken at some point before these changes. Attached lastest cs Regards, Gary ----- Original Message ----- From: "Gary Chambers" <gazzaguru2(a)btinternet.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, April 25, 2012 3:36 PM Subject: Re: [Pharo-project] Polymorph (and a few other) changes/fixes > Indeed. > > Hold off on integration for a few mins, some last minute fixes... > > Regards, Gary > > ----- Original Message ----- > From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Wednesday, April 25, 2012 1:17 PM > Subject: Re: [Pharo-project] Polymorph (and a few other) changes/fixes > > > In the future we will have to look at respondsTo: > and remove them because we should enforce for example that objects that > are used have the right protocol > > |label| > label := self checkboxLabelForText: aCheckbox label. > (label respondsTo: #enabled:) ifTrue: [ > label enabled: aCheckbox enabled]. > label font: self labelFont. > ^label > > > On Apr 25, 2012, at 1:53 PM, StÃ©phane Ducasse wrote: > >> I see such idiom and I'm thinking that it would be good to fix such kind >> of respondsTo: >> >> self allMorphsDo: [:m | >> (m ~= self and: [m respondsTo: #font:]) >> ifTrue: [m font: aFont]] >> >> >> Stef > > >

April 25, 2012

[Pharo-project] Who is maintaining the Grease configuration

by StÃ©phane Ducasse

Because we should create a symbolic version for 20 This package depends on the following classes: BlockContext You must resolve these dependencies before you will be able to load these definitions: fixCallbackTemps tempVarRefs valueWithPossibleArguments:

April 25, 2012

Re: [Pharo-project] Polymorph (and a few other) changes/fixes

by Gary Chambers

Indeed. Hold off on integration for a few mins, some last minute fixes... Regards, Gary ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, April 25, 2012 1:17 PM Subject: Re: [Pharo-project] Polymorph (and a few other) changes/fixes In the future we will have to look at respondsTo: and remove them because we should enforce for example that objects that are used have the right protocol |label| label := self checkboxLabelForText: aCheckbox label. (label respondsTo: #enabled:) ifTrue: [ label enabled: aCheckbox enabled]. label font: self labelFont. ^label On Apr 25, 2012, at 1:53 PM, StÃ©phane Ducasse wrote: > I see such idiom and I'm thinking that it would be good to fix such kind > of respondsTo: > > self allMorphsDo: [:m | > (m ~= self and: [m respondsTo: #font:]) > ifTrue: [m font: aFont]] > > > Stef

April 25, 2012

[Pharo-project] [update 2.0] #20010

by StÃ©phane Ducasse

20010 ----- reintroducing addPackage: so that we can load configuration. Stef

April 25, 2012

Re: [Pharo-project] Artefact - a PDF framework

by Gary Chambers

Hi, if you'd like any help with fonts and images I can assist. Perviously I've implemented those things on top of SPDF. Regards, Gary ----- Original Message ----- From: Olivier Auverlot To: Pharo-project(a)lists.gforge.inria.fr Sent: Wednesday, April 25, 2012 9:15 AM Subject: [Pharo-project] Artefact - a PDF framework Hi, I work actually on a PDF framework for Pharo. MCHttpRepository location: 'http://www.squeaksource.com/artefact' user: '' password: '' My project is in progress and many things are not finalized (no documentation, not enough unit tests, etc.). But, you can produce PDF documents with metadata, multiple page formats in a same document, draw tables, write text and paragraphs, play with colors and grey levels. If you test it, thanks for your remarks and suggestions. Best regards Olivier ;-) www.auverlot.fr

April 25, 2012