Pharo-dev
By thread
pharo-dev@lists.pharo.org
By month
Messages by month
- ----- 2026 -----
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
- 3 participants
- 144616 messages
Re: [Pharo-dev] ifTrue ifFalse shortcuts
by Esteban Lorenzano
> On 03 Aug 2016, at 10:52, Nicolai Hess <nicolaihess(a)gmail.com> wrote:
>
>
>
> 2016-08-03 10:36 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>:
> I will just re-post my first answer:
>
> if reintroduce them means reintroduce them hardcoded as before, then Iâm complete against it and I WILL NOT integrate such solution.
> Iâm sorry for being so strong here, but previous implementation was lame and we need to get rid of them.
>
> Now, I understand people are used to use those bindings and also some others (no idea which ones because I never used them⦠for me ocompletion is good enough⦠but those are tastes). So I would be very happy to integrate a generic way to define keybindings and outputs (which is already there, with keymapping, but I mean an editor or something), and I would be very happy to integrate a default configuration (which of course, will include #ifTrue:/##ifFalse:)
>
> we already have
> PharoShortcuts>>#displayIfFalseShortcut
> ^ $f alt
>
> this is defined and therefore in the same kind "hardcoded" as any other shortcut
> doItShortcut
> ^ $d meta
> inspectItShortcut
> ^ $i meta
> In PharoShortcuts
>
> the action (RubSmalltalkEditor>>displayIfFalse: aKeyboardEvent) is just not (yet) bound to this shortcut.
> I don't see how this is an argument against this shortcut definition. All other shortcuts are defined like that.
>
> And this is not really for adding a new feature. This shortcut already (always :) ) existed in the old PluggableTextMorph based editor, it was just lost (and not on purpose I think) like other things when
> we moved to rubric (as you can see, the code for this action is already there in rubric).
yes, it existed⦠and it was bad, as are bad all hardcoded shortcuts that yes, still exists a lot in the system.
but we want to clean the system, not perpetuate it.
for me, this is not a shortcut problem but a completion one⦠what we need to do is to enhance it. But even not doing it, I would not introduce new hardcoded shortcuts.
Esteban
>
>
>
>
>
>
>
>
>
> Esteban
>
>> On 03 Aug 2016, at 10:30, Denis Kudriashov <dionisiydk(a)gmail.com <mailto:dionisiydk@gmail.com>> wrote:
>>
>>
>> 2016-08-03 10:27 GMT+02:00 Guille Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>>:
>> I'm also against.
>>
>> - They take a place in the shortcuts that prevents others to use it
>> - If lazy people really needs this, the code completion should be enhanced. This is a code completion concern...
>>
>> +1
>
>
Aug. 3, 2016
Re: [Pharo-dev] ifTrue ifFalse shortcuts
by Nicolai Hess
2016-08-03 10:56 GMT+02:00 Ben Coman <btc(a)openinworld.com>:
> On Wed, Aug 3, 2016 at 4:36 PM, Esteban Lorenzano <estebanlm(a)gmail.com>
> wrote:
> > I will just re-post my first answer:
> >
> > if reintroduce them means reintroduce them hardcoded as before, then Iâm
> > complete against it and I WILL NOT integrate such solution.
> > Iâm sorry for being so strong here, but previous implementation was lame
> and
> > we need to get rid of them.
> >
> > Now, I understand people are used to use those bindings and also some
> others
> > (no idea which ones because I never used them⦠for me ocompletion is good
> > enough⦠but those are tastes). So I would be very happy to integrate a
> > generic way to define keybindings and outputs (which is already there,
> with
> > keymapping, but I mean an editor or something), and I would be very
> happy to
> > integrate a default configuration (which of course, will include
> > #ifTrue:/##ifFalse:)
>
> I would guess code expansions could be many and varied between
> different individuals, and quickly consume available keyboard
> shortcuts. Perhaps a generic mechanism would be single shortcut for
> "code expansion" which processes the letters preceding the cursor.
> For example, using shortcut <ctrl-e> for code expansion and typing...
>
> itf<ctrl-e>
>
> ==> ifTrue: [ ] ifFalse: [ ]
>
> The could be an interface to define these code expansions - initially
> at least on a purely personal basis.
>
> > And this is not really for adding a new feature. This shortcut already
> (always :) ) existed
>
> With a single shortcut for code expansion, perhaps a few other
> existing combinations could be freed up.
>
>
good idea, some kind of template expansion with user defined templates.
> cheers -ben
>
> >
> > Esteban
> >
> > On 03 Aug 2016, at 10:30, Denis Kudriashov <dionisiydk(a)gmail.com> wrote:
> >
> >
> > 2016-08-03 10:27 GMT+02:00 Guille Polito <guillermopolito(a)gmail.com>:
> >>
> >> I'm also against.
> >>
> >> - They take a place in the shortcuts that prevents others to use it
> >> - If lazy people really needs this, the code completion should be
> >> enhanced. This is a code completion concern...
> >
> >
> > +1
> >
> >
>
>
Aug. 3, 2016
[pharo-project/pharo-core]
by GitHub
Branch: refs/tags/60163
Home: https://github.com/pharo-project/pharo-core
Aug. 3, 2016
[pharo-project/pharo-core] f57843: 60163
by GitHub
Branch: refs/heads/6.0
Home: https://github.com/pharo-project/pharo-core
Commit: f578434a0d828004d918c36066a3cff9163f056b
https://github.com/pharo-project/pharo-core/commit/f578434a0d828004d918c360…
Author: Jenkins Build Server <board(a)pharo-project.org>
Date: 2016-08-03 (Wed, 03 Aug 2016)
Changed paths:
M AST-Core.package/RBArgumentNode.class/README.md
M AST-Core.package/RBBlockNode.class/README.md
M AST-Core.package/RBComment.class/README.md
M AST-Core.package/RBGlobalNode.class/README.md
M AST-Core.package/RBInstanceVariableNode.class/README.md
M AST-Core.package/RBLiteralValueNode.class/README.md
M AST-Core.package/RBMessageNode.class/README.md
M AST-Core.package/RBMethodNode.class/README.md
M AST-Core.package/RBParseErrorNode.class/README.md
M AST-Core.package/RBPatternPragmaNode.class/README.md
M AST-Core.package/RBPragmaNode.class/README.md
M AST-Core.package/RBProgramNode.class/README.md
M AST-Core.package/RBSequenceNode.class/README.md
M AST-Core.package/RBTemporaryNode.class/README.md
M AST-Core.package/RBVariableNode.class/README.md
R ConfigurationOfEpicea.package/ConfigurationOfEpicea.class/instance/tags/stable_.st
A ConfigurationOfEpicea.package/ConfigurationOfEpicea.class/instance/versions/stable_.st
A ConfigurationOfEpicea.package/ConfigurationOfEpicea.class/instance/versions/version796_.st
A ConfigurationOfEpicea.package/ConfigurationOfEpicea.class/instance/versions/version797_.st
M Epicea.package/EpLog.class/definition.st
R Epicea.package/EpLog.class/instance/accessing/commitAt_ifPresent_.st
R Epicea.package/EpLog.class/instance/accessing/commitAt_put_.st
A Epicea.package/EpLog.class/instance/copying/copyFromHead.st
M Epicea.package/EpLog.class/instance/initialization/initializeWith_.st
R Epicea.package/EpMonitor.class/class/accessing/detectLostLogAndDo_.st
R Epicea.package/EpMonitor.class/class/accessing/findLogFiles.st
R Epicea.package/EpMonitor.class/class/accessing/findLogFilesIn_.st
R Epicea.package/EpMonitor.class/class/accessing/loadAllLogs.st
R Epicea.package/EpMonitor.class/class/accessing/loadCurrentImageLogs.st
A Epicea.package/EpMonitor.class/class/accessing/logFilesIn_.st
A Epicea.package/EpPluggableFilter.class/class/special filters/after_.st
A Epicea.package/EpPluggableFilter.class/class/special filters/before_.st
A Epicea.package/EpPluggableFilter.class/class/special filters/todayFilter.st
M Epicea.package/EpPluggableFilter.class/class/well-known filters/behaviorFilter.st
M Epicea.package/EpPluggableFilter.class/class/well-known filters/codeChangeFilter.st
R Epicea.package/EpPluggableFilter.class/class/well-known filters/evaluationFilter.st
R Epicea.package/EpPluggableFilter.class/class/well-known filters/lastSixHoursFilter.st
M Epicea.package/EpPluggableFilter.class/class/well-known filters/logBrowserOperationFilter.st
M Epicea.package/EpPluggableFilter.class/class/well-known filters/methodFilter.st
M Epicea.package/EpPluggableFilter.class/class/well-known filters/noTriggerFilter.st
M Epicea.package/EpPluggableFilter.class/class/well-known filters/refactoringScopeFilter.st
R Epicea.package/EpPluggableFilter.class/class/well-known filters/todayFilter.st
A EpiceaBrowsers.package/EpAbsentItem.class/instance/converting/asMorph.st
R EpiceaBrowsers.package/EpAbsentItem.class/instance/operations/timeString.st
R EpiceaBrowsers.package/EpAbsentItem.class/instance/populating browser/displayWidget.st
A EpiceaBrowsers.package/EpEntryItem.class/instance/converting/asMorph.st
M EpiceaBrowsers.package/EpEntryItem.class/instance/populating browser/defaultMenuActions.st
R EpiceaBrowsers.package/EpEntryItem.class/instance/populating browser/displayWidget.st
A EpiceaBrowsers.package/EpFetchMoreItem.class/instance/converting/asMorph.st
R EpiceaBrowsers.package/EpFetchMoreItem.class/instance/operations/timeString.st
R EpiceaBrowsers.package/EpFetchMoreItem.class/instance/populating browser/displayWidget.st
M EpiceaBrowsers.package/EpFilteredEntriesItem.class/definition.st
M EpiceaBrowsers.package/EpFilteredEntriesItem.class/instance/accessing/entries.st
R EpiceaBrowsers.package/EpFilteredEntriesItem.class/instance/accessing/entries_.st
A EpiceaBrowsers.package/EpFilteredEntriesItem.class/instance/accessing/filteredEntriesCount.st
A EpiceaBrowsers.package/EpFilteredEntriesItem.class/instance/accessing/filteredEntriesCount_.st
A EpiceaBrowsers.package/EpFilteredEntriesItem.class/instance/accessing/olderFilteredEntry.st
A EpiceaBrowsers.package/EpFilteredEntriesItem.class/instance/accessing/olderFilteredEntry_.st
M EpiceaBrowsers.package/EpFilteredEntriesItem.class/instance/accessing/priorEntryReference.st
A EpiceaBrowsers.package/EpFilteredEntriesItem.class/instance/converting/asMorph.st
A EpiceaBrowsers.package/EpFilteredEntriesItem.class/instance/initialization/initialize.st
R EpiceaBrowsers.package/EpFilteredEntriesItem.class/instance/populating browser/displayWidget.st
M EpiceaBrowsers.package/EpFilteredEntriesItem.class/instance/testing/isCombinableWith_ifTrue_ifFalse_.st
A EpiceaBrowsers.package/EpLogBrowser.class/class/instance creation/openWithItems_.st
A EpiceaBrowsers.package/EpLogBrowser.class/instance/accessing filters/removeAllFilters.st
M EpiceaBrowsers.package/EpLogBrowser.class/instance/initialization/initializeFiltersModel.st
M EpiceaBrowsers.package/EpLogBrowser.class/instance/initialization/initializeItemsModel.st
M EpiceaBrowsers.package/EpLogBrowser.class/instance/initialization/initializeTabs.st
A EpiceaBrowsers.package/EpLogBrowserItem.class/instance/converting/asMorph.st
R EpiceaBrowsers.package/EpLogBrowserItem.class/instance/populating browser/displayWidget.st
M EpiceaBrowsers.package/EpLogBrowserView.class/instance/initialization/initializeBrowser.st
M EpiceaBrowsers.package/EpLostChangesDetector.class/class/startup - shutdown/startUp_.st
R EpiceaBrowsers.package/EpMenuActionsVisitor.class/instance/private - menu actions/redoMenuAction.st
M EpiceaBrowsers.package/EpMenuActionsVisitor.class/instance/private - menu actions/redoSelectionCompleteRefactoringMenuAction.st
M EpiceaBrowsers.package/EpMenuActionsVisitor.class/instance/private - menu actions/redoSelectionPropagateRefactoringMenuAction.st
R EpiceaBrowsers.package/EpMenuActionsVisitor.class/instance/private - menu actions/undoMenuAction.st
M EpiceaBrowsers.package/EpMenuActionsVisitor.class/instance/visitor/visitCodeChange_.st
R EpiceaBrowsers.package/EpMenuActionsVisitor.class/instance/visitor/visitExpressionEvaluation_.st
R EpiceaBrowsers.package/EpMenuActionsVisitor.class/instance/visitor/visitMonticelloVersionsLoad_.st
R EpiceaBrowsers.package/EpMenuActionsVisitor.class/instance/visitor/visitRedo_.st
R EpiceaBrowsers.package/EpPriorView.class/instance/initialization/initializeBrowser.st
M EpiceaBrowsers.package/EpPriorView.class/instance/private/draggingPassengerMorphsFor_.st
R EpiceaBrowsers.package/EpPriorView.class/instance/private/itemFor_.st
M EpiceaBrowsers.package/EpPriorView.class/instance/private/newFilteredItemFor_.st
M EpiceaBrowsers.package/EpPriorView.class/instance/private/next_from_.st
M EpiceaBrowsers.package/EpPriorView.class/instance/refreshing/refresh.st
A EpiceaBrowsers.package/EpRedoVisitor.class/instance/visitor/visitProtocolAddition_.st
M EpiceaBrowsers.package/EpRedoVisitor.class/instance/visitor/visitProtocolRemoval_.st
M EpiceaBrowsers.package/EpSelection.class/instance/accessing/entriesToRedo.st
A EpiceaBrowsers.package/EpSelection.class/instance/operations/filterAfter.st
A EpiceaBrowsers.package/EpSelection.class/instance/operations/filterBefore.st
A EpiceaBrowsers.package/EpSelection.class/instance/operations/removeAllFilters.st
M EpiceaBrowsers.package/EpSelection.class/instance/operations/spawnSorterWithSelection.st
M EpiceaBrowsers.package/EpSelection.class/instance/populating menu/filtersSubMenu.st
M EpiceaBrowsers.package/EpSelection.class/instance/populating menu/populateMenu_.st
M EpiceaBrowsers.package/EpSessionBrowser.class/instance/refresing/refresh.st
R EpiceaBrowsers.package/EpSorterView.class/instance/initialization/initializeBrowser.st
M EpiceaBrowsers.package/EpSorterView.class/instance/private/wantedItemsFrom_.st
A EpiceaBrowsers.package/EpUndoVisitor.class/instance/visitor/visitProtocolAddition_.st
A EpiceaBrowsers.package/EpUndoVisitor.class/instance/visitor/visitProtocolRemoval_.st
R EpiceaBrowsersTests.package/EpAbsentEntryViewTest.class/README.md
R EpiceaBrowsersTests.package/EpAbsentEntryViewTest.class/definition.st
R EpiceaBrowsersTests.package/EpAbsentEntryViewTest.class/instance/resources/newLog.st
R EpiceaBrowsersTests.package/EpAbsentEntryViewTest.class/instance/resources/pageSize.st
R EpiceaBrowsersTests.package/EpAbsentEntryViewTest.class/instance/tests/testRootItems.st
R EpiceaBrowsersTests.package/EpBeforeTestVisitor.class/README.md
R EpiceaBrowsersTests.package/EpBeforeTestVisitor.class/class/initialization/withMiniMonticello_.st
R EpiceaBrowsersTests.package/EpBeforeTestVisitor.class/definition.st
R EpiceaBrowsersTests.package/EpBeforeTestVisitor.class/instance/accessing/miniMonticelloResource_.st
R EpiceaBrowsersTests.package/EpBeforeTestVisitor.class/instance/visitor/visitClassAddition_.st
R EpiceaBrowsersTests.package/EpBeforeTestVisitor.class/instance/visitor/visitClassModification_.st
R EpiceaBrowsersTests.package/EpBeforeTestVisitor.class/instance/visitor/visitClassRemoval_.st
R EpiceaBrowsersTests.package/EpBeforeTestVisitor.class/instance/visitor/visitCodeChange_.st
R EpiceaBrowsersTests.package/EpBeforeTestVisitor.class/instance/visitor/visitMethodModification_.st
R EpiceaBrowsersTests.package/EpClassFactoryForTestCase.class/README.md
R EpiceaBrowsersTests.package/EpClassFactoryForTestCase.class/definition.st
R EpiceaBrowsersTests.package/EpClassFactoryForTestCase.class/instance/accessing/packageName.st
R EpiceaBrowsersTests.package/EpFilterTest.class/instance/tests/testEvaluation.st
R EpiceaBrowsersTests.package/EpMiniMonticelloResource.class/README.md
R EpiceaBrowsersTests.package/EpMiniMonticelloResource.class/definition.st
R EpiceaBrowsersTests.package/EpMiniMonticelloResource.class/instance/accessing/classFactory.st
R EpiceaBrowsersTests.package/EpMiniMonticelloResource.class/instance/accessing/currentSnapshot.st
R EpiceaBrowsersTests.package/EpMiniMonticelloResource.class/instance/accessing/patchRelativeTo_.st
R EpiceaBrowsersTests.package/EpMiniMonticelloResource.class/instance/accessing/utilityPackage.st
R EpiceaBrowsersTests.package/EpMiniMonticelloResource.class/instance/accessing/utilityRepo.st
R EpiceaBrowsersTests.package/EpMiniMonticelloResource.class/instance/accessing/utilityWorkingCopy.st
R EpiceaBrowsersTests.package/EpMiniMonticelloResource.class/instance/accessing/workingPatch.st
R EpiceaBrowsersTests.package/EpMiniMonticelloResource.class/instance/accessing/workingSnapshot.st
R EpiceaBrowsersTests.package/EpMiniMonticelloResource.class/instance/actions/revert.st
R EpiceaBrowsersTests.package/EpMiniMonticelloResource.class/instance/actions/snapshot.st
R EpiceaBrowsersTests.package/EpMiniMonticelloResource.class/instance/running/setUp.st
R EpiceaBrowsersTests.package/EpMiniMonticelloResource.class/instance/running/tearDown.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/README.md
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/class/accessing/resources.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/definition.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/asserting/assertNoChanges.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/asserting/assertNoChangesRelativeTo_.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/running/runCase.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/running/tearDown.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/test-generation/generateAllTests.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/tests/testBehaviorCategoryChange.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/tests/testBehaviorCommentChange.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/tests/testBehaviorNameChange.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/tests/testCategoryAddition.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/tests/testCategoryRemoval.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/tests/testCategoryRename.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/tests/testClassAddition.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/tests/testClassModification.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/tests/testClassRemoval.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/tests/testItem_.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/tests/testMethodAddition.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/tests/testMethodModification.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/tests/testMethodRemoval.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/tests/testProtocolAddition.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/tests/testProtocolRemoval.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/tests/testTraitAddition.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/tests/testTraitModification.st
R EpiceaBrowsersTests.package/EpRedoAndUndoVisitorTest.class/instance/tests/testTraitRemoval.st
R Ombu.package/OmSessionStore.class/instance/testing/isPointsTo_.st
A Reflectivity-Tools-Tests.package/MethodConstTests.class/README.md
A Reflectivity-Tools-Tests.package/MethodConstTests.class/definition.st
A Reflectivity-Tools-Tests.package/MethodConstTests.class/instance/tests/constFromBlock_.st
A Reflectivity-Tools-Tests.package/MethodConstTests.class/instance/tests/constFromReceiverExpression.st
A Reflectivity-Tools-Tests.package/MethodConstTests.class/instance/tests/sumOfTwoConsts_and_.st
A Reflectivity-Tools-Tests.package/MethodConstTests.class/instance/tests/testAPIFromBlock.st
A Reflectivity-Tools-Tests.package/MethodConstTests.class/instance/tests/testAPIFromMessageSendReceiver.st
A Reflectivity-Tools-Tests.package/MethodConstTests.class/instance/tests/testConstPlaceInTransformedMethod.st
A Reflectivity-Tools-Tests.package/MethodConstTests.class/instance/tests/testTwoConstsInSameMethod.st
A Reflectivity-Tools-Tests.package/MethodConstTests.class/instance/tests/testUsingConstJustInSameMethod.st
A Reflectivity.package/extension/Object/instance/asMethodConst.st
R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60162.st
A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60163.st
R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60162.st
A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60163.st
M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st
Log Message:
-----------
60163
18831 Integrate new Epicea version
https://pharo.fogbugz.com/f/cases/18831
18768 Inlined method const could be implemented by metalinks
https://pharo.fogbugz.com/f/cases/18768
18835 Update RBParser-Nodes class comments
https://pharo.fogbugz.com/f/cases/18835
http://files.pharo.org/image/60/60163.zip
Aug. 3, 2016
Re: [Pharo-dev] ifTrue ifFalse shortcuts
by Ben Coman
On Wed, Aug 3, 2016 at 4:36 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote:
> I will just re-post my first answer:
>
> if reintroduce them means reintroduce them hardcoded as before, then Iâm
> complete against it and I WILL NOT integrate such solution.
> Iâm sorry for being so strong here, but previous implementation was lame and
> we need to get rid of them.
>
> Now, I understand people are used to use those bindings and also some others
> (no idea which ones because I never used them⦠for me ocompletion is good
> enough⦠but those are tastes). So I would be very happy to integrate a
> generic way to define keybindings and outputs (which is already there, with
> keymapping, but I mean an editor or something), and I would be very happy to
> integrate a default configuration (which of course, will include
> #ifTrue:/##ifFalse:)
I would guess code expansions could be many and varied between
different individuals, and quickly consume available keyboard
shortcuts. Perhaps a generic mechanism would be single shortcut for
"code expansion" which processes the letters preceding the cursor.
For example, using shortcut <ctrl-e> for code expansion and typing...
itf<ctrl-e>
==> ifTrue: [ ] ifFalse: [ ]
The could be an interface to define these code expansions - initially
at least on a purely personal basis.
> And this is not really for adding a new feature. This shortcut already (always :) ) existed
With a single shortcut for code expansion, perhaps a few other
existing combinations could be freed up.
cheers -ben
>
> Esteban
>
> On 03 Aug 2016, at 10:30, Denis Kudriashov <dionisiydk(a)gmail.com> wrote:
>
>
> 2016-08-03 10:27 GMT+02:00 Guille Polito <guillermopolito(a)gmail.com>:
>>
>> I'm also against.
>>
>> - They take a place in the shortcuts that prevents others to use it
>> - If lazy people really needs this, the code completion should be
>> enhanced. This is a code completion concern...
>
>
> +1
>
>
Aug. 3, 2016
Re: [Pharo-dev] ifTrue ifFalse shortcuts
by Nicolai Hess
2016-08-03 10:36 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>:
> I will just re-post my first answer:
>
> if reintroduce them means reintroduce them hardcoded as before, then Iâm
> complete against it and I WILL NOT integrate such solution.
> Iâm sorry for being so strong here, but previous implementation was lame
> and we need to get rid of them.
>
> Now, I understand people are used to use those bindings and also some
> others (no idea which ones because I never used them⦠for me ocompletion is
> good enough⦠but those are tastes). So I would be very happy to integrate a
> generic way to define keybindings and outputs (which is already there, with
> keymapping, but I mean an editor or something), and I would be very happy
> to integrate a default configuration (which of course, will include
> #ifTrue:/##ifFalse:)
>
we already have
PharoShortcuts>>#displayIfFalseShortcut
^ $f alt
this is defined and therefore in the same kind "hardcoded" as any other
shortcut
doItShortcut
^ $d meta
inspectItShortcut
^ $i meta
In PharoShortcuts
the action (RubSmalltalkEditor>>displayIfFalse: aKeyboardEvent) is just not
(yet) bound to this shortcut.
I don't see how this is an argument against this shortcut definition. All
other shortcuts are defined like that.
And this is not really for adding a new feature. This shortcut already
(always :) ) existed in the old PluggableTextMorph based editor, it was
just lost (and not on purpose I think) like other things when
we moved to rubric (as you can see, the code for this action is already
there in rubric).
>
> Esteban
>
> On 03 Aug 2016, at 10:30, Denis Kudriashov <dionisiydk(a)gmail.com> wrote:
>
>
> 2016-08-03 10:27 GMT+02:00 Guille Polito <guillermopolito(a)gmail.com>:
>
>> I'm also against.
>>
>> - They take a place in the shortcuts that prevents others to use it
>> - If lazy people really needs this, the code completion should be
>> enhanced. This is a code completion concern...
>>
>
> +1
>
>
>
Aug. 3, 2016
Re: [Pharo-dev] ifTrue ifFalse shortcuts
by Esteban Lorenzano
I will just re-post my first answer:
if reintroduce them means reintroduce them hardcoded as before, then Iâm complete against it and I WILL NOT integrate such solution.
Iâm sorry for being so strong here, but previous implementation was lame and we need to get rid of them.
Now, I understand people are used to use those bindings and also some others (no idea which ones because I never used them⦠for me ocompletion is good enough⦠but those are tastes). So I would be very happy to integrate a generic way to define keybindings and outputs (which is already there, with keymapping, but I mean an editor or something), and I would be very happy to integrate a default configuration (which of course, will include #ifTrue:/##ifFalse:)
Esteban
> On 03 Aug 2016, at 10:30, Denis Kudriashov <dionisiydk(a)gmail.com> wrote:
>
>
> 2016-08-03 10:27 GMT+02:00 Guille Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>>:
> I'm also against.
>
> - They take a place in the shortcuts that prevents others to use it
> - If lazy people really needs this, the code completion should be enhanced. This is a code completion concern...
>
> +1
Aug. 3, 2016
Re: [Pharo-dev] ifTrue ifFalse shortcuts
by Denis Kudriashov
2016-08-03 10:27 GMT+02:00 Guille Polito <guillermopolito(a)gmail.com>:
> I'm also against.
>
> - They take a place in the shortcuts that prevents others to use it
> - If lazy people really needs this, the code completion should be
> enhanced. This is a code completion concern...
>
+1
Aug. 3, 2016
Re: [Pharo-dev] ifTrue ifFalse shortcuts
by Guille Polito
I'm also against.
- They take a place in the shortcuts that prevents others to use it
- If lazy people really needs this, the code completion should be
enhanced. This is a code completion concern...
In general, my rule of thumb is to answer the following questions:
How many people use it?
- if a lot, maybe it makes sense to integrate it
- if not a lot, make it a loadable extension
How often do people use it?
- if at least 10 times per hour (e.g., reformat code, senders,
implementors, search) the shortcut should be simple
- otherwise we can put it in a more complex combination to leave
place to the common ones.
Guille
-------- Original Message --------
> From a software design perspective it shouldn't be easy to insert
> #ifTrue:ifFalse :)
>
> Norbert
>
>> Am 03.08.2016 um 10:15 schrieb Nicolai Hess <nicolaihess(a)gmail.com
>> <mailto:nicolaihess@gmail.com>>:
>>
>> Any objections on using
>> cmd+t / cmd+f for insert ifTrue/ifFalse
>> (linux/windows this would be alt+t/alt+f, mac this would be cmd+t/cmd+f).
>>
>> 2015-08-12 18:52 GMT+02:00 stepharo <stepharo(a)free.fr
>> <mailto:stepharo@free.fr>>:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Le 11/8/15 10:25, Nicolai Hess a
>> écrit :
>>
>>
>>>
>>>
>>>
>>>
>>>
>>> I am nearly finished with converting old shortcut
>>> mapping (Editor/TextEditor cmdActions/shiftCmdAction
>>> map)
>>>
>>>
>>> to our keymapping framework.
>>>
>>>
>>>
>>>
>>> 15619 <https://pharo.fogbugz.com/default.asp?15619>
>>>
>>>
>>> cleanup TextEditors shortcut
>>> definition
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>> Thank a lot!
>>
>>
>>
>> Yesterday with guillermo and christophe we spent one full afternoon
>> reading all the recursive dependencies introduced
>>
>> when we just want to have monticello in the bootstrap (to be able to
>> load code).
>>
>> We filled up two black boards and I should say that I was a nice
>> down to see the complexity but we will fix it :).
>>
>>
>>
>> Yesterday Esteban sat with igor and started to integrate the
>> OSWindow integration work of igor (yes igor you should do pull
>> requests :).
>>
>> So there are some problems with the mac vm and this will have to be
>> fixed (probably next week).
>>
>> After I hope that we will get clean events from SDL
>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> I need some more time, one or two vm changes and some people
>>> testing this on a mac.
>>>
>>>
>>>
>>>
>>
>>
>>
>> Tell us we will :)
>>
>>
>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> I know, this is a bit late because we replace our text
>>> components with rubric, but if this
>>>
>>>
>>> is finished and working for "old" PluggableTextMorphs, I will do
>>> the same for rubric.
>>>
>>>
>>
>> Thanks thanks thanks.
>>
>> I often frustrated when I see myself doing things more than twice
>> but this is a pattern. I decided long time ago that
>>
>> if this is necessary to do intermediate actions to lower the stress
>> on the future actions, I'm ready to throw awy what
>>
>> I did to get the ultimate goal reached.
>>
>>
>>
>>
>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> 2015-08-08 14:57 GMT+02:00
>>> Esteban Lorenzano <estebanlm(a)gmail.com
>>> <mailto:estebanlm@gmail.com>>:
>>>
>>>
>>> if reintroduce
>>> them means reintroduce them hardcoded as
>>> before, then Iâm complete against it and I
>>> WILL NOT integrate such solution.
>>> Iâm sorry for being so strong here, but
>>> previous implementation was lame and we need
>>> to get rid of them.
>>>
>>>
>>>
>>>
>>> Now, I understand people are used to use
>>> those bindings and also some others (no idea
>>> which ones because I never used them⦠for me
>>> ocompletion is good enough⦠but those are
>>> tastes). So I would be very happy to
>>> integrate a generic way to define
>>> keybindings and outputs (which is already
>>> there, with keymapping, but I mean an editor
>>> or something), and I would be very happy to
>>> integrate a default configuration (which of
>>> course, will include #ifTrue:/##ifFalse:)
>>>
>>>
>>>
>>>
>>>
>>> Esteban
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>>
>>>> On 08 Aug 2015, at 12:45,
>>>> Peter Uhnák <i.uhnak(a)gmail.com <mailto:i.uhnak@gmail.com>>
>>>>
>>>> wrote:
>>>>
>>>>
>>>>
>>>>
>>>> I would also
>>>> appreciate if it was readded,
>>>> as I've been using it
>>>> regularly.
>>>>
>>>>
>>>>
>>>> Peter
>>>>
>>>>
>>>>
>>>>
>>>> On
>>>> Sat, Aug 8, 2015 at 12:21
>>>> PM, ThomasHeniart <heniart.thomas(a)gmail.com
>>>> <mailto:heniart.thomas@gmail.com>>
>>>> wrote:
>>>>
>>>>
>>>> I think
>>>> it could be nice to keep
>>>> this shortcut :)
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On 08/08/2015
>>>> 12:12, Franck
>>>> Warlouzet wrote:
>>>>
>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>>
>>>>>
>>>>> Yes it was not
>>>>> on purpose. It
>>>>> is not
>>>>> implemented in
>>>>> Rubric, but I
>>>>> can do it if
>>>>> there is a need
>>>>> of it (which
>>>>> seems to be the
>>>>> case).
>>>>>
>>>>>
>>>>>
>>>>> Franck
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------
>>>>> Date: Sat,
>>>>> 8 Aug 2015
>>>>> 12:09:22 +0200
>>>>>
>>>>> From: i.uhnak(a)gmail.com <mailto:i.uhnak@gmail.com>
>>>>>
>>>>> To: pharo-dev(a)lists.pharo.org
>>>>> <mailto:pharo-dev@lists.pharo.org>
>>>>>
>>>>> Subject:
>>>>> [Pharo-dev]
>>>>> ifTrue ifFalse
>>>>> shortcuts
>>>>>
>>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> was
>>>>> removal of
>>>>> ifTrue/ifFalse
>>>>> shortcuts on
>>>>> purpose, or by
>>>>> accident?
>>>>>
>>>>> https://pharo.fogbugz.com/f/cases/16125/Nautilus-doesn-t-recognize-the-cmd-…
>>>>>
>>>>>
>>>>> (maybe
>>>>> was caused by
>>>>> switch to
>>>>> Rubric?)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Peter
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>>
>>
>
>
>
>
Aug. 3, 2016
Re: [Pharo-dev] ifTrue ifFalse shortcuts
by Nicolai Hess
2016-08-03 10:21 GMT+02:00 Norbert Hartl <norbert(a)hartl.name>:
> From a software design perspective it shouldn't be easy to insert
> #ifTrue:ifFalse :)
>
:-)
>
> Norbert
>
> Am 03.08.2016 um 10:15 schrieb Nicolai Hess <nicolaihess(a)gmail.com>:
>
> Any objections on using
> cmd+t / cmd+f for insert ifTrue/ifFalse
> (linux/windows this would be alt+t/alt+f, mac this would be cmd+t/cmd+f).
>
> 2015-08-12 18:52 GMT+02:00 stepharo <stepharo(a)free.fr>:
>
>>
>>
>> Le 11/8/15 10:25, Nicolai Hess a écrit :
>>
>> I am nearly finished with converting old shortcut mapping
>> (Editor/TextEditor cmdActions/shiftCmdAction map)
>> to our keymapping framework.
>>
>> 15619 <https://pharo.fogbugz.com/default.asp?15619>
>> cleanup TextEditors shortcut definition
>>
>>
>> Thank a lot!
>>
>> Yesterday with guillermo and christophe we spent one full afternoon
>> reading all the recursive dependencies introduced
>> when we just want to have monticello in the bootstrap (to be able to load
>> code).
>> We filled up two black boards and I should say that I was a nice down to
>> see the complexity but we will fix it :).
>>
>> Yesterday Esteban sat with igor and started to integrate the OSWindow
>> integration work of igor (yes igor you should do pull requests :).
>> So there are some problems with the mac vm and this will have to be fixed
>> (probably next week).
>> After I hope that we will get clean events from SDL
>>
>>
>> I need some more time, one or two vm changes and some people testing this
>> on a mac.
>>
>>
>> Tell us we will :)
>>
>>
>> I know, this is a bit late because we replace our text components with
>> rubric, but if this
>> is finished and working for "old" PluggableTextMorphs, I will do the same
>> for rubric.
>>
>> Thanks thanks thanks.
>> I often frustrated when I see myself doing things more than twice but
>> this is a pattern. I decided long time ago that
>> if this is necessary to do intermediate actions to lower the stress on
>> the future actions, I'm ready to throw awy what
>> I did to get the ultimate goal reached.
>>
>>
>>
>>
>>
>> 2015-08-08 14:57 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>:
>>
>>> if reintroduce them means reintroduce them hardcoded as before, then Iâm
>>> complete against it and I WILL NOT integrate such solution.
>>> Iâm sorry for being so strong here, but previous implementation was lame
>>> and we need to get rid of them.
>>>
>>> Now, I understand people are used to use those bindings and also some
>>> others (no idea which ones because I never used them⦠for me ocompletion is
>>> good enough⦠but those are tastes). So I would be very happy to integrate a
>>> generic way to define keybindings and outputs (which is already there, with
>>> keymapping, but I mean an editor or something), and I would be very happy
>>> to integrate a default configuration (which of course, will include
>>> #ifTrue:/##ifFalse:)
>>>
>>> Esteban
>>>
>>>
>>>
>>> On 08 Aug 2015, at 12:45, Peter Uhnák <i.uhnak(a)gmail.com> wrote:
>>>
>>> I would also appreciate if it was readded, as I've been using it
>>> regularly.
>>>
>>> Peter
>>>
>>> On Sat, Aug 8, 2015 at 12:21 PM, ThomasHeniart <heniart.thomas(a)gmail.com
>>> > wrote:
>>>
>>>> I think it could be nice to keep this shortcut :)
>>>>
>>>>
>>>> On 08/08/2015 12:12, Franck Warlouzet wrote:
>>>>
>>>> Hi,
>>>>
>>>> Yes it was not on purpose. It is not implemented in Rubric, but I can
>>>> do it if there is a need of it (which seems to be the case).
>>>>
>>>> Franck
>>>>
>>>> ------------------------------
>>>> Date: Sat, 8 Aug 2015 12:09:22 +0200
>>>> From: i.uhnak(a)gmail.com
>>>> To: pharo-dev(a)lists.pharo.org
>>>> Subject: [Pharo-dev] ifTrue ifFalse shortcuts
>>>>
>>>> Hi,
>>>>
>>>> was removal of ifTrue/ifFalse shortcuts on purpose, or by accident?
>>>>
>>>> https://pharo.fogbugz.com/f/cases/16125/Nautilus-doesn-t-recognize-the-cmd-…
>>>> (maybe was caused by switch to Rubric?)
>>>>
>>>> Peter
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Aug. 3, 2016