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

Re: [Pharo-project] About CodeMorph and Styler dependency

by Fernando olivero

Oh! my mistake, sorry. i will add the bug entry now. Fernando On May 25, 2010, at 2:11 PM, StÃ©phane Ducasse wrote: > ok I forgot it. :( Please add a bug entry else we forgot. > > Stef > > On May 25, 2010, at 9:01 AM, Fernando olivero wrote: > >> Hi Stef, regarding some recent mails about CodeMorph and Shout dependency i don't know if you got this email. >> But i've removed the dependency from Shout and Styler. >> >> I'm still thinking about using Lukas petit parser to do the styling, or separating the Shout package in two different packages. >> One that deals with TextMorph and the other just for Styling text. >> >> Fernando >> >> >> Begin forwarded message: >> >>> From: Fernando olivero <oliverof(a)lu.unisi.ch> >>> Date: May 17, 2010 5:51:30 PM GMT+02:00 >>> To: "Pharo-project(a)lists.gforge.inria.fr" <Pharo-project(a)lists.gforge.inria.fr> >>> Subject: Re: [Pharo-project] TextEditor and NewTextMorph merges and fixes >>> >>> De nada ! >>> >>> Actually i just published another version of the CodeMorph. >>> I found no need for subclassing CodeMorph, since the accepting behavior is on the announcements now, having specific ClassDescriptionMorph and MethodMorph wouldn't be beneficial. >>> Also removed the dependency with the Shout ( and the styler). >>> >>> >>> Name: Morphic-FernandoOlivero.589 >>> Rethought the CodeMorph class hierarchy, removed the subclasses and added CodeMorph class methods for creating >>> "MethodMorph" and "ClassDefinitionMorph" >>> >>> >>> Fernando >>> >>> On May 17, 2010, at 3:35 PM, StÃ©phane Ducasse wrote: >>> >>>> Tx!!!! >>>> Gaucho man >>>> >>>> On May 17, 2010, at 3:32 PM, Fernando olivero wrote: >>>> >>>>> Issue: 2375 >>>>> >>>>> Name: System-Text-FernandoOlivero.8 >>>>> Author: FernandoOlivero >>>>> Time: 17 May 2010, 3:22:14 pm >>>>> >>>>> >>>>> >>>>> ###################################### >>>>> Issue: -- >>>>> >>>>> Name: Morphic-FernandoOlivero.588 >>>>> Author: FernandoOlivero >>>>> Time: 17 May 2010, 1:42:04 pm >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 25, 2010

Re: [Pharo-project] About CodeMorph and Styler dependency

by StÃ©phane Ducasse

ok I forgot it. :( Please add a bug entry else we forgot. Stef On May 25, 2010, at 9:01 AM, Fernando olivero wrote: > Hi Stef, regarding some recent mails about CodeMorph and Shout dependency i don't know if you got this email. > But i've removed the dependency from Shout and Styler. > > I'm still thinking about using Lukas petit parser to do the styling, or separating the Shout package in two different packages. > One that deals with TextMorph and the other just for Styling text. > > Fernando > > > Begin forwarded message: > >> From: Fernando olivero <oliverof(a)lu.unisi.ch> >> Date: May 17, 2010 5:51:30 PM GMT+02:00 >> To: "Pharo-project(a)lists.gforge.inria.fr" <Pharo-project(a)lists.gforge.inria.fr> >> Subject: Re: [Pharo-project] TextEditor and NewTextMorph merges and fixes >> >> De nada ! >> >> Actually i just published another version of the CodeMorph. >> I found no need for subclassing CodeMorph, since the accepting behavior is on the announcements now, having specific ClassDescriptionMorph and MethodMorph wouldn't be beneficial. >> Also removed the dependency with the Shout ( and the styler). >> >> >> Name: Morphic-FernandoOlivero.589 >> Rethought the CodeMorph class hierarchy, removed the subclasses and added CodeMorph class methods for creating >> "MethodMorph" and "ClassDefinitionMorph" >> >> >> Fernando >> >> On May 17, 2010, at 3:35 PM, StÃ©phane Ducasse wrote: >> >>> Tx!!!! >>> Gaucho man >>> >>> On May 17, 2010, at 3:32 PM, Fernando olivero wrote: >>> >>>> Issue: 2375 >>>> >>>> Name: System-Text-FernandoOlivero.8 >>>> Author: FernandoOlivero >>>> Time: 17 May 2010, 3:22:14 pm >>>> >>>> >>>> >>>> ###################################### >>>> Issue: -- >>>> >>>> Name: Morphic-FernandoOlivero.588 >>>> Author: FernandoOlivero >>>> Time: 17 May 2010, 1:42:04 pm >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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

May 25, 2010

Re: [Pharo-project] [BUG]UndefinedObject(Object)>>doesNotUnderstand: #binary

by Henrik Johansen

PS: the title of this thread would be much better if you went a step down, ie: "stream can be nil in DataStream setStream:". "UndefinedObject doesNotUnderstand: #binary" really tells nothing about what/where the error actually occurs. Cheers, Herny > > UndefinedObject(Object)>>doesNotUnderstand: #binary > ReferenceStream(DataStream)>>setStream: > ReferenceStream>>setStream: > ReferenceStream class(DataStream class)>>on: > ReferenceStream class>>on: > ReferenceStream class(DataStream class)>>newFileNamed: > ReferenceStream class>>newFileNamed:do: > [] in PatPatagoniaFileDatabase>>saveRepository > [] in Semaphore>>critical: > BlockClosure>>ensure: > Semaphore>>critical: > PatPatagoniaFileDatabase>>saveRepository > [] in PatPatagoniaFileDatabase>>takeSnapshot > [] in BlockClosure>>newProcess > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 25, 2010

Re: [Pharo-project] [BUG]UndefinedObject(Object)>>doesNotUnderstand: #binary

by Henrik Johansen

1. ReferenceStream newFileNamed:do: does not exist in base. 2. newFileNamed: can return nil, if it can't open a file stream, even after GC. 3. This usually implies too many file handles are open. 4. The best thing that can be done in core, is probably to raise an error in DataStream newFileNamed: if the opening of the underlying stream fails, but that won't really solve your problems. i.e., this is most probably an application error caused by not closing file streams so creating new ones fails. Cheers, Henry On May 25, 2010, at 1:03 54PM, damien.pollet(a)inria.fr wrote: > here insert explanation of what you were doing, suspect changes you've > made and so forth. > > 25 May 2010 1:03:21 pm > > VM: unix - x86_64 - linux - Squeak3.10.2 of '5 June 2008' [latest > update: #7179] > Image: Pharo-1.0 [Latest update: #10517] > > SecurityManager state: > Restricted: false > FileAccess: true > SocketAccess: true > Working Dir /var/www/seaside/register > Trusted Dir /var/www/seaside/register/secure > Untrusted Dir /var/www/seaside/register/My Squeak > > UndefinedObject(Object)>>doesNotUnderstand: #binary > Receiver: nil > Arguments and temporary variables: > aMessage: binary > exception: MessageNotUnderstood: receiver of "binary" is nil > resumeValue: nil > Receiver's instance variables: > nil > > ReferenceStream(DataStream)>>setStream: > Receiver: <<error during printing>> > Arguments and temporary variables: > aStream: nil > Receiver's instance variables: > byteStream: nil > topCall: nil > basePos: nil > references: nil > objects: nil > currentReference: nil > fwdRefEnds: nil > blockers: nil > skipping: nil > insideASegment: nil > > ReferenceStream>>setStream: > Receiver: <<error during printing>> > Arguments and temporary variables: > aStream: nil > Receiver's instance variables: > byteStream: nil > topCall: nil > basePos: nil > references: nil > objects: nil > currentReference: nil > fwdRefEnds: nil > blockers: nil > skipping: nil > insideASegment: nil > > ReferenceStream class(DataStream class)>>on: > Receiver: ReferenceStream > Arguments and temporary variables: > aStream: nil > Receiver's instance variables: > superclass: DataStream > methodDict: a MethodDictionary(#beginInstance:size:->a > CompiledMethod(117: Refe...etc... > format: 150 > instanceVariables: #('references' 'objects' 'currentReference' > 'fwdRefEnds' 'bl...etc... > organization: ('reading' beginReference: getCurrentReference > maybeBeginReferenc...etc... > subclasses: {SmartRefStream} > name: #ReferenceStream > classPool: a Dictionary(#RefTypes->an OrderedCollection(0 0 0 0 1 1 1 > 1 1 0 1 0...etc... > sharedPools: nil > environment: Smalltalk > category: #'System-Object Storage' > traitComposition: nil > localSelectors: nil > > ReferenceStream class>>on: > Receiver: ReferenceStream > Arguments and temporary variables: > aStream: nil > Receiver's instance variables: > superclass: DataStream > methodDict: a MethodDictionary(#beginInstance:size:->a > CompiledMethod(117: Refe...etc... > format: 150 > instanceVariables: #('references' 'objects' 'currentReference' > 'fwdRefEnds' 'bl...etc... > organization: ('reading' beginReference: getCurrentReference > maybeBeginReferenc...etc... > subclasses: {SmartRefStream} > name: #ReferenceStream > classPool: a Dictionary(#RefTypes->an OrderedCollection(0 0 0 0 1 1 1 > 1 1 0 1 0...etc... > sharedPools: nil > environment: Smalltalk > category: #'System-Object Storage' > traitComposition: nil > localSelectors: nil > > ReferenceStream class(DataStream class)>>newFileNamed: > Receiver: ReferenceStream > Arguments and temporary variables: > aString: > '/var/www/seaside/register/PatagoniaBackup/register/esug2010.1' > strm: nil > Receiver's instance variables: > superclass: DataStream > methodDict: a MethodDictionary(#beginInstance:size:->a > CompiledMethod(117: Refe...etc... > format: 150 > instanceVariables: #('references' 'objects' 'currentReference' > 'fwdRefEnds' 'bl...etc... > organization: ('reading' beginReference: getCurrentReference > maybeBeginReferenc...etc... > subclasses: {SmartRefStream} > name: #ReferenceStream > classPool: a Dictionary(#RefTypes->an OrderedCollection(0 0 0 0 1 1 1 > 1 1 0 1 0...etc... > sharedPools: nil > environment: Smalltalk > category: #'System-Object Storage' > traitComposition: nil > localSelectors: nil > > ReferenceStream class>>newFileNamed:do: > Receiver: ReferenceStream > Arguments and temporary variables: > aName: > '/var/www/seaside/register/PatagoniaBackup/register/esug2010.1' > aBlock: [closure] in [] in PatPatagoniaFileDatabase>>saveRepository > file: nil > Receiver's instance variables: > superclass: DataStream > methodDict: a MethodDictionary(#beginInstance:size:->a > CompiledMethod(117: Refe...etc... > format: 150 > instanceVariables: #('references' 'objects' 'currentReference' > 'fwdRefEnds' 'bl...etc... > organization: ('reading' beginReference: getCurrentReference > maybeBeginReferenc...etc... > subclasses: {SmartRefStream} > name: #ReferenceStream > classPool: a Dictionary(#RefTypes->an OrderedCollection(0 0 0 0 1 1 1 > 1 1 0 1 0...etc... > sharedPools: nil > environment: Smalltalk > category: #'System-Object Storage' > traitComposition: nil > localSelectors: nil > > [] in PatPatagoniaFileDatabase>>saveRepository > Receiver: a PatPatagoniaFileDatabase > Arguments and temporary variables: > fileName: > '/var/www/seaside/register/PatagoniaBackup/register/esug2010.1' > Receiver's instance variables: > conference: a PatConference > entryPoint: 'register/esug2010' > lock: a Semaphore(a Process in [] in Semaphore>>critical: a Process > in [] in Se...etc... > > [] in Semaphore>>critical: > Receiver: a Semaphore(a Process in [] in Semaphore>>critical: a Process > in [] in Semaphore>>critical...etc... > Arguments and temporary variables: > <<error during printing> > Receiver's instance variables: > firstLink: a Process in [] in Semaphore>>critical: > lastLink: a Process in [] in Semaphore>>critical: > excessSignals: 0 > > BlockClosure>>ensure: > Receiver: [closure] in Semaphore>>critical: > Arguments and temporary variables: > aBlock: [closure] in Semaphore>>critical: > returnValue: nil > b: nil > Receiver's instance variables: > outerContext: Semaphore>>critical: > startpc: 38 > numArgs: 0 > > Semaphore>>critical: > Receiver: a Semaphore(a Process in [] in Semaphore>>critical: a Process > in [] in Semaphore>>critical...etc... > Arguments and temporary variables: > <<error during printing> > Receiver's instance variables: > firstLink: a Process in [] in Semaphore>>critical: > lastLink: a Process in [] in Semaphore>>critical: > excessSignals: 0 > > PatPatagoniaFileDatabase>>saveRepository > Receiver: a PatPatagoniaFileDatabase > Arguments and temporary variables: > > Receiver's instance variables: > conference: a PatConference > entryPoint: 'register/esug2010' > lock: a Semaphore(a Process in [] in Semaphore>>critical: a Process > in [] in Se...etc... > > [] in PatPatagoniaFileDatabase>>takeSnapshot > Receiver: a PatPatagoniaFileDatabase > Arguments and temporary variables: > > Receiver's instance variables: > conference: a PatConference > entryPoint: 'register/esug2010' > lock: a Semaphore(a Process in [] in Semaphore>>critical: a Process > in [] in Se...etc... > > [] in BlockClosure>>newProcess > Receiver: [closure] in PatPatagoniaFileDatabase>>takeSnapshot > Arguments and temporary variables: > > Receiver's instance variables: > outerContext: PatPatagoniaFileDatabase>>takeSnapshot > startpc: 45 > numArgs: 0 > > > --- The full stack --- > UndefinedObject(Object)>>doesNotUnderstand: #binary > ReferenceStream(DataStream)>>setStream: > ReferenceStream>>setStream: > ReferenceStream class(DataStream class)>>on: > ReferenceStream class>>on: > ReferenceStream class(DataStream class)>>newFileNamed: > ReferenceStream class>>newFileNamed:do: > [] in PatPatagoniaFileDatabase>>saveRepository > [] in Semaphore>>critical: > BlockClosure>>ensure: > Semaphore>>critical: > PatPatagoniaFileDatabase>>saveRepository > [] in PatPatagoniaFileDatabase>>takeSnapshot > [] in BlockClosure>>newProcess > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 25, 2010

[Pharo-project] [BUG]UndefinedObject(Object)>>doesNotUnderstand: #binary

by damien.pollet＠inria.fr

here insert explanation of what you were doing, suspect changes you've made and so forth. 25 May 2010 1:03:21 pm VM: unix - x86_64 - linux - Squeak3.10.2 of '5 June 2008' [latest update: #7179] Image: Pharo-1.0 [Latest update: #10517] SecurityManager state: Restricted: false FileAccess: true SocketAccess: true Working Dir /var/www/seaside/register Trusted Dir /var/www/seaside/register/secure Untrusted Dir /var/www/seaside/register/My Squeak UndefinedObject(Object)>>doesNotUnderstand: #binary Receiver: nil Arguments and temporary variables: aMessage: binary exception: MessageNotUnderstood: receiver of "binary" is nil resumeValue: nil Receiver's instance variables: nil ReferenceStream(DataStream)>>setStream: Receiver: <<error during printing>> Arguments and temporary variables: aStream: nil Receiver's instance variables: byteStream: nil topCall: nil basePos: nil references: nil objects: nil currentReference: nil fwdRefEnds: nil blockers: nil skipping: nil insideASegment: nil ReferenceStream>>setStream: Receiver: <<error during printing>> Arguments and temporary variables: aStream: nil Receiver's instance variables: byteStream: nil topCall: nil basePos: nil references: nil objects: nil currentReference: nil fwdRefEnds: nil blockers: nil skipping: nil insideASegment: nil ReferenceStream class(DataStream class)>>on: Receiver: ReferenceStream Arguments and temporary variables: aStream: nil Receiver's instance variables: superclass: DataStream methodDict: a MethodDictionary(#beginInstance:size:->a CompiledMethod(117: Refe...etc... format: 150 instanceVariables: #('references' 'objects' 'currentReference' 'fwdRefEnds' 'bl...etc... organization: ('reading' beginReference: getCurrentReference maybeBeginReferenc...etc... subclasses: {SmartRefStream} name: #ReferenceStream classPool: a Dictionary(#RefTypes->an OrderedCollection(0 0 0 0 1 1 1 1 1 0 1 0...etc... sharedPools: nil environment: Smalltalk category: #'System-Object Storage' traitComposition: nil localSelectors: nil ReferenceStream class>>on: Receiver: ReferenceStream Arguments and temporary variables: aStream: nil Receiver's instance variables: superclass: DataStream methodDict: a MethodDictionary(#beginInstance:size:->a CompiledMethod(117: Refe...etc... format: 150 instanceVariables: #('references' 'objects' 'currentReference' 'fwdRefEnds' 'bl...etc... organization: ('reading' beginReference: getCurrentReference maybeBeginReferenc...etc... subclasses: {SmartRefStream} name: #ReferenceStream classPool: a Dictionary(#RefTypes->an OrderedCollection(0 0 0 0 1 1 1 1 1 0 1 0...etc... sharedPools: nil environment: Smalltalk category: #'System-Object Storage' traitComposition: nil localSelectors: nil ReferenceStream class(DataStream class)>>newFileNamed: Receiver: ReferenceStream Arguments and temporary variables: aString: '/var/www/seaside/register/PatagoniaBackup/register/esug2010.1' strm: nil Receiver's instance variables: superclass: DataStream methodDict: a MethodDictionary(#beginInstance:size:->a CompiledMethod(117: Refe...etc... format: 150 instanceVariables: #('references' 'objects' 'currentReference' 'fwdRefEnds' 'bl...etc... organization: ('reading' beginReference: getCurrentReference maybeBeginReferenc...etc... subclasses: {SmartRefStream} name: #ReferenceStream classPool: a Dictionary(#RefTypes->an OrderedCollection(0 0 0 0 1 1 1 1 1 0 1 0...etc... sharedPools: nil environment: Smalltalk category: #'System-Object Storage' traitComposition: nil localSelectors: nil ReferenceStream class>>newFileNamed:do: Receiver: ReferenceStream Arguments and temporary variables: aName: '/var/www/seaside/register/PatagoniaBackup/register/esug2010.1' aBlock: [closure] in [] in PatPatagoniaFileDatabase>>saveRepository file: nil Receiver's instance variables: superclass: DataStream methodDict: a MethodDictionary(#beginInstance:size:->a CompiledMethod(117: Refe...etc... format: 150 instanceVariables: #('references' 'objects' 'currentReference' 'fwdRefEnds' 'bl...etc... organization: ('reading' beginReference: getCurrentReference maybeBeginReferenc...etc... subclasses: {SmartRefStream} name: #ReferenceStream classPool: a Dictionary(#RefTypes->an OrderedCollection(0 0 0 0 1 1 1 1 1 0 1 0...etc... sharedPools: nil environment: Smalltalk category: #'System-Object Storage' traitComposition: nil localSelectors: nil [] in PatPatagoniaFileDatabase>>saveRepository Receiver: a PatPatagoniaFileDatabase Arguments and temporary variables: fileName: '/var/www/seaside/register/PatagoniaBackup/register/esug2010.1' Receiver's instance variables: conference: a PatConference entryPoint: 'register/esug2010' lock: a Semaphore(a Process in [] in Semaphore>>critical: a Process in [] in Se...etc... [] in Semaphore>>critical: Receiver: a Semaphore(a Process in [] in Semaphore>>critical: a Process in [] in Semaphore>>critical...etc... Arguments and temporary variables: <<error during printing> Receiver's instance variables: firstLink: a Process in [] in Semaphore>>critical: lastLink: a Process in [] in Semaphore>>critical: excessSignals: 0 BlockClosure>>ensure: Receiver: [closure] in Semaphore>>critical: Arguments and temporary variables: aBlock: [closure] in Semaphore>>critical: returnValue: nil b: nil Receiver's instance variables: outerContext: Semaphore>>critical: startpc: 38 numArgs: 0 Semaphore>>critical: Receiver: a Semaphore(a Process in [] in Semaphore>>critical: a Process in [] in Semaphore>>critical...etc... Arguments and temporary variables: <<error during printing> Receiver's instance variables: firstLink: a Process in [] in Semaphore>>critical: lastLink: a Process in [] in Semaphore>>critical: excessSignals: 0 PatPatagoniaFileDatabase>>saveRepository Receiver: a PatPatagoniaFileDatabase Arguments and temporary variables: Receiver's instance variables: conference: a PatConference entryPoint: 'register/esug2010' lock: a Semaphore(a Process in [] in Semaphore>>critical: a Process in [] in Se...etc... [] in PatPatagoniaFileDatabase>>takeSnapshot Receiver: a PatPatagoniaFileDatabase Arguments and temporary variables: Receiver's instance variables: conference: a PatConference entryPoint: 'register/esug2010' lock: a Semaphore(a Process in [] in Semaphore>>critical: a Process in [] in Se...etc... [] in BlockClosure>>newProcess Receiver: [closure] in PatPatagoniaFileDatabase>>takeSnapshot Arguments and temporary variables: Receiver's instance variables: outerContext: PatPatagoniaFileDatabase>>takeSnapshot startpc: 45 numArgs: 0 --- The full stack --- UndefinedObject(Object)>>doesNotUnderstand: #binary ReferenceStream(DataStream)>>setStream: ReferenceStream>>setStream: ReferenceStream class(DataStream class)>>on: ReferenceStream class>>on: ReferenceStream class(DataStream class)>>newFileNamed: ReferenceStream class>>newFileNamed:do: [] in PatPatagoniaFileDatabase>>saveRepository [] in Semaphore>>critical: BlockClosure>>ensure: Semaphore>>critical: PatPatagoniaFileDatabase>>saveRepository [] in PatPatagoniaFileDatabase>>takeSnapshot [] in BlockClosure>>newProcess

May 25, 2010

[Pharo-project] Using Pier to produce web sites

by Fernando olivero

Hi, can anybody point me to some useful guidelines/tutorial for developing web pages using Pier, other than the Pier web site itself. I've been unsuccessfully trying it out for the past days, get lost when trying to alter the default environments for creating new types of pages, or components. Fernando

May 25, 2010

Re: [Pharo-project] [Metacello] What packages to load from Metacello in PharoDev?

by Mariano Martinez Peck

On Sat, May 22, 2010 at 1:01 AM, Dale Henrichs <dhenrich(a)vmware.com> wrote: > > > I agree that for the default environment it is a good idea to include the > extra packages, since they provide a level of functionality/documentation > that should be present ... I will mention that the Metacello tests can be > slow to execute, since they do a lot of loading/unloading of packages (using > dictionary-based repositories)... > > Dale. Yesterday I run the tests and the package that is slow is Metacello-TestsMC. It takes at least half an hour. If you ask me, I don't care. I would include them in PharoDev anyway. It is worth. So, what other Pharaoers think? Cheers Mariano > Finally, you can use a valid version of Metacello .... it turns out that if > you specify a version of a project that is _older_ than the currently loaded > one, Metacello will use the current version and apply the load list to the > loaded version instead of the one listed ... if the loaded version is > _older_ than the specified version then the newer version will be loaded ... > > Sooo, all you have to do is specify a reasonable version of Metacello and > if later versions are loaded the correct pacakges will be loaded ... BTW, > the bug that you noticed with Seaside3.0 was related to this mechanism not > quite working correctly:) (oh and I've fixed this bug in 1.0-beta.26.2). > > The only time that a downgrade of mcz files occurs is when you explicitly > load a Configuration whose mcz files are older than the loaded versions. > Only the packages associated directly with the configuration are downgraded > ... the referenced projects follow the "standard rules". > > Dale > > ________________________________________ > From: metacello(a)googlegroups.com [metacello(a)googlegroups.com] On Behalf Of > Mariano Martinez Peck [marianopeck(a)gmail.com] > Sent: Friday, May 21, 2010 2:25 AM > To: metacello(a)googlegroups.com; Pharo Development > Subject: [Metacello] What packages to load from Metacello in PharoDev? > > Hi. For building PharoDev images, we take a PharoCore and just evaluate > something like: > > (ConfigurationOfPharo project version: '1.1-beta1.10517') load > > So....Metacello would be boostraped from > ConfigurationOfPharo>>ensureMetacello which does a (Smalltalk at: > #ConfigurationOfMetacello) perform: #loadLatestVersion > and ConfigurationOfMetacello>>loadLatestVersion does a "self project > latestVersion load" ... > > and, the default of ConfigurationOfMetacello is Core....so, in summary, > only core is loaded. Perfect. > > Now I was thinking that we should load more packages in PharoDev image. > > First, we want the Metacello tests. For all packages we include by default > in PharoDev, we also include its tests (by default). This is cool because > people test it, we can give you quick feedback, be sure all green tests, > etc. They are cool as documentation, blah blah blah. > > So, first question, which tests package should I load? > > Metacello-Tests > Metacello-TestsCore > Metacello-TestsMC > Metacello-TestsPlatform.pharo > Metacello-TestsReference > > Or, maybe even better, load the group 'Test'. I guess this is the correct > one. > > Now, I also think we could include all the following packages: > > - Tutorial: this is cool for newcomers. They want to do the Metacello > tutorial, and having it already in the image is cool I think. I want to > include also the tests for the tutorial > > - HelpSystem for Metacello: we need to copy this package from the > HelpSystem repo (see my other email) > > - Metacello ProfStef > > - Metacello OB: do you know if it is working in Pharo 1.1 and with OB 1.1.4 > ? > > What do you think about including these packages in PharoDev by default ? I > think it is a good idea. > > Regardless that, I am not sure how to load them. As I told you, when > building PharoDev images, Metacello is boostraped from the #ensureMetacello > of ConfigurationOfPharo. And this will load the Core. ANd this is correct > because other people use COnfigurationOfPharo for their own stuff and they > just want the core. But in the case of PharoDev, I want more packages. But > modifying #ensureMetacello is not an alternative. > > So...I can put a reference to ConfigurationOfMetacello in Conf of Pharo, > just like any other dependency, and there I specify the loads: with the > array of things I want. This seems better. But I still have a problem: > #ensureMetacello will load the latestVersion of it. It will load core. So, > which version of ConfigurationOfMetacello should I use in my version of > ConfigurationOfPharo. If I put a specific version, I may hve problems > because it will try to download different versions....So, I would like to > load the same as the #ensureMetacello. But I cannot specify in version > method lastVersion for metacello. > > what can I do ? don't specify the metacello version in the version method > so that it takes the last one ? > > Thanks and sorry for the long email > > Mariano > > >

May 25, 2010

[Pharo-project] [GSoC] Coding started yesterday!

by Mariano Martinez Peck

Hi everybody. First, let me apologize for the multiple cross post. I think it is good to show the Smalltalk community periodically the status of GSoC. The good news in this case is that yesterday the students started to code! This was one of the GSoC deadlines that you can read in http://gsoc2010.esug.org/ and in http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#… . Last two weeks or so, students have been talking and discussing with their mentors, reading and investigating about the projects. Some students already started to code before. But yesterday was the official day to start to code. For those that didn't know, we got not 5 but 6 projects. We asked more and they gave us one more ;) Once again, if you want to look at the 6 selected projects, see http://gsoc2010.esug.org/projects We already told students to ask in case of problems or questions to their mentors but also to the community (trough the mailing list). So, let's help them! Students: don't be shy. Ask! ;) Good luck to all students and enjoy this wonderful opportunity you have. Now we are in the best part of the program! Best regards, Mariano Martinez Peck GSoC admin gsoc-admin(a)esug.org http://gsoc2010.esug.org

May 25, 2010

Re: [Pharo-project] [Metacello] Re: [BetaTesting] [ANN] Pharo-1.1-11367-Beta1dev10.05.1

by Mariano Martinez Peck

On Tue, May 25, 2010 at 9:20 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > - query it via help > > What is this? > I do not see the point of having an ascii outdated version. We do not have > the manpower for doing that. > > I'm already losing my time with svn since some people committed over my > changes.... > > Stef > > > On May 24, 2010, at 11:41 PM, Torsten Bergmann wrote: > > >> We should listen to Torsten but as far as I would expect, only > HelpSystem, > >> but it is already included in both PharoCore and Squeak. > > > > The help system is included in Squeak trunk and Pharo core, so > > one should be able to load the three example books (Squeak, Pharo, > > Metacello) which I uploaded in squeksource/HelpSystem in both > > environments. Still they are just small demo books - no real > > docu since there is not much content yet. > > > > However - we could reuse them to document these systems if > > for instance Dale is willing to contribute stuff to the > > Metacello book or we create an ASCII version of the Metacello > > preview PBE chapter. Would be nice to have a real Metacello help book > > that would be part of the Metacello distro (similar to the ProfStef > > Tutorial on Metacello) ... > > > > Thanks > > T. > > > > > > > > > > > > > > > > > > -- > > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > > > _______________________________________________ > > 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 >

May 25, 2010

Re: [Pharo-project] Latex to HelpSystem converter? [WAS] Re: [Metacello] Re: [BetaTesting] [ANN] Pharo-1.1-11367-Beta1dev10.05.1

by StÃ©phane Ducasse

The only way is the pharo book you can generate latex browse it via google query it. There is a visitor so we can produce what we want from the book structure. Please no copy and paste. Stef On May 25, 2010, at 12:28 AM, Dale Henrichs wrote: > Mariano Martinez Peck wrote: >> On Mon, May 24, 2010 at 11:41 PM, Torsten Bergmann <astares(a)gmx.de<mailto:astares@gmx.de>> wrote: >>> We should listen to Torsten but as far as I would expect, only HelpSystem, >>> but it is already included in both PharoCore and Squeak. >> The help system is included in Squeak trunk and Pharo core, so >> one should be able to load the three example books (Squeak, Pharo, >> Metacello) which I uploaded in squeksource/HelpSystem in both >> environments. Still they are just small demo books - no real >> docu since there is not much content yet. > > I have pulled the Metacello-Help package over to the metacello repository and have added to a baseline for 1.0-beta.27... but it should have more content... > >> However - we could reuse them to document these systems if >> for instance Dale is willing to contribute stuff to the >> Metacello book or we create an ASCII version of the Metacello >> preview PBE chapter. > > Mariano is actually doing all of the heavy lifting on the PBE chapter:) > >> Maybe I am dreaming too much, but it would be cool to export somehow some chapters to HelpSystem. >> Is there a way to export from Latex to ASCII ? even more, how difficult could be to code a plugin (or whatever name is) to automatically generate the nice code for HelpSystem from Latex code? >> Then we can include PBE in the image also ;) > > This would be very cool! > > It seems that there is a place for online (pdf..) documentation, but the online and in-image documentation really needs to stay in synch! > > Dale > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 25, 2010