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

[Pharo-project] Date time iso8601 format

by laurent laffont

Hi, I cannot find which method to use to get a Date in iso 8601 format like '2008-02-10T12:00:00Z' ? Cheers, Laurent Laffont Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/

Nov. 6, 2010

[Pharo-project] Fwd:Dr.geo en Arabe

by Hilaire Fernandes

hanks Ahmed! A request. Is it possible to have Arab language under Pharo? Hilaire -------- Message original -------- Sujet: Dr.geo en Arabe Date : Sat, 06 Nov 2010 13:29:40 +0000 De : Ahmed Mansour <atphalix(a)inbox.com> Pour : Hilaire Fernandes <hilaire.fernandes(a)gmail.com> Bonjour Hilaire, Si joint la traduction de Dr.Geo II en Arabe, j'ai testÃ© uniquement sous Etoys vu qu'il a le support de Pango (indispensable pour le rendu de script complexe), est-t-il possible d'ajouter le support de Pango Ã Pharo dans une version prochaine? Cordialement, -- Ahmed Mansour http://olpc-maroc.blogspot.com http://twitter.com/OLPCMorocco ____________________________________________________________ Share photos & screenshots in seconds... TRY FREE IM TOOLPACK at http://www.imtoolpack.com/default.aspx?rc=if1 Works in all emails, instant messengers, blogs, forums and social networks.

Nov. 6, 2010

[Pharo-project] About simple morphic

by StÃ©phane Ducasse

Hi guys the mail may be a bit long sorry. ESUG was supporting Morphic 3 (a new proposal) of Juan. Now it occurred that Juan realized that he will not be able to deliver what he wanted. So After discussion one idea was to get simpleMorphic (not lighMorphic) a simpler version of Morphic done by juan for Squeak and Pharo. We believe that this is good because Juan could deliver something and we could support him. Juan sent us the code and I published it at http://code.google.com/p/pharo/issues/detail?id=3210 Here is the original text: > I'm really happy to tell you: SimpleMorphic for Pharo is working! The attached zip file contains a few numbered change sets, to be installed in Pharo in order. > > The contents of the change sets are as follows: > - SMx01-PharoEnhAndPreliminaries-jmv.3.cs and SMx02-PharoEnhAndPreliminariesCoda.1.cs contain some refactoring needed to make it possible to add another GUI to Pharo. Nothing here is specific to SimpleMorphic, and I recommend integrating them into Pharo. > - SMx03-ExtensionMethodsPart1.3.cs contains a few useful methods, not specific to SimpleMorphic, but optional anyway. You might integrate this into Pharo or consider it part of SimpleMorphic. > - SMx04-SimpleMorphic.11.cs This change set is the big one. It includes all the new SimpleMorphic classes. It doesn't include any method for existing classes (to make review easier). > - SMx05-ExtensionMethodsPart2.7.cs This change set includes the SimpleMorphic specific methods I added to existing classes. > > After loading them, you can evaluate 'SimpleMorphicUIManager start' to enter SimpleMorphic and 'SimpleMorphicUIManager stop' to return to regular Morphic. > > As SimpleMorphic is much simpler and easier to understand that regular Morphic, my biggest hope is that the Pharo community will adopt it, study it in detail, and be able to adapt it to Pharo's needs all way down. No need to walk away from overwhelming complexity anymore. > > I look forward for your comments! Now after discussion with Juan: we plan to integrate SM01, 02, and 03 to be able to load SM04. SM04 is not in a shape were we can simply migrate on it - Polymorph first polymorph is tight with the old Morphic - Preference are still used - FillInTheBlank, PopUp.... are used. Now I suggest that we integrate 01.02.03 and package the rest to be loaded in 1.2 This way we can either update SimpleMorphic to get more pharoed or we could use it to study and fix morphic. But all that will require some work. Tell us what you think.

Nov. 6, 2010

Re: [Pharo-project] The next milestone reached!

by StÃ©phane Ducasse

Cool! I hope to get some time this evening to work on the test reorganization and a couple of other things but my time is counted in this moment Stef On Nov 6, 2010, at 12:47 PM, Pavel Krivanek wrote: > This screenshot is more representative ;-) > > -- Pavel > > On Sat, Nov 6, 2010 at 12:12 PM, Pavel Krivanek > <pavel.krivanek(a)gmail.com> wrote: >> Hi all, >> >> I successfully loaded the the rest of PharoCore packages into the >> PharoKernel. The Morphic initialization works too. See the attached >> screenshot. I will publish the scripts later today. >> >> Cheers, >> -- Pavel >> > <PharoCore.png>

Nov. 6, 2010

Re: [Pharo-project] RoarVM - Pharo and Squeak on Multicore

by StÃ©phane Ducasse

Thanks Stefan Stef On Nov 6, 2010, at 11:11 AM, Stefan Marr wrote: > > On 06 Nov 2010, at 10:16, StÃ©phane Ducasse wrote: > >> Should it be included in pharo? >> IfTrue: open a bug tracker issue > That depends on what you think is the correct thing to do... > > Anyway: > http://code.google.com/p/pharo/issues/detail?id=3209 > > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > >

Nov. 6, 2010

Re: [Pharo-project] The next milestone reached!

by Pavel Krivanek

This screenshot is more representative ;-) -- Pavel On Sat, Nov 6, 2010 at 12:12 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi all, > > I successfully loaded the the rest of PharoCore packages into the > PharoKernel. The Morphic initialization works too. See the attached > screenshot. I will publish the scripts later today. > > Cheers, > -- Pavel >

Nov. 6, 2010

Re: [Pharo-project] The next milestone reached!

by laurent laffont

Yes yes !! So many good news these times :) Laurent On Sat, Nov 6, 2010 at 12:12 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com>wrote: > Hi all, > > I successfully loaded the the rest of PharoCore packages into the > PharoKernel. The Morphic initialization works too. See the attached > screenshot. I will publish the scripts later today. > > Cheers, > -- Pavel >

Nov. 6, 2010

Re: [Pharo-project] The next milestone reached!

by Tudor Girba

Nice job. This is exciting! Doru On 6 Nov 2010, at 12:12, Pavel Krivanek wrote: > Hi all, > > I successfully loaded the the rest of PharoCore packages into the > PharoKernel. The Morphic initialization works too. See the attached > screenshot. I will publish the scripts later today. > > Cheers, > -- Pavel > <PharoScreenshot.1.png> -- www.tudorgirba.com "Don't give to get. Just give."

Nov. 6, 2010

[Pharo-project] The next milestone reached!

by Pavel Krivanek

Hi all, I successfully loaded the the rest of PharoCore packages into the PharoKernel. The Morphic initialization works too. See the attached screenshot. I will publish the scripts later today. Cheers, -- Pavel

Nov. 6, 2010

Re: [Pharo-project] Writing API for XML (WAX) - Bibliography example

by Hannes Hirzel

Jaayer, Thanks, I checked out MCHttpRepository location: 'http://www.squeaksource.com/XMLSupport' user: '' password: '' and looked at XML-Parser-tg.101 Right version? the class comment of XMLWriter This class allows you to generate well-formed XML documents using an API similar to Seaside's canvas and tag brush API. Markup can be created by sending an instance any of the messages under "writing markup." The messages that take no arguments return an instance of an XMLMarkupWriter subclass. These objects can be configured with messages like #name: and #attributeAt:put:. Sending them #write or a specific writing message that accepts markup to embed within (#content: or #internalSubset: for example) causes the markup writer's configuration to be committed and its markup written to the output stream. For markup writers that can have embedded markup, the argument to the writing message can be a string, collection (of strings and blocks), a block, or nil. The block passed in can optionally take an argument, which will be the XMLWriter object that created the markup writer object. Within the block you can generate additional, child markup that will be contained by the parent. Creating additional non-embedded markup will cause any unwritten markup from a previous markup writer to be written, as will sending an XMLWriter or XMLMarkupWriter #contents, #asString, #printOn:, or #write. Here is an example, which you can highlight and evaluate with cmd-p to see the result: | writer | (writer := XMLWriter new) enablePrettyPrinting. writer xml. writer tag name: 'foo:bar'; xmlnsAt: 'foo' put: 'http://foo'; attributeAt: 'a' put: 'one'; attributeAt: 'b' put: 'two'; content: [ writer tag: 'bar' content: [ writer string: 'test'; tag: 'baz'; tag: 'foobar' content: 'test']] Nice, as I know the Seaside html builder pattern. It is the same. Remark: I think it should be in its own package Instead of XML-Parser-Writers I'd like to have XML-Writer because writing has nothing to do with parsing. However at this point it is minor cosmetics. Another remark: An example using tags like name, author, title would be helpful as well in the class comment because one sees more easily what is going on. For the current problem at hand I have started using WAX and I think I will continue to do so. One reason it that I might want to port my App to Java when finished prototyping in Smalltalk. MCHttpRepository location: 'http://www.squeaksource.com/WAX' user: '' password: '' I have not found XMLWriter tests whereas WAX has a considerable number of them. As for XMLWriter, I surely will look at it again in a few months time. Regards Hannes On 11/5/10, jaayer <jaayer(a)zoho.com> wrote: > > > > > ---- On Wed, 03 Nov 2010 11:28:13 -0700 Hannes Hirzel wrote ---- > >>Is XMLWriter in the upcoming 1.2 image? It is not in the 1.1 image. >> >>--Hannes > > The new XML writer is in the more recent versions, from version 96 on, but > at the moment you have to download it manually through Monticello or from > the XMLSupport page on squeaksource.com, as the most recent Metacello > configuration still points to v. 93. I'll try to update it shortly. > > >

Nov. 6, 2010