September 2014 - Pharo-users

Re: [Pharo-users] Unicode support in Pharo

by Sven Van Caekenberghe

On 27 Sep 2014, at 05:51, Alain Rastoul <alf.mmm.cat(a)gmail.com> wrote: > Le 27/09/2014 01:02, Sven Van Caekenberghe a Ã©crit : >> >> On 26 Sep 2014, at 23:22, Alain Rastoul <alf.mmm.cat(a)gmail.com> wrote: >> >>> Pasting a Greek string in a workspace shows hieroglyphs (editors? morph?), but GT Inspector display is ok. >> >> That is a font issue. Check your font settings in the Settings Browser. >> >> Like I mentioned in the chapter, you could try to use 'Arial Unicode MS'. >> >> I would guess you use Source Code Pro for code panes (like the workspace) and Open Sans for the rest. Source Code Pro has limited Unicode support. GT probably uses only Open Sans. >> > Ouch, forgot about different font settings for morphic elements, and evident, GTInspector could not display correctly if editor would not deal with WideString (forgot about bytestring/widestring transparency?). > BTW I do not have Arial unicode MS on my system, it comes with MS Office, but Deja Vu and Bitmap Deja vu display some Greek chars correctly. It is a TrueType font, you have to enable it in System Setting, then you should see a very long list of fonts to choose from, not just one or two.

Sept. 27, 2014

Re: [Pharo-users] Your picture on Pharo contributors :)

by Trygve Reenskaug

On 27.09.2014 09:26, Marcus Denker wrote: > > On 27 Sep 2014, at 07:17, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > >> Trygve >> >> We took exactly the same license process and text than squeak. This >> way people cannot argue that this is different >> because pharo is based on Squeak. It took squeak a large effort to >> relicense the code and we rewrote missing methods >> double blind to get clean. >> > > But it should be easy to change the PDF to contain the textâ¦ I put it > on the discussion for the board meeting. > > Marcus Much better, thank you. It's already here http://pharo.org/license Trygve

Sept. 27, 2014

Re: [Pharo-users] Your picture on Pharo contributors :)

by Marcus Denker

On 27 Sep 2014, at 07:17, stepharo <stepharo(a)free.fr> wrote: > Trygve > > We took exactly the same license process and text than squeak. This way people cannot argue that this is different > because pharo is based on Squeak. It took squeak a large effort to relicense the code and we rewrote missing methods > double blind to get clean. > But it should be easy to change the PDF to contain the textâ¦ I put it on the discussion for the board meeting. Marcus > Stef > > > On 26/9/14 10:19, Trygve Reenskaug wrote: >> With all due respect, I am reluctant to sign this agreement. It commits me to whatever might be published at the given URL at any time in the future. I wonder why you didn't make the agreement concrete by copying the current text into it? >> >> Current contents of <http://www.opensource.org/licenses/mit-license.php>: >> "Copyright (c) <year> <copyright holders> >> >> Permission is hereby granted, free of charge, to any person obtaining a copy >> of this software and associated documentation files (the "Software"), to deal >> in the Software without restriction, including without limitation the rights >> to use, copy, modify, merge, publish, distribute, sublicense, and/or sell >> copies of the Software, and to permit persons to whom the Software is >> furnished to do so, subject to the following conditions: >> >> The above copyright notice and this permission notice shall be included in >> all copies or substantial portions of the Software. >> >> THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR >> IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, >> FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE >> AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER >> LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, >> OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN >> THE SOFTWARE." >> I have no problem with signing this, but I have a problem with signing a carte blanche. >> --Trygve >> >> >> >> On 26.09.2014 07:25, stepharo wrote: >>> Hi guys >>> >>> do not forget to sign the license agreement >>> http://files.pharo.org/media/PharoSoftwareDistributionAgreement.pdf >>> and send us your picture to be added to >>> http://pharo.org/about >>> >>> Stef >>> >>> >>> >>> >>> >> >> -- >> >> Trygve Reenskaug mailto: trygver(a)ifi.uio.no >> Morgedalsvn. 5A http://folk.uio.no/trygver/ >> N-0378 Oslo http://fullOO.info >> Norway Tel: (+47) 22 49 57 27 >

Sept. 27, 2014

Hanging reference and sluggish image

by Alain Rastoul

Hi, I have a sluggish image due to some hanging reference on a big object (a BTree filled with test data) that I inspected with GTInspector, and can't get rid of those references. Opening a PointerExplorer on this object show me lot of various references from GLMCompositePresentations, GLMPanes, AnouncementSubscriptions, blocks etc. Is there a clean way to reset subscriptions , announcers and GLMPresentations ? Any help or suggestion will be greatly appreciated, thanks in advance, Alain

Sept. 27, 2014

Re: [Pharo-users] How to set a white background with Spec ?

by stepharo

One of these days we should do a pass because I do not get why such properties are not simply handled by the model. Stef > Changes on a widget attributes can be defined when it is build. > To hook into this, use #whenBuiltDo: > > |t| > t:= TextModel new. > t whenBuiltDo:[:a | a widget color: Color gray]. > t openWithSpec. > > > > > > 2014-09-26 15:51 GMT+02:00 Johan Fabry <jfabry(a)dcc.uchile.cl > <mailto:jfabry@dcc.uchile.cl>>: > > > I have not tried this, I just browsed the documentation, but I am > putting it here as this process usually is the right way to find > answers to these questions: I looked at the spec class for > windows: WindowModel and the âprotocol' protocol to see its > configuration options. None mention color. I looked at the > superclass: AbstractWindowModel, and the âprotocolâ protocol does > have a color: setter. > > So if you have a reference to the WindowModel for the window you > are using, you should be able to set the color. Please tell me if > this works for you. I think this question is a good candidate for > updating the documentation. > > On Sep 26, 2014, at 6:11 AM, Annick Fron <list(a)afceurope.com > <mailto:list@afceurope.com>> wrote: > > > Hi, > > > > I am using a window with spec, where can I define a white > background for it ? > > > > Annick > > > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/%7Ejfabry> > PLEIAD lab - Computer Science Department (DCC) - University of > Chile > > >

Sept. 27, 2014

Re: [Pharo-users] Your picture on Pharo contributors :)

by stepharo

Trygve We took exactly the same license process and text than squeak. This way people cannot argue that this is different because pharo is based on Squeak. It took squeak a large effort to relicense the code and we rewrote missing methods double blind to get clean. Stef On 26/9/14 10:19, Trygve Reenskaug wrote: > With all due respect, I am reluctant to sign this agreement. It > commits me to whatever might be published at the given URL at any time > in the future. I wonder why you didn't make the agreement concrete by > copying the current text into it? > > Current contents of <http://www.opensource.org/licenses/mit-license.php>: > > "Copyright (c) <year> <copyright holders> > > Permission is hereby granted, free of charge, to any person > obtaining a copy > of this software and associated documentation files (the > "Software"), to deal > in the Software without restriction, including without limitation > the rights > to use, copy, modify, merge, publish, distribute, sublicense, > and/or sell > copies of the Software, and to permit persons to whom the Software is > furnished to do so, subject to the following conditions: > > The above copyright notice and this permission notice shall be > included in > all copies or substantial portions of the Software. > > THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, > EXPRESS OR > IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF > MERCHANTABILITY, > FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT > SHALL THE > AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR > OTHER > LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, > ARISING FROM, > OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER > DEALINGS IN > THE SOFTWARE." > > I have no problem with signing this, but I have a problem with signing > a carte blanche. > --Trygve > > > > On 26.09.2014 07:25, stepharo wrote: >> Hi guys >> >> do not forget to sign the license agreement >> http://files.pharo.org/media/PharoSoftwareDistributionAgreement.pdf >> and send us your picture to be added to >> http://pharo.org/about >> >> Stef >> >> >> >> >> > > -- > > Trygve Reenskaug mailto: trygver(a)ifi.uio.no > Morgedalsvn. 5A http://folk.uio.no/trygver/ > N-0378 Oslo http://fullOO.info > Norway Tel: (+47) 22 49 57 27

Sept. 27, 2014

Re: [Pharo-users] Unicode support in Pharo

by Alain Rastoul

Le 27/09/2014 01:02, Sven Van Caekenberghe a Ã©crit : > > On 26 Sep 2014, at 23:22, Alain Rastoul <alf.mmm.cat(a)gmail.com> wrote: > >> Pasting a Greek string in a workspace shows hieroglyphs (editors? morph?), but GT Inspector display is ok. > > That is a font issue. Check your font settings in the Settings Browser. > > Like I mentioned in the chapter, you could try to use 'Arial Unicode MS'. > > I would guess you use Source Code Pro for code panes (like the workspace) and Open Sans for the rest. Source Code Pro has limited Unicode support. GT probably uses only Open Sans. > Ouch, forgot about different font settings for morphic elements, and evident, GTInspector could not display correctly if editor would not deal with WideString (forgot about bytestring/widestring transparency?). BTW I do not have Arial unicode MS on my system, it comes with MS Office, but Deja Vu and Bitmap Deja vu display some Greek chars correctly.

Sept. 27, 2014

Re: [Pharo-users] Unicode support in Pharo

by Sven Van Caekenberghe

On 26 Sep 2014, at 23:22, Alain Rastoul <alf.mmm.cat(a)gmail.com> wrote: > Pasting a Greek string in a workspace shows hieroglyphs (editors? morph?), but GT Inspector display is ok. That is a font issue. Check your font settings in the Settings Browser. Like I mentioned in the chapter, you could try to use 'Arial Unicode MS'. I would guess you use Source Code Pro for code panes (like the workspace) and Open Sans for the rest. Source Code Pro has limited Unicode support. GT probably uses only Open Sans.

Sept. 26, 2014

Re: [Pharo-users] Unicode support in Pharo

by Alain Rastoul

Le 26/09/2014 23:22, Alain Rastoul a Ã©crit : > Le 26/09/2014 20:47, stepharo a Ã©crit : >> I'm not expert and I would like to know what people think. >> But I think that we should consider >> >> - the impact of spur new object format. I would like to have >> unicode and clean the leadChar >> >> Stef >> >> > Just to start a new thread about that, because it deserves it > and also some people might appreciate :) > (was in: "Ridiculous we are"). > > I may not be the most qualified to state on that but I give my 2c > (this is a community isn't it ? please do not flame...) > > As Sven said, the situation is not so bad (quite good in fact): Pharo > has true unicode built-in support with WideString and encoders (great > job, IMHO this part of Zn components should be in the base system > or in an internationalization package not hidden in an htpp components > package). > - encoding support has to be in the system : ZnEncoders(?) for utf8, > unicode and other encoders for locale support because of existing system > basis, web (utf8) and internationalization. > - this will be transparent: Smalltalk is a typeless langage, one do not > have to specify String type (ByteString or WideString) > - Spur new character encoding is very interesting (in alpha stage now) > and will be transparent for the same reason (though I'm still wondering > of the 32bits/64 bits encoding on a 64 bits vm?). > - ByteString is needed for most european/occidental people who don't > care about internationalization and should stay because Pharo is an > european/english based system , also not to break existing code > (again will be transparent to most users for same reason). > - some parts of the system seems to be not "WideString/unicode aware" : > Pasting a Greek string in a workspace shows hieroglyphs (editors? > morph?), but GT Inspector display is ok. > Font plugin seems to require little work : uses fopen instead of _wfopen > (utf16 version) on windows and needs utf8 convertion on unix. > may be a check with File plugin (and other system related plugins) is > also needed? > > In short, some little additionnal work but a very good basis. > (but what is leadChar about?) > > Regards, > > Alain > > > This was not a new thread indeed, I did "respond to group" I am ridiculous ... hahaha :)

Sept. 26, 2014

Unicode support in Pharo

by Alain Rastoul

Le 26/09/2014 20:47, stepharo a Ã©crit : > I'm not expert and I would like to know what people think. > But I think that we should consider > > - the impact of spur new object format. I would like to have > unicode and clean the leadChar > > Stef > > Just to start a new thread about that, because it deserves it and also some people might appreciate :) (was in: "Ridiculous we are"). I may not be the most qualified to state on that but I give my 2c (this is a community isn't it ? please do not flame...) As Sven said, the situation is not so bad (quite good in fact): Pharo has true unicode built-in support with WideString and encoders (great job, IMHO this part of Zn components should be in the base system or in an internationalization package not hidden in an htpp components package). - encoding support has to be in the system : ZnEncoders(?) for utf8, unicode and other encoders for locale support because of existing system basis, web (utf8) and internationalization. - this will be transparent: Smalltalk is a typeless langage, one do not have to specify String type (ByteString or WideString) - Spur new character encoding is very interesting (in alpha stage now) and will be transparent for the same reason (though I'm still wondering of the 32bits/64 bits encoding on a 64 bits vm?). - ByteString is needed for most european/occidental people who don't care about internationalization and should stay because Pharo is an european/english based system , also not to break existing code (again will be transparent to most users for same reason). - some parts of the system seems to be not "WideString/unicode aware" : Pasting a Greek string in a workspace shows hieroglyphs (editors? morph?), but GT Inspector display is ok. Font plugin seems to require little work : uses fopen instead of _wfopen (utf16 version) on windows and needs utf8 convertion on unix. may be a check with File plugin (and other system related plugins) is also needed? In short, some little additionnal work but a very good basis. (but what is leadChar about?) Regards, Alain

Sept. 26, 2014