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

Re: [Pharo-dev] spec TreeNodeModel displayString

by Christophe Demarey

Sadly, it is not possible to use tree>>#displayBlock: directly because the tree is initialized with: columns := { TreeColumnModel new displayBlock: [:node | (self wrapItem: node content) ] } asValueHolder. TreeModel>>#wrapItem: anItem ^ displayBlock value cull: anItem cull: self As you can see, it is then impossible to get a reference to the node. You only get the node content and a reference to the tree itself. Le 2 juil. 2015 Ã 14:01, Peter UhnÃ¡k a Ã©crit : > Or you can use displayBlock: (and root: and children:) directly on the TreeModel. > > tree := self newTree. > > tree > roots: { root1 root2 }; > displayBlock: [ :node | node label ]; > childrenBlock: [ :node | node children ]; > iconBlock: [ :node | node icon ]. > > I'm not sure if direct creation of TreeColumnModel/TreeNodeModel is advised considering TreeModel is trying to hide it. > > Peter > > On Thu, Jul 2, 2015 at 1:33 PM, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > > Le 30 juin 2015 Ã 16:01, Christophe Demarey a Ã©crit : > > > Hi, > > > > I have a TreeModel with different kinds of TreeNodeModel and I would like to get a customizable display string depending on the node type. > > It looks like it is not possible to dispatch on nodes in a display block because it only takes the item (node content) and the tree as parameter. > > It is strange as I expect that to be a standard feature. Do I miss something? > > I found a workaround and it looks like a missing feature in Spec TreeModel. > You can customize the display by settings columns on the tree like this: > > self newTree > columns: { TreeColumnModel new > displayBlock: [:node | node label ] }; >

July 2, 2015

Re: [Pharo-dev] Blog post on the new Fast Table

by phil＠highoctane.be

Yes, very interesting work. We need to get the "slow feel" of the environment go away, thanks for working on that, Esteban. Is this something that would also address the slowness when we click on "Object" in Nautilus? Phil On Thu, Jul 2, 2015 at 1:59 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > On 02-07-15 12:07, Esteban Lorenzano wrote: > >> Hi, >> >> I made a small blog post explaining a bit of the new fast table. >> This is to encourage you to start using it and help me finish it :) >> >> http://smallworks.eu/web/blog/2015-07-02-fast-table-for-pharo >> > > Nice! > > I noticed that a startDrag: only happens when there is already a > selection. If the selection is empty you could select the element under the > hand as the selection, unless a modifier key is pressed telling you that a > multiple selection is supposed to happen instead of a drag. > > Stephan > > > >

July 2, 2015

[Pharo5] Update 150!

by Marcus Denker

Hi, We have update 150! https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-5-Publish/ <https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-5-Publish/> On the issue tracker, we already closed 451 issues for Pharo5. Marcus

July 2, 2015

[pharo-project/pharo-core]

by GitHub

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

July 2, 2015

[pharo-project/pharo-core] 36c2d7: 50150

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 36c2d701cd9d9cd1f7bab3edda5cced601ab64c3 https://github.com/pharo-project/pharo-core/commit/36c2d701cd9d9cd1f7bab3ed… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-07-02 (Thu, 02 Jul 2015) Changed paths: A Collections-Sequenceable.package/LinkedList.class/instance/enumerating/collect_thenReject_.st A Jobs.package/JobTest.class/instance/tests/testCurrentJob.st A Jobs.package/JobTest.class/instance/tests/testLookupJob.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50149.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50150.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50149.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50150.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50150 15881 Add a method to lookup a Job in the chain of parent jobs https://pharo.fogbugz.com/f/cases/15881 15883 LinkedList>>#collect:thenReject: is slow https://pharo.fogbugz.com/f/cases/15883 http://files.pharo.org/image/50/50150.zip

July 2, 2015

Re: [Pharo-dev] spec TreeNodeModel displayString

by Peter UhnÃ¡k

Or you can use displayBlock: (and root: and children:) directly on the TreeModel. tree := self newTree. tree roots: { root1 root2 }; displayBlock: [ :node | node label ]; childrenBlock: [ :node | node children ]; iconBlock: [ :node | node icon ]. I'm not sure if direct creation of TreeColumnModel/TreeNodeModel is advised considering TreeModel is trying to hide it. Peter On Thu, Jul 2, 2015 at 1:33 PM, Christophe Demarey < Christophe.Demarey(a)inria.fr> wrote: > > Le 30 juin 2015 Ã 16:01, Christophe Demarey a Ã©crit : > > > Hi, > > > > I have a TreeModel with different kinds of TreeNodeModel and I would > like to get a customizable display string depending on the node type. > > It looks like it is not possible to dispatch on nodes in a display block > because it only takes the item (node content) and the tree as parameter. > > It is strange as I expect that to be a standard feature. Do I miss > something? > > I found a workaround and it looks like a missing feature in Spec TreeModel. > You can customize the display by settings columns on the tree like this: > > self newTree > columns: { TreeColumnModel new > displayBlock: [:node | node label ] };

July 2, 2015

Re: [Pharo-dev] Blog post on the new Fast Table

by Stephan Eggermont

On 02-07-15 12:07, Esteban Lorenzano wrote: > Hi, > > I made a small blog post explaining a bit of the new fast table. > This is to encourage you to start using it and help me finish it :) > > http://smallworks.eu/web/blog/2015-07-02-fast-table-for-pharo Nice! I noticed that a startDrag: only happens when there is already a selection. If the selection is empty you could select the element under the hand as the selection, unless a modifier key is pressed telling you that a multiple selection is supposed to happen instead of a drag. Stephan

July 2, 2015

Review needed: 15072 Senders and implementors do not work when one parameter is a string containing â:'

by Marcus Denker

15072 Senders and implementors do not work when one parameter is a string containing â:' https://pharo.fogbugz.com/f/cases/15072

July 2, 2015

Review needed: 14785 intersecting not overlapping rectangles should returen an empty rectangle

by Marcus Denker

Hi, 14785 intersecting not overlapping rectangles should returen an empty rectangle https://pharo.fogbugz.com/f/cases/14785/

July 2, 2015

Re: [Pharo-dev] spec TreeNodeModel displayString

by Christophe Demarey

Le 30 juin 2015 Ã 16:01, Christophe Demarey a Ã©crit : > Hi, > > I have a TreeModel with different kinds of TreeNodeModel and I would like to get a customizable display string depending on the node type. > It looks like it is not possible to dispatch on nodes in a display block because it only takes the item (node content) and the tree as parameter. > It is strange as I expect that to be a standard feature. Do I miss something? I found a workaround and it looks like a missing feature in Spec TreeModel. You can customize the display by settings columns on the tree like this: self newTree columns: { TreeColumnModel new displayBlock: [:node | node label ] };

July 2, 2015