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

Re: [Pharo-project] [squeak-dev] Re:NativeBoost and NBOpenGL on Mac?

by Lawson English

There's bound to be a way. Perhaps an array of requests, followed by an array of responses, that can be normalized in a cross-platform way? The fact that the responses might be platform specific doesn't matter as long as they are consistent within the platform, right? You just need 2-way glue: 1 way to create the query and the other to put the query in a cross-platform format that can be used by the rest of the system. L. On 1/11/12 3:39 PM, Igor Stasenko wrote: > On 11 January 2012 20:10, Lawson English<lenglish5(a)cox.net> wrote: >> [pharo list added back in for real this time] >> >> Would it be best to have a VM primitive that actually gives this info in a >> cross-platform way since it is going to be more and more useful as time goes >> on? >> > one big issue with such primitive is lack of options which i able to > contol for context i creating. > As you may know there's a lot of different options , like > - depth buffer bits, color buffer bits, alpha bits number of back > buffers, subpixel antialiazing, > auxuliarry buffers etc > > as i said before in other posts.. it is really hard to create a > primitive which will allow > you to control all those options, especially a cross-platform one. > > I know that for most users you could take 1 pixel format, 1 back > buffer and you free to go, > but it just doesn't feels right to me, why we should lose all the > variety of control and put constrains at context creation stage. > That's why i striving for controlling context creation at image side, > and if that requires writing a platform-specific code > in image, so be it. But then i could make sure that you could access > all OpenGL capabilities similar to C/C++ code, > without limitations. > For beginners, these options may mean nothing, but for those who > dealing with OpenGL at more advanced levels, trust me, > they simply cannot live without it. Many advanced opengl examples and > rendering techniques requiring fine control on context creation. > > > >> On 1/11/12 11:56 AM, Hans-Martin Mosner wrote: >>> Am 11.01.2012 19:18, schrieb Bert Freudenberg: >>>> ... >>>> This primitive encapsulates the platform-dependent part of creating an >>>> OpenGL rendering context. OpenGL itself is platform-independent, but >>>> creating a window is not. The plugin has code for Mac, Windows, and Unix. >>>> >>>> So this creates a new borderless window that gets embedded in the "big" >>>> main window. It also creates an OpenGL context for that window and makes it >>>> current. After calling the primitive you can use any OpenGL commands to draw >>>> directly into it using the hardware renderer. I don't see a good reason why >>>> you would not want to use it. >>>> >>>> - Bert - >>>> >>> I'm currently also experimenting with this (under Linux) and it looks like >>> this does not fully work on my system - the >>> OpenGL output seems to be displayed for a very short moment, and then only >>> teh Squeak desktop is visible again. >>> Of course, it's nice to have the platform-dependent part within the >>> primitive, but at least for Windows and Linux/X11 >>> creating an OpenGL context is not really difficult, so since we already >>> have platform-dependent OpenGL subclasses >>> anyway, there is no strong reason to keep the context creation stuff in >>> primitive code. >>> >>> Cheers, >>> Hans-Martin >>> >>> >> > >

Jan. 13, 2012

Re: [Pharo-project] [Pharo-users] OCompletion configuration for 1.4

by StÃ©phane Ducasse

Thanks a lot!!!! Stef On Jan 13, 2012, at 3:53 PM, Guillermo Polito wrote: > I've written a new version of OCompletion for 1.4 with several fixes and compatibility additions for Pharo 1.4 > > Gofer it > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfOCompletion'; > load. > > ConfigurationOfOCompletion loadStable > > If someone wants to try it :). > > Guille

Jan. 13, 2012

Re: [Pharo-project] What is the difference between ActionSequence and WeakActionSequence

by Mariano Martinez Peck

On Fri, Jan 13, 2012 at 4:48 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Fri, Jan 13, 2012 at 4:44 PM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> But they are both defined the same way! >> >> Array variableSubclass: #WeakActionSequence >> instanceVariableNames: '' >> classVariableNames: '' >> poolDictionaries: '' >> category: 'Kernel-Objects' >> >> The only reference to it's weakness it its name! :P >> >> > I also see > > >> asActionSequenceTrappingErrors > > ^WeakActionSequenceTrappingErrors withAll: self > > > ;) > > But ActionSequence is the same jahahahha > >> On Fri, Jan 13, 2012 at 12:39 PM, Henrik Johansen < >> henrik.s.johansen(a)veloxit.no> wrote: >> >>> >>> On Jan 13, 2012, at 4:33 23PM, Guillermo Polito wrote: >>> >>> > In 1.3 they look the same, in 1.4 ActionSequence is not there any >>> more... >>> > >>> > Is the second one replacing the first one? are there any differences >>> for the user? >>> > >>> > Thanks, >>> > Guille >>> >>> >>> ActionSequence was not referenced by the base system any more, not sure >>> why it was removed instead of deprecated. >>> And yes, there is a difference for a user, the WeakActionSequence holds >>> actions weakly, while ActionSequence held them strongly. >>> (WeakActionSequence automatically removes the actions when there are no >>> other references to the registrar, while ActionSequence did not, and you >>> had to unregister manually before it would stop executing them) >>> >>> Cheers, >>> Henry >>> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

Jan. 13, 2012

Re: [Pharo-project] What is the difference between ActionSequence and WeakActionSequence

by Mariano Martinez Peck

On Fri, Jan 13, 2012 at 4:44 PM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > But they are both defined the same way! > > Array variableSubclass: #WeakActionSequence > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'Kernel-Objects' > > The only reference to it's weakness it its name! :P > > I also see >> asActionSequenceTrappingErrors ^WeakActionSequenceTrappingErrors withAll: self ;) > On Fri, Jan 13, 2012 at 12:39 PM, Henrik Johansen < > henrik.s.johansen(a)veloxit.no> wrote: > >> >> On Jan 13, 2012, at 4:33 23PM, Guillermo Polito wrote: >> >> > In 1.3 they look the same, in 1.4 ActionSequence is not there any >> more... >> > >> > Is the second one replacing the first one? are there any differences >> for the user? >> > >> > Thanks, >> > Guille >> >> >> ActionSequence was not referenced by the base system any more, not sure >> why it was removed instead of deprecated. >> And yes, there is a difference for a user, the WeakActionSequence holds >> actions weakly, while ActionSequence held them strongly. >> (WeakActionSequence automatically removes the actions when there are no >> other references to the registrar, while ActionSequence did not, and you >> had to unregister manually before it would stop executing them) >> >> Cheers, >> Henry >> > > -- Mariano http://marianopeck.wordpress.com

Jan. 13, 2012

Re: [Pharo-project] What is the difference between ActionSequence and WeakActionSequence

by Guillermo Polito

But they are both defined the same way! Array variableSubclass: #WeakActionSequence instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'Kernel-Objects' The only reference to it's weakness it its name! :P On Fri, Jan 13, 2012 at 12:39 PM, Henrik Johansen < henrik.s.johansen(a)veloxit.no> wrote: > > On Jan 13, 2012, at 4:33 23PM, Guillermo Polito wrote: > > > In 1.3 they look the same, in 1.4 ActionSequence is not there any more... > > > > Is the second one replacing the first one? are there any differences for > the user? > > > > Thanks, > > Guille > > > ActionSequence was not referenced by the base system any more, not sure > why it was removed instead of deprecated. > And yes, there is a difference for a user, the WeakActionSequence holds > actions weakly, while ActionSequence held them strongly. > (WeakActionSequence automatically removes the actions when there are no > other references to the registrar, while ActionSequence did not, and you > had to unregister manually before it would stop executing them) > > Cheers, > Henry >

Jan. 13, 2012

Re: [Pharo-project] What is the difference between ActionSequence and WeakActionSequence

by Henrik Johansen

On Jan 13, 2012, at 4:33 23PM, Guillermo Polito wrote: > In 1.3 they look the same, in 1.4 ActionSequence is not there any more... > > Is the second one replacing the first one? are there any differences for the user? > > Thanks, > Guille ActionSequence was not referenced by the base system any more, not sure why it was removed instead of deprecated. And yes, there is a difference for a user, the WeakActionSequence holds actions weakly, while ActionSequence held them strongly. (WeakActionSequence automatically removes the actions when there are no other references to the registrar, while ActionSequence did not, and you had to unregister manually before it would stop executing them) Cheers, Henry

Jan. 13, 2012

[Pharo-project] What is the difference between ActionSequence and WeakActionSequence

by Guillermo Polito

In 1.3 they look the same, in 1.4 ActionSequence is not there any more... Is the second one replacing the first one? are there any differences for the user? Thanks, Guille

Jan. 13, 2012

[Pharo-project] CommentReference removed?

by Guillermo Polito

I am trying to load OB in Pharo 1.4, but It seems CommentReference was removed from the image... Shouldn't it go to a deprecated package? Should we reitroduce it with the proper deprecation? Guille

Jan. 13, 2012

[Pharo-project] [ANN] DBXTalk site and mailing list little news

by Guillermo Polito

The dbxtalk mailing list is now availiable from Nabble :) http://forum.world.st/DBXTalk-f3718169.html Thank you very much Geert!! Also, the site is up again, hehe http://dbxtalk.smallworks.com.ar Thanks Diogenes! xD cheers, the DBXTalk team

Jan. 13, 2012

Re: [Pharo-project] Preparing 1.4 beta

by Henrik Johansen

On Jan 13, 2012, at 1:18 44PM, StÃ©phane Ducasse wrote: > thanks. May be I will add SystemAnnouncement and RPackage since this is stable. > We will check if we can push or not in 1.4 the clean of the eventBuff. > > Stef See issue 5172 - 5174 for my comments. TLDR; I don't think it's a good idea to include in Core for 1.4, a more pervasive integration with the base system would be desirable, so one could remove the old event-based system at the same time. (but have a backwards-compatible external package) Cheers, Henry

Jan. 13, 2012