August 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] The shiftEnclose: horror show

by StÃ©phane Ducasse

What is on our todo is to introduce keymapper or another solution to have no hardcoded keys in the complete system. Now my time is short... sadly. But indeed this is good if we can clean that part. Stef > http://code.google.com/p/pharo/issues/detail?id=4599 > > 2011/8/4 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >> I'm typing this message on a mac French keyboard. >> That means I can obtain the holy brackets [ | ] only through weird >> keystroke combinations >> | = shit+option+L >> [ = shift+option+( where shift+5 is ( >> >> Enclosing a text in square brackets would require some finger torture >> both in Squeak/Pharo >> shift+option+command+( >> But this does not work because of #shiftEnclose: rules encountered in >> #initializeShiftCmdKeyShortcuts >> (found both ParagraphEditor class and TextEditor class) >> >> "Note: Command key overrides shift key, so, for example, cmd-shift-9 >> produces $9 not $(" >> '9[,''' do: [ :char | cmdMap at: (char asciiValue + 1) put: >> #shiftEnclose: ]. "({< and double-quote" >> "Note: Must use cmd-9 or ctrl-9 to get '()' since cmd-shift-9 is a >> Mac FKey command." >> >> shiftEnclose: is badly designed because it does hardcode the keyboard >> layout (see below). >> This is not compatible with modern VMs, at least the mac ones, because >> they deliver a unicode codePoint for $[ or $|, not a raw keycode. >> It's easy to remove this anachronism and correct the mapping: >> >> "On some keyboards, these characters require a shift" >> '([<{|"''' do: [:char | cmdMap at: char asciiValue + 1 put: #enclose:]. >> >> To avoid pushing a mac-centric change in trunk, I need to know if the >> Linux/Windows VM would support above modification. >> Can anyone check for me ? >> >> Nicolas >> >> >> >> >> >> Example of hardcoded keyboard layout: >> TextEditor>>shiftEnclose: aKeyboardEvent >> "Insert or remove bracket characters around the current selection. >> Flushes typeahead." >> >> | char left right startIndex stopIndex oldSelection which text | >> char := aKeyboardEvent keyCharacter. >> char = $9 ifTrue: [ char := $( ]. >> char = $, ifTrue: [ char := $< ]. >> char = $[ ifTrue: [ char := ${ ]. >> char = $' ifTrue: [ char := $" ]. >> char asciiValue = 27 ifTrue: [ char := ${ ]. "ctrl-[" >> snip... >> >

Aug. 4, 2011

Re: [Pharo-project] [ANN] SmalltalkHub demo online

by Serge Stinckwich

Very similar to forks in github: if you have no access to a project or the project seems stalled, you fork the project ans apply your own patches. On Thu, Aug 4, 2011 at 1:25 PM, Torsten Bergmann <astares(a)gmx.de> wrote: >>Request: please include a way to store contributions from the public (like >>maybe per-project inboxes). >>Motivation: With SqS, it seems great fixes and enhancements often get lost >>on old hard drives or the mailing list because the authors don't have write >>access to the repo, and it's often hard to contact the admins. >>Result: every contribution will be preserved and easily findable from the >>project's repo, while admins maintain control over their codebase if >>desired. > > Great idead! > +1000 > > Bye > T. > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

Aug. 4, 2011

Re: [Pharo-project] The shiftEnclose: horror show

by Nicolas Cellier

http://code.google.com/p/pharo/issues/detail?id=4599 2011/8/4 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > I'm typing this message on a mac French keyboard. > That means I can obtain the holy brackets [ | ] only through weird > keystroke combinations > | = shit+option+L > [ = shift+option+( where shift+5 is ( > > Enclosing a text in square brackets would require some finger torture > both in Squeak/Pharo > shift+option+command+( > But this does not work because of #shiftEnclose: rules encountered in > #initializeShiftCmdKeyShortcuts > (found both ParagraphEditor class and TextEditor class) > > Â Â Â Â "Note: Command key overrides shift key, so, for example, cmd-shift-9 > produces $9 not $(" > Â Â Â Â '9[,''' do: [ :char | cmdMap at: (char asciiValue + 1) put: > #shiftEnclose: ]. Â Â Â "({< and double-quote" > Â Â Â Â "Note: Must use cmd-9 or ctrl-9 to get '()' since cmd-shift-9 is a > Mac FKey command." > > shiftEnclose: is badly designed because it does hardcode the keyboard > layout (see below). > This is not compatible with modern VMs, at least the mac ones, because > they deliver a unicode codePoint for $[ or $|, not a raw keycode. > It's easy to remove this anachronism and correct the mapping: > > Â Â Â Â "On some keyboards, these characters require a shift" > Â Â Â Â '([<{|"''' do: [:char | cmdMap at: char asciiValue + 1 put: #enclose:]. > > To avoid pushing a mac-centric change in trunk, I need to know if the > Linux/Windows VM would support above modification. > Can anyone check for me ? > > Nicolas > > > > > > Example of hardcoded keyboard layout: > TextEditor>>shiftEnclose: aKeyboardEvent > Â Â Â Â "Insert or remove bracket characters around the current selection. > Â Â Â Â Flushes typeahead." > > Â Â Â Â | char left right startIndex stopIndex oldSelection which text | > Â Â Â Â char := aKeyboardEvent keyCharacter. > Â Â Â Â char = $9 ifTrue: [ char := $( ]. > Â Â Â Â char = $, ifTrue: [ char := $< ]. > Â Â Â Â char = $[ ifTrue: [ char := ${ ]. > Â Â Â Â char = $' ifTrue: [ char := $" ]. > Â Â Â Â char asciiValue = 27 ifTrue: [ char := ${ ]. Â Â "ctrl-[" > snip... >

Aug. 4, 2011

Re: [Pharo-project] How to deprecate a Class?

by Nicolas Cellier

Why not make this class a factory in the interim ? DeprecatedClass class>>new self deprecated: 'DeprecatedClass use BrandNewClass instead'. ^BrandNewClass new 2011/8/4 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > On Thu, Aug 4, 2011 at 1:42 AM, Chris Cunningham <cunningham.cb(a)gmail.com> > wrote: >> >> On Mon, Aug 1, 2011 at 12:21 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >> > The most important aspects is that there is not reference to it. >> > and that if we replace it by something else, it works. >> > After we can write in the comments in big that the class is deprecated. >> > >> >> Could you (we) also deprecate all the methods in the class? Â Ideally >> in some automated way, of course. >> > > Or remove all methods and implement > > doesNotUnderstand: > > Â Â Â ^Error new signal: 'All mehtods of this class are deprecated, please use > ....' > > > hehhehehÂ :) > > > > -- > Mariano > http://marianopeck.wordpress.com > >

Aug. 4, 2011

[Pharo-project] The shiftEnclose: horror show

by Nicolas Cellier

I'm typing this message on a mac French keyboard. That means I can obtain the holy brackets [ | ] only through weird keystroke combinations | = shit+option+L [ = shift+option+( where shift+5 is ( Enclosing a text in square brackets would require some finger torture both in Squeak/Pharo shift+option+command+( But this does not work because of #shiftEnclose: rules encountered in #initializeShiftCmdKeyShortcuts (found both ParagraphEditor class and TextEditor class) "Note: Command key overrides shift key, so, for example, cmd-shift-9 produces $9 not $(" '9[,''' do: [ :char | cmdMap at: (char asciiValue + 1) put: #shiftEnclose: ]. "({< and double-quote" "Note: Must use cmd-9 or ctrl-9 to get '()' since cmd-shift-9 is a Mac FKey command." shiftEnclose: is badly designed because it does hardcode the keyboard layout (see below). This is not compatible with modern VMs, at least the mac ones, because they deliver a unicode codePoint for $[ or $|, not a raw keycode. It's easy to remove this anachronism and correct the mapping: "On some keyboards, these characters require a shift" '([<{|"''' do: [:char | cmdMap at: char asciiValue + 1 put: #enclose:]. To avoid pushing a mac-centric change in trunk, I need to know if the Linux/Windows VM would support above modification. Can anyone check for me ? Nicolas Example of hardcoded keyboard layout: TextEditor>>shiftEnclose: aKeyboardEvent "Insert or remove bracket characters around the current selection. Flushes typeahead." | char left right startIndex stopIndex oldSelection which text | char := aKeyboardEvent keyCharacter. char = $9 ifTrue: [ char := $( ]. char = $, ifTrue: [ char := $< ]. char = $[ ifTrue: [ char := ${ ]. char = $' ifTrue: [ char := $" ]. char asciiValue = 27 ifTrue: [ char := ${ ]. "ctrl-[" snip...

Aug. 4, 2011

Re: [Pharo-project] How to deprecate a Class?

by Mariano Martinez Peck

On Thu, Aug 4, 2011 at 1:42 AM, Chris Cunningham <cunningham.cb(a)gmail.com>wrote: > On Mon, Aug 1, 2011 at 12:21 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > > The most important aspects is that there is not reference to it. > > and that if we replace it by something else, it works. > > After we can write in the comments in big that the class is deprecated. > > > > Could you (we) also deprecate all the methods in the class? Ideally > in some automated way, of course. > > Or remove all methods and implement doesNotUnderstand: ^Error new signal: 'All mehtods of this class are deprecated, please use ....' hehheheh :) -- Mariano http://marianopeck.wordpress.com

Aug. 4, 2011

Re: [Pharo-project] Polymorph improvements

by Lorenzo Schiavina

Hi Gary, I have seen from your screenshots that you are working on OCR projecr; can you give my some information about it? Thanks Lorenzo ----- Original Message ----- From: Gary Chambers To: Pharo-project(a)lists.gforge.inria.fr Sent: Tuesday, August 02, 2011 5:51 PM Subject: Re: [Pharo-project] Polymorph improvements Screenshot of part of project: http://www.flickr.com/photos/12018791@N06/6001799235/in/photostream Regards, Gary ----- Original Message ----- From: Gary Chambers To: Pharo Development Sent: Tuesday, August 02, 2011 4:40 PM Subject: [Pharo-project] Polymorph improvements Hi all. I've added an issue with some tweaks/improvements to a few Polymorph classes. http://code.google.com/p/pharo/issues/detail?id=4590 Groupboxes can now have dynamic content (model/getContentSelector based). Abaility to create icon lists via builder/TEasilyThemed. Expander labels now LabelMorphs rather than TextMorphs (can therefore appear as disabled) IncrementalSliderMorphs now honour minWidth/minHeight in layouts Panel morphs allow event based mouse over handling (call to super was missing). Label groups allow for nil labels (equates to empty string) Regards, Gary

Aug. 4, 2011

Re: [Pharo-project] [Pharo-users] [PBE-Spanish] Status update 2011-08-03

by StÃ©phane Ducasse

version. :) Stef On Aug 4, 2011, at 12:24 AM, NicolÃ¡s Paez wrote: > Hello everyone, > > Finally we were able to fix the some of the errors in PDF generation and now, all the 14 chapters are published in PDF format :-) > > You can download them from PharoByExample page. > Direct link: https://gforge.inria.fr/frs/download.php/28829/PBE1-Spanish-FullDraft-2011-… > > At the same time, some new volunteers joined the project to collaborate in the revision. > > Saludos! > Nico. > blog: nicopaez.wordpress.com

Aug. 4, 2011

Re: [Pharo-project] [Pharo-users] [PBE-Spanish] Status update 2011-08-03

by StÃ©phane Ducasse

Thanks a lot nicolas When do you plan to have the final draft? Stef On Aug 4, 2011, at 12:24 AM, NicolÃ¡s Paez wrote: > Hello everyone, > > Finally we were able to fix the some of the errors in PDF generation and now, all the 14 chapters are published in PDF format :-) > > You can download them from PharoByExample page. > Direct link: https://gforge.inria.fr/frs/download.php/28829/PBE1-Spanish-FullDraft-2011-… > > At the same time, some new volunteers joined the project to collaborate in the revision. > > Saludos! > Nico. > blog: nicopaez.wordpress.com

Aug. 4, 2011

[Pharo-project] [update 1.4] #14074

by Marcus Denker

14074 ----- Issue 4565: Monticello workflow broken http://code.google.com/p/pharo/issues/detail?id=4565 Issue 4597: StrikeFont aggressive cleanup should remove DejaVu source http://code.google.com/p/pharo/issues/detail?id=4597 -- Marcus Denker -- http://marcusdenker.de

Aug. 4, 2011