Re: [Pharo-project] Jira plugin for Monticello
Thanks Camillo. There doesn't seem to be any interest either. We'll just use the API for now to close / comment issues. On 17.04.2013, at 20:39, Camillo Bruni wrote: > I don't think that exists... > > On 2013-04-17, at 20:11, Max Leske wrote: >> Hi guys >> >> Has anyone ever heard / used a Jira plugin for Monticello commits? Who would >> be interested in such a plugin? >> >> Cheers, >> Max > >
Re: [Pharo-project] plugin in Nautilus
Group are made for this. Maybe we should automatically create a new group when a package is loaded Ben On Apr 21, 2013, at 4:23 AM, Alexandre Bergel wrote: > I tried to use groups, but it does not really work for me. Here is my > scenario: > > I take a fresh image, I load Versionner then I load Roassal. > I open a code browser, and guess what, I want to see Roassal and Versionner > right away, and not have to scroll down. > > But I think that the most important, is to be able to particularize the > system, and not really to get the best behavior. > > Cheers, > Alexandre > > > > On Apr 20, 2013, at 3:32 AM, stephane ducasse > wrote: > >> I use a group for that :) >> >> And what I would love is a group: >> latest loaded packages. >> >> >> On Apr 20, 2013, at 12:24 AM, Alexandre Bergel >> wrote: >> >>> Hi! >>> >>> Is there a documentation on how to create a plugin for Nautilus? >>> >>> I would like to create a command 'Hide all packages' in the Package column >>> of Nautilus. Any hint on how to do this? >>> >>> Cheers, >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >
Re: [Pharo-project] Jira plugin for Monticello
Hi Max, Do you have Pharo code that works with Jira issues? Cheers, Doru On Apr 21, 2013, at 12:01 PM, Max Leske wrote: > Thanks Camillo. There doesn't seem to be any interest either. We'll just use > the API for now to close / comment issues. > > > On 17.04.2013, at 20:39, Camillo Bruni wrote: > >> I don't think that exists... >> >> On 2013-04-17, at 20:11, Max Leske wrote: >>> Hi guys >>> >>> Has anyone ever heard / used a Jira plugin for Monticello commits? Who >>> would be interested in such a plugin? >>> >>> Cheers, >>> Max >> >> > > -- www.tudorgirba.com "Live like you mean it."
Re: [Pharo-project] Jira plugin for Monticello
Working on it. First thing I want is to close / resolve / comment issues from Monticello commits. The API is good, so it's not a big thing. I'll share the code once it's ready if you like. Max On 21.04.2013, at 15:01, Tudor Girba wrote: > Hi Max, > > Do you have Pharo code that works with Jira issues? > > Cheers, > Doru > > > On Apr 21, 2013, at 12:01 PM, Max Leske wrote: > >> Thanks Camillo. There doesn't seem to be any interest either. We'll just use >> the API for now to close / comment issues. >> >> >> On 17.04.2013, at 20:39, Camillo Bruni wrote: >> >>> I don't think that exists... >>> >>> On 2013-04-17, at 20:11, Max Leske wrote: Hi guys Has anyone ever heard / used a Jira plugin for Monticello commits? Who would be interested in such a plugin? Cheers, Max >>> >>> >> >> > > -- > www.tudorgirba.com > > "Live like you mean it." > >
Re: [Pharo-project] Jira plugin for Monticello
I am definitely interested from two perspectives: - use the API for data analysis within Moose. - potentially use Jira as issue tracker for Moose. Cheers, Doru On Apr 21, 2013, at 4:01 PM, Max Leske wrote: > Working on it. First thing I want is to close / resolve / comment issues from > Monticello commits. The API is good, so it's not a big thing. I'll share the > code once it's ready if you like. > > Max > > On 21.04.2013, at 15:01, Tudor Girba wrote: > >> Hi Max, >> >> Do you have Pharo code that works with Jira issues? >> >> Cheers, >> Doru >> >> >> On Apr 21, 2013, at 12:01 PM, Max Leske wrote: >> >>> Thanks Camillo. There doesn't seem to be any interest either. We'll just >>> use the API for now to close / comment issues. >>> >>> >>> On 17.04.2013, at 20:39, Camillo Bruni wrote: >>> I don't think that exists... On 2013-04-17, at 20:11, Max Leske wrote: > Hi guys > > Has anyone ever heard / used a Jira plugin for Monticello commits? Who > would be interested in such a plugin? > > Cheers, > Max >>> >>> >> >> -- >> www.tudorgirba.com >> >> "Live like you mean it." >> >> > > -- www.tudorgirba.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."
[Pharo-project] [BUG] Fix for MorphTreeMorph>>updateList
The scrollbar should be scrolled to the position before update. Fix enclosed. Thanks Hilaire -- Dr. Geo http://drgeo.eu 'From Pharo1.4 of 18 April 2012 [Latest update: #14438] on 21 April 2013 at 4:53:42 pm'! !MorphTreeMorph methodsFor: 'updating' stamp: 'HilaireFernandes 4/21/2013 16:52'! updateList |value| value := scrollBar value. self updateContentsWithPreviouslyExpanded: self currentlyExpanded. self vScrollValue: value! !
Re: [Pharo-project] Any wishes for Roassal?
> I don't know if you add this feature recently but I would like to be able to > attach edges to center of nodes. This is well supported in Roassal. You simply have to send #attachPoint: to a line shape. Consider: -=-=-=-=-=-=-=-=-=-=-=-= | view rawView | rawView := ROView new. view := ROMondrianViewBuilder view: rawView. "-" "-" view shape rectangle size: 20. view nodes: #(1 2 3). view shape line attachPoint: ROCenteredAttachPoint instance. view edgesFromAssociations: (Array with: 1-> 2 with: 2 -> 3 with: 1 -> 3). view circleLayout "-" "-" "Below is the initiation of the menu and opening the visualization" ROEaselMorphic new populateMenuOn: view. view open -=-=-=-=-=-=-=-=-=-=-=-= Example about this: ROMondrianExample>>attachPointOn: Cheers, Alexandre > > Le 20 avr. 2013 à 01:58, Alexandre Bergel a écrit : > >> Hi! >> >> Roassal 2.0 is on the way. We would like to make sure everybody find this >> release attractive. >> We are wondering whether you have some particular requirements you would >> like us to address or some bugs you would like to see fixed. >> >> Feel free to speak up! >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Re: [Pharo-project] [BUG] Fix for MorphTreeMorph>>updateList
Hi, the easiest way to get fixes integrated is: -> add a bug tracker entry -> Make a SLICE, upload it to the inbox -> mention that there is a slice and set the issue in the tracker to "review need" If the person who did a fix does all that it will be the fastest. Marcus On Apr 21, 2013, at 4:56 PM, Hilaire Fernandes wrote: > The scrollbar should be scrolled to the position before update. > Fix enclosed. > > Thanks > > Hilaire > > -- > Dr. Geo http://drgeo.eu >
Re: [Pharo-project] [BUG] Fix for MorphTreeMorph>>updateList
I know, but I will not do it right now and I don't want to forget it. Hilaire Le 21/04/2013 17:13, Marcus Denker a écrit : > Hi, > > the easiest way to get fixes integrated is: > > -> add a bug tracker entry > -> Make a SLICE, upload it to the inbox > -> mention that there is a slice and set the issue in the tracker to > "review need" > > If the person who did a fix does all that it will be the fastest. > > Marcus > > On Apr 21, 2013, at 4:56 PM, Hilaire Fernandes > wrote: > >> The scrollbar should be scrolled to the position before update. >> Fix enclosed. >> >> Thanks >> >> Hilaire >> >> -- >> Dr. Geo http://drgeo.eu >> > > > -- Dr. Geo http://drgeo.eu
Re: [Pharo-project] [BUG] Fix for MorphTreeMorph>>updateList
|( that's what issue trackers are for not mailinglists... On 2013-04-21, at 17:27, Hilaire Fernandes wrote: > I know, but I will not do it right now and I don't want to forget it. > > Hilaire > > Le 21/04/2013 17:13, Marcus Denker a écrit : >> Hi, >> >> the easiest way to get fixes integrated is: >> >> -> add a bug tracker entry >> -> Make a SLICE, upload it to the inbox >> -> mention that there is a slice and set the issue in the tracker to >> "review need" >> >> If the person who did a fix does all that it will be the fastest. >> >> Marcus >> >> On Apr 21, 2013, at 4:56 PM, Hilaire Fernandes >> wrote: >> >>> The scrollbar should be scrolled to the position before update. >>> Fix enclosed. >>> >>> Thanks >>> >>> Hilaire >>> >>> -- >>> Dr. Geo http://drgeo.eu >>> >> >> >> > > > -- > Dr. Geo http://drgeo.eu > >
Re: [Pharo-project] [BUG] Fix for MorphTreeMorph>>updateList
On Apr 21, 2013, at 5:27 PM, Hilaire Fernandes wrote: > I know, but I will not do it right now and I don't want to forget it. > To not forget it, I added https://pharo.fogbugz.com/f/cases/10352/Fix-for-MorphTreeMorph-updateList ;-) > Hilaire > > Le 21/04/2013 17:13, Marcus Denker a écrit : >> Hi, >> >> the easiest way to get fixes integrated is: >> >> -> add a bug tracker entry >> -> Make a SLICE, upload it to the inbox >> -> mention that there is a slice and set the issue in the tracker to >> "review need" >> >> If the person who did a fix does all that it will be the fastest. >> >> Marcus >> >> On Apr 21, 2013, at 4:56 PM, Hilaire Fernandes >> wrote: >> >>> The scrollbar should be scrolled to the position before update. >>> Fix enclosed. >>> >>> Thanks >>> >>> Hilaire >>> >>> -- >>> Dr. Geo http://drgeo.eu >>> >> >> >> > > > -- > Dr. Geo http://drgeo.eu > >
Re: [Pharo-project] plugin in Nautilus
yes! we could try to see. > Group are made for this. > > Maybe we should automatically create a new group when a package is loaded > Ben > > On Apr 21, 2013, at 4:23 AM, Alexandre Bergel wrote: > >> I tried to use groups, but it does not really work for me. Here is my >> scenario: >> >> I take a fresh image, I load Versionner then I load Roassal. >> I open a code browser, and guess what, I want to see Roassal and Versionner >> right away, and not have to scroll down. >> >> But I think that the most important, is to be able to particularize the >> system, and not really to get the best behavior. >> >> Cheers, >> Alexandre >> >> >> >> On Apr 20, 2013, at 3:32 AM, stephane ducasse >> wrote: >> >>> I use a group for that :) >>> >>> And what I would love is a group: >>> latest loaded packages. >>> >>> >>> On Apr 20, 2013, at 12:24 AM, Alexandre Bergel >>> wrote: >>> Hi! Is there a documentation on how to create a plugin for Nautilus? I would like to create a command 'Hide all packages' in the Package column of Nautilus. Any hint on how to do this? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >
