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

Re: [Pharo-project] NonInteractiveUIManager

by Igor Stasenko

On 30 January 2012 19:49, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > > On 30 Jan 2012, at 17:20, StÃ©phane Ducasse wrote: > >> Seems so because I do not understand anything. >> >> Stef >> >> On Jan 30, 2012, at 12:23 PM, Sven Van Caekenberghe wrote: >> >>> When making syntax errors in a startup script you get >>> >>> Â Â Â SubclassResponsibility: a NonInteractiveUIManager had the subclass responsibility to implement #syntaxErrorNotificationDefaultAction: >>> >>> Would it not be a better idea to just handle and print the syntax error ? >>> >>> Sven > > I am not that sure what to do exactly either, I turned this into an issue: > > http://code.google.com/p/pharo/issues/detail?id=5227 > > Igor ? > The main issue there is that when i implemented NonInteractiveUIManager , i made sure that all subclasses of UIManager supporting same protocol. Now if people just adding methods to MorphicUIManager and using them, without caring to properly add same protocol in parallel to others, you getting errors like that. Sure thing, it is easy to fix, you just implement this message in NonInteractiveUIManager :) > Sven > > -- Best regards, Igor Stasenko.

Jan. 30, 2012

Re: [Pharo-project] pharo vision

by StÃ©phane Ducasse

Thanks in fact I wanted to send it to the mailing list of our team because I wanted to gather feedback before sending it to the mailing-list to ask for another set of feedback. So I will finish it now :) Stef On Jan 30, 2012, at 5:46 PM, dimitris chloupis wrote: > Thanks stef for this . The document informed me of things I was not aware of and now after reading it I like Pharo even more . > > From: Henrik Johansen <henrik.s.johansen(a)veloxit.no> > To: Pharo-project(a)lists.gforge.inria.fr > Sent: Monday, 30 January 2012, 18:10 > Subject: Re: [Pharo-project] pharo vision > > > On Jan 30, 2012, at 9:24 14AM, StÃ©phane Ducasse wrote: > >> <main.pdf> > Nice! > > Some comments on the parts I'm most familiar with: > 3.2 > I agree, the nice parts in FS to me is the path manipulation API. > Going back to pure ANSI-streams as provided by FSFileStream is not really an option. > Since it's a clean break from FileDirectory & friends though, it might be the perfect time to introduce XTreams; -or it might be too much hassle to have to change both parts in existing code at once. > > A good compromise would be to make it pluggable, using the existing Standard/MultiByteFileStreams by default, but making XStreams pluggable (on a use--by-use basis, so you can write new code with XStreams while maintaining old code where you have only had time to rewrite the path handling) > > 3.3 > "Using ephemerons we can then simplify the Announcement and make sure that clients do not have to worry about weak or not registration." > You still have to worry about whether you want weak or strong registration. > "Do I have strict requirements for when the announcement should stop being delivered in relation to subscriber lifespan?" is still a valid question. > What you don't have to worry about, is what _type_ of subscription (action blocks or message sends), you are allowed to use when registering weakly. > > Ends with "In addition, " then nothing :) > > Cheers, > Henry > >

Jan. 30, 2012

Re: [Pharo-project] Collection new

by Marcus Denker

On Jan 30, 2012, at 4:35 PM, Marcus Denker wrote: > > On Jan 30, 2012, at 4:30 PM, Andrew P. Black wrote: > >> Hmm, is this really right? I'm used to seeing "Error in printString ..." >> > > Wasn't that a bug we already fixed? In 1.4 I can do Collection new and I get the subclass responsibility... > And I thought we back-ported the fix to 1.3, too. > > Need to check... Ah, the One-Click is 13315, but there is a #13320... We should update the download. (which includes fixing the jenkins build, for the VM, too). Marcus -- Marcus Denker -- http://marcusdenker.de

Jan. 30, 2012

Re: [Pharo-project] Collection new

by Marcus Denker

On Jan 30, 2012, at 4:30 PM, Andrew P. Black wrote: > Hmm, is this really right? I'm used to seeing "Error in printString ..." > Wasn't that a bug we already fixed? In 1.4 I can do Collection new and I get the subclass responsibility... And I thought we back-ported the fix to 1.3, too. Need to check... > > On 30 Jan 2012, at 11:12 , Milan Mimica wrote: > >> >> >> On 30 January 2012 19:31, Andrew P. Black <black(a)cs.pdx.edu> wrote: >> >> But I don't understand the root cause. Printing eventually sends do:, which is self subclassResponsibility. Why don't we get a clean failure? >> >> Andrew >> >> When an error occurs during error handling (which includes printing) it is not a clean failure. Emergency evaluator pops up in that case. >> > > -- Marcus Denker -- http://marcusdenker.de

Jan. 30, 2012

Re: [Pharo-project] Collection new

by Andrew P. Black

Hmm, is this really right? I'm used to seeing "Error in printString ..." On 30 Jan 2012, at 11:12 , Milan Mimica wrote: > > > On 30 January 2012 19:31, Andrew P. Black <black(a)cs.pdx.edu> wrote: > > But I don't understand the root cause. Printing eventually sends do:, which is self subclassResponsibility. Why don't we get a clean failure? > > Andrew > > When an error occurs during error handling (which includes printing) it is not a clean failure. Emergency evaluator pops up in that case. >

Jan. 30, 2012

Re: [Pharo-project] Collection new

by Milan Mimica

On 30 January 2012 19:31, Andrew P. Black <black(a)cs.pdx.edu> wrote: > > > But I don't understand the root cause. Printing eventually sends do:, > which is self subclassResponsibility. Why don't we get a clean failure? > > Andrew > When an error occurs during error handling (which includes printing) it is not a clean failure. Emergency evaluator pops up in that case. -- Milan Mimica http://sparklet.sf.net

Jan. 30, 2012

[Pharo-project] Help with markdown is coming...

by Igor Stasenko

a bit messy, because Camillo is a bad guy! ;) -- Best regards, Igor Stasenko.

Jan. 30, 2012

[Pharo-project] Collection new

by Andrew P. Black

Teaching a class of novices, it's not surprising that someone tried "Collection new". What was surprising is that this got the VM is a loop of some kind, with emergency stack dumps and so on. Here is my reply: > On 30 Jan 2012, at 01:18 , Xingzhi Harry Pan wrote: > >> ...it's pretty innocent: >> Collection new > > > OK. I looked at this. The problem comes when trying to print the collection. Somehow the VM gets confused when trying to do do: ... I'm not quite clear why. > > The quick fix is to change the Collection>>new method to > > self error: 'Collection is an abstract class, and cannot be instantiated' > > However this will break Heap>>new: , which sends super new. It ought to send self basicNew instead. > > These two changes seem to avoid the problem, but I'm waiting to see ... > > Andrew But I don't understand the root cause. Printing eventually sends do:, which is self subclassResponsibility. Why don't we get a clean failure? Andrew

Jan. 30, 2012

Re: [Pharo-project] Morpheas , bringing Morphic to Opengl (3d GUIs)

by dimitris chloupis

> I am not proposing to help with coding your actual project, > i just providing a support for > NativeBoost and NBOpenGL, in case if you choose them to use. I did not say that. I thought you thought I was asking for help with the coding.Â Yeap that exactly what I asked from you, support on NB and NBOGL , mainly documentation and potential bug fixes. Thats all.Â > It is not insanity. My first small project when i joined squeak community were > GLCanvas, so i am also kind of infected with weird ideas of > implementing a novel UIs > using opengl and smalltalk. > But road is long, and needs to be walked.. and waking with party is > much easier and fun. I realise that , however I have a very specific vision of what I want to achieve. I am doing this only on the grounds of enjoyment and not end result. But If I can found people with their own vision and with a similar path to mine, I have no issue to join forces with them. Actually several people seem to want a port Morphic to OGL and I am already with communication with them via #squeak at freenode.net (currently there are 3 of us) so yes I welcome it as an option to have a high level of cooperation on the subject. Â I hope this thread to be a motivation for all of us OGL to join code. On the other hand thats not up to me only ;) > right now, most of it onÂ http://code.google.com/p/nativeboost/w/list > we're also writing a book chapter about it, >Â https://gforge.inria.fr/scm/viewvc.php/*checkout*/PharoByExampleTwo-Eng/Ali… > which is work in progress. ah lovely , of course I am aware of your wiki but I was not aware of the PBE chapter and the on-board reference. > thanks for valuing my effort :) but frankly my opinion about my workÂ is not that high Well maybe my project and other projects that will use NBOGL will change your mind one day ;)Â I will back with further questions

Jan. 30, 2012

Re: [Pharo-project] Which COG VM?

by Andrew P. Black

On 20 Jan 2012, at 07:31 , Bernardo Ezequiel Contreras wrote: > try > > Smalltalk vm version This just answers 'Pharo1.3', which is not surprising, since Smalltalk vm == SmalltalkImage current. SystemVersion current version answers the same string. On the latest Jenkins build, found from the responses in this thread, I get SmalltalkImage current vmVersion ==> 'Croquet Closure Cog VM [CoInterpreter VMMaker-oscog-EstebanLorenzano.139] 21.0' Andrew

Jan. 30, 2012