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

[Pharo-project] spec + shortcuts

by Camillo Bruni

I just looked at https://code.google.com/p/pharo/issues/detail?id=6736 Everything looks more or less ok, the keymapping integration is nice! I have one doubt though (and I really don't know anything about spec...). How do I explicitly set the default focus when opening an spec UI-item?

Oct. 8, 2012

Re: [Pharo-project] Emacs and Smalltalk code

by Oscar E A CallaÃº

Thanks guys for your replies. On Oct 8, 2012, at 15:02 , Frank Shearar <frank.shearar(a)gmail.com> wrote: > On 8 October 2012 18:31, Damien Cassou <damien.cassou(a)gmail.com> wrote: >> On Mon, Oct 8, 2012 at 4:51 PM, Oscar E A CallaÃº <oalvarez(a)dcc.uchile.cl> wrote: >>> I'm using Aquamacs (mac UI for emacs) as my default editor. But I have a problem, when trying to read a .st file, I don't get the syntax highlighting (so all is black-&-white). How I can solve this issue? >> >> Pharo/Smalltalk is not meant to be coded in Emacs, you have to use >> Pharo currently (that may change in the future). > > For shame, Damien. Why is Smalltalk not meant to be coded in a text > editor? It is text, after all. Next thing you'll suggest that one > shouldn't use git to store one's code. Relax guys. I known that when programming in Pharo, it is better to use the built-in browser, like Nautilus. However in some cases, I have a Smalltalk file (.st) outside the image, and I just want to see the code and not installing (file-in, compiling, â¦) it. That is the reason, why asking for emacs. Cheers.

Oct. 8, 2012

Re: [Pharo-project] Emacs and Smalltalk code

by Frank Shearar

On 8 October 2012 19:02, Frank Shearar <frank.shearar(a)gmail.com> wrote: > On 8 October 2012 18:31, Damien Cassou <damien.cassou(a)gmail.com> wrote: >> On Mon, Oct 8, 2012 at 4:51 PM, Oscar E A CallaÃº <oalvarez(a)dcc.uchile.cl> wrote: >>> I'm using Aquamacs (mac UI for emacs) as my default editor. But I have a problem, when trying to read a .st file, I don't get the syntax highlighting (so all is black-&-white). How I can solve this issue? >> >> Pharo/Smalltalk is not meant to be coded in Emacs, you have to use >> Pharo currently (that may change in the future). > > For shame, Damien. Why is Smalltalk not meant to be coded in a text > editor? It is text, after all. Next thing you'll suggest that one > shouldn't use git to store one's code. Alright, OK, I wrote that with at least 50% troll in the mix. (*) There's no reason why one shouldn't be able to use standard text manipulation techniques to hack on Smalltalk code. We simply never bothered doing so, and I dare say that the majority of people on this list are happy not supporting text-using tools. (*) OK, OK, 75%. frank >> If you still want to >> use Emacs, you will have to install a smalltalk mode. One can be found >> with gnu-smalltalk. If you are on a Debian-based Linux distribution, >> install gnu-smalltalk-el. >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill >>

Oct. 8, 2012

Re: [Pharo-project] Emacs and Smalltalk code

by Frank Shearar

On 8 October 2012 18:31, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Mon, Oct 8, 2012 at 4:51 PM, Oscar E A CallaÃº <oalvarez(a)dcc.uchile.cl> wrote: >> I'm using Aquamacs (mac UI for emacs) as my default editor. But I have a problem, when trying to read a .st file, I don't get the syntax highlighting (so all is black-&-white). How I can solve this issue? > > Pharo/Smalltalk is not meant to be coded in Emacs, you have to use > Pharo currently (that may change in the future). For shame, Damien. Why is Smalltalk not meant to be coded in a text editor? It is text, after all. Next thing you'll suggest that one shouldn't use git to store one's code. frank > If you still want to > use Emacs, you will have to install a smalltalk mode. One can be found > with gnu-smalltalk. If you are on a Debian-based Linux distribution, > install gnu-smalltalk-el. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

Oct. 8, 2012

Re: [Pharo-project] Emacs and Smalltalk code

by Frank Shearar

On 8 October 2012 15:51, Oscar E A CallaÃº <oalvarez(a)dcc.uchile.cl> wrote: > Hi all, > > I'm using Aquamacs (mac UI for emacs) as my default editor. But I have a problem, when trying to read a .st file, I don't get the syntax highlighting (so all is black-&-white). How I can solve this issue? I use GNU Smalltalk's smalltalk-mode. These instructions should see you on your way: http://www.cs.utah.edu/dept/old/texinfo/mst/mst.html#SEC7 I hope! frank > Cheers.

Oct. 8, 2012

Re: [Pharo-project] Emacs and Smalltalk code

by Damien Cassou

On Mon, Oct 8, 2012 at 4:51 PM, Oscar E A CallaÃº <oalvarez(a)dcc.uchile.cl> wrote: > I'm using Aquamacs (mac UI for emacs) as my default editor. But I have a problem, when trying to read a .st file, I don't get the syntax highlighting (so all is black-&-white). How I can solve this issue? Pharo/Smalltalk is not meant to be coded in Emacs, you have to use Pharo currently (that may change in the future). If you still want to use Emacs, you will have to install a smalltalk mode. One can be found with gnu-smalltalk. If you are on a Debian-based Linux distribution, install gnu-smalltalk-el. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Oct. 8, 2012

Re: [Pharo-project] Emacs and Smalltalk code

by dimitris chloupis

the first advice I can give is not to use aquamacs. Gnu emacs for macos is much better and much more powerful and complete. You can find it here -> http://emacsformacosx.com/ from there on you need to make sure smalltalk mode is enabled when an st file is opened to see syntax highlighting. ________________________________ From: Oscar E A CallaÃº <oalvarez(a)dcc.uchile.cl> To: "Pharo-project(a)lists.gforge.inria.fr" <Pharo-project(a)lists.gforge.inria.fr> Sent: Monday, 8 October 2012, 17:51 Subject: [Pharo-project] Emacs and Smalltalk code Hi all, Â Â I'm using Aquamacs (mac UI for emacs) as my default editor. But I have a problem, when trying to read a .st file, I don't get the syntax highlighting (so all is black-&-white). How I can solve this issue? Cheers.

Oct. 8, 2012

Re: [Pharo-project] Global session object?

by David T. Lewis

On Mon, Oct 08, 2012 at 04:12:13PM +0200, Igor Stasenko wrote: > > Another question, why session id was not exposed to language by VM > (your primitive in OSProcess plugin does that, but since plugin is > optional, the question remains the same). I don't know. Maybe nobody other than me ever wanted to use it ;) The session identifier is exposed through the InterpreterProxy, so it is part of the defined interface that is available to plugins. FilePlugin (and SocketPlugin IIRC) uses this identifier in its data structure to represent a file, so it provides a check to ensure that a file reference was created in the current session. I used this in OSPP because I wanted a separate plugin (not an extension of FilePlugin or SocketPlugin) that could interact with those same data structures. I did it that way because I wanted OSPP to be separate from the VM and the standard plugins, so anybody could build it without help from a VM guru. And I added the primitive so that I could do as much of the work in the image as possible. I guess we think alike in that regard ;) > The proposed change is trivial to introduce and use, but what > important, it don't requires altering VM. > Altering VM in order to fix/improve session management, will > immediately bring new issue: how to play nicely when running images > which expect such feature to be present, while users (for no good > reason, of course ;) using old/obsolete VMs to run image. > > This is yet another thing which demonstrates that the less code you > put in VM, the less you have to maintain and care less about > compatibility issues. I agree. Dave

Oct. 8, 2012

Re: [Pharo-project] Global session object?

by Henrik Sperre Johansen

On 08.10.2012 16:35, Igor Stasenko wrote: > On 8 October 2012 13:41, Henrik Sperre Johansen > <henrik.s.johansen(a)veloxit.no> wrote: >> On 08.10.2012 13:25, Igor Stasenko wrote: >>> On 8 October 2012 13:06, Henrik Sperre Johansen >>> <henrik.s.johansen(a)veloxit.no> wrote: >>>> On 08.10.2012 13:03, Henrik Sperre Johansen wrote: >>>>> >>>>> >>>>> IMO, lazily checking whether the image has been restarted whenever you >>>>> want to do something stinks. >>>>> Registering to be notified when image starts/stops is a lot better. >>>> Not to mention, less error-prone. >>>> Miss one session check that the current session is the right one >>>> somewhere... and everything might blow up if that is the first piece of >>>> functionality used. >>>> >>> True. >>> I did not said that my method should replace old. Sometimes lazy >>> initialization is not what you want. >>> But having no way to perform lazy initialization is even worse. >> Ah, I just objected to the notion that startup lists inherently stinks, and >> took the diametrical view for the sake of argument :) >> Yes, lazy initialization has its uses too, but some guidelines/advice* on >> when to what those uses are, and when you'd use startUp: registration >> instead, is needed I think. >> >> Notice; in most cases where such cleanup at startup is needed (sockets, >> window handles, etc.), additional cleanup is needed when the object goes out >> of scope during regular use, and so a registry usually exist. > Yes. > >> Thus, your startup code isn't usually >> X allInstancesDo: #something >> but >> X weakRegistry allEntriesDo: #someting. >> >> which stinks a whole lot less. >> > in perfect world, yes :) > > But world is imperfect.. > For example, look here: > > FT2Handle>>shutDown: quitting > "we must not save handles (which are pointers) in the image" > self clearRegistry. > FreeTypeFace allInstances do:[:i | > "destroy any faces that are still being referenced" > i isValid > ifTrue:[i destroyHandle]]. > FT2Handle allSubInstances do: [:h | h beNull]. "if some handle was > not registered" > > because of the above, when i pass freetype faces handles to Cairo, > which caching a lot of stuff inside (obviously for performance reasons), > when you save an image, and then try to use Cairo after that (like > rendering text with same font) > an image is crashing. > Which means that "we must not save handles (which are pointers) in the > image" now blocking > me from having nice interoperability with Cairo.. > > Needless to say that destroying handles will force their recreation > after snapshot, since image > continues running and will keep using freetype fonts. > > This is actually the reason why i want to introduce session object(s), > so that i can fix freetype code > to play more nicely with cairo library. I agree with this part from the wiki entry: "Dolphin does not free external resources on a snapshot. Resources are freed on shutdown (by registering for the shutdown events) and pointers/handles are cleared on *startup*. Having worked with it for years, I have gone from considering it strange to believing it is the correct design." Rewriting the shutdown to a startUp: method (conditional on the resuming parameter) shouldn't be too much work. A short analysis of the code reveals: 1) FT2Face/FT2MemoryFaceData aren't instatiated. 2) Both FT2Face and FreeTypeExternalMemory instances are both registered in the FT2Handle registry. (if used in a way which instantiates handle) 3) FT2Library recreates a new instance based for each call to current, which may be problematic, but current return values are never kept, just used to check that FT is present. So really, cleaning the entries found in registry is all that's actually needed at startup. Cheers, Henry

Oct. 8, 2012

[Pharo-project] Emacs and Smalltalk code

by Oscar E A CallaÃº

Hi all, I'm using Aquamacs (mac UI for emacs) as my default editor. But I have a problem, when trying to read a .st file, I don't get the syntax highlighting (so all is black-&-white). How I can solve this issue? Cheers.

Oct. 8, 2012