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

Re: [Pharo-users] Pharo Video Tutorial: Package Tags

by Thierry Goubier

Le 04/06/2015 21:30, stepharo a Ã©crit : > Guys > > I would not use sub-packages. Think about newbies please. > We have packages and tags and ideally I would remove tags but we will > not because else people will cry. I would cry because I remember Pharo going through the RPackage without tags idea and how it was killed and replaced by RPackage + Tags. (It's there somewhere in AltBrowser github history, along with the Spec version of AltBrowser... looked and felt exactly like today's packageName + tags, by the way ) Thierry > > Stef > > Le 3/6/15 12:30, Sergio Fedi a Ã©crit : >> Since Tags have a different behaviour than Packages, I think we should. >> (specially when adding comments, which Packages support and Tags don't) >> >> â > > > >

June 4, 2015

Re: [Pharo-users] Pharo Video Tutorial: Package Tags

by stepharo

Guys I would not use sub-packages. Think about newbies please. We have packages and tags and ideally I would remove tags but we will not because else people will cry. Stef Le 3/6/15 12:30, Sergio Fedi a Ã©crit : > Since Tags have a different behaviour than Packages, I think we should. > (specially when adding comments, which Packages support and Tags don't) > > â

June 4, 2015

collectionDo: vs. collection do:

by Peter UhnÃ¡k

Hi, is there some best practice about collectionDo: versus collection do: ? I see many times the first used (e.g. String>>linesDo:); I see a benefit if there is no accessor to the collection, but more times than not there actually is. >From my perspective it further pollutes the protocol and as a user of such method I will never be sure what to actually use without looking at the implementation to see if there is any actual difference. So is there some consensus on this? Thanks, Peter

June 4, 2015

Re: [Pharo-users] loading Coral from SmalltalkHub

by stepharo

Thanks Stefan Francisco there is nothing new in Coral we got stalled again because we focused on pillar. Stef Le 4/6/15 11:20, Stephan Eggermont a Ã©crit : > On 04-06-15 01:46, Francisco Garau wrote: >> I've tried loading Coral by following the below instructions in its >> website <http://rmod.lille.inria.fr/coral/getting-started.html> but they >> failed when trying to load Readline. >> >> Gofer new url: 'http://ss3.gemstone.com/ss/coral'; >> package: 'ConfigurationOfCoral'; >> load. >> >> ConfigurationOfCoral loadDevelopment. > > Yes, that is an old configuration. I've updated it > on smalltalkhub: PharoExtras/Coral, but that was before > the release of Pharo4. CDLM, Damien C and Stef have worked > on it this year. > > As PetitParser still uses the > #stable and #development style of symbolic naming, > instead of #release5.1, things can break when a new > version of Moose is released. > >> It seems the project was moved to Smalltalk Hub >> (http://smalltalkhub.com/#!/~PharoExtras/Coral/) >> >> What expressions should I evaluate in a Pharo5 image to get the latest >> Coral project loaded. > > I've added a Pharo 5 build to > https://ci.inria.fr/pharo-contribution/job/Coral/ > The 4 and 5 builds are green > > I've also added a Pharo4 and Pharo5 build to OSProcess > https://ci.inria.fr/pharo-contribution/job/OSProcess/ > The 4 and 5 builds each have 3 failures > > It is possible that some changes to the parser are needed > due to improvements in PetitParser. I ran into that last > time I tried, and forgot whether that got fixed. > > Stephan > > > > >

June 4, 2015

Re: [Pharo-users] Proposed enhancements to get.pharo.org

by stepharo

Hi jason Thanks. > I have a simple suggestion for the ZeroConf Bash scripts. The > suggestion is to automatically discern the image that the scripts use. > E.g. > > For the pharo script: > https://gist.github.com/jacaetevha/7c4206d2cfadd54a492c#file-pharo > > For the pharo-ui script: > https://gist.github.com/jacaetevha/7c4206d2cfadd54a492c#file-pharo-ui > > I tried to bring this up in the IRC channel, but things seem pretty > quiet there. I'm not sure where to post this, so I'm just posting it here. This is the right place :) > > -- > Jason Rogers

June 4, 2015

Proposed enhancements to get.pharo.org

by Jason Rogers

I have a simple suggestion for the ZeroConf Bash scripts. The suggestion is to automatically discern the image that the scripts use. E.g. For the pharo script: https://gist.github.com/jacaetevha/7c4206d2cfadd54a492c#file-pharo For the pharo-ui script: https://gist.github.com/jacaetevha/7c4206d2cfadd54a492c#file-pharo-ui I tried to bring this up in the IRC channel, but things seem pretty quiet there. I'm not sure where to post this, so I'm just posting it here. -- Jason Rogers

June 4, 2015

Re: [Pharo-users] [Pharo-dev] Roassal Camp Smalltalk

by Peter UhnÃ¡k

Hi Alex, is it possible to add some discussion about stuff we did in roassal for dynacase to the list? Because I feel there is some duplication effort and also we could probably contribute some stuff we did back. Or perhaps even more general discussion about using roassal for more dynamic and modifiable visualizations/modeling (e.g. composite shapes, bendable lines, resizable boxes, etc.) Peter On Thu, Jun 4, 2015 at 7:55 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Dear Colleagues and Friends, > > We are happy to announce we will organize a CampSmalltalk about the > Roassal visualization engine, on _Sunday 12 July_. > > As far as we have seen, the interests are multiple. Here is a list of > topics we will happy to work on: > - Port of Roassal on VisualWorks > - Using Roassal on Gemstone > - HTML/JavaScript export > - Improving Grapher, our charting library > > If you wish to participate, get in touch with us. Since we will probably > have a sponsoring of the event, it would be nice to know how many will > attend to ease the logistic and the pizza ordering :-) > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

June 4, 2015

Roassal Camp Smalltalk

by Alexandre Bergel

Dear Colleagues and Friends, We are happy to announce we will organize a CampSmalltalk about the Roassal visualization engine, on _Sunday 12 July_. As far as we have seen, the interests are multiple. Here is a list of topics we will happy to work on: - Port of Roassal on VisualWorks - Using Roassal on Gemstone - HTML/JavaScript export - Improving Grapher, our charting library If you wish to participate, get in touch with us. Since we will probably have a sponsoring of the event, it would be nice to know how many will attend to ease the logistic and the pizza ordering :-) Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 4, 2015

Re: [Pharo-users] Visualizing a repository tree

by Peter UhnÃ¡k

Omg I just found out that if I click on the node representing an McVersionInfo it actually opens it in the inspector and I didn't even needed to implement anything special. That's really cool! Peter On Tue, Jun 2, 2015 at 6:59 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Interesting visualization! Keep going! > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Jun 2, 2015, at 10:57 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > On Tue, Jun 2, 2015 at 3:07 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Interesting. The dominance tree layout is quite interesting for this use >> case. >> > > There were some upward lines at the bottom of the graph for no apparent > reason, not sure what was going on there yet, so I'll look into the layout > when I have more time. > > Alternatively you could also use Sugiyama, however either due to the > choice of heuristics, or some bug it places high priority on last levels > which is really bad (since it is no longer at proper hierarchical layers). > > Peter > > >> Doru >> >> On Tue, Jun 2, 2015 at 12:09 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> 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 >>> ~~~~~~~~~~~~~~~~ >>> >>> >>> <2015-06-02_12:04:32.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 >>>>> >>>>> >>>>> >>>> >>>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > >

June 4, 2015

Re: [Pharo-users] case-insensitive regexp

by Usman Bhatti

Thanks Peter. On Thu, Jun 4, 2015 at 1:51 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > I do not think this is possible. The problem is that the Regex compiles > (parses) the pattern so once it's created you would have to reparse it. > Theoretically speaking you could add ignoreCase accessors to RxMatcher but > it is likely it would break things; or add method to RxMatcher that would > return a new RxMatcher object with the proper settings. > > Also note that regular expressions in Pharo are not the extended versions, > where these things are usually available (alongside lookahead/lookbehind > and other). > And personally I find the Regex library so awkward to use that I always > opt for PetitParser. > > ~~~~ > myParser := 'hello' asParser. > myParser matches: 'Hello'. "false" > myParser caseInsensitive matches: 'Hello'. "true" > ~~~~ > > on the other hand there is no option to turn it back again. So if you > regularly need to switch it back and forth it wouldn't be solution either. > > Peter >

June 4, 2015