Re: [Pharo-dev] [squeak-dev] Unicode Support

2015-12-06 Thread Sven Van Caekenberghe
Well written, Todd. I agree, the loss of indexing might not be that big a problem in practice. The only way to find out it to try an experiment I guess. Sven > On 06 Dec 2015, at 17:37, Todd Blanchard wrote: > > (Resent because of bounce notification (email handling in osx

Re: [Pharo-dev] [Help needed] final push for Rubric editor

2015-12-06 Thread Alain Plantec via Pharo-dev
--- Begin Message --- > On 06 Dec 2015, at 17:07, Nicolai Hess wrote: > > in: > > 17192 > > UITheme should not use PluggableTextMorph > > what should we use to replace

Re: [Pharo-dev] Unicode Support

2015-12-06 Thread Sven Van Caekenberghe
> On 05 Dec 2015, at 17:35, Todd Blanchard wrote: > > would suggest that the only worthwhile encoding is UTF8 - the rest are > distractions except for being able to read and convert from other encodings > to UTF8. UTF16 is a complete waste of time. > > Read

[Pharo-dev] model vs interactionModel in rubric

2015-12-06 Thread Andrei Chis
Hi, RubScrolledTextModel fails sometimes if the model does not have an interaction model set. For example in a few places there is a check that verifies if the model understands a message and then the message is send to the interaction model. evaluate: aStream andDo: aBlock (self model

Re: [Pharo-dev] [Help needed] final push for Rubric editor

2015-12-06 Thread Nicolai Hess
in: 17192 UITheme should not use PluggableTextMorph what should we use to replace PluggableTextMorph, RubPluggableTextMorph or RubScrolledTextMorph ? I think RubPluggableTextMorph, because we need a way to adapt

Re: [Pharo-dev] [squeak-dev] Unicode Support

2015-12-06 Thread Todd Blanchard
(Resent because of bounce notification (email handling in osx is really beginning to annoy me). Sorry if its a dup) I used to worry a lot about strings being indexable. And then I eventually let go of that and realized that it isn't a particularly important property for them to have. I

Re: [Pharo-dev] issue 12231 DisplayScreen hostWindowTitle: not working on Linux (ubuntu)

2015-12-06 Thread stepharo
What everybody should understand is that context switch is difficult and cost a lot of energy. So making clear what is the next step for an action is really important. It helps people to follow. Stef Le 6/12/15 06:05, Ben Coman a écrit : On Sat, Dec 5, 2015 at 7:40 PM, kmo

[Pharo-dev] Debian 8 Jessie ia32-libs is not available

2015-12-06 Thread Ben Coman
Installation instructions [1] for Debian 8 Jessie 64-bits currently says... sudo dpkg --add-architecture i386 sudo apt-get update sudo apt-get install ia32-libs sudo apt-get install libx11-6:386 sudo apt-get install libgl1-mesa-glx:i386 sudo apt-get install libfontconfig1:i386 sudo

Re: [Pharo-dev] issue 12231 DisplayScreen hostWindowTitle: not working on Linux (ubuntu)

2015-12-06 Thread kmo
Very interesting idea, bug bankruptcy. We certainly suffer from it where I work. As for the bug, I'd just like to thank Nicolai for taking the time to investigate it and work out a fix. -- View this message in context:

[Pharo-dev] context menu keyboard key

2015-12-06 Thread Peter Uhnak
Hi, is there a way to open context menu without using mouse/right click? Keyboards generally have a special key for this, but Pharo doesn't seem to even recognize the keypress. To anyone familiar with this, can this be fixed in image? Or digging into VM is needed? Thanks, -- Peter

Re: [Pharo-dev] context menu keyboard key

2015-12-06 Thread Nicolai Hess
2015-12-06 12:40 GMT+01:00 Nicolai Hess : > > > 2015-12-06 12:37 GMT+01:00 Peter Uhnak : > >> Hi, >> >> is there a way to open context menu without using mouse/right click? >> >> Keyboards generally have a special key for this, but Pharo doesn't seem >>

Re: [Pharo-dev] context menu keyboard key

2015-12-06 Thread Nicolai Hess
2015-12-06 12:37 GMT+01:00 Peter Uhnak : > Hi, > > is there a way to open context menu without using mouse/right click? > > Keyboards generally have a special key for this, but Pharo doesn't seem > to even recognize the keypress. > some time ago, esc-key was used for that. >

Re: [Pharo-dev] model vs interactionModel in rubric

2015-12-06 Thread Nicolai Hess
2015-12-06 15:28 GMT+01:00 Andrei Chis : > Hi, > > RubScrolledTextModel fails sometimes if the model does not have an > interaction model set. > For example in a few places there is a check that verifies if the model > understands a message and then the message is send

Re: [Pharo-dev] Unicode Support

2015-12-06 Thread EuanM
Thanks for those pointers, Steph. I'll make sure they are on my reading list. (I have a limited weekly time-budget for Unicode work, but I expect this is a long-term project). I'll keep in touch with Steph, so any new facilities can be immediately useful to Pharo, and someone can guide them to

Re: [Pharo-dev] Unicode Support

2015-12-06 Thread EuanM
Todd, As long as others are using it, it's useful to be able to send UTF16, and to successfully import it. I like systems that play well with others. :-) On 5 December 2015 at 16:35, Todd Blanchard wrote: > would suggest that the only worthwhile encoding is UTF8 - the rest

Re: [Pharo-dev] Unicode Support

2015-12-06 Thread EuanM
Steph - I'll dig out the Fr phone book ordering from wherever it was I read about it! I thought I ghad it to hand, but I haven;t found it tonight. It can't be far away. On 5 December 2015 at 13:08, stepharo wrote: > Hi EuanM > > Le 4/12/15 12:42, EuanM a écrit : >> >> I'm

Re: [Pharo-dev] Unicode Support

2015-12-06 Thread Max Leske
> On 06 Dec 2015, at 18:44, Sven Van Caekenberghe wrote: > > >> On 05 Dec 2015, at 17:35, Todd Blanchard wrote: >> >> would suggest that the only worthwhile encoding is UTF8 - the rest are >> distractions except for being able to read and convert from other

Re: [Pharo-dev] [squeak-dev] Unicode Support

2015-12-06 Thread Sven Van Caekenberghe
Ah yes, Go is a good example, thanks Mark. After reading these two blog articles: http://blog.golang.org/strings http://blog.golang.org/normalization And especially after looking through their libraries/APIs, the conclusion is: this is not simple. I am also not so sure they managed to offer

[Pharo-dev] displayingProgress on demand

2015-12-06 Thread Hernán Morales Durand
Hello everyone, Is there a reason why #collect:displayingProgress: was removed or never included? And as more general question, is there any pointer to automatically add progress bar to iterator messages? For example doing: SmalltalkImage setDisplayProgressTo: MyClass. SmalltalkImage

[Pharo-dev] [OT] Microsoft JavaScript engine goes open source

2015-12-06 Thread Torsten Bergmann
https://blogs.windows.com/msedgedev/2015/12/05/open-source-chakra-core/

Re: [Pharo-dev] [squeak-dev] Unicode Support

2015-12-06 Thread Sven Van Caekenberghe
BTW, does anyone know of any programming language that did go that way or has a library that directly implements 'storing all strings as utf-8' ? > On 06 Dec 2015, at 18:45, Sven Van Caekenberghe wrote: > > Well written, Todd. I agree, the loss of indexing might not be that big a

Re: [Pharo-dev] displayingProgress on demand

2015-12-06 Thread Sven Van Caekenberghe
There is still #do:displayingProgress: There is Job. In general, the collection API should not be concerned with GUI matters, does it ? We can't have equivalents of all collection methods for displaying progress, nor can it be a (semi-) global setting. If you look at how HTTPProgress is

Re: [Pharo-dev] [squeak-dev] Unicode Support

2015-12-06 Thread Mark Bestley
On 06/12/2015 19:08, Sven Van Caekenberghe wrote: BTW, does anyone know of any programming language that did go that way or has a library that directly implements 'storing all strings as utf-8' ? Java is UTF-16 Python3, Go and Swift are UTF-8 as I suspect are other new languages not based on

[Pharo-dev] textColor: overrides the color attribute of the Text object

2015-12-06 Thread Andrei Chis
Hi, Consider the following two code snippet below: [1] (RubScrolledTextMorph new textColor: Smalltalk ui theme textColor; setText: (Text string: 'a b c' attributes: {TextColor green}); yourself) openInWorld. [2] (RubScrolledTextMorph new setText: (Text string: 'a b c' attributes: {TextColor

Re: [Pharo-dev] displayingProgress on demand

2015-12-06 Thread stepharo
Probably because it was badly done. Le 6/12/15 20:05, Hernán Morales Durand a écrit : Hello everyone, Is there a reason why #collect:displayingProgress: was removed or never included? And as more general question, is there any pointer to automatically add progress bar to iterator

Re: [Pharo-dev] [squeak-dev] Unicode Support

2015-12-06 Thread Gabriel Cotelli
As far as I know Dart also uses utf-16 for Strings On Dec 6, 2015 16:33, "Mark Bestley" wrote: > On 06/12/2015 19:08, Sven Van Caekenberghe wrote: > >> BTW, does anyone know of any programming language that did go that way or >> has a library that directly implements 'storing