March 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [TODO 1.4] 12 issues left

by Stefan Marr

On 26 Mar 2012, at 10:43, Marcus Denker wrote: > Just 12 issues left that are tagged 1.4: > > http://code.google.com/p/pharo/issues/list?&q=milestone%3D1.4 > > -> are any of these not show stoppers? > -> are there any other tracker entries that are show stoppers for a release? 5147 isn't a show stopper. (but it looks to me as if it is a trivial fix, which is attached) http://code.google.com/p/pharo/issues/detail?id=5147 -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

March 26, 2012

[Pharo-project] VM on iOS: still no luck, even with 4.2 and Cmake 2.8.3

by philippe.back＠highoctane.be

Hello, Out of options for 4.3, I downloaded Xcode 4.2 and installed it back alongside 4.3. Then cleaned about everything, regenerated sources (including the IOSPlugin issue). xcode select to go back to 4.2 Then did a cmake -G Xcode . in build/ An Xcode project materialized there. Opening it works,.. well, opens as an empty project in Xcode. There are lots of stuff in the package tough. Viewable and all. But nothing to build... :-( Argh. /Philippe

March 26, 2012

[Pharo-project] Pharo 1.3 - Build # 25 - Still Unstable!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

March 26, 2012

Re: [Pharo-project] [TODO 1.4] 12 issues left

by StÃ©phane Ducasse

I have the same analysis than you. Stef > There are still 6 pending :). I'll try to manage and fix some this afternoon. What I see from my point of view: > > Show stoppers: > > http://code.google.com/p/pharo/issues/detail?id=5445 > > > Non-Show stoppers(but important maybe, or easy): > > http://code.google.com/p/pharo/issues/detail?id=5534 Is it the rename of the #onDisk/... methods? Can someone add more detail to the bug? I can supply a fix this afternoon if I know what to do :). > > http://code.google.com/p/pharo/issues/detail?id=5250 Fix some settings around sound > > http://code.google.com/p/pharo/issues/detail?id=5057 We've lived with this a lot of time... > > http://code.google.com/p/pharo/issues/detail?id=5155 I think it's an oldie too > > http://code.google.com/p/pharo/issues/detail?id=5147 some assertion, seems easy to fix. > > > Other: > > http://code.google.com/p/pharo/issues/detail?id=5531 is not Core stuff. > > > On Mon, Mar 26, 2012 at 5:43 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Just 12 issues left that are tagged 1.4: > > http://code.google.com/p/pharo/issues/list?&q=milestone%3D1.4 > > -> are any of these not show stoppers? > -> are there any other tracker entries that are show stoppers for a release? > > > > -- > Marcus Denker -- http://marcusdenker.de > > >

March 26, 2012

[Pharo-project] 3D from the past

by Schwab,Wilhelm K

Hello all, The attached is something that I cobbled together using Squeak Alice (in Squeak 3.6). Faced with this problem now, I would make 2D drawings in QCad, but at the time, I didn't have that option. So I built some code that made it easy to put actors on "shelves" and then stack same, add some vertical posts, and boom. It allowed me to see that the items in question (medical monitors, a computer, other junk) would actually fit on a cart I was planning to buy - visibility was high, so I didn't want any goof ups. There are buttons to move/look up/down, zoom in/out, and to spin the object. It was a nice way to visualize the pile of junk in question. This is a simple example of things that I would like to be able to do with 3D: create some objects, put meshes on them, and render in a window. Whether the objects are controlled by buttons or are flying around shooting each other would depend on the project and my mood. Bill

March 26, 2012

Re: [Pharo-project] Building the iOS VM

by philippe.back＠highoctane.be

Hello, I have spent a fair chunk of my day grinding my teeth at getting this working in Xcode 4.3 Not there yet. I am better at Cmake, Xcode 4.3, iOS5.1 SDK and GenerateSources for sure... The Xcode project gets generated but Xcode doesn't agrees with me opening it. Key findings: * all pathes are different with Xcode 4.3 - there is a patch for Cmake to deal with this, I applied it into my macports install. * several frameworks are not findable as expressed in the cmake config (CoreGraphics, UIKit, ..) * there was a bug in the image, where sqTouch.m is involved. The correct thing is IOSPlugin and not touchplugin as mentioned * a lot of pathes are hardcoded in the image and it for sure doesn't help with the relocation of stuff by Apple It would be great to be able to discuss this in an IM session one of these days. The answer is not far. Attached the cmake stuff from the main dir (there are things in all plugins but they all come from generate sources initially). Kind Regards, Philippe

March 26, 2012

Re: [Pharo-project] Building the iOS VM - Help

by philippe.back＠highoctane.be

Hello, I have spent a fair chunk of my day grinding my teeth at getting this working in Xcode 4.3 Not there yet. I am better at Cmake, Xcode 4.3, iOS5.1 SDK and GenerateSources for sure... The Xcode project gets generated but Xcode doesn't agrees with me opening it. Key findings: * all pathes are different with Xcode 4.3 - there is a patch for Cmake to deal with this, I applied it into my macports install. * several frameworks are not findable as expressed in the cmake config (CoreGraphics, UIKit, ..) * there was a bug in the image, where sqTouch.m is involved. The correct thing is IOSPlugin and not touchplugin as mentioned * a lot of pathes are hardcoded in the image and it for sure doesn't help with the relocation of stuff by Apple It would be great to be able to discuss this in an IM session one of these days. The answer is not far. Attached the cmake stuff from the main dir (there are things in all plugins but they all come from generate sources initially). Kind Regards, Philippe 2012/3/26 philippe.back(a)highoctane.be <philippe.back(a)gmail.com> > Hello > > I have been working at this today. > > cmake 2.8.3 gives me a weird message (always the same kind, so it looks > like fixable...) > > I managed to get the sources generated (but a Pharo 1. 4 image failed, I > used the script provided in image and this fetched me an image from Lille > that worked - or so it seems). > > Here is the cmake issue: > > PhilMac:build philippeback$ cmake -G Xcode . > > Adding internal plugin: ADPCMCodecPlugin > Adding internal plugin: BMPReadWriterPlugin > Adding internal plugin: B2DPlugin > Adding internal plugin: BitBltPlugin > Adding internal plugin: DSAPrims > Adding internal plugin: ZipPlugin > Adding internal plugin: FFTPlugin > Adding internal plugin: FilePlugin > Adding internal plugin: FloatArrayPlugin > Adding internal plugin: HostWindowPlugin > Adding internal plugin: JPEGReadWriter2Plugin > Adding internal plugin: JPEGReaderPlugin > Adding internal plugin: LargeIntegers > Adding internal plugin: Matrix2x3Plugin > Adding internal plugin: MiscPrimitivePlugin > Adding internal plugin: SecurityPlugin > Adding internal plugin: SoundCodecPrims > Adding internal plugin: SoundPlugin > Adding internal plugin: SurfacePlugin > Adding internal plugin: UUIDPlugin > Adding internal plugin: ObjectiveCPlugin > Adding internal plugin: IOSPlugin > CMake Error: The following variables are used in this project, but they > are set to NOTFOUND. > Please set them or make sure they are set and tested correctly in the > CMake files: > CoreGraphics_FMWK > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > OpenGLES_FMWK > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > UIKit_FMWK > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > linked by target "iStackVM" in directory > /Users/philippeback/iosvm/cog-osx/build > > -- Configuring incomplete, errors occurred! > > 2012/3/24 Esteban Lorenzano <estebanlm(a)gmail.com> > >> Hi, >> >> this are, more or less, the instructions to build an iOS vm: >> >> you need: >> >> - cmake 2.8.3 (not working with latest 2.8.7 because chainsets changed) >> - xcode 4.1 or 4.2 (not working on 4.3 because cmake is not prepared to >> build correct project for latest xcode version) >> >> 1) clone cog-osx (mine) or blessed from git [1] >> 2) in ./image download a 1.4 and install ConfigurationOfCog (latest) >> 3) execute: >> >> StackIPhoneConfig new >> generateSources; generate >> >> 4) in ./build execute >> >> cmake -G Xcode . >> >> 5) open iStackVM.xcodeproj >> 6) add your own provisioning data >> 7) run :) >> >> cheers, >> Esteban >> >> [1] https://gitorious.org/~estebanlm/cogvm/cog-osx >> >> El 24/03/2012, a las 3:25p.m., phil(a)highoctane.be escribiÃ³: >> >> I am trying to build the VM for iOS. >> Got the sources from the ci jenkins server (the ones that built last >> month, as the current one is red). >> >> /platforms has something looking like it. (iOS) >> >> But Cog is x86 and iOS is ARM7. >> >> So, I guess that I have to build a StackVM for it to work. >> >> But there is nothing about iOS in the instructions (Part1, Part2, ...) >> >> The MacOSX VM is documented but not the iOS version. >> >> As maintenance was taken over from John, how do we build from here? (I >> also tried from a copy out of squeak-svn to no avail). >> >> My setup: OSX Lion, latest XCode upgraded from Snow Leopard, so I do have >> GCC on it as well (as LLVM doesn't work). >> >> Target devices: iPad 2 3G, iPad 2 Wifi, iPhone 3GS (All with iOS 5.1). >> >> My wife is a math teacher and my point with all this is to have a working >> VM running Dr Geo II. >> >> I am currently having fun with Arduino and would like to bridge it with >> the iPad through the web (using an Ethernet Shield on the Arduino) - the >> whole chain running Pharo inside self build VMs. >> >> The ultimate point is to run a summer camp with kids if I can put >> everything together by then. >> >> Thanks in advance, >> Philippe >> >> -- >> Philippe Back >> "Helping you hit the top 3 outcomes you really want to achieve" >> >> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: >> phil(a)highoctane.be | Web: http://philippeback.eu | Blog: >> http://philippeback.be >> >> High Octane SPRL >> rue cour Boisacq 101 >> 1301 Bierges >> >> >> >

March 26, 2012

[Pharo-project] XMLParser tiny bug

by Bernat Romagosa

Hi! I've found a little bug in XMLParser and fixed it, but I haven't found any issue tracker for the project, so I don't know where should I submit it. The bug occurs when the parsed page has the xml:lang property set to empty, in which case (anAttributeDictionary at: 'xml:lang') fails. So here's what I did: SAXHandler >> handleStartTag: anElementName attributes: anAttributeDictionary namespaces: aNamespaceDictionary | prefix localName namespaceUri | self elementNester startedElement: anElementName. (anAttributeDictionary includesKey: 'xml:lang') ifTrue: [ self languageEnvironment: ((anAttributeDictionary at: 'xml:lang') ifEmpty: [ Latin1Environment defaultEncodingName ]) ]. " â here " anElementName splitQualifiedNameInto: [ :prefixPart :localPart | prefix := prefixPart. localName := localPart. namespaceUri := '' ]. self usesNamespaces ifTrue: [ self scopeAllocator enterScope. self declareNamespaces: aNamespaceDictionary. namespaceUri := self scopeAllocator resolvePrefix: prefix. self validateStartTag: anElementName prefix: prefix attributes: anAttributeDictionary ]. self saxHandler startElement: anElementName prefix: prefix uri: namespaceUri localName: localName attributes: anAttributeDictionary Cheers! -- View this message in context: http://forum.world.st/XMLParser-tiny-bug-tp4506051p4506051.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 26, 2012

Re: [Pharo-project] CogVM speed

by Milan Mimica

Just wanted to point you that 64-bit code is notably faster than 32-bit code on 64-bit CPUs. You could put it another way: in order for a Smalltalk program to be equivalent to a C/C++ program, you would have to strip out all those things you mention there. But you can't. Now, whose limitation is that? On 26 March 2012 09:07, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > I did it on 64bit. However among other things, there is a big issue > with equivalence of the programs. Because the same program in C/C++ > would have to be able to be interrupted any time by an user, contain > debug information to be able to show the computation state in context > of the source codes and modify temporary and instance variables, > enumerate instances of any arbitrary class, serialize current > computation state and continue even on the different platform etc. > That all costs something and in this light the results of Smalltalk > look quite impressive ;-) > > -- Pavel > > On Mon, Mar 26, 2012 at 8:20 AM, Milan Mimica <milan.mimica(a)gmail.com> > wrote: > > Have you compared with 32-bit binaries generated by gcc? > > > > > > On 25 March 2012 23:43, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > >> > >> Hi, > >> > >> I tried a few benchmarks from Computer Language Benchmark Game > >> > >> ( > http://shootout.alioth.debian.org/u32/which-programming-languages-are-faste… > ) > >> on CogVM to compare it with VisualWorks and with the rest of the > >> world. > >> > >> Of course this benchmarks are not ideal (like all benchmarks) but the > >> result is that CogVM is in average 1.8 times slower than VisualWorks > >> 7.8 NC. For the most successful benchmark (binary-trees) it was 13.5 > >> times slower than C (gcc) but in general we may except CogVM to be > >> 20-30 times slower than C for this kind of tasks. > >> > >> Thank you for the great work! > >> > >> Cheers, > >> -- Pavel > >> > > > > > > > > -- > > Milan Mimica > > http://sparklet.sf.net > > -- Milan Mimica http://sparklet.sf.net

March 26, 2012

[Pharo-project] Pharo 1.4 Tests-Unix - Build # 310 - Unstable!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

March 26, 2012