8 Feb
2012
8 Feb
'12
2:10 p.m.
Hi,
On Wed, Feb 8, 2012 at 1:37 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote:
Hi,
I think next moose move is to run in pharo 1.4. Isn't?
After we release 1.3. As I said, the problem is that we do not have a
proper configuration for 1.3, so we are stuck.
So, best approach is start moving moose components to
pharo, step by step. This is where metacello can be really valuable:
-you move glamour
-then you move another moose component, etc.
-in the end, you move all moose.
In the mean time, you can keep moose for 1.3 with some bugfixes if needed (and yes, you
will have some mess in version, if you doit wrong: best way is to not use same
autoassigned numbers for bugfix monticello versions). For instance
"Glamour-Helpers-Author-NewNumber.mcz" could be numbered:
"Glamour-Helpers-FixNumber-Author-OldNumber.mcz" (sounds messy, but as there
shouldn't be much fix versions, not a really issue)
But this is, of course, in the assumption effort will be moving to 1.4 as a priority (and
I think it should).
It is, but first we have to release 4.6 on pharo 1.3.
I can prepare a metacello version for glamour in pharo
1.4, yes...
Actually, I am first interested in the configuration for 1.3.
Afterwards the 1.4 one :).
Cheers,
Doru
best,
Esteban
El 08/02/2012, a las 3:50a.m., Tudor Girba escribió:
--
www.tudorgirba.com
"Every thing has its own flow"
Theoretically yes. In practice:
- The Glamour configuration does not have proper versioning numbers (and basically no
real way to update those numbers properly). It would be great to get one working, but it
is also important to have it working within the whole of Moose, which is not so easy
apparently. Would you like to work on this?
- Working in the same repository for two versions of Pharo will create a mess with the
numbering scheme. I would be happy to be proved wrong.
Cheers,
Doru
On 7 Feb 2012, at 21:41, Esteban Lorenzano wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev I don't think so... but why wait? we can
create a new metacello config to deal with 1.4 without harm 1.3.
best,
Esteban
El 07/02/2012, a las 4:27p.m., Tudor Girba escribió:
--
www.tudorgirba.com
"Presenting is storytelling."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi Esteban,
Sounds great. Are the changes compatible with 1.3? If not, I would prefer to wait until
Moose is out. Any day now.
Cheers,
Doru
On 7 Feb 2012, at 17:39, Esteban Lorenzano wrote:
> Hi,
>
> I made glamour to load on pharo 1.4... now, I have some errors on tests (17), most of
them because MorphTreeMorph>>#mouseUp:onMorph: does not exists anymore.
> I don't know how to fix that. Should I commit my changes anyway, and hope some
benevolent developer to fix that (Doru?)
>
> best,
> Esteban
>
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"What is more important: To be happy, or to make happy?"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev