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

Re: [Pharo-users] Environment-independent styler?

by Marcus Denker

> On 17 Jun 2015, at 18:54, Martin Dias <tinchodias(a)gmail.com> wrote: > > Hello, > > Suppose that you want to show the diff between the source code of two methods. In the case that both methods are in the same class, and that such class is present in the system, then no problem: In a DiffModel, one can set a context to the smalltalk syntax styler and get a nice output. > > DiffModel new > leftText: (Point >> #x) sourceCode; > rightText: (Point >> #y) sourceCode; > contextClass: Point; > openWithSpec. > > <Screen Shot 2015-06-17 at 18.33.22.png> > > But what happens in the case that the class does not exist in the system? > > If one doesn't set any context to the styler, then the string will be shown all in black, which is not nice. A partial solution could be to set Object as a context, then the styler will color the code, but instance variables are in red: > > DiffModel new > leftText: (Point >> #x) sourceCode; > rightText: (Point >> #y) sourceCode; > contextClass: Object; > openWithSpec. > > <Screen Shot 2015-06-17 at 18.33.27.png> > > Which is also not nice. In my opinion, there should be a styler that just colors the code following the syntax, without checking if the variables or classes are present in the system. It would be an environment-independent styler. > > What do you recommend to implement this? I guess it should be easy to subclass SHTextStylerST80 and override some methods to do not check anything in the environment. > > What's your opinion? > Right now we have the problem that we have 3 Stylersâ¦ (for the old text model one based on Shout, one AST, and one for TxText based on the AST. Ah, and Rubric subclasses the shout one, too. Which means 4. One question is: could a styler fall back onto a being environment independent as soon as the environment is not set? Marcus

June 22, 2015

Re: [Pharo-users] About generating chapters with Pillar/Pier tools

by HernÃ¡n Morales Durand

Thank you Ben for taking the time to read. Do you (or anyone) mind to share which command do you use to convert from Pillar generated .tex to .pdf in Linux or OS/X? Cheers, HernÃ¡n 2015-06-21 12:15 GMT-03:00 Ben Coman <btc(a)openinworld.com>: > > > On Sun, Jun 21, 2015 at 11:21 AM, HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> wrote: >> >> >> Now I am the only one generating PDF with Pillar in Windows? >> > > Back when I did a bit on Pillar, difficulties with latex was part of the > reason I moved to OSX. > cheers -ben >

June 22, 2015

Re: [Pharo-users] Any YAML parser?

by Peter UhnÃ¡k

I suggest using http://forum.world.st/ for searching through mailing lists; using Google is often hit-or-miss (which even with all its neural networks and tracking me everywhere is still after years suggesting Pharaoh...) Anyway, there seems to be something http://forum.world.st/PetitYAML-td4803677.html If you are not familiar with PetitParser, there's a chapter about it in PBE2 ( http://pharobooks.gforge.inria.fr/PharoByExampleTwo-Eng/latest/PetitParser.… ) Peter On Sat, Jun 20, 2015 at 4:10 PM, Julien Delplanque <julien(a)tamere.eu> wrote: > Hi everybody, > > I googled a bit for a YAML parser in Pharo but I didn't found anything. > > Does anybody wrote a YAML parser for Pharo? > > Regards, > Julien > >

June 21, 2015

Re: [Pharo-users] Status of Twitter (api/analysis/visualization) in Pharo?

by MartinW

Offray wrote > Ok. Let me know what happens. Hi Offray, I got the scraping, importing and visualization working. Not sure, what went wrong the first time. I found one little bug, when the avatar was a jpeg. It can be solved by changing the following lines in TwitterProfile>>scrapAvatarFrom: from: ((avatarUrl asLowercase endsWith: '.jpeg') or: (avatarUrl asLowercase endsWith: '.jpg')) ifTrue: [ avatarImage := ZnEasy get: avatarUrl. "(PNGReadWriter on: avatarImage ) nextPutImage: (JPEGReadWriter on: avatarImage )" ]. to: ((avatarUrl asLowercase endsWith: '.jpeg') or: (avatarUrl asLowercase endsWith: '.jpg')) ifTrue: [avatarImage := ZnEasy getJpeg: avatarUrl.]. Very nice result. Thank you a lot for sharing it! 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 21, 2015

Re: [Pharo-users] crm in pharo?

by Ben Coman

I only know of Bahman planning to do an ERP [1], which anyway is different to a CRM. cheers -ben [1] http://www.bahmanm.com/blogs/a-new-platform-for-business-app-development On Sun, Jun 21, 2015 at 9:01 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Is there any CRM (customer relationship manager) library for Pharo? > > Cheers, > Tudor > > -- > www.tudorgirba.com > > "Every thing has its own flow"

June 21, 2015

Re: [Pharo-users] About generating chapters with Pillar/Pier tools

by Ben Coman

On Sun, Jun 21, 2015 at 11:21 AM, HernÃ¡n Morales Durand < hernan.morales(a)gmail.com> wrote: > > > Now I am the only one generating PDF with Pillar in Windows? > Back when I did a bit on Pillar, difficulties with latex was part of the reason I moved to OSX. cheers -ben

June 21, 2015

crm in pharo?

by Tudor Girba

Hi, Is there any CRM (customer relationship manager) library for Pharo? Cheers, Tudor -- www.tudorgirba.com "Every thing has its own flow"

June 21, 2015

About generating chapters with Pillar/Pier tools

by HernÃ¡n Morales Durand

Hello, I have experimented several dissapointing errors when working with updated Pillar tools. I am not doing anything special besides working under Windows. Apparently the Pillar CommandLineHandler is not working because OSEnvironment exception (Windows 8.1). When executing Pharo.exe Pillar.image export --to=html BioPharo.pier The attached exception raises. This happens in all the images from: https://ci.inria.fr/pharo-contribution/job/Pillar/PHARO=40,VERSION=stable,V… Pharo4.0 (Latest update: #40614) https://ci.inria.fr/pharo-contribution/job/Pillar/PHARO=40,VERSION=developm… Pharo4.0 (Latest update: #40614) https://ci.inria.fr/pharo-contribution/job/Pillar/PHARO=50,VERSION=stable,V… Pharo5.0 Latest update: #50124 Changing the method #baseDirectory to use %CD% environment variable doesn't fix it even when it works in command line: c:\MySmalltalkProjects\Pillar\pharo-vm>echo %PWD% %PWD% c:\MySmalltalkProjects\Pillar\pharo-vm>echo %CD% c:\MySmalltalkProjects\Pillar\pharo-vm The solution I found was to replace the OSEnvironment line with FileSystem workingDirectory as suggested at: https://pharo.fogbugz.com/f/cases/15356/Pillar-command-line-script-doesn-t-… About instructions given here https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… you do not need MinGW to export a Pier chapter. See here https://github.com/biosmalltalk/biopharo/blob/develop/doc/pier2tex.bat for an example Another (worst) situation happened when I wanted to convert a generated LaTeX to PDF. I had to remove all tables, annotations and notes from the .pier file because errors reported in pdfLaTeX . For tables : ! Undefined control sequence. l.176 \toprule For notes (i.e. @@note ) ! LaTeX Error: Environment note undefined. See the LaTeX manual or LaTeX Companion for explanation. Type H <return> for immediate help. ... l.178 \begin{note} Finally generated PDF looks different from previous versions. Previous Pillar version: https://github.com/biosmalltalk/biopharo/blob/develop/doc/BioPharo.pier.pdf Current Pillar version (>= 0.56) : https://github.com/biosmalltalk/biopharo/blob/develop/doc/BioPharo.pdf Now I am the only one generating PDF with Pillar in Windows? HernÃ¡n

June 21, 2015

Re: [Pharo-users] Chaning node colors in a RTMondrian view (It was Re: Understanding edge connections and tree layout)

by Alexandre Bergel

Hi Offray, Rather easy. Simply use a new shape. For example: -=-=-=-= b := RTMondrian new. b shape circle size: [ :cls | cls numberOfMethods log * 10 ]; color: (Color red alpha: 0.5). b nodes: RTObject withAllSubclasses. b layout flow. b -=-=-=-= Another example: -=-=-=-= classes := RTObject withAllSubclasses. largestNumberOfMethods := (classes collect: #numberOfMethods) max. colorNormalizer := RTMultiLinearColor new colors: (ColorPalette sequential colors: 8 scheme: 'Reds'); command: [ :cls | cls numberOfMethods / largestNumberOfMethods ]. b := RTMondrian new. b shape circle size: [ :cls | cls numberOfMethods log * 10 ]; color: colorNormalizer. b nodes: classes. b layout flow. b -=-=-=-= Many more example are available in the mondrian example class. Have you tried: RTMondrianExample inspect ? Cheers, Alexandre > On Jun 20, 2015, at 9:03 PM, Offray Vladimir Luna CÃ¡rdenas <offray(a)riseup.net> wrote: > > Hi again :), > > I would like to start a new exploration: How to change the color of the nodes in the RTMondrian view. The examples in the agile visualization book are with RTView, and I have seen some examples at the object profile gallery, but I would like to start with something simpler. So if I have the code running at [1], how can I change the color of the nodes on the tree to reflect some property of the node? > > [1] http://ws.stfx.eu/Q4I6UO67ZM4P > > Cheers, > > Offray > > Ps: By the way, inspired by Wolfram's Tweet a Program (https://twitter.com/wolframtap/) and Sven's elegant code examples, I'm trying to "package and share" some examples of the knowledge we build here to the external world in Twitter with the hashtag #PharoTip. Something like See for example: https://twitter.com/offrayLC/status/612409697975599104 > > On 20/06/15 13:44, Offray Vladimir Luna CÃ¡rdenas wrote: >> Thanks Alexandre and Nicolai, >> >> Now with a modified version of the script at http://ws.stfx.eu/AOPPDKEGTVFG I get the result below at the left, which has practically the same topology of the original fossil timeline tree below at right. Now I would like to change the edge length so it can convey commit date information (when commit happens) and look even more similar. I will make some test with RTMultiLine and orthoVertical shapes for edges, but any pointer to edge length variation and node distance examples will be greatly appreciated. >> >> Finally about why "parents" instead of "parent" I try to use the same terms in the Json file export for the properties imported in the object. I imagine that if a commit is a merge of several branches, it could have several parents. I will test with more complicated trees to test if this case prompts. >> >> <Mail Attachment.png><Mail Attachment.png> >> >> >> Cheers, >> >> Offray >> >> >> >> On 20/06/15 12:46, Alexandre Bergel wrote: >>> Hi Offray, >>> >>> The problem is rather easy to solve. Consider this script: >>> >>> -=-=-=-=-=-=-=-=-=-=-=-= >>> timeline := FossilTimeline new. >>> timeline importFromUrl: ' >>> http://mutabit.com/deltas/repos.fossil/piamed/libro/doc/tip/Libro/timeline-… >>> '. >>> >>> >>> "Visualization" >>> view := RTMondrian new. >>> view nodes: timeline commits. >>> view edges >>> connectFrom: #parents. >>> view layout tree. >>> view. >>> -=-=-=-=-=-=-=-=-=-=-=-= >>> >>> Apparently, each fossil commit has a parent. The parent could be nil (which is okay). >>> Why do you call the variable âparentsâ and not âparentâ ? >>> >>> Cheers, >>> Alexandre >>> >>> >>>> On Jun 19, 2015, at 9:41 AM, Offray Vladimir Luna CÃ¡rdenas <offray(a)riseup.net> >>>> wrote: >>>> >>>> Alexandre, >>>> >>>> Could you please run this: >>>> >>>> ~~~~~~~~~ >>>> "Adapted from: >>>> https://vimeo.com/116886609 >>>> " >>>> | view timeline | >>>> >>>> "Loading package for working with fossil" >>>> "Integration with external tools" >>>> Gofer new >>>> smalltalkhubUser: 'Offray' project: 'Grafoscopio'; >>>> package: 'Grafoscopio-ExternalTools'; >>>> load. >>>> >>>> "Extracting data" >>>> timeline := FossilTimeline new. >>>> timeline importFromUrl: ' >>>> http://mutabit.com/deltas/repos.fossil/piamed/libro/doc/tip/Libro/timeline-… >>>> '. >>>> >>>> "Visualization" >>>> view := RTMondrian new. >>>> view nodes: timeline commits. >>>> view edges >>>> connectFrom: [#parents first]. >>>> view layout tree. >>>> view. >>>> "(timeline commits at: 1) parents first" >>>> ~~~~~~~~~ >>>> >>>> At the end you will get a set of squares visualized like this ones: >>>> >>>> <jcjdcjje..png> >>>> ^Up Graphic 1: Trying to understand edges. >>>> >>>> These squares are representations of FossilCommits objects imported from a Json file, and the "connectFrom: [#parents first]" is the line I'm having problems with. "#parents first" is the message I send to each node to know its parents in that very collection of commits, so I imagined that if I put that as the block argument for "connectFrom" I would get a nice tree, similar to the graphic 2 below. I don't get what's happening here or what I'm missing. >>>> >>>> <cfbfiagc..png> >>>> ^ Up Graphic 2: A nicely drawn mondrian tree layout for RTLayout. >>>> >>>> Any help on how to get tree like visualizations for this Fossil objects would be greatly appreciated. >>>> >>>> Thanks, >>>> >>>> Offray >>>> >>>> Ps: Something was happening with ws.stfx.eu this morning at 7:00 (GMT -5) and trying to publish a workspace gives a 500 error. >>>> >>>> >>>> On 16/06/15 16:08, Alexandre Bergel wrote: >>>> >>>>> I am not really following. Hard to guess here. >>>>> >>>>> Can you make the image accessible for me? I can then have a closer look at it. >>>>> >>>>> Alexandre >>>>> >>>>> >>>>> >>>>> >>>>>> On Jun 15, 2015, at 3:18 PM, Offray Vladimir Luna CÃ¡rdenas <offray(a)riseup.net> >>>>>> >>>>>> wrote: >>>>>> >>>>>> 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 >>>>>>>> ~~~~~~~~~~~~~~~~ >>>>>>>> >>>>>>>> >>>>>>>> <Mail Attachment.png> >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Peter >>>>>>>> â >>>>>>>> >>>>>>>> On Tue, Jun 2, 2015 at 5:39 AM, Offray Vladimir Luna CÃ¡rdenas >>>>>>>> >>>>>>>> <offray(a)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 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >> > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 21, 2015

Re: [Pharo-users] Understanding edge connections and tree layout (it was Re: Visualizing a repository tree)

by Alexandre Bergel

Hi I do not recommend to use Mondrian for doing what you need. Actually, I suggest to make your own layout. You may want to check the following code example: -=-=-=-=-=-=-=-=-= classes := RTShape withAllSubclasses. oldestAge := (classes collect: #ageInDays) max. v := RTView new. v @ RTDraggableView. classes doWithIndex: [ :c :index | elements := RTEllipse new elementsOn: c methods. v addAll: elements. RTMetricNormalizer new elements: elements; normalizeX: #ageInDaysAsInteger min: 0 max: 200 minValue: 0 maxValue: oldestAge. elements translateBy: 0 @ (index * 10). RTEdgeBuilder new view: v; linkElements: elements. ]. v -=-=-=-=-=-=-=-=-= I guess it is kind of close of what you need. Cheers, Alexandre > On Jun 20, 2015, at 3:44 PM, Offray Vladimir Luna CÃ¡rdenas <offray(a)riseup.net> wrote: > > Thanks Alexandre and Nicolai, > > Now with a modified version of the script at http://ws.stfx.eu/AOPPDKEGTVFG I get the result below at the left, which has practically the same topology of the original fossil timeline tree below at right. Now I would like to change the edge length so it can convey commit date information (when commit happens) and look even more similar. I will make some test with RTMultiLine and orthoVertical shapes for edges, but any pointer to edge length variation and node distance examples will be greatly appreciated. > > Finally about why "parents" instead of "parent" I try to use the same terms in the Json file export for the properties imported in the object. I imagine that if a commit is a merge of several branches, it could have several parents. I will test with more complicated trees to test if this case prompts. > > <abjfehfd..png><jfbdfbaj..png> > > > Cheers, > > Offray > > > > On 20/06/15 12:46, Alexandre Bergel wrote: >> Hi Offray, >> >> The problem is rather easy to solve. Consider this script: >> >> -=-=-=-=-=-=-=-=-=-=-=-= >> timeline := FossilTimeline new. >> timeline importFromUrl: ' >> http://mutabit.com/deltas/repos.fossil/piamed/libro/doc/tip/Libro/timeline-… >> '. >> >> >> "Visualization" >> view := RTMondrian new. >> view nodes: timeline commits. >> view edges >> connectFrom: #parents. >> view layout tree. >> view. >> -=-=-=-=-=-=-=-=-=-=-=-= >> >> Apparently, each fossil commit has a parent. The parent could be nil (which is okay). >> Why do you call the variable âparentsâ and not âparentâ ? >> >> Cheers, >> Alexandre >> >> >>> On Jun 19, 2015, at 9:41 AM, Offray Vladimir Luna CÃ¡rdenas <offray(a)riseup.net> >>> wrote: >>> >>> Alexandre, >>> >>> Could you please run this: >>> >>> ~~~~~~~~~ >>> "Adapted from: >>> https://vimeo.com/116886609 >>> " >>> | view timeline | >>> >>> "Loading package for working with fossil" >>> "Integration with external tools" >>> Gofer new >>> smalltalkhubUser: 'Offray' project: 'Grafoscopio'; >>> package: 'Grafoscopio-ExternalTools'; >>> load. >>> >>> "Extracting data" >>> timeline := FossilTimeline new. >>> timeline importFromUrl: ' >>> http://mutabit.com/deltas/repos.fossil/piamed/libro/doc/tip/Libro/timeline-… >>> '. >>> >>> "Visualization" >>> view := RTMondrian new. >>> view nodes: timeline commits. >>> view edges >>> connectFrom: [#parents first]. >>> view layout tree. >>> view. >>> "(timeline commits at: 1) parents first" >>> ~~~~~~~~~ >>> >>> At the end you will get a set of squares visualized like this ones: >>> >>> <jcjdcjje..png> >>> ^Up Graphic 1: Trying to understand edges. >>> >>> These squares are representations of FossilCommits objects imported from a Json file, and the "connectFrom: [#parents first]" is the line I'm having problems with. "#parents first" is the message I send to each node to know its parents in that very collection of commits, so I imagined that if I put that as the block argument for "connectFrom" I would get a nice tree, similar to the graphic 2 below. I don't get what's happening here or what I'm missing. >>> >>> <cfbfiagc..png> >>> ^ Up Graphic 2: A nicely drawn mondrian tree layout for RTLayout. >>> >>> Any help on how to get tree like visualizations for this Fossil objects would be greatly appreciated. >>> >>> Thanks, >>> >>> Offray >>> >>> Ps: Something was happening with ws.stfx.eu this morning at 7:00 (GMT -5) and trying to publish a workspace gives a 500 error. >>> >>> >>> On 16/06/15 16:08, Alexandre Bergel wrote: >>> >>>> I am not really following. Hard to guess here. >>>> >>>> Can you make the image accessible for me? I can then have a closer look at it. >>>> >>>> Alexandre >>>> >>>> >>>> >>>> >>>>> On Jun 15, 2015, at 3:18 PM, Offray Vladimir Luna CÃ¡rdenas <offray(a)riseup.net> >>>>> >>>>> wrote: >>>>> >>>>> 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 >>>>>>> ~~~~~~~~~~~~~~~~ >>>>>>> >>>>>>> >>>>>>> <Mail Attachment.png> >>>>>>> >>>>>>> Cheers, >>>>>>> Peter >>>>>>> â >>>>>>> >>>>>>> On Tue, Jun 2, 2015 at 5:39 AM, Offray Vladimir Luna CÃ¡rdenas >>>>>>> >>>>>>> <offray(a)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 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 21, 2015