[Pharo-dev] WhatsUp from: 2015-08-03 until: 2015-08-16

2015-08-02 Thread seaside
Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVE

Re: [Pharo-dev] Google Code Shutdown

2015-08-02 Thread Alexandre Bergel
Github is indeed appealing. Cheers, Alexandre > On Aug 2, 2015, at 10:14 PM, Sean P. DeNigris wrote: > > Tudor Girba-2 wrote >> Would you like to help us move the moose-technology project? > > Sure. What do you have in mind? It seems exporting to GitHub is the easiest > option. There are a

Re: [Pharo-dev] Google Code Shutdown

2015-08-02 Thread Sean P. DeNigris
Tudor Girba-2 wrote > Would you like to help us move the moose-technology project? Sure. What do you have in mind? It seems exporting to GitHub is the easiest option. There are a few limitations, but I've had good experiences... - Cheers, Sean -- View this message in context: http://forum.

Re: [Pharo-dev] Nautilus new buttons not buttons?

2015-08-02 Thread Stephan Eggermont
On 01/08/15 13:25, Franck Warlouzet wrote: Hello, Yes it looks a little bit 'lite' but we did not want to have 2 buttons with the same look but two different kinds of actions. Hierarchy button changes the window itself and variable and scoped open a new menu or window. I agree about the class s

Re: [Pharo-dev] [ann] jdt2famix - an open-source java importer project

2015-08-02 Thread Tudor Girba
Hi (again), The project below is made possible by JNIPort. Thanks, Joachim! Cheers, Doru On Sun, Aug 2, 2015 at 11:26 PM, Tudor Girba wrote: > Hi, > > I would like to announce the jdt2famix project. This aims to be an > open-source solution for importing Java projects into Moose: > http://www

Re: [Pharo-dev] Nautilus new buttons not buttons?

2015-08-02 Thread Esteban Lorenzano
> On 01 Aug 2015, at 22:45, Peter Uhnák wrote: > > > > On Sat, Aug 1, 2015 at 10:10 PM, stepharo > wrote: > > > Le 1/8/15 13:54, Esteban Lorenzano a écrit : >> >>> On 01 Aug 2015, at 13:25, Franck Warlouzet >> > wrote: >>> >>> H

Re: [Pharo-dev] Google Code Shutdown

2015-08-02 Thread Tudor Girba
Hi Sean, Would you like to help us move the moose-technology project? Cheers, Doru On Sun, Aug 2, 2015 at 5:19 PM, Sean P. DeNigris wrote: > Sean P. DeNigris wrote > > In case anyone hasn't heard, Google Code will shut down entirely on > > January 25, 2016. > > UPDATE: Impending Deadline: "Go

Re: [Pharo-dev] Google Code Shutdown

2015-08-02 Thread Sean P. DeNigris
Sean P. DeNigris wrote > In case anyone hasn't heard, Google Code will shut down entirely on > January 25, 2016. UPDATE: Impending Deadline: "Google Code will be turning read-only on August 25th" Already Moved: magritte-metamodel phratch seaside metacello Unknown: moose-technology marsonpharo n

Re: [Pharo-dev] Nautilus new buttons not buttons?

2015-08-02 Thread Alexandre Bergel
Why not making the label text change color when the mouse is above? This cheap to do Alexandre > Le 1 août 2015 à 08:56, stepharo a écrit : > > Yes I think that we should do something to make sure that we understand that > this is a button. > > Stef > > >

Re: [Pharo-dev] cleanup rubric

2015-08-02 Thread Esteban Lorenzano
> On 02 Aug 2015, at 10:24, Nicolai Hess wrote: > > > Am 02.08.2015 10:09 vorm. schrieb "Alain Plantec" >: > > > > Hello all, > > Yes we have both PluggableTextMorph and Rubric so it is a mess. > > Yes Rubric was a fork, so a lot of code is duplicated. > > I wou

Re: [Pharo-dev] cleanup rubric

2015-08-02 Thread Nicolai Hess
Am 02.08.2015 10:09 vorm. schrieb "Alain Plantec" : > > Hello all, > Yes we have both PluggableTextMorph and Rubric so it is a mess. > Yes Rubric was a fork, so a lot of code is duplicated. > I would say just wait that all PluggableTextMorph uses are removed > then we will be able to clean-up thing

Re: [Pharo-dev] cleanup rubric

2015-08-02 Thread Alain Plantec via Pharo-dev
--- Begin Message --- Hello all, Yes we have both PluggableTextMorph and Rubric so it is a mess. Yes Rubric was a fork, so a lot of code is duplicated. I would say just wait that all PluggableTextMorph uses are removed then we will be able to clean-up things. Now, remember that I was not so excite