- Pharo-users - lists.pharo.org

Re: [Pharo-users] Running agile visualization examples on pharo 4 doesn't show the RTView

by Peter UhnÃ¡k

Indeed, I always run this script to get in Pharo 4 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "=== Roassal presentations ===" Gofer new smalltalkhubUser: 'Moose' project: 'GToolkit'; package: 'GT-InspectorExtensions-CoreRoassal'; load. Gofer new smalltalkhubUser: 'Moose' project: 'Glamour'; package: 'Glamour-Tools'; package: 'Glamour-Roassal2-Presentations'; load. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Peter On Sat, Apr 25, 2015 at 7:05 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > If you do not have a Moose image, you have to load the Glamour Roassal > presentation and the GT-InspectorExtensions-CoreRoassal > > Cheers, > Doru > > On Sat, Apr 25, 2015 at 7:01 PM, Offray Vladimir Luna CÃ¡rdenas < > offray(a)riseup.net> wrote: > >> Hi, >> >> I'm just testing/porting some of my stuff on pharo 4 (congrats again for >> the release!) and I see something strange. When I run the examples of agile >> visualization on a playground I don't get all the tabs that I get on Pharo >> 3.0 and Moose 5.0 and 5.1, only the "Raw" and "Meta". Tabs like "View" and >> "Elements" are lost, which are particulary needed when you explore a >> visualization. >> >> To repeat this behaviour, just run any example of agile visualization >> book on a fresh image of Pharo 4. >> >> I'm running Pharo4.0 Latest update: #40611 on an Arch Linux system. >> >> Hope it helps, >> >> Offray >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

April 25, 2015

Re: [Pharo-users] Running agile visualization examples on pharo 4 doesn't show the RTView

by Tudor Girba

If you do not have a Moose image, you have to load the Glamour Roassal presentation and the GT-InspectorExtensions-CoreRoassal Cheers, Doru On Sat, Apr 25, 2015 at 7:01 PM, Offray Vladimir Luna CÃ¡rdenas < offray(a)riseup.net> wrote: > Hi, > > I'm just testing/porting some of my stuff on pharo 4 (congrats again for > the release!) and I see something strange. When I run the examples of agile > visualization on a playground I don't get all the tabs that I get on Pharo > 3.0 and Moose 5.0 and 5.1, only the "Raw" and "Meta". Tabs like "View" and > "Elements" are lost, which are particulary needed when you explore a > visualization. > > To repeat this behaviour, just run any example of agile visualization book > on a fresh image of Pharo 4. > > I'm running Pharo4.0 Latest update: #40611 on an Arch Linux system. > > Hope it helps, > > Offray > > -- www.tudorgirba.com "Every thing has its own flow"

April 25, 2015

Running agile visualization examples on pharo 4 doesn't show the RTView

by Offray Vladimir Luna CÃ¡rdenas

Hi, I'm just testing/porting some of my stuff on pharo 4 (congrats again for the release!) and I see something strange. When I run the examples of agile visualization on a playground I don't get all the tabs that I get on Pharo 3.0 and Moose 5.0 and 5.1, only the "Raw" and "Meta". Tabs like "View" and "Elements" are lost, which are particulary needed when you explore a visualization. To repeat this behaviour, just run any example of agile visualization book on a fresh image of Pharo 4. I'm running Pharo4.0 Latest update: #40611 on an Arch Linux system. Hope it helps, Offray

April 25, 2015

Re: [Pharo-users] issue with monticello ancestor ?

by Thierry Goubier

Le 25/04/2015 18:09, Yuriy Tymchuk a Ã©crit : > >> On 25 Apr 2015, at 18:00, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >> >> Hi Alexandre, >> >> with Esteban, we've been chasing around some of those bugs around for a while. >> >> But, in your case, it could perfectly be that: >> >> .6 in your image has .4 as ancestor; and .6 in your repository has .5 as ancestorâ¦ > > Sorry for this remark, but is this really perrfect that the same version of the same project can have two different ancestors depending in which repository it is? Yes, it is Monticello perfect :) Thierry > :) > Uko > >> >> If you could, I'd like that, on that very same inspector, you inspect the model of the PluggableListMorph (Ctrl+Shift+Click on the left pane, choose inspect, choose PluggableIconListMorph, choose the model, and tell me what you have in the selectPackageAncestors. >> >> Thierry >> >> Le 25/04/2015 17:46, Alexandre Bergel a Ã©crit : >>> Hi! >>> >>> I often experience that ancestors are not properly marked as non-bold in >>> monticello. Consider the following: >>> >>> >>> Why .5.mcz is in bold since it is the ancestor of version 6? >>> >>> Am I the only one to experience this? >>> >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >> >> > > > >

April 25, 2015

Re: [Pharo-users] issue with monticello ancestor ?

by Yuriy Tymchuk

> On 25 Apr 2015, at 18:00, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Hi Alexandre, > > with Esteban, we've been chasing around some of those bugs around for a while. > > But, in your case, it could perfectly be that: > > .6 in your image has .4 as ancestor; and .6 in your repository has .5 as ancestorâ¦ Sorry for this remark, but is this really perrfect that the same version of the same project can have two different ancestors depending in which repository it is? :) Uko > > If you could, I'd like that, on that very same inspector, you inspect the model of the PluggableListMorph (Ctrl+Shift+Click on the left pane, choose inspect, choose PluggableIconListMorph, choose the model, and tell me what you have in the selectPackageAncestors. > > Thierry > > Le 25/04/2015 17:46, Alexandre Bergel a Ã©crit : >> Hi! >> >> I often experience that ancestors are not properly marked as non-bold in >> monticello. Consider the following: >> >> >> Why .5.mcz is in bold since it is the ancestor of version 6? >> >> Am I the only one to experience this? >> >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> > >

April 25, 2015

Re: [Pharo-users] issue with monticello ancestor ?

by Thierry Goubier

Hi Alexandre, with Esteban, we've been chasing around some of those bugs around for a while. But, in your case, it could perfectly be that: .6 in your image has .4 as ancestor; and .6 in your repository has .5 as ancestor... If you could, I'd like that, on that very same inspector, you inspect the model of the PluggableListMorph (Ctrl+Shift+Click on the left pane, choose inspect, choose PluggableIconListMorph, choose the model, and tell me what you have in the selectPackageAncestors. Thierry Le 25/04/2015 17:46, Alexandre Bergel a Ã©crit : > Hi! > > I often experience that ancestors are not properly marked as non-bold in > monticello. Consider the following: > > > Why .5.mcz is in bold since it is the ancestor of version 6? > > Am I the only one to experience this? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > >

April 25, 2015

issue with monticello ancestor ?

by Alexandre Bergel

Hi! I often experience that ancestors are not properly marked as non-bold in monticello. Consider the following: Why .5.mcz is in bold since it is the ancestor of version 6? Am I the only one to experience this? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 25, 2015

Re: [Pharo-users] QualityAssistant ignoring rules

by Yuriy Tymchuk

Thatâs why itâs not in production :). Thank you for the feedback > On 25 Apr 2015, at 11:54, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Excellent! > > I'm also noticing that this doesn't use the CriticBrowser's Manifest class, but I assume this is already somewhere on your todo list. (I'm not very fond of the pragma usage here, it would be nice to have it as metadata (in a possibly separate window which I can't open/close on demand)). > > Thanks! > > Peter > > > > On Sat, Apr 25, 2015 at 10:30 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: > Hi Peter. > > For now - no, but you can check a prototype if you load QualityAssistant with: > > Metacello new > baseline: #QualityAssistant; > repository: 'github://Uko/QualityAssistant:development'; > load > > Want to make a whole new philosophy of how do you tell which parts should be checked with which rules. So in future youâll be able to tell on the level of a package, class or method which rules do you want to run and which rules do you want to skip, or which parameters (number of methods in a class) should a rule use when it checks your entities. > > For now you can skip rule on the level of class or method. When you do this a specific code is written down in the class or method, so if the other developer will read your code he can also se the youâve skipped the rule on porpoise and itâs a planned decision. > > Cheers! > Uko > > > On 25 Apr 2015, at 09:50, Peter UhnÃ¡k <i.uhnak(a)gmail.com <mailto:i.uhnak@gmail.com>> wrote: > > > > Hi, > > > > is there a simple way to add certain rule as ignored? Something like "right click -> supress rule" > > I am working on tools that do use metaprogramming, so it tends to complain, and for example in roassal there is a common pattern > > element := RTBox new size: 50; elementOn: 'sth'. > > But that of course complains about missing "; yourself". Of course I could break it into two statements but that is counter-productive. > > So it would be nice if I could with a simple click ignore certain rules. > > > > Thanks, > > Peter > > >

April 25, 2015

STON references class removed in Pharo 5

by Jan BlizniÄenko

Hello I'd just like to note that STON package is referencing class TimeStamp in its tests, which has been deprecated and got removed in Pharo 5 (since image 50003), so if I want to use latest image (which I do), I get a warning that STON package depends on non-existing class. Jan -- View this message in context: http://forum.world.st/STON-references-class-removed-in-Pharo-5-tp4821773.ht… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 25, 2015

Re: [Pharo-users] QualityAssistant ignoring rules

by Peter UhnÃ¡k

Excellent! I'm also noticing that this doesn't use the CriticBrowser's Manifest class, but I assume this is already somewhere on your todo list. (I'm not very fond of the pragma usage here, it would be nice to have it as metadata (in a possibly separate window which I can't open/close on demand)). Thanks! Peter On Sat, Apr 25, 2015 at 10:30 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Hi Peter. > > For now - no, but you can check a prototype if you load QualityAssistant > with: > > Metacello new > baseline: #QualityAssistant; > repository: 'github://Uko/QualityAssistant:development'; > load > > Want to make a whole new philosophy of how do you tell which parts should > be checked with which rules. So in future youâll be able to tell on the > level of a package, class or method which rules do you want to run and > which rules do you want to skip, or which parameters (number of methods in > a class) should a rule use when it checks your entities. > > For now you can skip rule on the level of class or method. When you do > this a specific code is written down in the class or method, so if the > other developer will read your code he can also se the youâve skipped the > rule on porpoise and itâs a planned decision. > > Cheers! > Uko > > > On 25 Apr 2015, at 09:50, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > > Hi, > > > > is there a simple way to add certain rule as ignored? Something like > "right click -> supress rule" > > I am working on tools that do use metaprogramming, so it tends to > complain, and for example in roassal there is a common pattern > > element := RTBox new size: 50; elementOn: 'sth'. > > But that of course complains about missing "; yourself". Of course I > could break it into two statements but that is counter-productive. > > So it would be nice if I could with a simple click ignore certain rules. > > > > Thanks, > > Peter > > >

April 25, 2015