- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Shortcuts are broken under Windows

by Blondeau Vincent

De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Nicolai Hess EnvoyÃ© : mercredi 17 fÃ©vrier 2016 20:48 Ã : Pharo Development List Objet : Re: [Pharo-dev] Shortcuts are broken under Windows 2016-02-17 18:33 GMT+01:00 Blondeau Vincent <vincent.blondeau(a)worldline.com<mailto:vincent.blondeau@worldline.com>>: Hi, Due to recent changes on shortcuts, on the new image several shortcuts (CTRL+V,Z,M,W,Enter and the Alt ones) are not active at least in the debugger and in the senders listâ¦ ctrl+v ctrl+z ctrl+w are working for me ctrl+m does not work, this is known what "the Alt ones" do you mean? The same with alt: it was possible to use the shortcuts with alt and ctrl. Alt+V is the same as Ctrl +V. Now both donât workâ¦ in the sender and implementers list, and in the GTdebugger. Edit: I updated the VM to 20160203. Excepted the CTRL+M, everything seems to work again. Thanks Nicolai Vincent I would like to fix this but I donât know what changedâ¦ How do I change the configuration? Is it in <keymap> pragmated methods? Or it is another bug? Cheers, Vincent ________________________________ Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. ________________________________ Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Feb. 18, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50587 Home: https://github.com/pharo-project/pharo-core

Feb. 18, 2016

[pharo-project/pharo-core] 63177d: 50587

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 63177d4fbedbd3b765f7f9126c77498309fa4bf8 https://github.com/pharo-project/pharo-core/commit/63177d4fbedbd3b765f7f912… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-02-18 (Thu, 18 Feb 2016) Changed paths: M ConfigurationOfGTDebugger.package/ConfigurationOfGTDebugger.class/instance/symbolic versions/stable_.st A ConfigurationOfGTDebugger.package/ConfigurationOfGTDebugger.class/instance/versions/version17_.st M GT-Debugger.package/GTMoldableDebugger.class/class/accessing/spanNewSessionFrom_.st M Kernel-Tests.package/CompiledMethodTest.class/instance/tests - accessing/testSelector.st M NautilusRefactoring.package/extension/RBAddMethodChange/instance/oldVersionTextToDisplay.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50586.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50587.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50586.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50587.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50587 17602 duplicated UI processes while running tests from Nautilus https://pharo.fogbugz.com/f/cases/17602 17630 CompiledMethodTest >> #testSelector asks for Author when run https://pharo.fogbugz.com/f/cases/17630 17599 Refectory change method added diff does not take into account class side methods https://pharo.fogbugz.com/f/cases/17599 http://files.pharo.org/image/50/50587.zip

Feb. 18, 2016

[ANN] Pharo Sprint 26 Feb

by Marcus Denker

We will organize a Pharo sprint / Moose dojo Friday, 26 Feb, starting at 10:00am. (Local Time Lille). It will be at the Inria Lille, Building B, third floor (RMoD offices). Remotely, you can join us on Slack or the IRC channel #pharo on irc.freenode.net <http://irc.freenode.net/> server. During the sprint, we will try to synchronize local and remote Pharo sprinters. As the building is not open to the public, please contact us before if you plan to come.

Feb. 18, 2016

Re: [Pharo-dev] [ANN] The Pharo Unicode Project

by Sven Van Caekenberghe

> On 18 Feb 2016, at 06:30, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > >> On Feb 18, 2016, at 2:05 AM, Ben Coman <btc(a)openInWorld.com> wrote: >> >> On Wed, Feb 17, 2016 at 5:16 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> ... >> >>> We also added an extension to our environmentâs search system to allow you to look up characters by name: >> >> Is there a #unicode filter for Spotter? > > Any category can be used as a filter. So, if the category is called #'Unicode Characterâ, you can use #unicode as a filter. Ah, I love it when you get things for free ! > Cheers, > Doru > > -- > www.tudorgirba.com > www.feenk.com > > "We cannot reach the flow of things unless we let go." > > > > >

Feb. 18, 2016

Re: [Pharo-dev] [ANN] The Pharo Unicode Project

by Tudor Girba

Hi, > On Feb 18, 2016, at 2:05 AM, Ben Coman <btc(a)openInWorld.com> wrote: > > On Wed, Feb 17, 2016 at 5:16 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> ... > >> We also added an extension to our environmentâs search system to allow you to look up characters by name: > > Is there a #unicode filter for Spotter? Any category can be used as a filter. So, if the category is called #'Unicode Characterâ, you can use #unicode as a filter. Cheers, Doru -- www.tudorgirba.com www.feenk.com "We cannot reach the flow of things unless we let go."

Feb. 18, 2016

Re: [Pharo-dev] [ANN] The Pharo Unicode Project

by Tudor Girba

Thank you very much! This is an important project. It would be great if others would join you. Cheers, Doru > On Feb 17, 2016, at 10:16 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > In Pharo we can deal with and represent any Unicode character and string, but there are still some important pieces of functionality missing. > > The goal of the Pharo Unicode project is to gradually improve and expand Unicode support in Pharo. We started in December last year to lay the foundation and are now ready to go public with what we built. > > The first delivery is an implementation of Unicode Normalization, together with an implementation of the Unicode Character Database. > > Please read the following article for more information (the appendix explains how to get the code). > > An Implementation of Unicode Normalisation > > Streaming NFC, NFD, NFKC & NFKD, normalization QC and normalization preserving concatenation. > > https://medium.com/concerning-pharo/an-implementation-of-unicode-normalizat… > > The development branch also contains a work in progress implementation of Unicode Collation. > > Much work remains to be done and contributions are more than welcome. > > Sven & Henrik -- www.tudorgirba.com www.feenk.com "Beauty is where we see it."

Feb. 18, 2016

Re: [Pharo-dev] [ANN] The Pharo Unicode Project

by Ben Coman

On Wed, Feb 17, 2016 at 5:16 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > In Pharo we can deal with and represent any Unicode character and string, but there are still some important pieces of functionality missing. > > The goal of the Pharo Unicode project is to gradually improve and expand Unicode support in Pharo. We started in December last year to lay the foundation and are now ready to go public with what we built. > > The first delivery is an implementation of Unicode Normalization, together with an implementation of the Unicode Character Database. > > Please read the following article for more information (the appendix explains how to get the code). > > An Implementation of Unicode Normalisation > > Streaming NFC, NFD, NFKC & NFKD, normalization QC and normalization preserving concatenation. > > https://medium.com/concerning-pharo/an-implementation-of-unicode-normalizat… > > The development branch also contains a work in progress implementation of Unicode Collation. > > Much work remains to be done and contributions are more than welcome. > > Sven & Henrik This is really great. Thanks Sven & Henrik. > The right pane shows a large glyph view of the character involved. This is very cool !! Does it rely on font support, or is it bitmap or SVG based? Maybe it could dynamically download SVG data as needed from somewhere like here... http://www.fileformat.info/info/unicode/char/00f6/index.htm > We also added an extension to our environmentâs search system to allow you to look up characters by name: Is there a #unicode filter for Spotter? check repeated phrase... > and replace it with and replace it with I bumped into an interesting "Good, Bad, Ugly" comparison of Unicode support in other programming languages (though circa 2011) https://www.azabani.com/pages/gbu/ and this sparked a thought to wonder if the consortium would consider it worthwhile paying someone external (like that author) with broad cross platform Unicode experience to consult on getting Pharo to a pragmatic point where we look attractive in such comparisons, which may also provide a side-channel advertisement for Pharo when such comparisons are presented at conferences (??) cheers -ben

Feb. 18, 2016

Re: [Pharo-dev] [ANN] The Pharo Unicode Project

by Henrik Sperre Johansen

Because, who doesn't want to spend an evening with a workspace like this: http://pastebin.com/gdxCrTgM trying to figure out why some of the last 7 out of 189k official collate tests fail? Seriously though, personally I was just tired of having to answer "Sort of, but not really" every time the question of Unicode support is raised, specifically the last discussion that lead nowhere back in December. Better to show in code how you think a decent implementation might look like, and Sven made it easier to get rolling when he wrote import code for many of the data tables needed, parsing text is one of the things I dislike most... Cheers, Henry P.S. Unicode Collation is more of an intellectual exercise. For practical collation you need the locale tailorings from CLDR, which is kept in a, frankly, abominable format. The object model / actual collate algorithms should carry over nicely though, so it's not a complete waste. On Wed, Feb 17, 2016 at 7:56 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > I read the whole Article, seems like a tricky, to not say hard, > subject. The article is very detailed and well written though. > > What is the rationale behind embracing such a challenging feature like > supporting Unicode? > > Regards! > > > Esteban A. Maringolo > > > 2016-02-17 15:24 GMT-03:00 Max Leske <maxleske(a)gmail.com>: > > Good stuff guys! > > > >> On 17 Feb 2016, at 10:16, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> > >> Hi, > >> > >> In Pharo we can deal with and represent any Unicode character and > string, but there are still some important pieces of functionality missing. > >> > >> The goal of the Pharo Unicode project is to gradually improve and > expand Unicode support in Pharo. We started in December last year to lay > the foundation and are now ready to go public with what we built. > >> > >> The first delivery is an implementation of Unicode Normalization, > together with an implementation of the Unicode Character Database. > >> > >> Please read the following article for more information (the appendix > explains how to get the code). > >> > >> An Implementation of Unicode Normalisation > >> > >> Streaming NFC, NFD, NFKC & NFKD, normalization QC and normalization > preserving concatenation. > >> > >> > https://medium.com/concerning-pharo/an-implementation-of-unicode-normalizat… > >> > >> The development branch also contains a work in progress implementation > of Unicode Collation. > >> > >> Much work remains to be done and contributions are more than welcome. > >> > >> Sven & Henrik > > > > > >

Feb. 18, 2016

Re: [Pharo-dev] [ANN] The Pharo Unicode Project

by Sven Van Caekenberghe

> On 17 Feb 2016, at 19:56, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > > I read the whole Article, seems like a tricky, to not say hard, subject. Yes. The Unicode specs are big and complex. Step one is to read & understand them, at least well enough to find your way. Doing some implementation is not too hard, but getting 100% scores on the very extensive test suites was/is quite hard. > The article is very detailed and well written though. Thx. > What is the rationale behind embracing such a challenging feature like supporting Unicode? Unicode is the de facto standard for internationalisation of computer software. Any serious platform has to tackle (big parts of) Unicode. > Regards! > > > Esteban A. Maringolo > > > 2016-02-17 15:24 GMT-03:00 Max Leske <maxleske(a)gmail.com>: >> Good stuff guys! >> >>> On 17 Feb 2016, at 10:16, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> Hi, >>> >>> In Pharo we can deal with and represent any Unicode character and string, but there are still some important pieces of functionality missing. >>> >>> The goal of the Pharo Unicode project is to gradually improve and expand Unicode support in Pharo. We started in December last year to lay the foundation and are now ready to go public with what we built. >>> >>> The first delivery is an implementation of Unicode Normalization, together with an implementation of the Unicode Character Database. >>> >>> Please read the following article for more information (the appendix explains how to get the code). >>> >>> An Implementation of Unicode Normalisation >>> >>> Streaming NFC, NFD, NFKC & NFKD, normalization QC and normalization preserving concatenation. >>> >>> https://medium.com/concerning-pharo/an-implementation-of-unicode-normalizat… >>> >>> The development branch also contains a work in progress implementation of Unicode Collation. >>> >>> Much work remains to be done and contributions are more than welcome. >>> >>> Sven & Henrik >> >> >

Feb. 17, 2016