June 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Morph as floating palette?

by Stephan Eggermont

On 15-06-15 20:53, Stephan Eggermont wrote: > On 15-06-15 20:42, Hilaire wrote: >> setProperty: #morphicLayerNumber toValue: 5 And looks like https://vimeo.com/130781061 Stephan

June 15, 2015

Re: [Pharo-users] Morph as floating palette?

by Stephan Eggermont

On 15-06-15 20:42, Hilaire wrote: > setProperty: #morphicLayerNumber toValue: 5 Thanks, that works fine. Stephan

June 15, 2015

Re: [Pharo-users] Morph as floating palette?

by Hilaire

...and for example, use it as: window setProperty: #morphicLayerNumber toValue: 5. Hilaire Le 15/06/2015 20:19, Nicolai Hess a Ã©crit : > > #morphicLayerNumber > maybe? > > > > 2015-06-15 19:29 GMT+02:00 Stephan Eggermont <stephan(a)stack.nl > <mailto:stephan@stack.nl>>: > > How do I make sure a floating palette morph stays in front of all > of my application morphs (except the menu)? Do I have to manage > ordering myself? > > Stephan > > -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu

June 15, 2015

Re: [Pharo-users] NativeBoost nested structures

by Nicolai Hess

2015-06-15 17:14 GMT+02:00 Matthieu Lacaton <matthieu.lacaton(a)gmail.com>: > Hello everyone, > > I have a nested struct, let's say "struct1" which contains "struct2" which > contains an int field named "field". > > When I try to update the field from struct 1 directly I can't. What I mean > is if I do : "struct1 struct2 field: 4" for instance, the value in field is > not updated. Even if I inspect "struct1 struct2" and I manually set the > "field variable by doing : "self field: 4" then if I go back to my struct1 > and do "self struct2 field" the value has not been updated. > So basically the only way I have to update a field in a nested structure > is to recreate the second struct entirely : "struct1 struct2: (Struct2 new > field: 4)" and now it works. > > It seems odd because in C you can do "struct1.struct2.field = 4;" and it > works fine. > yes, self struct2 will create a copy of the struct2 and any change to struct2 value only applies to this copy. > > You can reproduce this with the NBTestNestedStructure class from > NativeBoost itself : > > | myStruct | > > myStruct := (NBTestNestedStructure new oneByte: (NBTestStructure1byte new > field: 1)). > Transcript show: myStruct oneByte field; cr. > myStruct oneByte field: 4. > Transcript show: myStruct oneByte field; cr. > myStruct oneByte: (NBTestStructure1byte new field: 4). > Transcript show: myStruct oneByte field; cr. > > For me the Transcript shows 1 1 4 whereas in my opinion it should show 1 4 > 4. > > So am I doing something wrong or is this some kind of a bug ? > I am not sure, I think there is no other way to handle this kind of nested structures. Are you bound to exactly this structure? If you can define the structure, you can use a nested structure that uses pointers instead of values: NBTestNestedStructure2>> fieldsDesc ^ #( NBTestStructure1byte* oneByte; int otherField ) Now you can create and access the innerstructure like this myStruct := (NBTestNestedStructure2 new oneByte: (NBTestStructure1byte externalNew field: 1)). myStruct oneByte field. " -> 1 " myStruct oneByte field: 4. myStruct oneByte field. " -> 4 " Whereas I don't know if the external memory is freed. > Thanks, > > Matthieu >

June 15, 2015

Re: [Pharo-users] Morph as floating palette?

by Nicolai Hess

#morphicLayerNumber maybe? 2015-06-15 19:29 GMT+02:00 Stephan Eggermont <stephan(a)stack.nl>: > How do I make sure a floating palette morph stays in front of all of my > application morphs (except the menu)? Do I have to manage ordering myself? > > Stephan >

June 15, 2015

Understanding edge connections and tree layout (it was Re: Visualizing a repository tree)

by Offray Vladimir Luna CÃ¡rdenas

Hi all. Is me again :), I have being fighting all this morning trying to bet a better understanding of edge connections and tree layouts. I'm making some progress, but still I don't grasp it. At [1] you can find my starting example. So far, so good, so I created my own variation for my own data at [2]. My main issue is the #connectFrom message argument. If you uncomment the last line of [1] you will see that sending the #superclass message gives me an object that is of the same kind that the ones have been added to the view previously and I imagine that the reason they can be connected in a tree. With the example at [2] the message [#parents first] gives me a fossil commit object, but if I ran the code, the nodes are unconnected. What I'm missing? [1] http://ws.stfx.eu/DK3VNXBVAHXF [2] http://ws.stfx.eu/DHF4VIR8TSPC Thanks, Offray On 15/06/15 06:47, Offray Vladimir Luna CÃ¡rdenas wrote: > Hi Peter, > > Thanks for your quick answer. I was pretty curious about trying to > implement some of this ideas, but only until today I had the proper > time to do it. I ran your code and now I'm trying to translate the > ideas on it to my problem: Drawing a tree for the story of a fossil > repository. > > First, using the procedure at [1] I was able to export a fossil commit > repo history as Json and by running the script at [2] I was able to > get a small set of dots, which represent dictionaries with all commit > data, including ancestors for each node, like the attached screenshot > shows. In the video at [3] at 1:06 min, seems that lays the key for my > visualization, but for that I need to create a fossil commit object > that can understand the #ancestor message. Because I already have them > as dictionaries thanks to NeoJson, seems that I'm really close to get > the visualization I'm looking for. I hope to work on it this morning > and return to the list with data visualizations or more questions. > > > [1] > http://stackoverflow.com/questions/30577090/how-to-export-fossil-scm-timeli… > [2] http://ws.stfx.eu/A5C8JJMA2HUK > [3] https://vimeo.com/116886609 > > Cheers, > > Offray > > > > On 02/06/15 05:09, Peter UhnÃ¡k wrote: >> HI Offray, >> >> I gave it a quick bash and come up with the following code. It's just >> a prototype and could be greatly simplified. >> >> - MCVersionInfo ancestors for whatever reason returned empty array >> down the line (so its cut off at the end), but I didn't investigate >> the problem >> - edge building and possibly ancestor retrieval could be simplified >> with builders; I think RTMondrian has methods for it but can't >> remember exactly (agilevisualization mentioned RTGraphBuilder but >> that has been removed to my knowledge) >> >> ~~~~~~~~~~~~~~~ >> mc := MCSmalltalkhubRepository allInstances detect: [ :m | m project >> = 'Roassal2' ]. >> >> root := mc versionInfoFromFileNamed: mc readableFileNames first. >> >> family := Set new. >> retriever := nil. >> retriever := [ :child | >> family add: child. >> child ancestors do: [ :a | retriever value: a ] >> ]. >> retriever value: root. >> obs := family asGroup. >> >> v := RTView new. >> es := RTEllipse new size: 15; color: Color blue; elementsOn: obs. >> v addAll: es. >> >> edges := RTEdge >> buildEdgesFromObjects: obs >> from: #yourself >> toAll: #ancestors >> using: (RTArrowedLine new withShorterDistanceAttachPoint; color: >> Color red) >> scope: es. >> v addAll: edges. >> >> es @ RTDraggable. >> es @ (RTLabelled new text: [ :m | m nameWithout: 'Roassal2' ]). >> >> v @ RTDraggableView. >> v @ RTZoomableView. >> >> RTDominanceTreeLayout new >> verticalGap: 30; >> horizontalGap: 15; >> on: es. >> >> v open >> ~~~~~~~~~~~~~~~~ >> >> >> >> Cheers, >> Peter >> â >> >> On Tue, Jun 2, 2015 at 5:39 AM, Offray Vladimir Luna CÃ¡rdenas >> <offray(a)riseup.net <mailto:offray@riseup.net>> wrote: >> >> Hi, >> >> On a closer detail, seems that [1] contains the starting point >> I'm looking for. I'll keep you posted and of course any other >> approach will be listened. >> >> [1] >> https://dl.dropboxusercontent.com/u/31543901/AgileVisualization/Roassal/010… >> >> Cheers, >> >> Offray >> >> >> On 01/06/15 22:04, Offray Vladimir Luna CÃ¡rdenas wrote: >> >> Hi all, >> >> I had asked a similar question before with no much advances, >> but today I made a discovery that can improve the things a >> lot: how to export timeline data as structured JSON [1] (and >> of course this open the possibility to work with it on >> Pharo). Now I would like to graph the data as a tree with >> forks, merges and dates and authors of commits. I have seen >> chronia, but seems overkill for this feature (and is >> integrated with CVS only). >> >> [1] >> http://stackoverflow.com/questions/30577090/how-to-export-fossil-scm-timeli… >> >> As usual, any pointer on how to get this going will be >> greatly appreciated and I will give feedback to the community >> on how to do it. >> >> Cheers, >> >> Offray >> >> >> >> >> >

June 15, 2015

Morph as floating palette?

by Stephan Eggermont

How do I make sure a floating palette morph stays in front of all of my application morphs (except the menu)? Do I have to manage ordering myself? Stephan

June 15, 2015

NativeBoost nested structures

by Matthieu Lacaton

Hello everyone, I have a nested struct, let's say "struct1" which contains "struct2" which contains an int field named "field". When I try to update the field from struct 1 directly I can't. What I mean is if I do : "struct1 struct2 field: 4" for instance, the value in field is not updated. Even if I inspect "struct1 struct2" and I manually set the "field variable by doing : "self field: 4" then if I go back to my struct1 and do "self struct2 field" the value has not been updated. So basically the only way I have to update a field in a nested structure is to recreate the second struct entirely : "struct1 struct2: (Struct2 new field: 4)" and now it works. It seems odd because in C you can do "struct1.struct2.field = 4;" and it works fine. You can reproduce this with the NBTestNestedStructure class from NativeBoost itself : | myStruct | myStruct := (NBTestNestedStructure new oneByte: (NBTestStructure1byte new field: 1)). Transcript show: myStruct oneByte field; cr. myStruct oneByte field: 4. Transcript show: myStruct oneByte field; cr. myStruct oneByte: (NBTestStructure1byte new field: 4). Transcript show: myStruct oneByte field; cr. For me the Transcript shows 1 1 4 whereas in my opinion it should show 1 4 4. So am I doing something wrong or is this some kind of a bug ? Thanks, Matthieu

June 15, 2015

Status of Twitter (api/analysis/visualization) in Pharo?

by MartinW

Hi, I want to do some interaction with the Twitter API (retrieve tweets based on hashtags mostly) and visualize results of some analyses using Roassal. I saw there are some projects on Smalltalkhub, but none has much/any/up-to-date documentation. What is the current status of these projects? Does anyone know about any up-to-date documentation or examples? I am thankful for all hints. Best regards, Martin. -- View this message in context: http://forum.world.st/Status-of-Twitter-api-analysis-visualization-in-Pharo… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 15, 2015

Re: [Pharo-users] Visualizing a repository tree

by Offray Vladimir Luna CÃ¡rdenas

Hi Peter, Thanks for your quick answer. I was pretty curious about trying to implement some of this ideas, but only until today I had the proper time to do it. I ran your code and now I'm trying to translate the ideas on it to my problem: Drawing a tree for the story of a fossil repository. First, using the procedure at [1] I was able to export a fossil commit repo history as Json and by running the script at [2] I was able to get a small set of dots, which represent dictionaries with all commit data, including ancestors for each node, like the attached screenshot shows. In the video at [3] at 1:06 min, seems that lays the key for my visualization, but for that I need to create a fossil commit object that can understand the #ancestor message. Because I already have them as dictionaries thanks to NeoJson, seems that I'm really close to get the visualization I'm looking for. I hope to work on it this morning and return to the list with data visualizations or more questions. [1] http://stackoverflow.com/questions/30577090/how-to-export-fossil-scm-timeli… [2] http://ws.stfx.eu/A5C8JJMA2HUK [3] https://vimeo.com/116886609 Cheers, Offray On 02/06/15 05:09, Peter UhnÃ¡k wrote: > HI Offray, > > I gave it a quick bash and come up with the following code. It's just > a prototype and could be greatly simplified. > > - MCVersionInfo ancestors for whatever reason returned empty array > down the line (so its cut off at the end), but I didn't investigate > the problem > - edge building and possibly ancestor retrieval could be simplified > with builders; I think RTMondrian has methods for it but can't > remember exactly (agilevisualization mentioned RTGraphBuilder but that > has been removed to my knowledge) > > ~~~~~~~~~~~~~~~ > mc := MCSmalltalkhubRepository allInstances detect: [ :m | m project = > 'Roassal2' ]. > > root := mc versionInfoFromFileNamed: mc readableFileNames first. > > family := Set new. > retriever := nil. > retriever := [ :child | > family add: child. > child ancestors do: [ :a | retriever value: a ] > ]. > retriever value: root. > obs := family asGroup. > > v := RTView new. > es := RTEllipse new size: 15; color: Color blue; elementsOn: obs. > v addAll: es. > > edges := RTEdge > buildEdgesFromObjects: obs > from: #yourself > toAll: #ancestors > using: (RTArrowedLine new withShorterDistanceAttachPoint; color: Color > red) > scope: es. > v addAll: edges. > > es @ RTDraggable. > es @ (RTLabelled new text: [ :m | m nameWithout: 'Roassal2' ]). > > v @ RTDraggableView. > v @ RTZoomableView. > > RTDominanceTreeLayout new > verticalGap: 30; > horizontalGap: 15; > on: es. > > v open > ~~~~~~~~~~~~~~~~ > > > > Cheers, > Peter > â > > On Tue, Jun 2, 2015 at 5:39 AM, Offray Vladimir Luna CÃ¡rdenas > <offray(a)riseup.net <mailto:offray@riseup.net>> wrote: > > Hi, > > On a closer detail, seems that [1] contains the starting point I'm > looking for. I'll keep you posted and of course any other approach > will be listened. > > [1] > https://dl.dropboxusercontent.com/u/31543901/AgileVisualization/Roassal/010… > > Cheers, > > Offray > > > On 01/06/15 22:04, Offray Vladimir Luna CÃ¡rdenas wrote: > > Hi all, > > I had asked a similar question before with no much advances, > but today I made a discovery that can improve the things a > lot: how to export timeline data as structured JSON [1] (and > of course this open the possibility to work with it on Pharo). > Now I would like to graph the data as a tree with forks, > merges and dates and authors of commits. I have seen chronia, > but seems overkill for this feature (and is integrated with > CVS only). > > [1] > http://stackoverflow.com/questions/30577090/how-to-export-fossil-scm-timeli… > > As usual, any pointer on how to get this going will be greatly > appreciated and I will give feedback to the community on how > to do it. > > Cheers, > > Offray > > > > >

June 15, 2015