- Pharo-dev - lists.pharo.org

Re: [Pharo-project] What is the future of GUI in Pharo?

by nullPointer

I donÂ´t understand something. The implementation of new widgets will based on SimpleMorphic, o really will be the base Morph is based in SimpleMorphic? If I could create new widgets and new UI functionalities I must work with SimpleMorphic? Will be change some things for work with openGL or others or really all is based in classic morphic? Regards. -- View this message in context: http://forum.world.st/What-is-the-future-of-GUI-in-Pharo-tp3400855p3403870.… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 24, 2011

Re: [Pharo-project] What is the future of GUI in Pharo?

by nullPointer

I donÂ´t understand something. The implementation of new widgets will based on SimpleMorphic, o really will be the base Morph is based in SimpleMorphic? If I could create new widgets and new UI functionalities I must work with SimpleMorphic? Will be change some things for work with openGL or others or really all is based in classic morphic? Regards. -- View this message in context: http://forum.world.st/What-is-the-future-of-GUI-in-Pharo-tp3400855p3403869.… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 24, 2011

Re: [Pharo-project] [COTDC] 35 - MCPackageCache

by laurent laffont

Thanks Stef. Laurent. On Thu, Mar 24, 2011 at 9:50 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > I'm a kind of cache for versions and filenames of packages. > > Stef > > On Mar 24, 2011, at 7:18 PM, laurent laffont wrote: > > > Anyone or abort ? > > > > Laurent. > > > > On Wed, Mar 23, 2011 at 6:40 PM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > > Today: MCPackageCache > > > > > > Comment Of The Day Contest - One Day One Comment > > Rules: > > #1: Each day a not commented class is elected. Each day the best comment > will be integrated with name of the author(s). > > #2: If you cannot comment it, deprecate it. > > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > > > Laurent > > > > >

March 24, 2011

Re: [Pharo-project] Issue 3861 in pharo: Image freeze when changing system time

by pharo＠googlecode.com

Comment #2 on issue 3861 by lem...(a)gmail.com: Image freeze when changing system time http://code.google.com/p/pharo/issues/detail?id=3861 Ok, i opened a ticket in the cog bugtracker. :-)

March 24, 2011

[Pharo-project] positionalMesssge breaks literal array parsing

by Eliot Miranda

Hi All, the following won't parse because of support for positional messages (whatever they are; I'll come to that later). #(word()) should be equal to { #word. #() } but because of the type == #leftParenthesis clause in the below it causes a syntax error: Scanner methods for multi-character scans xLetter "Form a word or keyword." | type | buffer reset. [(type := self typeTableAt: hereChar) == #xLetter or: [type == #xDigit or: [type == #xUnderscore and:[self allowUnderscoreSelectors]]]] whileTrue: ["open code step for speed" buffer nextPut: hereChar. hereChar := aheadChar. aheadChar := source atEnd ifTrue: [30 asCharacter "doit"] ifFalse: [source next]]. tokenType := (type == #colon or: [type == #xColon and: [aheadChar ~~ $=]]) ifTrue: [buffer nextPut: self step. "Allow any number of embedded colons in literal symbols" [(self typeTableAt: hereChar) == #xColon] whileTrue: [buffer nextPut: self step]. #keyword] ifFalse: [type == #leftParenthesis ifTrue: [buffer nextPut: self step; nextPut: $). #positionalMessage] ifFalse:[#word]]. token := buffer contents e.g. evaluate any of the following: #(word()) Compiler evaluate: '#(word())' Scanner new scanTokens: '#(word())' What is this support for? Is it for those funky ffi calls in the OpenGL code? Can it not be hoisted out of the scanner and into the parser proper? [and optimistically anyone have a fix already?] best, Eliot

March 24, 2011

Re: [Pharo-project] custom code on squeaksource

by StÃ©phane Ducasse

> > > yes now we should probably avoid to have syntax in the class definition but in a description of the slots. > > What means exactly: #identityHash => 20 => #Align => 32. > > This is just an example Yes I see that but I value real examples I cannot imagine :) So we could have a nice BitFieldSlot class with nice message and creation interface (no magic intepretation needed and we would write something like HeapField subclass: #ObjectHeaderLittleEndian instanceVar: 'identityHash <BitFieldSlot length: 20 aligned: 32> ' or something like that and it will be quite cool. > but it means a 20-bit unsigned integer field aligned on a 32-bit boundary. In the above #isPointers => 1 => #Boolean would mean a 1 bit-field accessed as a boolean (a flag). The above is close to the object header in the new GC I want to build. > > > For slots we did a first experience with marcus in 2008/9 where we show that we could get first class instanceVariable > without speed penalties. We postpone our experience because it required a working new compiler and a complete rewrite > of classBuilder. > We want to be able to define > active value > hashTable > relationship > magritte like description > and a lot more > > So if you have ideas or wishes let us know. > > Stef > > >

March 24, 2011

Re: [Pharo-project] Issue 3863 in pharo: packages cleanup needed

by pharo＠googlecode.com

Comment #1 on issue 3863 by stephane...(a)gmail.com: packages cleanup needed http://code.google.com/p/pharo/issues/detail?id=3863 this is strange because I thought that scriptLoader was setting a repo automatically. We should check that.

March 24, 2011

Re: [Pharo-project] Issue 3861 in pharo: Image freeze when changing system time

by pharo＠googlecode.com

Comment #1 on issue 3861 by stephane...(a)gmail.com: Image freeze when changing system time http://code.google.com/p/pharo/issues/detail?id=3861 Tx may be you should open a ticket on the Cog bugtracker.

March 24, 2011

Re: [Pharo-project] custom code on squeaksource

by Igor Stasenko

On 24 March 2011 21:52, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > On Thu, Mar 24, 2011 at 1:45 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> >> > >> > >> > I like it! Â A great use for tuples. Â Not sure I like sots vs >> > instanceVarables, but then I'm an old man ;) >> > Have you thought about automatically creating accessors for byte data? >> > Â I'm imagining >> > >> > HeapField subclass: #ObjectHeaderLittleEndian >> > Â Â type: #Bits >> > Â Â fields: { >> > Â Â Â Â #classTag => 20. >> > Â Â Â Â #isPointers => 1 => #Boolean. >> > Â Â Â Â #isIndexable => 1 => #Boolean. >> > Â Â Â Â #slotSize => 8 => #Align => 8. >> > Â Â Â Â #identityHash => 20 => #Align => 32. >> > Â Â Â Â #isMarked => 1 => #Boolean. >> > Â Â Â Â #isForwarded => 1 => #Boolean. >> > Â Â Â Â #isWeak => 1 => #Boolean. >> > Â Â Â Â #isEphemeron => 1 => #Boolean. } >> > Â Â Â Â classSlots: {} >> > Â Â Â globals: '' >> > Â Â Â category: #'VMMaker-MemoryManager' >> >> yes now we should probably avoid to have syntax in the class definition >> but in a description of the slots. >> >> What means exactly: Â Â #identityHash => 20 => #Align => 32. > > This is just an example but it means a 20-bit unsigned integer field aligned > on a 32-bit boundary. Â In the above Â #isPointers => 1 => #Boolean would mean > a 1 bit-field accessed as a boolean (a flag). Â The above is close to the > object header in the new GC I want to build. kekeke... i like it when people see a direct benefits for themselves :) >> >> For slots we did a first experience with marcus in 2008/9 where we show >> that we could get first class instanceVariable >> without speed penalties. We postpone our experience because it required a >> working new compiler and a complete rewrite >> of classBuilder. >> We want to be able to define >> Â Â Â Â active value >> Â Â Â Â hashTable >> Â Â Â Â relationship >> Â Â Â Â magritte like description >> Â Â Â Â and a lot more >> >> So if you have ideas or wishes let us know. >> >> Stef >> >> > > -- Best regards, Igor Stasenko AKA sig.

March 24, 2011

Re: [Pharo-project] custom code on squeaksource

by Eliot Miranda

On Thu, Mar 24, 2011 at 1:45 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > > > > > I like it! A great use for tuples. Not sure I like sots vs > instanceVarables, but then I'm an old man ;) > > Have you thought about automatically creating accessors for byte data? > I'm imagining > > > > HeapField subclass: #ObjectHeaderLittleEndian > > type: #Bits > > fields: { > > #classTag => 20. > > #isPointers => 1 => #Boolean. > > #isIndexable => 1 => #Boolean. > > #slotSize => 8 => #Align => 8. > > #identityHash => 20 => #Align => 32. > > #isMarked => 1 => #Boolean. > > #isForwarded => 1 => #Boolean. > > #isWeak => 1 => #Boolean. > > #isEphemeron => 1 => #Boolean. } > > classSlots: {} > > globals: '' > > category: #'VMMaker-MemoryManager' > > yes now we should probably avoid to have syntax in the class definition but > in a description of the slots. > > What means exactly: #identityHash => 20 => #Align => 32. > This is just an example but it means a 20-bit unsigned integer field aligned on a 32-bit boundary. In the above #isPointers => 1 => #Boolean would mean a 1 bit-field accessed as a boolean (a flag). The above is close to the object header in the new GC I want to build. > For slots we did a first experience with marcus in 2008/9 where we show > that we could get first class instanceVariable > without speed penalties. We postpone our experience because it required a > working new compiler and a complete rewrite > of classBuilder. > We want to be able to define > active value > hashTable > relationship > magritte like description > and a lot more > > So if you have ideas or wishes let us know. > > Stef > > >

March 24, 2011