February 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Workspace API

by Keith Hodges

>>> >>> >>> >> I thought that MinimalMorphic was released 2 years ago? >> >> ok I was mistaken, I meant the etoys removal script Keith

Feb. 12, 2009

Re: [Pharo-project] isActive and isEnable

by Alexandre Bergel

Maybe some comments could be added in the class OBCommand Shall I do it? But I cannot say more than what you just said Cheers, Alexandre On 12 Feb 2009, at 14:49, David RÃ¶thlisberger wrote: > >> #isActive would probably better be called #isVisible. > > yeah, that's true. > > So #isActive in the context of a command tells you whether this > command is present > for the given entity and #isEnabled whether it's also selectable. > For an example see 'redo' of OB-Refactory. If there is no redo- > action available, the > command is still visible in the menu but not selectable. > > David > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 12, 2009

Re: [Pharo-project] isActive and isEnable

by David RÃ¶thlisberger

> #isActive would probably better be called #isVisible. yeah, that's true. So #isActive in the context of a command tells you whether this command is present for the given entity and #isEnabled whether it's also selectable. For an example see 'redo' of OB-Refactory. If there is no redo-action available, the command is still visible in the menu but not selectable. David

Feb. 12, 2009

Re: [Pharo-project] OB 10231: search bar does not work

by David RÃ¶thlisberger

Hi Simon > Using the latest pharo dev 10231dev09.02.1, I cant use the search bar > anymore. I got a OBEnhancementMetaNode(Object)>>doesNotUnderstand: #fan: I fixed this in latest OBAlpha. Can you check if it works for you too? David

Feb. 12, 2009

Re: [Pharo-project] Workspace API

by StÃ©phane Ducasse

Come on this is not the same.... On Feb 12, 2009, at 1:49 PM, Keith Hodges wrote: > StÃ©phane Ducasse wrote: >> I know. I just want to tell you that nothing is easy. >> Now saying that we do not pay attention is not exact. >> But really beside integrating fixes and cleaning etoy I have no time. >> >> Stef >> >> > I thought that MinimalMorphic was released 2 years ago? > > Keith > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 12, 2009

Re: [Pharo-project] looking for Unicode testers

by Michael Rueger

John M McIntosh wrote: > No, it's just more smalltalk coding, the utf8-plain-text bytes need to > be translated into bytes according to Somewhere in the call chain it is finally FFI calls as you illustrate below. How much would it take to have the primitive return the normalized UTF-8 string directly? Michael > > "Normalizes the string into the specified form as described in Unicode > Technical Report #15." > and ensure we return the bytes as UTF8. > > The FFI calls let the macintosh operating system deal with the messy > details. > > > http://unicode.org/unicode/standard/reports/tr15/tr15-18.html > also see > http://developer.apple.com/qa/qa2001/qa1235.html > > Say is that a precomposed and decomposed Unicode you have there, really > what does squeak want? want does the operating system want. > Choices choices. > > PS beware the utf8 to macroman or macroman to utf8 text converts in > squeak, I don't think the one that came from etoys does the right thing > can't remember, it's named wrong, does utf8 to ascii or something... > > > On 11-Feb-09, at 7:29 AM, Michael Rueger wrote: > >> Michael Rueger wrote: >> >>>> Well that *is* the extended clipboard support. Just need the >>>> smalltalk code to make the proper primitive calls to the extended >>>> clipboard plugin. >>>> You need the ClipboardExtendedPlugin.bundle >> >> Hmm, you still need FFI despite the plugin: >> >> readUTF8StringClipboardData >> | bytes | >> "utf8" >> >> bytes := self readClipboardData: 'public.utf8-plain-text'. >> bytes := MacCFString callMakeUTF8NormalizedStringViaByteString: >> bytes asString. >> ^bytes ifNil: [bytes] ifNotNil: >> [bytes asString convertFromWithConverter: (UTF8TextConverter >> new)] >> >> >> >> Michael > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > >

Feb. 12, 2009

Re: [Pharo-project] Workspace API

by Keith Hodges

StÃ©phane Ducasse wrote: > I know. I just want to tell you that nothing is easy. > Now saying that we do not pay attention is not exact. > But really beside integrating fixes and cleaning etoy I have no time. > > Stef > > I thought that MinimalMorphic was released 2 years ago? Keith

Feb. 12, 2009

Re: [Pharo-project] Workspace API

by Keith Hodges

> Our goal is to make progress. Squeak is dying don't see it? > The reason it is dying is because once anyone starts a significant project they are stuck with the same image that they started with. Thus everyone gets left along the path of progress. They keep up or get left behind to fork their own little world. Pharo perpetuates and exacerbates this problem through its philosophy. You could have picked a slice of squeak, instituted a project to improve it, and then contributed that improved slice back to everyone, and so on. The kernel image itself is not that important to getting actual work done, once you eliminate certain headaches like FileDirectory (Rio was my choice of the section of the kernel to improve). Sure, if you are doing academic little projects, you might be constantly irked by the lack of change in the kernel. If you are working on a big project with clients breathing down your neck, you just get on with it. The cause (since captials are deemed to be rude, sorry Paul) of squeak dying is that those who move it forward are too busy making progress and they dont think about the users of older images. How many of our potential millions of future xo users will be taking their future xo software apart to find Pharo inside? >> And you are ignoring those tools, because you dont see them as >> important. >> > I would love to have a buildServer and also run automatically > SmallLint rules on the code > now either pharo does not exist because we build those tools or pharo > exist. So please .... explain this to me.... why cant. Project A working on the kernel and not the tools, fit together with project B, working on the tools and not the kernel? Looks simple on paper doesn't it. Think it over, A+B = AB, and B + A = BA, hmm it works, infact its kind of obvious. Now why is it that this doesn't work I wonder? Please explain this to me? Correct me if I am wrong, but I think it is because Project A is working on the kernel, and is for some reason forking the loadable tools (which should be outside of their remit) thus absorbing all of the expertise, making things more difficult for everyone. Project B then gives up and goes off to do something else, because they realise that 3 years of efforts trying to open up repositories and to encourage people to contribute collaboratively to tools as shared resources over the whole community of projects, is a total and utter waste of time. All the repo's on Project B are public, and anyone can contribute, however the majority of Project A contributors don't join in. > buildserver and this is why > I have been working on the Build server since Feb 2007. That was where the idea for Rio originally came from. The ruby version of Bob did work but it was tricky to set up. The smalltalk one only needs one day of work to complete, and I said that 3 months ago. However since no-one from your team seems willing to join on fixing up MC1.5 etc I was left to spend yesterday fixing an MC1.5 bug. Perhaps there is no point in doing that one day of work on Bob because no-one will bother looking at it anyway. > we started to write on Installer (and you know that this is not only > for pharo so you should be happy). > You did? > Now you should ask yourself the question why people are not all using > your tool extensions. > Actually they are. If they were not I wouldn't be here now. > Conservatism? stupidity? lack of time? lack of trust? Dont'care? > None of the above. Many people load LPF and get on with the job they have to do. Keith

Feb. 12, 2009

Re: [Pharo-project] isActive and isEnable

by Lukas Renggli

#isActive would probably better be called #isVisible. Lukas On Thu, Feb 12, 2009 at 1:28 PM, Alexandre Bergel <Alexandre.Bergel(a)inria.fr> wrote: > Dear OBers, > > What is the difference between these two methods? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 12, 2009

[Pharo-project] isActive and isEnable

by Alexandre Bergel

Dear OBers, What is the difference between these two methods? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 12, 2009