- Pharo-dev - lists.pharo.org

[Pharo-project] Issue 3738 in pharo: Morphic Animations enhancement
by pharo＠googlecode.com Feb. 21, 2011

Feb. 21, 2011

Status: New Owner: ---- New issue 3738 by fernando...(a)gmail.com: Morphic Animations enhancement http://code.google.com/p/pharo/issues/detail?id=3738 I've implemented a Morphic-Animations runner. The idea is to reify animations as strategy objects, that can be accessed and run from any Morph, centralized in an MorphicAnimationsRunner class, ( to avoid pupulating Morph with extra methods, similar to Seaside "brush" idea). You can try it out via the examples, MorphicAnimationExamples class. Integration with the SystemWindow is provided also, if you enable the animate windows setting you can give it a try. I think this could be integated into Morphic, as Morphic-Animations category. For 1.3

1 2

[Pharo-project] about GLMOrangeUITheme [WAS] Re: [update 1.2] #12302
by Mariano Martinez Peck Feb. 21, 2011

Feb. 21, 2011

On Thu, Jan 13, 2011 at 9:15 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > 12302 > ----- > > - GLMOrangeUITheme. Thanks Igor Stasenko > I don't agree with this kind of changes. Tomorrow I want Watery2BlackTheme and GLMYellowUITHeme and what? we are going to integrate it also? I don't understand. The change should be to create a setting to set the color and then igor runs a script in his own image that set it to orange. Me to yellow. And you to pink. > > - Issue 3538: Add a "Browse test" in the TestRunner failed/error list. > Thanks Benjamin van Ryseghem > > Stef >

8 8

[Pharo-project] Alien + MacVM + plugin/primitive error
by Luc Fabresse Feb. 21, 2011

Feb. 21, 2011

Hi Guys, Jannik pointed an interesting problem. If I load Alien in both 1.1 or 1.2. Gofer it squeaksource: 'MetacelloRepository' ; package: 'ConfigurationOfAlien'; load. ((Smalltalk globals at: #ConfigurationOfAlien) project version: 'Pharo 1.1') load: {'All'. 'MacOSX'} - with the MacVM 4.2.5beta1U => 40 tests green (it works) - with the MacVM 5.7.4 => 20 tests green and 20 errors (can't call a simple external function) it seems that the I32ABI plugin is not loaded correctly. AlienLibrary>>primLoadLibrary: 'IA32ABI' failed. Any clue to make it work in the MacVM 5.7.4? #Luc

4 13

[Pharo-project] [ANN] ConfigurationOfOSProcess with symbolic versions
by Miguel CobÃ¡ Feb. 21, 2011

Feb. 21, 2011

Hi all, I have updated the Metacello configuration for OSProcess. Changes ------- - Uses symbolic versions - Adds support for release 4.4.0 of OSProcess - Applies MetacelloToolBox validations to the old versions of the configuration and corrects them Install -------- In a PharoCore image evaluate in a workspace: Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfOSProcess'; load. ((Smalltalk globals at: #ConfigurationOfOSProcess) project version: #stable) load. This will install the stable version for the platform you are installing to. This is using symbolic versions and permits to rely on the maintainers to specify the stable version (4.3.11, 4.3.12, 4.4.0) for a given platform version (PharoCore 1.1.1, PharoCore 1.2). Other versions and groups --------------------------- To load older versions: ((Smalltalk globals at: #ConfigurationOfOSProcess) project version: '4.3.11') load. To load other groups: ((Smalltalk globals at: #ConfigurationOfOSProcess) project version: #stable) load: 'Tests'. or ((Smalltalk globals at: #ConfigurationOfOSProcess) project version: '4.3.11') load: 'Tests'. Platforms ---------- This was tested on - PharoCore 1.1.1 190 run, 190 passes, 0 expected failures, 0 failures, 0 errors, 0 unexpected passes - PharoCore 1.2 (build #199 from Hudson) 190 run, 190 passes, 0 expected failures, 0 failures, 0 errors, 0 unexpected passes P.S. I'm cross-posting to pharo and metacello lists but I don't know what is the correct way to announce a new configuration. Advise? Enjoy! -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

3 5

[Pharo-project] [ANN] Moose 4.3
by Tudor Girba Feb. 20, 2011

Feb. 20, 2011

We are happy to announce the Moose Suite version 4.3: *http://moosetechnology.org/download* What is new: - New look and feel - New and flexible API to browse FAMIX models - Extensible Moose Finder - Enhanced Glamour engine to deal with complex actions - Enhanced FAMIX support for Java systems - Enhanced Glamour rendering for Morphic - Enhanced meta browser - Enhanced documentation of Mondrian - Enhanced XMLSupport - Enhanced Smalltalk importer A list of issues addressed in this release can be found at: *http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%20milestone=4.3* Have fun, The Moose Team

1 0

[Pharo-project] [COTDC] 14 - MCSnapshotReader
by laurent laffont Feb. 20, 2011

Feb. 20, 2011

Today: MCSnapshotReader 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

2 2

[Pharo-project] Is there a http server that understands PUT?
by Norbert Hartl Feb. 20, 2011

Feb. 20, 2011

While trying to consume some PUT urls with Seaside-REST I noticed that the transmitted content is missing. I tried Comanche as well as swazoo. At this moment I'm not sure if I did something wrong but I seems that only GET and POST are treated. Does anyone has some experience on this? thanks, Norbert

6 8

Feb. 20, 2011

Does anybody have an idea what is the purpose of this function in the vm? Stef sqInt setCompilerInitialized(sqInt newFlag) { register struct foo * foo = &fum; sqInt oldFlag; oldFlag = foo->compilerInitialized; foo->compilerInitialized = newFlag; return oldFlag; }

4 4

Feb. 20, 2011

HI guys I was rambling.... so I looked at other frameworks (RIO, FileMan) and I prefer FS. So I will start to write again comments, continue to reorganize the current structure. I was in contact with colin that told me that he found the improved version that he was doing after ESUG. I asked him to publish it into filesystem I will integrate the fixes of damien. I would like to have - a better help (already there). - Rename workingDirectory as workingDirectoryPath - add workingDirectory returning a FSReference - Every method with an adequate comment. The idea is that the comment should describe what the method does when we do not see its body: let us try to think a bit in JavaDoc or Ruby Yard fashion for once. - Use rename primitives - Have the possibility to create empty file - Clean identification of implementation tests and black box tests - Integrate Gemstone fixes - Stream usage clearly identified to support Gemstone migration) - Onion like structure so that we can have one or two packages that are really the core (yes I still want a minimal kernel). - Check the file API creation: old, new, exist.... - Prepare a migration path for 1.3 - Fix filesystem workingDirectory isWorkingDirectory returns false. - rename fileDoesNotExist: and friends do convey that its goal is mainly to raise en exception raiseFileDoesNotExistsFor: Of course I would like to avoid to throw away all that good energy so I hope to collaborate with colin. We will see what will happen. I can understand that he has another agenda/time frame but we should move on this front. So all my code will be publicly available in the SqueakSource/fs repository. If you think that this is the wrong path, let me know. I will report my changes regularly. Stef

4 8

Feb. 20, 2011

Begin forwarded message: > From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Date: February 20, 2011 8:54:54 AM GMT+01:00 > To: Colin Putney <colin(a)wiresong.com> > Subject: Re: Need your point of view on FSPath * and others > > Thanks I will take into that and write better comments. > > I was looking at makeRelative: they look to me as 'private methods' used for double dispatch while > relativeTo: is the public one. I imagine that I'm correct. > >> With that in mind, I added the #/ and #* methods to make the >> filesystem API easier to use. I think binary selectors are >> under-exploited in Smalltalk, and we'd gain a lot in terms of succinct >> and readable code by making better use of them. >> >>> 2- Then I was wondering if it would not be good to have validating creation methods >>> >>> (FSPath * 'parent/child/') isRelative >>> true >>> (FSPath * '/parent/child/') isAbsolute >>> false >>> because the string is not checked >>> FSPath * '/parejhkjhhg %% ^%$%^(%$546547675 nt??child/' >> >> That's not how paths are meant to be used - the string arguments >> should be file- or directory names, not path fragments. #* creates a >> relative path (it's meant to be similar mnemonically to >> ./parent/child, while #/ creates an absolute path. > > > indeed this is cool. > I was trying to find what you tried to express because I was sure that there was something like that > But I was already reading it as star and not dot :) > With dot and slash it makes a lot more sense. > > >> >> (FSPath * 'parent' / 'child') isRelative "true" >> (FSPath / 'parent' / 'child') isAbsolute "true" >> >> >>> I saw that there is >>> readFrom: aStream delimiter: aCharacter >>> >>> so I created an unchecking instance creation category and I added with: and * in it. >> >> It's not a matter of checked and unchecked so much as parsed and >> unparsed. #/ and #* provide a mini-DSL for building up paths, while >> #readFrom:delimiter: parses path strings. >> >>> 3- Then finally the following confuses me >>> >>> (FSPath with: 'parent/child/') isRelative true >> >> That creates to a relative path to a file/directory called >> 'parent/child'. In bash you'd escape the slashes like this: >> >> parent\/child\/ >> >>> (FSPath with: '/parent/child/') isRelative true >> >> That's a relative path to '/parent/child'. In bash: /\parent\/child\/ > > I was not aware of relative path starting with / > Ugly bash. > >> >>> (FSPath with: '') isRelative false >> >> That's an absolute path to the root of the file system. Absolute paths >> have an empty first element. If you consider $/ the a separator, >> '/usr/local/bin' has an empty first element, right? >> >>> Either with: create relative path or isRelative is not consistent. >>> If with: creates relative path then the last one should be true >>> or isRelative should return false on the second one. ? >> >> Ok, it's a bit of an unusual case, but I think it's important to be >> able to represent paths like \/parent\/child. Their perfectly valid as >> far as the filesystem is concerned, and we want to be able to work >> with such oddly-named files. >> >>> 4 - about FSPath root >>> we have >>> >>> root >>> "Return the relative root path" >>> ^ self with: '' >>> >>> FSPath root >>> returns / >>> and I like that >>> >>> Now what about defining root as >>> >>> root >>> ^ self with: '/' >>> >>> It would be more consistent. Now it breaks everything. So I did not do it :) >> >> I suppose that, strictly speaking, the most consistent way to >> represent the root directory is >> >> root >> ^ self withAll: #('' '') >> >> It still ends up being a bit of a special case, though. >> >> Colin >

1 0