March 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] Pharo 1.4 Tests-Unix - Build # 272 - Still Unstable!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

March 7, 2012

Re: [Pharo-project] GSoC ideas, 5 days to go!

by Geoffroy Couprie

The old (97) Excel file format is a weird file system acting as a database. It is also used for doc, msi and cab files. The new format (xslx, docx, etc) is just a zipped bunch of xml files, so it's quite easy to parse :) On Wed, Mar 7, 2012 at 3:05 PM, Carla F. Griggio <carla.griggio(a)gmail.com>wrote: > Great! > > That reminds me... would it be too hard to be able to export Excel files > from Pharo? Or at least Open Office Spreadsheets? > > That could be a project idea too. > > On Wed, Mar 7, 2012 at 10:38 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi, >> >> Good one, Nick. I can offer to be second mentor on this one as well. >> >> Cheers, >> Doru >> >> >> >> On Wed, Mar 7, 2012 at 2:32 PM, Nick Ager <nick.ager(a)gmail.com> wrote: >> > Hi Janko, >> > >> > Here you go: 'ePUB Output for Pier Books' >> > >> > -------------- >> > >> > Name: ePUB Output for Pier Books >> > Level: Intermediate >> > Possible mentor: Nick Ager >> > Possible second mentor: Lukas Rengli >> > >> > Description >> > Pier [1,2] is an extensible object-oriented content management >> system that >> > includes a book authoring engine. The book authoring engine has been >> used to >> > document a number of Smalltalk based projects, most notable Seaside [3] >> as >> > well as Moose [4] and Pharo [5]. >> > >> > The goal of this project is add ePUB [6] as an output format to Pier >> > enabling existing and future Pier books and other Pier content to be >> output >> > in a format readable by popular eReaders. >> > >> > [1] http://www.piercms.com/ >> > [2] http://code.google.com/p/pier/ >> > [3] http://book.seaside.st/ >> > [4] http://www.themoosebook.org/ >> > [5] http://book.pharo-project.org/ >> > [6] http://en.wikipedia.org/wiki/EPUB >> > >> > Technical Details >> > >> > Content in Pier is parsed into a document tree that supports the visitor >> > pattern [7] for traversing the internal representation. Pier currently >> > supports a number of output formats such as HTML, plain text, RSS, wiki >> > text. These formats are generated by visitors. The existing visitors >> would >> > act as a template for creation of an ePUB visitor which would generate >> ePUB >> > compatible output. >> > >> > [7] http://en.wikipedia.org/wiki/Visitor_pattern >> > >> > Benefits to the Student >> > The project is well defined with a clear deliverable. The student will >> gain >> > an understanding of the internals of a powerful, well structured content >> > management system as well as the satisfaction of having a set of >> artefacts >> > in the format of the existing Pier book content translated into ePUB >> > format. >> > >> > Benefits to the Community >> > The Smalltalk community and others using the Pier book authoring engine >> will >> > gain ePUB as an output format. With an ebook output format authors have >> a >> > potential new revenue source, encouraging a virtuous cycle of increasing >> > documentation within and outside the community. >> > >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> >> >

March 7, 2012

Re: [Pharo-project] GSoC ideas, 5 days to go!

by Carla F. Griggio

Great! That reminds me... would it be too hard to be able to export Excel files from Pharo? Or at least Open Office Spreadsheets? That could be a project idea too. On Wed, Mar 7, 2012 at 10:38 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Good one, Nick. I can offer to be second mentor on this one as well. > > Cheers, > Doru > > > > On Wed, Mar 7, 2012 at 2:32 PM, Nick Ager <nick.ager(a)gmail.com> wrote: > > Hi Janko, > > > > Here you go: 'ePUB Output for Pier Books' > > > > -------------- > > > > Name: ePUB Output for Pier Books > > Level: Intermediate > > Possible mentor: Nick Ager > > Possible second mentor: Lukas Rengli > > > > Description > > Pier [1,2] is an extensible object-oriented content management > system that > > includes a book authoring engine. The book authoring engine has been > used to > > document a number of Smalltalk based projects, most notable Seaside [3] > as > > well as Moose [4] and Pharo [5]. > > > > The goal of this project is add ePUB [6] as an output format to Pier > > enabling existing and future Pier books and other Pier content to be > output > > in a format readable by popular eReaders. > > > > [1] http://www.piercms.com/ > > [2] http://code.google.com/p/pier/ > > [3] http://book.seaside.st/ > > [4] http://www.themoosebook.org/ > > [5] http://book.pharo-project.org/ > > [6] http://en.wikipedia.org/wiki/EPUB > > > > Technical Details > > > > Content in Pier is parsed into a document tree that supports the visitor > > pattern [7] for traversing the internal representation. Pier currently > > supports a number of output formats such as HTML, plain text, RSS, wiki > > text. These formats are generated by visitors. The existing visitors > would > > act as a template for creation of an ePUB visitor which would generate > ePUB > > compatible output. > > > > [7] http://en.wikipedia.org/wiki/Visitor_pattern > > > > Benefits to the Student > > The project is well defined with a clear deliverable. The student will > gain > > an understanding of the internals of a powerful, well structured content > > management system as well as the satisfaction of having a set of > artefacts > > in the format of the existing Pier book content translated into ePUB > > format. > > > > Benefits to the Community > > The Smalltalk community and others using the Pier book authoring engine > will > > gain ePUB as an output format. With an ebook output format authors have a > > potential new revenue source, encouraging a virtuous cycle of increasing > > documentation within and outside the community. > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > >

March 7, 2012

Re: [Pharo-project] GSoC ideas, 5 days to go!

by Tudor Girba

Hi, Good one, Nick. I can offer to be second mentor on this one as well. Cheers, Doru On Wed, Mar 7, 2012 at 2:32 PM, Nick Ager <nick.ager(a)gmail.com> wrote: > Hi Janko, > > Here you go: 'ePUB Output for Pier Books' > > -------------- > > Name: ePUB Output for Pier Books > Level: Intermediate > Possible mentor: Nick Ager > Possible second mentor: Lukas Rengli > > Description > Pier [1,2]Â isÂ anÂ extensibleÂ object-oriented content management systemÂ that > includes a book authoring engine. The book authoring engine has been used to > document a number of Smalltalk based projects, most notable Seaside [3] as > well as Moose [4]Â and Pharo [5]. > > The goal of this project is add ePUB [6] as an output format to Pier > enabling existing and future Pier books and other Pier content to be output > in a format readable by popular eReaders. > > [1]Â http://www.piercms.com/ > [2]Â http://code.google.com/p/pier/ > [3]Â http://book.seaside.st/ > [4]Â http://www.themoosebook.org/ > [5]Â http://book.pharo-project.org/ > [6]Â http://en.wikipedia.org/wiki/EPUB > > Technical Details > > Content in Pier is parsed into a document tree that supports the visitor > pattern [7] for traversing the internal representation. Pier currently > supports a number of output formats such as HTML, plain text, RSS, wiki > text. These formats are generated by visitors. The existing visitors would > act as a template for creation of an ePUB visitor which would generate ePUB > compatible output. > > [7]Â http://en.wikipedia.org/wiki/Visitor_pattern > > Benefits to the Student > The project is well defined with a clear deliverable. The student will gain > an understanding of the internals of a powerful, well structured content > management system as well as the satisfaction of having a set of artefacts > in the format of the existing Pier book content translated into ePUB > format. > > Benefits to the Community > The Smalltalk community and others using the Pier book authoring engine will > gain ePUB as an output format. With an ebook output format authors have a > potential new revenue source, encouraging a virtuous cycle of increasing > documentation within and outside the community. > -- www.tudorgirba.com "Every thing has its own flow"

March 7, 2012

Re: [Pharo-project] GSoC ideas, 5 days to go!

by Nick Ager

Hi Janko, Here you go: 'ePUB Output for Pier Books' -------------- Name: ePUB Output for Pier Books Level: Intermediate Possible mentor: Nick Ager Possible second mentor: Lukas Rengli Description Pier [1,2] is an *extensible* object-oriented content management system that includes a book authoring engine. The book authoring engine has been used to document a number of Smalltalk based projects, most notable Seaside [3] as well as Moose [4] and Pharo [5]. The goal of this project is add ePUB [6] as an output format to Pier enabling existing and future Pier books and other Pier content to be output in a format readable by popular eReaders. [1] http://www.piercms.com/ [2] http://code.google.com/p/pier/ [3] http://book.seaside.st/ [4] http://www.themoosebook.org/ [5] http://book.pharo-project.org/ [6] http://en.wikipedia.org/wiki/EPUB Technical Details Content in Pier is parsed into a document tree that supports the visitor pattern [7] for traversing the internal representation. Pier currently supports a number of output formats such as HTML, plain text, RSS, wiki text. These formats are generated by visitors. The existing visitors would act as a template for creation of an ePUB visitor which would generate ePUB compatible output. [7] http://en.wikipedia.org/wiki/Visitor_pattern Benefits to the Student The project is well defined with a clear deliverable. The student will gain an understanding of the internals of a powerful, well structured content management system as well as the satisfaction of having a set of artefacts in the format of the existing Pier book content translated into ePUB format. Benefits to the Community The Smalltalk community and others using the Pier book authoring engine will gain ePUB as an output format. With an ebook output format authors have a potential new revenue source, encouraging a virtuous cycle of increasing documentation within and outside the community.

March 7, 2012

Re: [Pharo-project] We crossed 5000 closed issues!

by Sven Van Caekenberghe

On 07 Mar 2012, at 11:52, StÃ©phane Ducasse wrote: > We underestimate the amount of work we put in the system :) Yes. > And this is great to have a way to get reminded that we should just continue. Yes. > The future is bright :) Yes! ;-) Sven

March 7, 2012

[Pharo-project] [update 1.4] #14381

by Marcus Denker

14381 ----- Issue 5443: Adding SimpleSwitchMorph (for Stef) http://code.google.com/p/pharo/issues/detail?id=5443 Issue 5105: it allows me to install a method when the class doesnt exists. http://code.google.com/p/pharo/issues/detail?id=5105 -- Marcus Denker -- http://marcusdenker.de

March 7, 2012

Re: [Pharo-project] Smalltalk as embedded platform/language?

by StÃ©phane Ducasse

+ 1 I know personally Philippe Mougin... Can't we focus on OUR future :)? Stef > not really, why asking? > I know there's plenty of alternatives.. > And how do you see f-script could help us? > It is objective-c (or Mac ) oriented. If you would want to use > different platform , then what? > > > > -- > Best regards, > Igor Stasenko. >

March 7, 2012

[Pharo-project] [update 1.3] #13326

by Marcus Denker

13326 ----- Issue 5153: warningAllowed does not work with undefined selectors http://code.google.com/p/pharo/issues/detail?id=5153 -- Marcus Denker -- http://marcusdenker.de

March 7, 2012

Re: [Pharo-project] Mouse move and button down events

by Hilaire Fernandes

I did this ugly hack Child>>handleMouseMove: evt self owner owner owner mouseMove: evt I would like a cleaner way to handle it. Le 07/03/2012 11:16, Hilaire Fernandes a Ã©crit : > Hello, > > I have two embedded morphs: a parent and a child. > > On the child I want to handle mouse down event, > > Child>>handlesMouseDown: event > ^true > > On parent I want to handle mouse down+move event: > > There are not distinct handlesMouseMove, only > Parent>>handlesMouseDown: event > ^true > > Now, events received by child handlesMouseDown are always > MouseButtonEvent, never MouveMoveEvent, so no chance to answer true or > false accordingly. I guess MouseButtonEvent is catched first, then other > mouseMove event discarded > > What I want is the child to received clic events, but the parent move > events. It does not seem possible, am I wrong? > > -- Dr. Geo -- http://www.drgeo.eu

March 7, 2012