October 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Can this be improved in Glamourous?
by Marcus Denker Oct. 16, 2011

Oct. 16, 2011

On Oct 16, 2011, at 9:36 PM, Tudor Girba wrote: > Hi, > > I load it in a fresh Pharo 1.3 13287 image just like the squeaksource page says: > 13287 is very (very!!!) old.. the last version of the Full image is 13307, the last Core image (which we need to build a full image of, after fixing the Shout MetaCello package) is 13315. Marcus

2 1

[Pharo-project] External arrays (DWORD, DOUBLE, etc.)
by Schwab,Wilhelm K Oct. 16, 2011

Oct. 16, 2011

Hello all, I have some classes that started out as place holders to allow me to load code I wrote for Dolphin, and over time, have become almost useful :) One thing I really needed was a contiguous array of doubles; there is a LOT of code that uses them. Enter ExternalArray with many subclasses, most of which translate #at: and #at:put: into appropriate methods of ByteArray (#doubleAt:put:, etc.). The numbers end up being stored in a byte array, so the indexing looks at position and element size. Access is very slow, but most of the time, I simply allocate a block of memory (e.g. create a byte array, which is fast) and then pass it to an external C/C++ function to do the real work. The passing is the subject of this message. I end up (for FFI) describing the arguments as void*, passing the byte array to the function. Is there a way to tell FFI that an instance of DOUBLEArray can be treated as a double*? Bill

2 1

[Pharo-project] Can this be improved in Glamourous?
by Mariano Martinez Peck Oct. 16, 2011

Oct. 16, 2011

Hi Tudor. Today I wanted to give it a try to 'GT-Inspector' 'GT-Playground' hence I did: (ConfigurationOfGlamoroust project version: #bleedingEdge) load: #('GT-Inspector' 'GT-Playground' ). In a Pharo 1.3 release. To my surprise, it took like half an hour to install, and it even was broken because it installed a different version of refactoring browser that is not working in 1.3. So..can I ask.. are all of those projects really needed just for 2 simples things like a cool inspector and a cool workspace? do you need Nile, Grease, RefactoringBrowser, EyeSee, Magritte ??? can I somehow just load a minimal core for those things I need ? Thanks linear load : linear load : baseline-0.1 [ConfigurationOfGlamoroust] load : ConfigurationOfGlamour atomic load : baseline-0.1 [ConfigurationOfGlamoroust] linear load : default [ConfigurationOfGlamour] load : ConfigurationOfEyeSee linear load : default [ConfigurationOfGlamour] load : ConfigurationOfGrease linear load : default [ConfigurationOfGlamour] load : ConfigurationOfMondrian linear load : default [ConfigurationOfGlamour] load : ConfigurationOfShout atomic load : default [ConfigurationOfGlamour] load : CollectionExtensions load : Glamour-Announcements load : Glamour-Helpers load : Glamour-Core load : Glamour-Presentations load : Glamour-Browsers load : Glamour-Tests-Core load : Glamour-Morphic-Theme load : Glamour-Examples load : Glamour-Tools load : Glamour-Morphic-Widgets load : Glamour-Morphic-Renderer load : Glamour-Tests-Morphic linear load : default [ConfigurationOfMondrian] load : ConfigurationOfProfStef linear load : default [ConfigurationOfMondrian] load : ConfigurationOfHealthReportProducer linear load : default [ConfigurationOfMondrian] load : ConfigurationOfShapeST80 atomic load : default [ConfigurationOfMondrian] atomic load : 0.2-baseline [ConfigurationOfHealthReportProducer] load : HealthReportProducer load : CollectionExtensions load : Nile-Base load : Mondrian-ComplexShape load : Mondrian-Core load : Mondrian-Layouts load : Mondrian-Help load : Mondrian-Easel load : Mondrian-Pharo-Tests load : Mondrian-Shapes load : Mondrian-Events load : Mondrian-Visitor load : Mondrian-Util load : Mondrian-Normalizers load : Mondrian-Example load : Mondrian-ShapeVisitor load : Mondrian-Pharo-Morphic load : Mondrian-Tests load : Mondrian-FADELayout load : Glamour-Mondrian-Presentations load : Glamour-Tests-Mondrian atomic load : default [ConfigurationOfEyeSee] load : EyeSee-Events load : EyeSee-Axis load : EyeSee-Tests-Core load : EyeSee-Support load : EyeSee-Core load : Glamour-EyeSee-Presentations load : Glamour-Tests-EyeSee linear load : 1.0.6.1 [ConfigurationOfGrease] load : ConfigurationOfRefactoringBrowser linear load : 1.0.6.1 [ConfigurationOfGrease] load : Grease-Slime-lr.13 load : Magritte-Model load : Magritte-Pharo-Model load : Magritte-Morph load : Glamour-Magritte-Presentations load : Magritte-Tests-Model load : GT-Playground load : GT-Inspector -- Mariano http://marianopeck.wordpress.com

4 13

Re: [Pharo-project] Can this be improved in Glamourous?
by Marcus Denker Oct. 16, 2011

Oct. 16, 2011

On Oct 16, 2011, at 10:00 PM, Tudor Girba wrote: > Ok. We did it. Now, the whole Moose is unbuildable :) > > The issue is that it tells us that: > > *** Warning: Warning: You are about to load new versions of the following packages that have unsaved changes in the image. If you continue, you will lose these changes. > > Refactoring-Tests-Core > > > We are loading ConfigurationOfRB stable. We really need to make a version of everytthing based on 13315. Marcus -- Marcus Denker -- http://marcusdenker.de

2 1

[Pharo-project] why doing RPackage is a pain
by StÃ©phane Ducasse Oct. 16, 2011

Oct. 16, 2011

RPackage is nice simple fast and robust now the integration within categories crap and packageInfo and PackageOrganizer and MCWorkingCopies.... are a pain. Examples: MCWorkingCopy allManagers size 177 PackageOrganizer default packages size 422 Stef :(

1 2

[Pharo-project] KeyMapping bug: set to default
by laurent laffont Oct. 16, 2011

Oct. 16, 2011

Hi Guillermo, with KeyMapping loaded, open Settings Browser, select a shortcut, right-click, set to default => Message not understood ex. for Move cursor end: KMSettings class(Object)>>doesNotUnderstand: #cursorEnd: Laurent.

1 0

[Pharo-project] [update 1.4] #14198
by StÃ©phane Ducasse Oct. 16, 2011

Oct. 16, 2011

14198 ----- - better unsubscribe for SystemAnnouncer - removing support for pre methodReference list.... so long time ago.

1 0

Oct. 16, 2011

14197 ----- - Issue 4905: Clean SystemAnnouncement private/public. - Issue 4912: Float infinity and Float nan should print themselves. Float are self evaluating finally.

1 0

[Pharo-project] Native Windows
by Sean P. DeNigris Oct. 16, 2011

Oct. 16, 2011

What are the current options/future-possibilities? I was playing with Fffenestri's DisplayHostWindow, which kind of works in 1.3. What ever happened to that project? What is the status of Mars? Are there any other avenues? Thanks. Sean -- View this message in context: http://forum.world.st/Native-Windows-tp3905413p3905413.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

4 5

Oct. 15, 2011

14196 ----- - Issue 4900: CompiledMethod printString. - Fixing FlatListBrowser (not to use third from event but second). - Issue 4912: Float infinity and Float nan should print themselves - Fix users ot tools registry>>browse:selector: to use now Smalltalk tools browser

1 0