- Pharo-dev - lists.pharo.org

[Pharo-project] yarg: Pharo grammar ...

by James Ladd

This is Yet Another Request for the Grammar to Pharo/Squeak Smalltalk? I have seen this: http://wiki.squeak.org/squeak/409 but it is very old and doesn't appear to cater for Pharo/Squeak additions. Can someone point me to a more recent grammar? Rgs, James.

Sept. 8, 2010

Re: [Pharo-project] UbiquiTalk running in Pharo 1.1

by Sean P. DeNigris

Miguel Enrique CobÃ¡ MartÃnez-2 wrote: > > Exactly, that is the reason that I put AFAIK, and the reason I said it > was bloated. The fact that you can download from a Mantis, squeakmap, > GOODs, a magma repo, universes or a ftp repo has little impact if 99% of > the times you are downloading from http repos squeaksource and > gemstone. :) > [thinking out loud] This sounds like a great reason to clean and modularize, but why a whole new thing. -- View this message in context: http://forum.world.st/UbiquiTalk-running-in-Pharo-1-1-tp2400767p2530693.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 8, 2010

Re: [Pharo-project] Compiling the VM for MacOSX

by John M McIntosh

On 2010-09-07, at 3:44 PM, Alexandre Bergel wrote: > Thanks, it works fine now. > > I use an obsolete version? Strange. I downloaded the lastest version of VMMaker. By the way, the produced vm is fairly slow. I do not know whether there is an option somewhere for inline or something... > > Thanks, > Alexandre Ah, you'll need to explain which VM you built? Also when you build you get to pick between DEBUG and Deployment/Release in OS-X and I assure you the DEBUG version is 10x slower than the non-debug one. Now. VMMaker translates a subset of Smalltalk known as Slang to C code. This is the core of the Virtual Machine and processes Smalltalk byte codes it reads from the Squeak Image to perform some obscure task... As Block Closures and Cog JIT work , UTC time, etc, have been added in the last year that has resulted in new versions of VMMaker since we are changing the functionality of the VM. However the VM is decoupled from the issue of the supporting platform, which progresses at a different rate. In order to run the VM on a particular hardware device/software platform the person wanting to port the VM has to follow documentation such as found as http://isqueak.org/PlatformVMAPI to create the platform specific API to enable a user of the device to enter UI input and have the VM produce some form of output (may or may not be visual). The 'Mac OS' folder contains platform code to build a carbon based OS-X system which has it's roots in Apple's OS 7.5.x from 1991. This evolved over the years to support OS-X as an 'OS-X legacy carbon application' and is known as the 3.x series before MacIntel machines, and 4.x after MacIntel with 4.2.5 being the last shipped version. In June of 2008 the ESUG board provided funding to assist in the development of the platform files for the iPhone, further funding granted in October of 2009 enabled us to rebuild a new set of platform files for OS-X and iOS that (a) Bring the macintosh os-x platform support code up to the latest version of API support using Cocoa. (b) Enable the ability of the VM & API to run in 32 bit or 64 bit mode on MacIntel or PowerPC. * (c) Enable the ability to run the VM in 64 bit mode working with a 32 bit image (d) Enable the ability to run the VM in 64 bit mode working with a 64 bit image. (e) Rewrite the Squeak in the Browser api to work with Apple's 64 bit requirements. *Cough* pending... This resulted in the current 5.x series, which support 32bit/64bit VM on os-x against a 32bit or 64bit image, or a 32bit VM with 32bit image on iOS devices. Work from teleplace also offers a 32bit vm in stack or JIT implementation against a 32bit image. *Apple did not supply 64bit versions of the GUI for the PowerPC which makes it impossible to offer a 64bit compiled VM on the PowerPC because one lacks a Graphical User Interface. -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Sept. 8, 2010

Re: [Pharo-project] Compiling the VM for MacOSX

by Alexandre Bergel

Thanks, it works fine now. I use an obsolete version? Strange. I downloaded the lastest version of VMMaker. By the way, the produced vm is fairly slow. I do not know whether there is an option somewhere for inline or something... Thanks, Alexandre On 7 Sep 2010, at 15:05, John M McIntosh wrote: > Ah well actually you are attempting to build an obsolete VM. However we might as well ensure you can do that for historical reasons. > > I'm not sure why the setMicroSecondsandOffset does not resolve into a default setMicroSecondsandOffset in the interp.c > since mine has > /* A default substitute for unimplemented ioUtcWithOffset external function. */ > > sqInt setMicroSecondsandOffset(sqLong * microSeconds, int * utcOffset) { > flag("toRemove"); > return -1; > } > > > However buried in a email message from last March is a slight error which prevented the ioUtcWithOffset() defined in sqMacTime.c > from being used. Therefore I've altered sqMacTime.c & sqPlatformSpecific.h in the Mac OS carbon SVN tree. You should check > out a new copy of that. > > Ok, so building an obsolete VM might be fun and let's see if you can do it, but you should build a 5.x VM from the iOS tree. > > See platform/iOS/vm/SqueakPureObjc.xcodeproj in order to build > SqueakPureObjc The cocoa based 5.x VM for OSX 32bit & 64bit supporting a 32bit image format > SqueakPureObjc64*64 The cocoa based 5.x VM for OSX 64bit supporting a 64bit image format > SqueakNoOGLIPhone The cocoa based 2.x VM for the iOS devices > > Also lurking in there is the > SqueakPureObjcCogVM.xcodeproj > which lets you build: > SqueakNoOGLIPhone The cocoa based Cog Stack Based VM for iOS devices > SqueakPureObjc The cocoa based Cog JIT VM for OSX 32bit. > However that xcodeproj is still a work in progress and Eliot and I are still merging changes. > > > Later open SqueakPureObjc.xcodeproj > compile link you'll find a pre-existing src file that is somewhat current. > Swap in a newer one if needbe. > > > On 2010-09-07, at 10:00 AM, Alexandre Bergel wrote: > >> Undefined symbols: >> "_setMicroSecondsandOffset", referenced from: >> _primitiveUtcWithOffset in interp.o >> ld: symbol(s) not found >> collect2: ld returned 1 exit status >> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> >> Where this _setMicroSecondsandOffset is defined? >> >> No idea whether this is related or not, but I had to leave TestOSAPlugin out when generating the vm code. This plugin cannot be produced apparently, a class is missing. >> >> Cheers, >> Alexandre > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 7, 2010

Re: [Pharo-project] primitive 65 failures

by Eliot Miranda

On Tue, Sep 7, 2010 at 2:13 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>wrote: > Why does primitive 65 (#next) include a test on the position vs. read > length and sometimes fall back on indexing the collection? I have been > creating my own stream for serial ports, and it was driving me nuts. After > staring at the obvious (the primitive was failing sooner than I expected), I > finally looked at Dolphin and saw the same test and fallback. Doing the > analogous things in my code left it working a lot better than it had been. > > What gives? Are we perhaps suffering from a primitive that fails too > easily and is running slow code as a result, or is there a "valid" reason > for the primitive to fail? > Bill, try removing use of the primitive and see if you can see any slowdown in the system. If you don't (as I've also) then perhaps the primitive is a bad idea anyway. 2Â¢ Eliot > > Bill > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 7, 2010

[Pharo-project] primitive 65 failures

by Schwab,Wilhelm K

Why does primitive 65 (#next) include a test on the position vs. read length and sometimes fall back on indexing the collection? I have been creating my own stream for serial ports, and it was driving me nuts. After staring at the obvious (the primitive was failing sooner than I expected), I finally looked at Dolphin and saw the same test and fallback. Doing the analogous things in my code left it working a lot better than it had been. What gives? Are we perhaps suffering from a primitive that fails too easily and is running slow code as a result, or is there a "valid" reason for the primitive to fail? Bill

Sept. 7, 2010

Re: [Pharo-project] glamorous theme :)

by Tudor Girba

It's not bad, but and I do not use this metaphor in the theme. As I said, the goal of the theme is to be really simple and to exercise the minimum amount of graphical variables that would still enable the distinction between the different ui states. The theme is not quite where I would like it to be, but definitely the "pressed button" would introduce another graphical variable that is not really needed from my point of view. Cheers, Doru On 7 Sep 2010, at 22:37, laurent laffont wrote: > On Tue, Sep 7, 2010 at 9:48 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi Laurent, > > On the Macbook Pro monitor it works well, but indeed, I also thought this would be a problem on less strong monitors. > > I now updated the color to get a stronger shade of blue. > > What do you think of this one (with a pressed look) ? > > buttonSelectedFillStyleFor: aButton > "Return the normal button fillStyle for the given button." > > | toptop top bottom base | > base := self glamorousBaseColorFor: aButton. > toptop := base muchDarker. > top := base. > bottom := (self glamorousLightSelectionColorFor: aButton) muchLighter. > > ^(GradientFillStyle ramp: { > 0.0->toptop. > 0.1->top. > 0.9->bottom.}) > origin: aButton bounds origin; > direction: 0 @ aButton height; > radial: false > > > > Laurent Laffont > > http://pharocasts.blogspot.com/ > http://magaloma.blogspot.com/ > > > > Cheers, > Doru > > > On 7 Sep 2010, at 08:47, laurent laffont wrote: > > > Hi Doru, > > > > Using Glamourous I hardly see which button is focused in System Browser between instance or class. So I've made mistakes several times yesterday :) > > > > I really like this theme, especially on a slow computer. > > > > > > Cheers, > > > > Laurent Laffont > > > > http://pharocasts.blogspot.com/ > > http://magaloma.blogspot.com/ > > > > > > On Sat, Sep 4, 2010 at 11:18 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > > Hi, > > > > Over the past week I worked on a new theme for Pharo called the Glamorous Theme :). The theme is developed in the context of the Glamour project, and its goal is to create a look that: > > - does not look like a specific operating system. In particular, the icons should be operating system agnostic, because, for example, people in Windows are confused by the red, yellow, green buttons of apple. > > - uses a limited amount of colors and effects. > > > > It is still work in progress, but you can get the current version by executing: > > > > Gofer new > > squeaksource: 'Glamour'; > > package: 'Glamour-Morphic-Theme'; > > load. > > GLMUITheme defaultSettings: nil. > > GLMUITheme beCurrent. > > GLMUITheme setPreferredWorldBackground. > > > > Cheers, > > Doru > > > > -- > > www.tudorgirba.com > > > > "Problem solving efficiency grows with the abstractness level of problem understanding." > > > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > www.tudorgirba.com > > "It's not what we do that matters most, it's how we do it." > > -- www.tudorgirba.com "Relationships are of two kinds: those we choose and those that happen. They both matter."

Sept. 7, 2010

Re: [Pharo-project] [squeak-dev] Experimental Cocoa OS-X based Squeak Cog JIT VM 5.8b7

by John M McIntosh

Ok, well it's great someone is actually paying attention. In 4.2.4 if (stat(unixPath, &statBuf) && lstat(unixPath, &statBuf)) and pull these values time_t st_mtime; /* [XSI] Last data modification time */ time_t st_ctime; /* [XSI] Time of last status change */ For your examples the lstat() is the one populating the structure. Also described in the man page as the time file was last accessed or modified, of when the inode was last changed, or the birth time of the inode. We then consider localtime(&unixTime)->tm_gmtoff; to create a time in the Squeak epoch. Now for the Cocoa Version we take NSFileCreationDate The key in a file attribute dictionary whose value indicates the file's creation date. NSFileModificationDate The key in a file attribute dictionary whose value indicates the file's last modified date. { NSFileCreationDate = 2010-08-20 13:25:54 -0700; NSFileExtendedAttributes = { "com.apple.quarantine" = <30303030 3b346337 36396138 623b5361 66617269 2e617070 3b7c636f 6d2e6170 706c652e 53616661 7269>; }; NSFileExtensionHidden = 0; NSFileGroupOwnerAccountID = 0; NSFileGroupOwnerAccountName = wheel; NSFileHFSCreatorCode = 1178686292; NSFileHFSTypeCode = 1398039400; NSFileModificationDate = 2010-09-06 18:00:05 -0700; NSFileOwnerAccountID = 501; NSFileOwnerAccountName = johnmci; NSFilePosixPermissions = 420; NSFileReferenceCount = 1; NSFileSize = 4073312; NSFileSystemFileNumber = 81731241; NSFileSystemNumber = 234881026; NSFileType = NSFileTypeRegular; } Now actually another bug is that I'm not re-calculating for DayLightSavings time. I've fixed that for 5.8b10 where the date below shows as 17:00:05 but really it should be 18:00:05 In checking the creation time in Squeak I see it thinks it is "2010-08-20T13:25:54+00:00" which baring the timezone/daylightsavings +00.00? issue seems correctly stated. Let me send you a 5.8b10 VM to test /Users/johnmci/Shared/TextFlow-trunk/trunk.changes On 2010-09-07, at 9:53 AM, Juan Vuletich wrote: > John M McIntosh wrote: >> I've stuck a version (5.8b7) of the cocoa based os-x squeak cog JIT based VM in my experimental folder. Please ensure drawing looks sane, and how it interacts with the mouse and keyboard seems viable. >> http://homepage.mac.com/johnmci/.Public/experimental/Squeak%205.8b7.app.zip >> >> I finished the open/GL tuning and based on benchmarking I simplified the explicit flush required when a Smalltalk Morphic draw cycle fails to do a flush. Lastly I cross check the source code to ensure it compiles >> correctly for the iOS platform. >> -- >> =========================================================================== >> John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 >> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com >> ========================================================================== >> > > Hi John, > > I found something strange with reported file creation and modification time. The values answered by #primLookupEntryIn:index: are (Tested on Squeak 4.1, Mac OS 10.5.8): > > 4.2.4 VM (Stack VM): > 3461318674 3461318674 newFile > 3449660476 3447966888 Squeak 4.2.4beta1U.app > 3460975777 3460916669 Squeak.app > 3460551046 3460551046 Squeak4.1.image > 3449660435 3448977726 SqueakV41.sources > > 5.8b7 (Cog experimental VM) > 3461314066 3461314066 newFile > 3447962280 3447962280 Squeak 4.2.4beta1U.app > 3460912061 3460912061 Squeak.app > 3448973124 3460546438 Squeak4.1.image > 3448973118 3448973118 SqueakV41.sources > > Take for instance SqueakV41.sources: > DateAndTime fromSeconds: 3449660435 2010-04-25T15:00:35-03:00 > DateAndTime fromSeconds: 3448977726 2010-04-17T17:22:06-03:00 "This is the correct one according to Finder, 4.2.4 modification time" > DateAndTime fromSeconds: 3448973118 2010-04-17T16:05:18-03:00 > DateAndTime fromSeconds: 3448973118 2010-04-17T16:05:18-03:00 > > So I'm, getting incorrect time info in the FileList. > > Something else I see is that 4.2.4 VM answers the same value for creation and modification time for some files, while 5.8b7 answers the same value for other files. (Why?) For the newly created "newFile", both answer the same value for creation and modification time. The correct value is (again) the one answered by 4.2.4. > > I'm at the ART time zone. > > Thanks, > Juan Vuletich -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Sept. 7, 2010

Re: [Pharo-project] glamorous theme :)

by laurent laffont

On Tue, Sep 7, 2010 at 9:48 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi Laurent, > > On the Macbook Pro monitor it works well, but indeed, I also thought this > would be a problem on less strong monitors. > > I now updated the color to get a stronger shade of blue. > What do you think of this one (with a pressed look) ? buttonSelectedFillStyleFor: aButton "Return the normal button fillStyle for the given button." | toptop top bottom base | base := self glamorousBaseColorFor: aButton. toptop := base muchDarker. top := base. bottom := (self glamorousLightSelectionColorFor: aButton) muchLighter. ^(GradientFillStyle ramp: { 0.0->toptop. 0.1->top. 0.9->bottom.}) origin: aButton bounds origin; direction: 0 @ aButton height; radial: false Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/ > > Cheers, > Doru > > > On 7 Sep 2010, at 08:47, laurent laffont wrote: > > > Hi Doru, > > > > Using Glamourous I hardly see which button is focused in System Browser > between instance or class. So I've made mistakes several times yesterday :) > > > > I really like this theme, especially on a slow computer. > > > > > > Cheers, > > > > Laurent Laffont > > > > http://pharocasts.blogspot.com/ > > http://magaloma.blogspot.com/ > > > > > > On Sat, Sep 4, 2010 at 11:18 PM, Tudor Girba <tudor.girba(a)gmail.com> > wrote: > > Hi, > > > > Over the past week I worked on a new theme for Pharo called the Glamorous > Theme :). The theme is developed in the context of the Glamour project, and > its goal is to create a look that: > > - does not look like a specific operating system. In particular, the > icons should be operating system agnostic, because, for example, people in > Windows are confused by the red, yellow, green buttons of apple. > > - uses a limited amount of colors and effects. > > > > It is still work in progress, but you can get the current version by > executing: > > > > Gofer new > > squeaksource: 'Glamour'; > > package: 'Glamour-Morphic-Theme'; > > load. > > GLMUITheme defaultSettings: nil. > > GLMUITheme beCurrent. > > GLMUITheme setPreferredWorldBackground. > > > > Cheers, > > Doru > > > > -- > > www.tudorgirba.com > > > > "Problem solving efficiency grows with the abstractness level of problem > understanding." > > > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > www.tudorgirba.com > > "It's not what we do that matters most, it's how we do it." > >

Sept. 7, 2010

[Pharo-project] [Moose-dev] glamorous theme :)

by Stephan Eggermont

Sven wrote: >I would include a small number of well maintained/supported >themes. >Of course, every image needs a default, but choice is good here (it is the whole point). This is something I have to disagree strongly with. Choice in themes does not work for us. We don't have the manpower to maintain them. In user interfaces, consistency is good, and I want one good theme, not ten bad or mediocre. Stephan Eggermont

Sept. 7, 2010