April 2016 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

April 17, 2016

[pharo-project/pharo-core] 272265: 50697

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 272265df3226759c797bcf338772ec8254835fd7 https://github.com/pharo-project/pharo-core/commit/272265df3226759c797bcf33… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-04-17 (Sun, 17 Apr 2016) Changed paths: A Morphic-Widgets-Taskbar.package/TShowInTaskbar.class/README.md A Morphic-Widgets-Taskbar.package/TShowInTaskbar.class/definition.st A Morphic-Widgets-Taskbar.package/TShowInTaskbar.class/instance/taskbar-private/customizeTaskbarButton_.st A Morphic-Widgets-Taskbar.package/TShowInTaskbar.class/instance/taskbar-private/taskbarButtonFor_.st A Morphic-Widgets-Taskbar.package/TShowInTaskbar.class/instance/taskbar-private/taskbarTask.st A Morphic-Widgets-Taskbar.package/TShowInTaskbar.class/instance/taskbar-public/taskbarButtonClicked.st A Morphic-Widgets-Taskbar.package/TShowInTaskbar.class/instance/taskbar-public/taskbarButtonMenu_.st A Morphic-Widgets-Taskbar.package/TShowInTaskbar.class/instance/taskbar-public/taskbarIcon.st A Morphic-Widgets-Taskbar.package/TShowInTaskbar.class/instance/taskbar-required/taskbarButtonIsActive.st A Morphic-Widgets-Taskbar.package/TShowInTaskbar.class/instance/taskbar-required/taskbarLabel.st A Morphic-Widgets-Taskbar.package/TShowInTaskbar.class/instance/taskbar-required/taskbarState.st A Morphic-Widgets-Taskbar.package/TShowInTaskbar.class/instance/taskbar-thumbnail/taskbarButtonEntered_event_in_.st A Morphic-Widgets-Taskbar.package/TShowInTaskbar.class/instance/taskbar-thumbnail/taskbarButtonLeft_event_in_.st A Morphic-Widgets-Taskbar.package/TShowInTaskbar.class/instance/taskbar-thumbnail/taskbarCanShowThumbnail.st A Morphic-Widgets-Taskbar.package/extension/UITheme/instance/newBasicTaskbarButtonIn_for_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50696.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50697.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50696.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50697.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50697 17905 TaskbarMorph should not kill an image when not all required methods are implemented https://pharo.fogbugz.com/f/cases/17905 http://files.pharo.org/image/50/50697.zip

April 17, 2016

[pharo-project/pharo-core]

by GitHub

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

April 17, 2016

[pharo-project/pharo-core] 400241: 50696

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 4002410504da6c134335dbc4e18d58d74111c51c https://github.com/pharo-project/pharo-core/commit/4002410504da6c134335dbc4… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-04-17 (Sun, 17 Apr 2016) Changed paths: M ConfigurationOfSton.package/ConfigurationOfSton.class/README.md M ConfigurationOfSton.package/ConfigurationOfSton.class/instance/symbolic versions/stable_.st A ConfigurationOfSton.package/ConfigurationOfSton.class/instance/versions/version18_.st M STON-Core.package/STON.class/README.md M STON-Core.package/STON.class/class/accessing/jsonWriter.st A STON-Core.package/STONJSON.class/README.md A STON-Core.package/STONJSON.class/class/convenience/fromStream_.st A STON-Core.package/STONJSON.class/class/convenience/fromString_.st A STON-Core.package/STONJSON.class/class/convenience/put_onStreamPretty_.st A STON-Core.package/STONJSON.class/class/convenience/put_onStream_.st A STON-Core.package/STONJSON.class/class/convenience/toStringPretty_.st A STON-Core.package/STONJSON.class/class/convenience/toString_.st A STON-Core.package/STONJSON.class/definition.st M STON-Core.package/STONReader.class/definition.st M STON-Core.package/STONReader.class/instance/initialize-release/initialize.st M STON-Core.package/STONReader.class/instance/initialize-release/optimizeForLargeStructures.st R STON-Core.package/STONReader.class/instance/parsing-internal/parseCharacterHex.st A STON-Core.package/STONReader.class/instance/private/parseCharacterHex.st A STON-Core.package/STONReader.class/instance/private/parseCharacterHex4Value.st A STON-Core.package/STONReader.class/instance/private/parseTrailingSurrogateHexEscape.st M STON-Core.package/STONReader.class/instance/private/processSubObjectsOf_.st M STON-Core.package/STONReader.class/instance/private/resolveReference_.st M STON-Core.package/STONReader.class/instance/public/next.st M STON-Core.package/STONWriter.class/README.md M STON-Core.package/STONWriter.class/instance/private/encodeCharacter_.st A STON-Core.package/STONWriter.class/instance/private/escapeUnicode4_.st A STON-Core.package/STONWriter.class/instance/private/escapeUnicode_.st A STON-Core.package/extension/Dictionary/instance/stonPostReferenceResolution.st A STON-Core.package/extension/Interval/class/fromSton_.st A STON-Core.package/extension/Interval/instance/fromSton_.st A STON-Core.package/extension/Interval/instance/stonOn_.st A STON-Core.package/extension/Object/instance/stonPostReferenceResolution.st A STON-Core.package/extension/Set/instance/stonPostReferenceResolution.st A STON-Tests.package/STONJSONTests.class/README.md A STON-Tests.package/STONJSONTests.class/definition.st A STON-Tests.package/STONJSONTests.class/instance/tests/testBooleans.st A STON-Tests.package/STONJSONTests.class/instance/tests/testCircular.st A STON-Tests.package/STONJSONTests.class/instance/tests/testFloats.st A STON-Tests.package/STONJSONTests.class/instance/tests/testIntegers.st A STON-Tests.package/STONJSONTests.class/instance/tests/testLists.st A STON-Tests.package/STONJSONTests.class/instance/tests/testMaps.st A STON-Tests.package/STONJSONTests.class/instance/tests/testNull.st A STON-Tests.package/STONJSONTests.class/instance/tests/testShared.st A STON-Tests.package/STONJSONTests.class/instance/tests/testStrings.st A STON-Tests.package/STONJSONTests.class/instance/tests/testUnknown.st A STON-Tests.package/STONReaderTests.class/instance/tests/testDeepStructure.st A STON-Tests.package/STONReaderTests.class/instance/tests/testDictionaryWithIndirectReferenceKeys.st A STON-Tests.package/STONReaderTests.class/instance/tests/testDictionaryWithReferenceKeys.st A STON-Tests.package/STONReaderTests.class/instance/tests/testNonBMPCharacterDecoding.st A STON-Tests.package/STONReaderTests.class/instance/tests/testSetWithIndirectReferenceElements.st A STON-Tests.package/STONReaderTests.class/instance/tests/testSetWithReferenceElements.st A STON-Tests.package/STONWriteAsciiOnlyReadTests.class/README.md A STON-Tests.package/STONWriteAsciiOnlyReadTests.class/definition.st A STON-Tests.package/STONWriteAsciiOnlyReadTests.class/instance/private/serializeJson_.st A STON-Tests.package/STONWriteAsciiOnlyReadTests.class/instance/private/serialize_.st A STON-Tests.package/STONWriteReadTests.class/instance/tests/testIntervals.st A STON-Tests.package/STONWriteReadTests.class/instance/tests/testSpecialCharacters.st A STON-Tests.package/STONWriterTests.class/instance/tests/testNonBMPCharacterEncoding.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50695.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50696.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50695.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50696.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50696 18009 STON Update April 2016 https://pharo.fogbugz.com/f/cases/18009 http://files.pharo.org/image/50/50696.zip

April 17, 2016

Re: [Pharo-dev] [Pharo-users] GTDebugger shortcuts usability

by Peter UhnÃ¡k

So they use F keys, however they are clearly not uniform either, so I don't see the appeal. Not to mention that they will be just as hard to remember. On Sun, Apr 17, 2016 at 6:00 PM, Ben Coman <btc(a)openinworld.com> wrote: > Interesting. A search turned up... Quick Tip Debugger Shortcut Key > Reference > http://www.mularien.com/blog/category/eclipse/ > > cheers -ben > > On Sun, Apr 17, 2016 at 11:15 PM, philippe.back(a)highoctane.be > <philippe.back(a)gmail.com> wrote: > > Most of the world IDE use function keys for debugging. > > > > Additional benefit: easier for newcomers to use it. > > > > Having the buttons on the top is a pain as the code pane is at the bottom > > and requires travels all the time. > > > > Phil > > > > On Apr 17, 2016 4:57 PM, "Peter UhnÃ¡k" <i.uhnak(a)gmail.com> wrote: > >> > >> Well, I've added a startup script for myself... but it would be nice to > >> have it everywhere by default in some variant... > >> > >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > >> StartupPreferencesLoader default executeAtomicItems: { > >> StartupAction > >> name: 'Change debugger labels & shortcuts' > >> code: [ > >> GLMMorphicActionRenderer compile: ( > >> (GLMMorphicActionRenderer>>#render:) sourceCode > >> copyReplaceAll: 'setBalloonText: (anAction title' > >> with: 'setBalloonText: (anAction title asString' > >> ). > >> RestartDebugAction compile: 'defaultKeyText > >> ^ ''R'''. > >> RestartDebugAction compile: 'defaultLabel > >> ^ ''Restart'' asText addAttribute: TextEmphasis underlined from: 1 to: > 1'. > >> ResumeDebugAction compile: 'defaultKeyText > >> ^ ''P'''. > >> ResumeDebugAction compile: 'defaultLabel > >> ^ ''Proceed'' asText addAttribute: TextEmphasis underlined from: 1 to: > 1'. > >> StepIntoDebugAction compile: 'defaultKeyText > >> ^ ''I'''. > >> StepIntoDebugAction compile: 'defaultLabel > >> ^ ''Into'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. > >> StepOverDebugAction compile: 'defaultLabel > >> ^ ''Over'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. > >> StepThroughDebugAction compile: 'defaultLabel > >> ^ ''Through'' asText addAttribute: TextEmphasis underlined from: 1 to: > 1'. > >> ] > >> runOnce: true. > >> } > >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > >> > >> > >> > >> On Sat, Apr 16, 2016 at 11:39 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> > wrote: > >>>> > >>>> Letâs turn this energy into something positive. Please propose a > >>>> concrete set of default keybindings that you think would work better. > In > >>>> this process, please take into account all keybindings that are > already > >>>> defined in the code editor (it might not be so easy as it appears). > >>> > >>> > >>> As I've said: > >>> > >>> 1. can we unify the shift vs ctrl+shift nonsense? (I'm using linux btw) > >>> 2. can we use the default shortcuts pattern where one of the letters is > >>> underlined? > >>> > >>> as for the shortcuts themselves, problem is proceed, restart & into > >>> > >>> proceed: ctrl+shift+p is not taken, so I don't see why it has shortcut > >>> confusing with restart > >>> restart: ctrl+shift+r indents, but I'd argue that uniformity is more > >>> important here... indent is just convenience > >>> into: ctrl+shift+i is taken (I've never used it, but it maybe it's > >>> important), but we can still use ctrl+shift+n and underline n (point 2) > >>> > >>> If points 1 & 2 are implemented, then the letter is not as important, > >>> although first letter is always preferable. > >>> > >>> Peter > >>> > >>>> > >>>> Cheers, > >>>> Doru > >>>> > >>>> > >>>> > On Apr 16, 2016, at 8:37 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > >>>> > > >>>> > Hi, > >>>> > > >>>> > I'm getting fed-up with GTDebugger shortcuts since they are > completely > >>>> > random. > >>>> > > >>>> > Can we have them more meaningful and/or somehow visible? > >>>> > > >>>> > For now I ended up overriding the labels so I can at least see > them... > >>>> > but doing this is also stupid, because I still have to look at them > since I > >>>> > cannot remember random shortcuts. > >>>> > > >>>> > <debugger.png> > >>>> > > >>>> > 1. can we unify the shift vs ctrl+shift nonsense? (I'm using linux > >>>> > btw) > >>>> > 2. can we use the default shortcuts pattern where one of the letters > >>>> > is underlined? > >>>> > > >>>> > Peter > >>>> > >>>> -- > >>>> www.tudorgirba.com > >>>> www.feenk.com > >>>> > >>>> "Value is always contextual." > >>>> > >>>> > >>>> > >>>> > >>>> > >>> > >> > >

April 17, 2016

Re: [Pharo-dev] correct 32bit libssl library for CentOS 7.2?

by Bernhard Pieber

Hi Pierce, thanks for the information. Cheers, Bernhard > Am 17.04.2016 um 13:49 schrieb Pierce Ng <pierce(a)samadhiweb.com>: > > On Sun, Apr 17, 2016 at 09:54:24AM +0200, Bernhard Pieber wrote: >> Googling did not bring up any solution so far. Any help would be greatly >> appreciated. > > If you have the 32bit C development toolchain installed you can try building > from source. I wrote a blog post on swapping in LibreSSL for OpenSSL. I use > Ubuntu but in this case the distro shouldn't matter. > > http://www.samadhiweb.com/blog/2015.10.22.libressl.html > > Pierce

April 17, 2016

Re: [Pharo-dev] pharo -spur - vm source

by Nicolai Hess

2016-04-17 17:49 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > On Sun, Apr 17, 2016 at 10:56 PM, Nicolai Hess <nicolaihess(a)gmail.com> > wrote: > > Is https://github.com/pharo-project/pharo-vm the place to look > > for the current pharo spur vm source ? > > I load the master and build a vm but it isn't a spur vm. > > I only saw two other branches, legacy-cog and spur64. Where is the > > source for building the current latest pharo spur vm ? > > > > nicolai > > Wanting to do this a few weeks ago, at a guess googling "pharo-vm > jenkins" I followed the path from... > https://ci.inria.fr/pharo/view/5.0-VM-Spur/job/PharoVM-spur32/473/console > > through to... > > https://ci.inria.fr/pharo/job/PharoVM-spur32/Architecture=32,Slave=vm-build… > > where currently 476 is shown to be the last green build, which indeed > matches... > http://files.pharo.org/vm/pharo-spur32/linux/ > > so... > > https://ci.inria.fr/pharo/job/PharoVM-spur32/Architecture=32,Slave=vm-build… > shows how it is built > > and... > > https://ci.inria.fr/pharo/job/PharoVM-spur32/Architecture=32,Slave=vm-build… > provides the last sources used. > > I don't know how to match this back to a github commit. It would be > nice if github was tagged (e.g. 476) for each successful build, or at > least a moving "ci" tag to show where the Jenkins is currently pulling > from - but hopefully the above is enough hint. > Thanks ben > > cheers -ben > >

April 17, 2016

Re: [Pharo-dev] [Pharo-users] GTDebugger shortcuts usability

by Ben Coman

Interesting. A search turned up... Quick Tip Debugger Shortcut Key Reference http://www.mularien.com/blog/category/eclipse/ cheers -ben On Sun, Apr 17, 2016 at 11:15 PM, philippe.back(a)highoctane.be <philippe.back(a)gmail.com> wrote: > Most of the world IDE use function keys for debugging. > > Additional benefit: easier for newcomers to use it. > > Having the buttons on the top is a pain as the code pane is at the bottom > and requires travels all the time. > > Phil > > On Apr 17, 2016 4:57 PM, "Peter UhnÃ¡k" <i.uhnak(a)gmail.com> wrote: >> >> Well, I've added a startup script for myself... but it would be nice to >> have it everywhere by default in some variant... >> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> StartupPreferencesLoader default executeAtomicItems: { >> StartupAction >> name: 'Change debugger labels & shortcuts' >> code: [ >> GLMMorphicActionRenderer compile: ( >> (GLMMorphicActionRenderer>>#render:) sourceCode >> copyReplaceAll: 'setBalloonText: (anAction title' >> with: 'setBalloonText: (anAction title asString' >> ). >> RestartDebugAction compile: 'defaultKeyText >> ^ ''R'''. >> RestartDebugAction compile: 'defaultLabel >> ^ ''Restart'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. >> ResumeDebugAction compile: 'defaultKeyText >> ^ ''P'''. >> ResumeDebugAction compile: 'defaultLabel >> ^ ''Proceed'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. >> StepIntoDebugAction compile: 'defaultKeyText >> ^ ''I'''. >> StepIntoDebugAction compile: 'defaultLabel >> ^ ''Into'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. >> StepOverDebugAction compile: 'defaultLabel >> ^ ''Over'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. >> StepThroughDebugAction compile: 'defaultLabel >> ^ ''Through'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. >> ] >> runOnce: true. >> } >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> >> >> >> On Sat, Apr 16, 2016 at 11:39 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>>> >>>> Letâs turn this energy into something positive. Please propose a >>>> concrete set of default keybindings that you think would work better. In >>>> this process, please take into account all keybindings that are already >>>> defined in the code editor (it might not be so easy as it appears). >>> >>> >>> As I've said: >>> >>> 1. can we unify the shift vs ctrl+shift nonsense? (I'm using linux btw) >>> 2. can we use the default shortcuts pattern where one of the letters is >>> underlined? >>> >>> as for the shortcuts themselves, problem is proceed, restart & into >>> >>> proceed: ctrl+shift+p is not taken, so I don't see why it has shortcut >>> confusing with restart >>> restart: ctrl+shift+r indents, but I'd argue that uniformity is more >>> important here... indent is just convenience >>> into: ctrl+shift+i is taken (I've never used it, but it maybe it's >>> important), but we can still use ctrl+shift+n and underline n (point 2) >>> >>> If points 1 & 2 are implemented, then the letter is not as important, >>> although first letter is always preferable. >>> >>> Peter >>> >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> > On Apr 16, 2016, at 8:37 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>>> > >>>> > Hi, >>>> > >>>> > I'm getting fed-up with GTDebugger shortcuts since they are completely >>>> > random. >>>> > >>>> > Can we have them more meaningful and/or somehow visible? >>>> > >>>> > For now I ended up overriding the labels so I can at least see them... >>>> > but doing this is also stupid, because I still have to look at them since I >>>> > cannot remember random shortcuts. >>>> > >>>> > <debugger.png> >>>> > >>>> > 1. can we unify the shift vs ctrl+shift nonsense? (I'm using linux >>>> > btw) >>>> > 2. can we use the default shortcuts pattern where one of the letters >>>> > is underlined? >>>> > >>>> > Peter >>>> >>>> -- >>>> www.tudorgirba.com >>>> www.feenk.com >>>> >>>> "Value is always contextual." >>>> >>>> >>>> >>>> >>>> >>> >>

April 17, 2016

Re: [Pharo-dev] pharo -spur - vm source

by Ben Coman

On Sun, Apr 17, 2016 at 10:56 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > Is https://github.com/pharo-project/pharo-vm the place to look > for the current pharo spur vm source ? > I load the master and build a vm but it isn't a spur vm. > I only saw two other branches, legacy-cog and spur64. Where is the > source for building the current latest pharo spur vm ? > > nicolai Wanting to do this a few weeks ago, at a guess googling "pharo-vm jenkins" I followed the path from... https://ci.inria.fr/pharo/view/5.0-VM-Spur/job/PharoVM-spur32/473/console through to... https://ci.inria.fr/pharo/job/PharoVM-spur32/Architecture=32,Slave=vm-build… where currently 476 is shown to be the last green build, which indeed matches... http://files.pharo.org/vm/pharo-spur32/linux/ so... https://ci.inria.fr/pharo/job/PharoVM-spur32/Architecture=32,Slave=vm-build… shows how it is built and... https://ci.inria.fr/pharo/job/PharoVM-spur32/Architecture=32,Slave=vm-build… provides the last sources used. I don't know how to match this back to a github commit. It would be nice if github was tagged (e.g. 476) for each successful build, or at least a moving "ci" tag to show where the Jenkins is currently pulling from - but hopefully the above is enough hint. cheers -ben

April 17, 2016

Re: [Pharo-dev] [Pharo-users] GTDebugger shortcuts usability

by philippe.back＠highoctane.be

Most of the world IDE use function keys for debugging. Additional benefit: easier for newcomers to use it. Having the buttons on the top is a pain as the code pane is at the bottom and requires travels all the time. Phil On Apr 17, 2016 4:57 PM, "Peter UhnÃ¡k" <i.uhnak(a)gmail.com> wrote: > > Well, I've added a startup script for myself... but it would be nice to have it everywhere by default in some variant... > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > StartupPreferencesLoader default executeAtomicItems: { > StartupAction > name: 'Change debugger labels & shortcuts' > code: [ > GLMMorphicActionRenderer compile: ( > (GLMMorphicActionRenderer>>#render:) sourceCode > copyReplaceAll: 'setBalloonText: (anAction title' > with: 'setBalloonText: (anAction title asString' > ). > RestartDebugAction compile: 'defaultKeyText > ^ ''R'''. > RestartDebugAction compile: 'defaultLabel > ^ ''Restart'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. > ResumeDebugAction compile: 'defaultKeyText > ^ ''P'''. > ResumeDebugAction compile: 'defaultLabel > ^ ''Proceed'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. > StepIntoDebugAction compile: 'defaultKeyText > ^ ''I'''. > StepIntoDebugAction compile: 'defaultLabel > ^ ''Into'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. > StepOverDebugAction compile: 'defaultLabel > ^ ''Over'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. > StepThroughDebugAction compile: 'defaultLabel > ^ ''Through'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. > ] > runOnce: true. > } > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > On Sat, Apr 16, 2016 at 11:39 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>> >>> Letâs turn this energy into something positive. Please propose a concrete set of default keybindings that you think would work better. In this process, please take into account all keybindings that are already defined in the code editor (it might not be so easy as it appears). >> >> >> As I've said: >> >> 1. can we unify the shift vs ctrl+shift nonsense? (I'm using linux btw) >> 2. can we use the default shortcuts pattern where one of the letters is underlined? >> >> as for the shortcuts themselves, problem is proceed, restart & into >> >> proceed: ctrl+shift+p is not taken, so I don't see why it has shortcut confusing with restart >> restart: ctrl+shift+r indents, but I'd argue that uniformity is more important here... indent is just convenience >> into: ctrl+shift+i is taken (I've never used it, but it maybe it's important), but we can still use ctrl+shift+n and underline n (point 2) >> >> If points 1 & 2 are implemented, then the letter is not as important, although first letter is always preferable. >> >> Peter >> >>> >>> Cheers, >>> Doru >>> >>> >>> > On Apr 16, 2016, at 8:37 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>> > >>> > Hi, >>> > >>> > I'm getting fed-up with GTDebugger shortcuts since they are completely random. >>> > >>> > Can we have them more meaningful and/or somehow visible? >>> > >>> > For now I ended up overriding the labels so I can at least see them... but doing this is also stupid, because I still have to look at them since I cannot remember random shortcuts. >>> > >>> > <debugger.png> >>> > â >>> > 1. can we unify the shift vs ctrl+shift nonsense? (I'm using linux btw) >>> > 2. can we use the default shortcuts pattern where one of the letters is underlined? >>> > >>> > Peter >>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "Value is always contextual." >>> >>> >>> >>> >>> >> >

April 17, 2016