September 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] FTSelectionStrategy>>toggleRowIndex: logic duplication

by Esteban Lorenzano

> On 10 Sep 2015, at 11:53, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > In FTSelectionStrategy>>toggleRowIndex: there is a code: > > ((self table selectedRowIndexes includes: rowIndex) > and: [ self table selectedRowIndexes size = 1 "just one selected" > and: [ self table allowsDeselection ] ]) > ifTrue: [ > self table allowsDeselection > ifTrue: [ self table selectRowIndexes: #() ] ] > > if first set of expressions is evaluated to true, then "self table allowsDeselectionâ returns true. Why do we check it again in the ifTrue: block? there *was* a reason I think, but most probably is a refactor remaining :) again feel free to submit an issue and to provide a fix :) Esteban ps: Thank you very much for taking a look at fast table. As I said when we integrated it: it is not finished and we count on you to submit the issues that emerge (and of course, if you are âin the moodâ, to provide fixes :P) > > Uko

Sept. 10, 2015

Re: [Pharo-dev] Pharo on iPad Pro

by Esteban Lorenzano

;) > On 10 Sep 2015, at 11:36, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Now we have to make the first IDE tailored specially for iPad Pro :) > > Uko >

Sept. 10, 2015

Re: [Pharo-dev] Disable focusing of FastTable

by Esteban Lorenzano

> On 10 Sep 2015, at 00:06, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Hi, > > is there a nice way to forbid a fast table to take focus? > > because #takesKeyboardFocus is implemented as: â^ self enabledâ. And #enabled is inherited from Morph and is always true. Do I really have to subclass the FTTableMorph just to get rid of focusing? nope. I started to implement that part then I needed to jump to other stuff. you can report an issue and feel free to propose an implementation :) cheers, Esteban > > Uko

Sept. 10, 2015

Re: [Pharo-dev] FastTable non-selectable, clickable

by Yuriy Tymchuk

Thanks, Iâll take a look on that. What would be interesting is to add a stripe like line numbers but with critic indicators. Do you know how this should work? Uko > On 10 Sep 2015, at 12:01, Stephan Eggermont <stephan(a)stack.nl> wrote: > > On 10-09-15 11:41, Yuriy Tymchuk wrote: >> Ideally I want it to be embedded into rubric representation. But I donât know where to start with that. > > Add an instance variable qualitySummary to NautilusAnnotationDisplayer. > > add qualitySummary := self qualitySummaryMorph to noteNewOwner: aMorph > > in qualitySummaryMorph, return a morph that draws the summary and reacts to click by opening the QA panel. > > Stephan > >

Sept. 10, 2015

Re: [Pharo-dev] [ANN] MessageFlowBrowser

by Esteban Lorenzano

> On 09 Sep 2015, at 21:14, Torsten Bergmann <astares(a)gmx.de> wrote: > > Some new changes: > > - Catalog methods were added and config is in MetaRepoForPharo50 > => should be available in CatalogBrowser and Spotter by tomorrow after catalog job run > - it is now possible to browse the methods > - class comment added > - syntax highlighting is now working correctly (was easier than I thought - should always remember GT methods also accept blocks!) > > Is there any code that marks/selects messages in a smalltalkCode editor? > Would be cool if you browse the messages that a method sends and you > click on the displaed method selectors in the tree they will be highlighted > in the code pane... > > Alexandre wrote: > >Also, it would be great to have it accessible from the World/Tools menu. > > No as it is not a standalone tool. You need to have a method or selector first > to display some contents. +1 > When catalog job is ready and catches the new > ConfigurationOfMessageFlowBrowser (tomorrow) you can: > > - hit ALT+ENTER to open spotter > - search for the project by entering "Flow" and load it > - when it is loaded just use "Method Flow" on a method in Nautilus not there yetâ¦ I suppose we need to wait the refresh :) > > Maybe it would be good to have something similar to Cmd+M shortcut > that works on selected text and that is interpretet as selector. > > Stef wrote: > >Thanks for it. This was a project I wanted to propose. yes, this was a missing tool. we could discuss also itâs introduction in the core distributionâ¦ what do you think? Esteban > > If you feel something is missing: the repo is open. An improved version > could possibly be a part of Pharo 5. A nice extension would be to add > also "local senders" and "local implementors" to it (= local to the class and > up the hierarchy) > > Have fun > T. > >

Sept. 10, 2015

Re: [Pharo-dev] FastTable non-selectable, clickable

by Stephan Eggermont

On 10-09-15 12:01, Stephan Eggermont wrote: > add qualitySummary := self qualitySummaryMorph to noteNewOwner: aMorph and add it to the Morph as submorph

Sept. 10, 2015

Re: [Pharo-dev] FastTable non-selectable, clickable

by Stephan Eggermont

On 10-09-15 11:41, Yuriy Tymchuk wrote: > Ideally I want it to be embedded into rubric representation. But I donât know where to start with that. Add an instance variable qualitySummary to NautilusAnnotationDisplayer. add qualitySummary := self qualitySummaryMorph to noteNewOwner: aMorph in qualitySummaryMorph, return a morph that draws the summary and reacts to click by opening the QA panel. Stephan

Sept. 10, 2015

FTSelectionStrategy>>toggleRowIndex: logic duplication

by Yuriy Tymchuk

In FTSelectionStrategy>>toggleRowIndex: there is a code: ((self table selectedRowIndexes includes: rowIndex) and: [ self table selectedRowIndexes size = 1 "just one selected" and: [ self table allowsDeselection ] ]) ifTrue: [ self table allowsDeselection ifTrue: [ self table selectRowIndexes: #() ] ] if first set of expressions is evaluated to true, then "self table allowsDeselectionâ returns true. Why do we check it again in the ifTrue: block? Uko

Sept. 10, 2015

Re: [Pharo-dev] FastTable non-selectable, clickable

by Yuriy Tymchuk

Ideally I want it to be embedded into rubric representation. But I donât know where to start with that. > On 10 Sep 2015, at 11:34, Stephan Eggermont <stephan(a)stack.nl> wrote: > > On 09-09-15 23:42, Yuriy Tymchuk wrote: >> Iâm trying to move QualityAssistant to FastTable and I really like it. Now as you may have noticed, you cannot select a list item in the QA plugin, but you can click on it to get the issue highlighted (if the rule allows). How can I mimic this with FT? Should I create a subclass of FTSelectionStrategy and redefine #selectRowIndex:event: not to do anything and just announce that there was a click on a list item? Or is there a better way? > > Wouldn't QualityAssistant fit better in the NautilusAnnotationDisplayer? > With only showing the number of problems and a summary of the severest one, using a hover text for a longer description and a popup menu showing all details and actions? > > The picture shows the possible location. There should probably be no direct actions aside from popping up the quality assistant. There should definitely not be a fat red cross taking away attention from the editor. > > The current vertical space taken up seems somewhat excessive > > Stephan > > > <QA.png>

Sept. 10, 2015

Re: [Pharo-dev] Magritte-XMLBinding causes DNU when using Seaside editor example

by Skip

On Sep 10, 2015, at 10:53, Stephan Eggermont <stephan(a)stack.nl> wrote: > How are you loading what combination of versions of what in what version of Pharo? I will try from a clean image, latest version of Pharo 4 (#40621). I do the following: 1) Install MagritteMagic Stable using Configuration browser (I needed #asComponent to experiment with some things). - This will install also Seaside, Magritte, etc. 2) Seaside Control Panel, add ZnZincServerAdaptor, start the server. 3) Point browser to http://localhost:8080/magritte/editor. 4) Click âAddâ button. 5) View exception. Perhaps I should have just installed the Seaside group of Magritte3âs ConfigurationOfâ¦ > Do the tests run green, or is there already a problem with that? 1) Open Test runner 2) Select all tests with âMagritteâ in it. 3) 1922 run, 1898 passes, 0 skipped, 0 expected failures, 1 failures, 23 errors, 0 unexpected passes. Test in failure: MXXmlPersonTargetTest>>#testContainerElementCustom Test in error: All of MAStraitMementoTest (22 tests), and MXXmlPersonReferenceTest>>#testMultipleOption > I don't know anyone using the MADescriptionEditor, does that still work with other descriptions? Iâm new so Iâm currently breaking a lot. :P

Sept. 10, 2015