Hi all,
I am working hard on being able to test and edit my configurations with Metaceller as well. I do this currently for my own needs: when I need to change a configuration, I change this.
The new metaceller can be opened in Moose with the command GTMetaceller2 open. I am not done yet, as some of the functionality that is in Metaceller, does not have a place in the new Metaceller. Also I have not tested all my buttons ... a few buttons even have a todo as action. For anyone who is curious: give it a try. It is in beta, so you should expect some bugs. But if you report bugs, I will fix them asap.
One of the configurations I have changed is the configuration of GToolkit, so please take a look at how it formats the code. It writes in the order of the platforms, and within a platform it first writes projects, then packages and finally groups. And within it orders them alphabetically. So in the beginning this will cause a lot of changes, but it should be more stable if everyone starts using Metaceller to change their configurations.
Please give your first impressions,
Diego
Hi,
in TRAbstractBoxShape there is the leftPosition: method wichi calls
position: but position: is not defined in TRAbstractBoxShape or its
superclasses.
I don't know if position: has been forgotten or if leftPosition: is not
suppose to be implemented.
Leo Perard
Hi all,
Does anyone know why the TextProperty underline does not work anymore in the glamour browsers? Is this a problem with the default font in Moose? Because with the original font it seems to work.
Diego
Hi all,
I am working hard on being able to test and edit my configurations with Metaceller as well. I do this currently for my own needs: when I need to change a configuration, I change this.
The new metaceller can be opened in Moose with the command GTMetaceller2 open. I am not done yet, as some of the functionality that is in Metaceller, does not have a place in the new Metaceller. Also I have not tested all my buttons … a few buttons even have a todo as action. For anyone who is curious: give it a try. It is in beta, so you should expect some bugs. But if you report bugs, I will fix them asap.
One of the configurations I have changed is the configuration of GToolkit, so please take a look at how it formats the code. It writes in the order of the platforms, and within a platform it first writes projects, then packages and finally groups. And within it orders them alphabetically. So in the beginning this will cause a lot of changes, but it should be more stable if everyone starts using Metaceller to change their configurations.
Please give your first impressions,
Diego
Currently, there is no object in my knowledge to represent a metric in
Moose. I would like to have this kind of object to ask it for example the
name of the metric, a description, the associated selector...
Ideally this object should have the same behaviour than Unit framework; it
should resolve units for example if you divide number of bugs by lines of
code, you should get numberOfBugs.linesOfCode^(-1); then if you multiply
this by line of code to get the estimated average value you get
numberOfBugs...
If I missed an existing implementation close to this, thank you very much
in advance to indicate me otherwise I will create a project for this and
you are welcome to contribute.
--
*Guillaume Larcheveque*
Begin forwarded message:
> From: Igor Stasenko <siguctua(a)gmail.com>
> Subject: Re: [rmod] One more productive day: 2014-04-01
> Date: 1 Apr 2014 18:28:31 GMT+2
> To: "rmod(a)inria.fr list" <rmod(a)inria.fr>
> Reply-To: rmod(a)inria.fr
>
> - updated NB & Athens with fix, including configs and slice
> https://pharo.fogbugz.com/f/cases/13150/Different-memory-alignment-on-diffe…
>
>
> On 1 April 2014 18:00, <seaside(a)rmod.lille.inria.fr> wrote:
> Your daily reminder to brag on progress :)
> Just answer this mail, it will go to rmod(a)inria.fr
>
>
>
>
> --
> Best regards,
> Igor Stasenko.
Hi guys.
This is strange that moose is using a so old version of Athens.
Stef
Begin forwarded message:
> From: Igor Stasenko <siguctua(a)gmail.com>
> Subject: Re: [Pharo-dev] Font problem is still there
> Date: 28 Mar 2014 14:03:17 GMT+1
> To: Pharo Development List <pharo-dev(a)lists.pharo.org>
> Reply-To: Pharo Development List <pharo-dev(a)lists.pharo.org>
>
> so, i checked both in 4.9 and 5.0 Moose images on linux...
> got weird results and sometimes crashes.
>
> in 5.0 image the version is:
> Athens-Cairo-MarcusDenker.51
>
> - this one uses pretty old code, which renders text using 'toy' cairo api for text rendering.
>
> in my working image, where i work every day it is:
>
> Athens-Cairo-SvenVanCaekenberghe.64
>
> and there's also couple important fixes since .51 as well as different font rendering code which no longer using toy api..
>
> so, guys, if you want me to continue, please try using latest versions and report problems about it,
> because it makes no sense to find a fix in something which outdated and thrown away many months ago.
>
> Load the latest dev version of Athens from smalltalkhub (it is version 2.5)
>
> ConfigurationOfAthens loadDevelopment.
>
> try it out.
>
>
> Here's what i got on latest fresh vanilla out of the box Pharo 3.0 image on linux system:
>
>
>
>
> P.S. i am not saying that it is *impossible* that there is problems in new version, just asking you to report problems with that version,
> not one which year(s) old.
>
> --
> Best regards,
> Igor Stasenko.
