- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3564 in pharo: Comparison of source references (for sorting)

by pharo＠googlecode.com

Comment #3 on issue 3564 by marcus.d...(a)gmail.com: Comparison of source references (for sorting) http://code.google.com/p/pharo/issues/detail?id=3564 12317 TODO: 1.3

Jan. 21, 2011

Re: [Pharo-project] Issue 3564 in pharo: Comparison of source references (for sorting)

by pharo＠googlecode.com

Updates: Status: Fixed Comment #2 on issue 3564 by johanbri...(a)me.com: Comparison of source references (for sorting) http://code.google.com/p/pharo/issues/detail?id=3564 Fixed in SLICE-Issue-3564-Not-all-SourceReference-subclasses-implement--JohanBrichau.3 (probably best to integrate in 1.2 because the bug breaks the source searching tools...)

Jan. 21, 2011

Re: [Pharo-project] Issue 3179 in pharo: Failing Tests for Monticello

by pharo＠googlecode.com

Comment #4 on issue 3179 by cy.delau...(a)gmail.com: Failing Tests for Monticello http://code.google.com/p/pharo/issues/detail?id=3179 I join a changeSet that make all monticello test green. For that, I made the fix provided by stephane in issue 2294 (see above), and fix the remaining test: MCChangeNotificationTest >> testExtMethodModified. That's the method I modified to solve the problem: mockClassExtension "I change the protocol of this method (to be '*monticellomocks' instead of 'mocks') to resolve the failing test: MCChangeNotificationTest >> testExtMethodModified. This test basically test that when we modified an extension method, the extended package is marked as 'modified'. The problem is that Monticello treat differently a classic method from an extension method, and this only by checking if the protocol name start with a star. Therefore, if the protocol does not match the extending package name, the extending package name will never be notified, and the test will fail. " Attachments: issue3179.1.cs 3.1 KB

Jan. 21, 2011

Re: [Pharo-project] Pharo on the iPhone

by Alexandre Bergel

Thanks John for these pointers Alexandre On 21 Jan 2011, at 03:05, John M McIntosh wrote: > (a) sign up for Apple's SDK, to install apps on the iPhone you have to pay $99 per year. > > (b) visit squeakvm.org download the source tree > > (c) look for the SqueakPureObjc.xcodeproj > compile/link/debug/run the iPhone app > > (d) Optionally look for the SqueakPureObjcCogVM.xcodeproj after download the COG tree. > Don't cut yourself on the rough edges, but I think Esteban has a workable version now? > > The difference between the two is that the SqueakPureObjcCogVM builds a stack VM, where as the SqueakPureObjc builds the traditional VM but is about 30% slower. > > The image has to include the objective-c bridge and iphone stuff, there is a sample image (broken) in the source tree. > > On 2011-01-20, at 5:10 PM, Alexandre Bergel wrote: > >> Hi! >> >> iPhone 4 is amazing. It will be even better with Pharo inside. Is there a way to install it? >> >> Cheers, >> Alexandre >> >> NB: my device is non jailbreaked. >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 21, 2011

Re: [Pharo-project] Using AlienOpenGL

by Alexandre Bergel

Thanks Fernando for offering your help. We are still at the phase to decide what techno to use. Lumiere has indeed many good things (even though I do not agree with every design decision made in it :-) Cheers, Alexandre On 21 Jan 2011, at 04:21, Fernando Olivero wrote: > Lumeire fulfills the specified goals: creating a world (scene) + > cameras + light sources + 3d objects. > > Lumiere currently uses AlienOpenGL to comunicate with OpenGl, it could > easily use OpenGL FFI as well as the underlying glue code to the > rendering library. > > So resuming: > > 1) Lumiere abstractions over matrixes and OGL. > > 2) Rendering engined wrapper: AlienOpenGL (unmaintaned currently), > OpenGL FFI , NativeBoost OpenGL (only windows for now, until someone > compiles native boost vm for other OS). > > If someone needs the good abstractions of Lumiere, i could give some > pointers on were to remove the AlienOpenGL dependency and "plug" the > preferred engine. > > Fernando > > On Fri, Jan 21, 2011 at 1:43 AM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: >> I feel that we will take the easiest way: implement a small 3d engine. This is about 100 lines of code for something simple (what we need in fact). >> Ricardo and Patricio spent several days having something that run with AlienOpenGL, and the technical problems are numerous (Cog vs Standard, Linux, ...) >> >> We will let you know. >> >> Cheers, >> Alexandre >> >>> If I knew what worked, I'd be making a recommendation :) As it is, I can perhaps help you work through the debugging process. As I said, you could indeed be missing a needed library, there could be dependencies missing that make a .so unable to load, a .so could be just plain broken (I've seen that once or twice), or the vm could be looking in the wrong place and saying absolutely nothing about it. If you can post more about what is going wrong and how, we might be able to sort it out, hopefully w/o having to hack the vm (but no promises). >>> >>> My 3D goals would generally be to create a view/world, add a light source or two and a camera, and to load a few meshes onto some type of retained mode objects and start prodding them in simple ways. Croquet's code for that looked like it was perfect for what I have in mind, but the 3D needs to go in the software, not the other way around. Scouting reports would be most welcome. >>> >>> Bill >>> >>> >>> ________________________________________ >>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Alexandre Bergel [alexandre(a)bergel.eu] >>> Sent: Thursday, January 20, 2011 7:22 PM >>> To: Pharo-project(a)lists.gforge.inria.fr >>> Subject: Re: [Pharo-project] Using AlienOpenGL >>> >>>> Not that you are wrong, but how did you choose AlienOpenGL over CroquetGL? >>> >>> We're just looking for something that works. >>> Is there currently a solution to make 3d with Pharo 1.2 and that works with windows, linux and mac? >>> The idea is to have a 3d version of Mondrian. No need of fancy 3d effect so far. >>> >>> Cheers, >>> Alexandre >>> >>> >>> >>> >>> >>> >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 21, 2011

[Pharo-project] Issue 3565 in pharo: Undeclared ref in 1.1.1

by pharo＠googlecode.com

Status: Fixed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.1.1 New issue 3565 by marcus.d...(a)gmail.com: Undeclared ref in 1.1.1 http://code.google.com/p/pharo/issues/detail?id=3565 Fix attached... Attachments: UndeclaredFix.1.cs 5.2 KB

Jan. 21, 2011

Re: [Pharo-project] Issue 3465 in pharo: Hundson OneClick: Does not show Mac menues

by pharo＠googlecode.com

Updates: Cc: eliot.miranda marianopeck Comment #2 on issue 3465 by Torsten....(a)astares.de: Hundson OneClick: Does not show Mac menues http://code.google.com/p/pharo/issues/detail?id=3465 Setting Eliot on CC for this issue. Maybe the mac menu support code is only in the standard VM and not yet integrated into Cog VM. Mariano: You should note the exact image (download location) here so Eliot can reproduce it.

Jan. 21, 2011

Re: [Pharo-project] Issue 3542 in pharo: Add SmalltalkImage>>#gcBiasToGrow: and friends to core

by pharo＠googlecode.com

Comment #18 on issue 3542 by Torsten....(a)astares.de: Add SmalltalkImage>>#gcBiasToGrow: and friends to core http://code.google.com/p/pharo/issues/detail?id=3542 Mariano: ImageForDevelopers is used in the build for the upcoming Pharo 1.2, isnt it? Phillipe: is #loadLatestVersion of Seaside 3.0 working/compatible with the upcoming Pharo 1.2 already?

Jan. 21, 2011

Re: [Pharo-project] Instruments for headless images

by Igor Stasenko

On 21 January 2011 11:28, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > > On 21 Jan 2011, at 11:19, Igor Stasenko wrote: > >>> What is interesting (and we might make that an option) is that the 'no display' error results in the image being saved 'headfull' so that you can start it up using a display to debug it (suspended process/debugger). >> >> That could be done.. but not as userful as simply report an error. >> Usually we (developers) knowing what we want to do, >> and what i don't want to see in my headless image is any attempts to >> access display/ui. > > Yeah, that's why I said it would better be an option. The first thing to do is simply report the error (and quit, or maybe that should be an option too). But many people playing with headless images (myself included) have had blocking/locked up images: having a log would be great, but adding this option to debug the cause further would be great. > this is next step.. I think this could be set by preference system on error: - print error to log and quit - print error to log and do save & quit - print error to log and do save new version & quit In future , by adding support from VM side we could also have: - switch to interactive(headfull) mode, by creating an OS window opening debugger , showing dialog(s) etc etc > Sven > -- Best regards, Igor Stasenko AKA sig.

Jan. 21, 2011

Re: [Pharo-project] Issue 3520 in pharo: Workspaces do not recognize previously evaluated temps

by pharo＠googlecode.com

Updates: Status: Closed Comment #9 on issue 3520 by marcus.d...(a)gmail.com: Workspaces do not recognize previously evaluated temps http://code.google.com/p/pharo/issues/detail?id=3520 13007

Jan. 21, 2011