- Pharo-dev - lists.pharo.org

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

by nicolas petton

Thanks for the suggestion. I don't know yet how it would fit with SmalltalkHub, and how to integrate it, but it could be a nice addition indeed. Cheers, Nico 2011/8/4 Torsten Bergmann <astares(a)gmx.de> > Serge wrote > >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. > > But with one difference: a fork means really forking (the whole) codebase > and this fork is usually available at a different location. > You can (and have to) completely maintain this fork then. This could > be good or bad. The more forks exist the more people can be confused... > > > But an projects "Inbox" would be bound to the project - so project > developers/admins could decide which "inbox" contribution to accept > and integrate into the code base. People who provide good contributions > could later be added as project developers and even when a contribution is > not integrated it is close to the project for others to use. > > Currently we do something similar with Pharo and PharoInbox - but they > are two separate projects in SqS. A default "Inbox" for any project > would IMHO a nice addition. > > Bye > T. > > > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > >

Aug. 4, 2011

[Pharo-project] [ANN] SmalltalkHub demo online

by Torsten Bergmann

Serge wrote >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. But with one difference: a fork means really forking (the whole) codebase and this fork is usually available at a different location. You can (and have to) completely maintain this fork then. This could be good or bad. The more forks exist the more people can be confused... But an projects "Inbox" would be bound to the project - so project developers/admins could decide which "inbox" contribution to accept and integrate into the code base. People who provide good contributions could later be added as project developers and even when a contribution is not integrated it is close to the project for others to use. Currently we do something similar with Pharo and PharoInbox - but they are two separate projects in SqS. A default "Inbox" for any project would IMHO a nice addition. Bye T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

Aug. 4, 2011

[Pharo-project] [update 1.4] #14076

by Marcus Denker

14076 ----- Issue 4596: WeakOrderedColllection array is replaced by an Array instead of a WeakArray (part 2) -- Marcus Denker -- http://marcusdenker.de

Aug. 4, 2011

Re: [Pharo-project] ThreadSafeTranscript

by Pavel Krivanek

Ok, please try to integrate this fix: http://code.google.com/p/pharo/issues/detail?id=4533 -- Pavel On Thu, Aug 4, 2011 at 12:26 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Because we removed the (attempt based on CUIS and fernando) due to too many problem. > ThreadSafeTranscript was not removed we just linked back Transcript to this class. > We did the same with 1.3 > So normally you should have the same problem with 1.3 and 1.4 > > Stef > >> Hi, >> >> why in the latest 1.4 image is ThreadSafeTranscript back? Wasn't it >> replaced by TranscriptModel? It breaks Pharo-Kernel CI job (it doesn't >> report fail but I will fix that). >> >> -- Pavel >> > > >

Aug. 4, 2011

[Pharo-project] [update 1.4] #14075

by Marcus Denker

14075 ----- Issue 4596: WeakOrderedColllection array is replaced by an Array instead of a WeakArray (part 1) -- Marcus Denker -- http://marcusdenker.de

Aug. 4, 2011

Re: [Pharo-project] ThreadSafeTranscript

by StÃ©phane Ducasse

Because we removed the (attempt based on CUIS and fernando) due to too many problem. ThreadSafeTranscript was not removed we just linked back Transcript to this class. We did the same with 1.3 So normally you should have the same problem with 1.3 and 1.4 Stef > Hi, > > why in the latest 1.4 image is ThreadSafeTranscript back? Wasn't it > replaced by TranscriptModel? It breaks Pharo-Kernel CI job (it doesn't > report fail but I will fix that). > > -- Pavel >

Aug. 4, 2011

[Pharo-project] ThreadSafeTranscript

by Pavel Krivanek

Hi, why in the latest 1.4 image is ThreadSafeTranscript back? Wasn't it replaced by TranscriptModel? It breaks Pharo-Kernel CI job (it doesn't report fail but I will fix that). -- Pavel

Aug. 4, 2011

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