- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Roassal 3D empty windows

by Nicolai Hess

Thank you Alexandre, this was what I tried under windows, (I wasn't sure if this is still the right way to do it, I read it the Roassal3dTutorial.pdf). But it doesn't work. Either I am getting empty windows or (with an other NBOpenGL version) Frame buffer is incomplete: GL_FRAMEBUFFER_UNSUPPORTED') I tried this once with linux too, and it didn't worked. But I am not sure how long ago :) I'll try it again and report back. (Another note, after downloading the configuration, this: (Smalltalk at: #ConfigurationOfRoassal3d) loadDevelopment takes awfully long on windows (~ 5 min). I am sure it was much faster on linux, any idea how that can be?) 2014-03-17 14:34 GMT+01:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > Hi Nicolai, > > Roassal3d works well with the last Pharo 3.0. > You just need to execute the following incantation: > > -=-=-=-=-=-=-=-=-= > Gofer new smalltalkhubUser: 'ronsaldo' project: 'roassal3d'; package: > 'ConfigurationOfRoassal3d'; load. (Smalltalk at: #ConfigurationOfRoassal3d) > loadDevelopment > -=-=-=-=-=-=-=-=-= > > This does not work for you? > It works well on OSX and on Linux > > Alexandre > > > On Mar 15, 2014, at 10:52 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > Hi, > > > > what could be the reason, that any Roassal3d example from the > > Roassal3DTutorial.pdf only shows white empty windows? > > > > I loaded ConfigurationOfRoassal3d-RonieSalgado.10 and > > (Smalltalk at: > > #ConfigurationOfRoassal3d) loadDevelopment > > > > Any ideas? > > > > > > regards > > Nicolai > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

March 17, 2014

Re: [Pharo-dev] WhatsUp from: 2014-03-17 until: 2014-03-31

by Esteban Lorenzano

On 17 Mar 2014, at 07:00, seaside(a)rmod.lille.inria.fr wrote: > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: > > - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS - preparing vm for release pharo3 > > ### What's next, until 2014-03-31 (*): > > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION - prepare pharo3 for release :) > > (*) we'll be expecting results by then ;) >

March 17, 2014

Re: [Pharo-dev] WhatsUp from: 2014-03-17 until: 2014-03-31

by Ben Coman

seaside(a)rmod.lille.inria.fr wrote: > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: * Had a dozen or so bug fixes integrated. Surprised myself by how far I could dig into the system and it still made sense. I've learnt a lot about corners of the system I'd normally never poke around in. Its been fun. > ### What's next, until 2014-03-31 (*): > > Squash more bugs.

March 17, 2014

Re: [Pharo-dev] Roassal 3D empty windows

by Alexandre Bergel

Hi Nicolai, Roassal3d works well with the last Pharo 3.0. You just need to execute the following incantation: -=-=-=-=-=-=-=-=-= Gofer new smalltalkhubUser: 'ronsaldo' project: 'roassal3d'; package: 'ConfigurationOfRoassal3d'; load. (Smalltalk at: #ConfigurationOfRoassal3d) loadDevelopment -=-=-=-=-=-=-=-=-= This does not work for you? It works well on OSX and on Linux Alexandre On Mar 15, 2014, at 10:52 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > Hi, > > what could be the reason, that any Roassal3d example from the > Roassal3DTutorial.pdf only shows white empty windows? > > I loaded ConfigurationOfRoassal3d-RonieSalgado.10 and > (Smalltalk at: > #ConfigurationOfRoassal3d) loadDevelopment > > Any ideas? > > > regards > Nicolai > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 17, 2014

Re: [Pharo-dev] NBOpenGL on Windows

by Igor Stasenko

https://ci.inria.fr/pharo-contribution/job/NBOpenGL/ On 16 March 2014 00:02, Nicolai Hess <nicolaihess(a)web.de> wrote: > Is there a working version (maybe with examples) > for NBOpenGL on Windows? > > > -- Best regards, Igor Stasenko.

March 17, 2014

Re: [Pharo-dev] Adding a new catalog entry

by Nicolas Cellier

2014-03-17 10:15 GMT+01:00 Pharo4Stef <pharo4Stef(a)free.fr>: > > well we will have to clean and simplify all that in the future. >> This is why versionner should be good so that people use it and we can >> simplify the declarations. >> >> Stef >> >> > But I had the feeling that Versionner UI is currently very limited vs > Metacello options (especially w.r.t. cross dialect support) > > > > The problem is that metacello is too complex. :) > And the API could be better. > > Agree, see my other reply to Sven. An alternative is to - keep UI simple (mostly as it is now) by focusing onto single dialect/single dialect version - to automate the single dialect extract and cross dialect merge But maybe it's easier to say than do ;) > Or do you have a different POV, like only Pharo3.0 stuff should go to > MetaRepoForPharo3.0, and the ConfigurationOf... should be expunged from any > other dialect/version ? > > > For now this is ok to have multiple dialects in the metarepo because > people may want to have gemstone and squeak version. > Now for the core Pharo tool configruations should be as simple as possible > (RB, ...) > > Stef > > > >> >>> >>> Bye >>> T. >>> >>> *Gesendet:* Sonntag, 16. MÃ¤rz 2014 um 17:31 Uhr >>> *Von:* "Nicolas Cellier" <nicolas.cellier.aka.nice(a)gmail.com> >>> *An:* "Pharo Development List" <pharo-dev(a)lists.pharo.org> >>> *Betreff:* Re: [Pharo-dev] Adding a new catalog entry >>> >>> 2014-03-16 16:06 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>>> >>>> Nicolas, >>>> >>>> On 16 Mar 2014, at 10:08, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>> > To get access your StHub account, if you have any, should be part of >>>> the Pharo team, but I don't think I can do that. >>>> >>>> I now see that 'nice' is part of 'Pharo', so I think you should be able >>>> to save to MetaRepoForPharo30. >>>> >>> >>> >>> Thanks, I think I messed up when entering my credentials... >>> I have now published with a symbolic stable version. >>> >>> >>>> Sven >>> >>> >

March 17, 2014

Re: [Pharo-dev] Just a reminder

by Jan Vrany

On 17/03/14 09:45, Henrik Johansen wrote: >> >> Now how many do have to follow through all this? >> >> So well yes in the end it means not thinking about compatibility costs a >> lot thereafter.... >> > > Smalltalk os platformName -> works in Pharo 1.3, 1.4, 2.0, 3.0, Squeak 4.1 (in other words, the first new code release after relicensing effort). > > Smalltalk platformName -> works in all older version of Pharo/Squeak. > > While thereâs many places backwards compat could be better preserved, this is not one of themâ¦ > It is. There are other Smalltalks out there and most of them (maybe except GemStone?) have an object globally accessible under name #Smalltalk. So, Smalltalk platformName is the only sensible default as Friedrich pointed out. Best, Jan

March 17, 2014

Re: [Pharo-dev] Just a reminder

by Henrik Johansen

On 15 Mar 2014, at 8:05 , Friedrich Dominicus <frido(a)q-software-solutions.de> wrote: > That if you the developers of Phar change things many have to follow and > it comes to things like this: > "protocol: version dependent" > platformName > "After Squeak version 3.6, #platformName was moved to SmalltalkImage Some > versions of Pharo move this to OSPlatform and issue deprecation warnings > about the other usages. The original idiom (Squeak 3.6 and earlier) is the sensible > default, but here we attempt to support other implementations if the sensible > default is not available." > > "OSProcess platformName" > > (Smalltalk respondsTo: #platformName) > ifTrue: [^ Smalltalk platformName]. > self isPharo3AndLater > ifTrue: [ ^ (Smalltalk perform: #os) name ]. > ^ (((Smalltalk hasClassNamed: #OSPlatform) > and: [(Smalltalk at: #OSPlatform) > respondsTo: #platformName]) > ifTrue: [Smalltalk at: #OSPlatform] > ifFalse: [((Smalltalk classNamed: 'SmalltalkImage') > ifNil: [^ Smalltalk osVersion]) current]) platformName > > Now how many do have to follow through all this? > > So well yes in the end it means not thinking about compatibility costs a > lot thereafter.... > Smalltalk os platformName -> works in Pharo 1.3, 1.4, 2.0, 3.0, Squeak 4.1 (in other words, the first new code release after relicensing effort). Smalltalk platformName -> works in all older version of Pharo/Squeak. While thereâs many places backwards compat could be better preserved, this is not one of themâ¦ Cheers, Henry

March 17, 2014

Please add me to PharoExtras

by Stephan Eggermont

So I can save a working version of ConfigurationOfXMLSupport (it cannot load XMLWriter, due to a missing mc) Stephan

March 17, 2014

Re: [Pharo-dev] WhatsUp from: 2014-03-17 until: 2014-03-31

by Pharo4Stef

> > ### Here's what I've been up to since the last WhatsUp: - working on new book chapter - better catalog - working on finding money for engineers. > > ### What's next, until 2014-03-31 (*): - consortium more work. - working on finding money for engineers - unreloader

March 17, 2014