- Pharo-users - lists.pharo.org

Re: [Pharo-users] Package Dependencies Analyzer

by stepharo

thanks baptiste I will try it on polymorph :) Stef On 12/7/14 12:34, Baptiste QuidÃ© wrote: > > Hi Stef, > > I think it's not normal. I will fix it when I will be at home or work. > Try the gofer script and everything should be ok > > Le 12 juil. 2014 12:26, "stepharo" <stepharo(a)free.fr > <mailto:stepharo@free.fr>> a Ã©crit : > > Hi baptiste > > I loaded your tools via the metacello browser in Pharo40 but I do > not get a menu to invoke it. > Is it normal? > > Stef > > On 11/7/14 18:42, Baptiste QuidÃ© wrote: > > Hello Pharo users, > > let me introduce a new tool that I developed in the RMOD team: > package dependencies analyzer. > > This project provides a tool able to analyze Smalltalk project > packages and detect dependencies to other packages. It enables > automatic dependency analysis to detect wrong project > description (declared dependencies). It's very easy to use and > i hope it will be helpful during your development time. > > As soon as possible, a next version will enable to detect > cycle dependencies among packages. > > The description of the project is on this web-page : > http://www.baptistequide.fr/packagedependencies.php > It's already available on the Configuration Browser on Pharo. > > Your feedback and suggestions are mostly welcome to improve > this project. I invite you to test the tool. > > Cheers, > > Baptiste > > > >

July 14, 2014

Re: [Pharo-users] Should I be reporting bugs in Pharo 3.0?

by Ben Coman

July 14, 2014

Pharo 40 June meeting

by stepharo

Hi guys We run the first checkpoint meeting around meeting with the team at rmod and we analysed why we did not get public sprints and regular hangouts. We were tired I guessed. Now we will have a public calendar with the next 6 months of planified events. The calendar will be (may be it is already) added to the web site. Since the team is reorganizing itself and its priority here is a report of our analysis for the first iteration. If you have resources and you want to get an impact please join and let us know. Pharo 40 features list ====================== - Modularisation is under way - Tools - Morphic - Polymorph package structure is slowly getting cleaner - Infrastructure - Android (Missing management events and graphics) - Raspberry (FFI works, vm works, OS process) - Spur should be finished this week - found a bug in Spur related to weak structure (already fixed by Eliot) - release each image we produce to Spur format - nativeBoost is not working - large integer plugin is not working - Host window integration - OSWindow common interface - Multiple back-ends (VM, SDL2, plugin) - Ready to be integrated. - Need some class comments! - New bytecode set - integrated this morning - needs a new vm for the bytecodeset - Spur 64 bits - starting to work on it in September - Removing old compiler - reloadable - needed for VM - Spur - System Localization - usman should open a bug issue - Leading Char Removal - probably we will not do it. - Guille Core - bootstrap - next fridayâ¦ - Unloading Reloading tools - JB will help - Athens - roadmap - missing txText - TxText - Widget is there and working - Morph is working - Spec integration - Not all tool use Spec - Clean version - Igor MUST release a version and not try to make the complete system working with it. - Remove the old browser - kill the filePackage browser - We should get Nautilus or OndoBrowser browsing Ring - Spec - Should do a pass - Check the design (in particular link between adapter and morph) - Examples-driven are needed - GitSupport - filetree integration is working but not good enough - small progress. - Martin should check with Max the status of libgit2 - Need to build on top of that. - Morph and theme - we will see if we have the time - brainstorming on a solution - Make sure that we do not overuse Ring - Font with FreeType - Glamour - esteban roadmap - first bootstrap - second only a stripped down version - development outside the image - Ombu/Epicea - call for more users - ZnUrl should be used in place of URI URL - Keychain Removal - Morph class side announcer - we should look at the announcer plague - Intersect: - should be finished - Image-level resources - brainstorming prototyping - Opal there is progress! - slots <-> OPAL - subclassing and adding instance compiled - specific slots are on the way - ClassBuilder - should be revisited. Previous wish list ================== - Web site animation - catalog (meta data and ressources) - videos - Infrastructure ppa linux linux [glibc] win32 OSX iOS android (Missing management events and graphics) raspberry (works) solaris CentOS + OSX - Investigate obs openbuild service - extracting VM as dylib + GUI + console

July 14, 2014

Consortium report

by stepharo

Hi pharoers Here is the report of the consortium meeting held in late June. Sorry for the time it took to send it around. It is the same as the one we sent in the consortium mailing-list and is public. There is a draft of a roadmap for Pharo 40. Stef

July 14, 2014

Re: [Pharo-users] get the names of the currently loaded mcz files

by Tudor Girba

In the inspector :). When using the GTInspector, if you inspect MCWorkingCopy, you will get the list of all managers in a dedicated tab. Doru On Mon, Jul 14, 2014 at 1:08 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Sven Van Caekenberghe-2 wrote > > (MCWorkingCopy allManagers asSortedCollection: [ :a :b | a packageName <= > > b packageName ]) collect: #description. > > This is useful enough to go somewhere more permanent... any ideas? > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/get-the-names-of-the-currently-loaded-mcz-files-tp476… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > -- www.tudorgirba.com "Every thing has its own flow"

July 14, 2014

Re: [Pharo-users] get the names of the currently loaded mcz files

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > (MCWorkingCopy allManagers asSortedCollection: [ :a :b | a packageName <= > b packageName ]) collect: #description. This is useful enough to go somewhere more permanent... any ideas? ----- Cheers, Sean -- View this message in context: http://forum.world.st/get-the-names-of-the-currently-loaded-mcz-files-tp476… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 13, 2014

Re: [Pharo-users] Should I be reporting bugs in Pharo 3.0?

by Tim Mackinnon

Thanks for the fog bugz tips. Duplicating a bug is useful for several reasons I've found in the past: A) if you want to submit the same bug for two streams (eg Pharo 3 & 4) to be dealt with differently - copying them is handy. B) if you have a similar bug with similar steps bar 1, or a bug fix improves the situation but highlights another different problem... It's useful to duplicate a bug (with it conveniently linked) to save time. I'm not a huge Jira fan - but it makes that really easy & I'm suprised that fog bugz is so basic. Of course it's not the end of the world - but you do wonder why all bug tracking software is so clunky. I'm equally suprised that linking bugs by using the parent/child fields is the only way - if bugs are peers, it seems natural to just link them that way without needing a parent. Anyway - I'll use what we've got and get used to its eccentricities. Tim Sent from my iPhone On 13 Jul 2014, at 19:14, "Ben Coman [via Smalltalk]" <ml-node+s1294792n4767653h23(a)n4.nabble.com> wrote: > Tim Mackinnon wrote: > > > Can I check one more item - should I record the actual Image version where > > bugs occur? > > > > In fogbugz, there is a version field - but I'm not sure what your convention > > is for these things? (Is it written down somewhere for me to read how to > > report good bugs using FogBugz). > > > > As an aside - I'm quite surprised how poor Fogbugz is. I had read it was a > > good bug tracker - but in practice its quite minimal. I'm quite shocked you > > can't easily duplicate a bug-report (I wrote to them and they said you have > > to use some browser plugin as its not built in), I also can't see how to > > link bug-report (as in, similar to X). > > > > Not Pharo's fault of course. > > > > Tim > > > There are two ways to link bug reports. > 1. By writing 'Case #####' anywhere in the ticket. > 2. Adding case number ##### to the Parent and Subcase fields in the > side-bar. The Pharo CI Monkey only picks up slices for a parent case > once all child cases are closed. > > Now I've never needed to duplicate a bug report. I'd like to understand > what your use case is there? > > cheers -ben > > > > > > If you reply to this email, your message will be added to the discussion below: > http://forum.world.st/Should-I-be-reporting-bugs-in-Pharo-3-0-tp4767284p476… > To unsubscribe from Should I be reporting bugs in Pharo 3.0?, click here. > NAML -- View this message in context: http://forum.world.st/Should-I-be-reporting-bugs-in-Pharo-3-0-tp4767284p476… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 13, 2014

Re: [Pharo-users] Should I be reporting bugs in Pharo 3.0?

by Ben Coman

Tim Mackinnon wrote: > Can I check one more item - should I record the actual Image version where > bugs occur? > > In fogbugz, there is a version field - but I'm not sure what your convention > is for these things? (Is it written down somewhere for me to read how to > report good bugs using FogBugz). > > As an aside - I'm quite surprised how poor Fogbugz is. I had read it was a > good bug tracker - but in practice its quite minimal. I'm quite shocked you > can't easily duplicate a bug-report (I wrote to them and they said you have > to use some browser plugin as its not built in), I also can't see how to > link bug-report (as in, similar to X). > > Not Pharo's fault of course. > > Tim > There are two ways to link bug reports. 1. By writing 'Case #####' anywhere in the ticket. 2. Adding case number ##### to the Parent and Subcase fields in the side-bar. The Pharo CI Monkey only picks up slices for a parent case once all child cases are closed. Now I've never needed to duplicate a bug report. I'd like to understand what your use case is there? cheers -ben

July 13, 2014

Re: [Pharo-users] Roassal2 Composite Shape

by Peter UhnÃ¡k

Thank you, the example now works. However as I've mentioned in previous post I'm not sure about the rest of the shapes posted in the attachment. E.g. I haven't seen any notion of "box with rounded corners". I could compose it from four RTArc nad four RTLine but it seems to me overly complex compared to creating new Trachert/Roassal classes. The same would go for the other shapes. What are your thoughts/recommendations on that? Peter On Sun, Jul 13, 2014 at 3:25 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Sorry, the version was not properly saved in SmalltalkHub. If you update Roassal2 and Trachel, you should be able to execute the code snippet Iâve sent you. Maybe you want to add âv openâ at the end. If you are using GTInspector, this is not necessary. > > As far as I understand your description of the problem, you do not need to create your own shape. > > Let me know how it goes. > > Cheers, > Alexandre > > > On Jul 13, 2014, at 10:38 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > >> Thank you both for suggestions. >> >> According to Monticello I have latest Roassal2 and yet I don't see RTMultiCompositeShape, but I would assume it should be what I was looking for originally. >> >> In the meantime I chose to do it manually - creating a custom shape in both Roassal and Trachert: >> I've done it in a single path because it seems that having multiple separate paths just creates more trouble. >> ======== >> computePath >> canvas ifNil: [ ^ self ]. >> path := self athensCanvas >> createPath: [ :builder | >> builder absolute. >> self ccwCirclePath: builder radius: 0.5. "building circular path with specified radius" >> self cwCirclePath: builder radius: 0.48. >> self ccwCirclePath: builder radius: 0.4 ] >> ======== >> >> But even if I could manage to do this with MultiCompositeShape I'm not sure about the rest of the shapes (see attachment). >> >> Peter >> >> >> >> >> On Sun, Jul 13, 2014 at 1:18 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> Hi Peter, >> >> I am not sure what you try to do. Having two ellipses with the same center? But different radius? >> >> Something like that maybe: >> -=-=-=-=-=-=-=-=-= >> | v | >> v := RTView new. >> v @ RTDraggableView. >> >> shape := RTMultiCompositeShape new. >> shape add: (RTEllipse new color: (Color yellow alpha: 0.3); size: [:c | c numberOfMethods sqrt * 10 ]). >> shape add: (RTEllipse new color: (Color green alpha: 0.3); size: [:c | c numberOfLinesOfCode sqrt * 10 ]). >> >> v addAll: (shape elementsOn: RTShape withAllSubclasses). >> RTFlowLayout on: v elements. >> >> v >> -=-=-=-=-=-=-=-=-= >> >> <Screen Shot 2014-07-13 at 1.18.36 AM.png> >> >> Alexandre >> >> >> On Jul 11, 2014, at 11:05 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> >>> Hi >>> >>> I'm trying to draw an ellipse inside another ellipse but to no avail. I've tried using RTCompositeShape but that just expands the size of the smaller shape. Is there something else I'm missing (like fixing dimensions so they won't get updated) or should I subclass RTAbstractCompositeShape and try to make something on my own? >>> >>> Thanks, >>> Peter >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> <shapes.png> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

July 13, 2014

Re: [Pharo-users] Roassal2 Composite Shape

by Alexandre Bergel

Sorry, the version was not properly saved in SmalltalkHub. If you update Roassal2 and Trachel, you should be able to execute the code snippet Iâve sent you. Maybe you want to add âv openâ at the end. If you are using GTInspector, this is not necessary. As far as I understand your description of the problem, you do not need to create your own shape. Let me know how it goes. Cheers, Alexandre On Jul 13, 2014, at 10:38 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Thank you both for suggestions. > > According to Monticello I have latest Roassal2 and yet I don't see RTMultiCompositeShape, but I would assume it should be what I was looking for originally. > > In the meantime I chose to do it manually - creating a custom shape in both Roassal and Trachert: > I've done it in a single path because it seems that having multiple separate paths just creates more trouble. > ======== > computePath > canvas ifNil: [ ^ self ]. > path := self athensCanvas > createPath: [ :builder | > builder absolute. > self ccwCirclePath: builder radius: 0.5. "building circular path with specified radius" > self cwCirclePath: builder radius: 0.48. > self ccwCirclePath: builder radius: 0.4 ] > ======== > > But even if I could manage to do this with MultiCompositeShape I'm not sure about the rest of the shapes (see attachment). > > Peter > > > > > On Sun, Jul 13, 2014 at 1:18 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi Peter, > > I am not sure what you try to do. Having two ellipses with the same center? But different radius? > > Something like that maybe: > -=-=-=-=-=-=-=-=-= > | v | > v := RTView new. > v @ RTDraggableView. > > shape := RTMultiCompositeShape new. > shape add: (RTEllipse new color: (Color yellow alpha: 0.3); size: [:c | c numberOfMethods sqrt * 10 ]). > shape add: (RTEllipse new color: (Color green alpha: 0.3); size: [:c | c numberOfLinesOfCode sqrt * 10 ]). > > v addAll: (shape elementsOn: RTShape withAllSubclasses). > RTFlowLayout on: v elements. > > v > -=-=-=-=-=-=-=-=-= > > <Screen Shot 2014-07-13 at 1.18.36 AM.png> > > Alexandre > > > On Jul 11, 2014, at 11:05 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > >> Hi >> >> I'm trying to draw an ellipse inside another ellipse but to no avail. I've tried using RTCompositeShape but that just expands the size of the smaller shape. Is there something else I'm missing (like fixing dimensions so they won't get updated) or should I subclass RTAbstractCompositeShape and try to make something on my own? >> >> Thanks, >> Peter > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > <shapes.png> -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 13, 2014