issue 496: Morph>>heading
Locked
 
|
Hi,
Morph>>heading is from eToy. It is used to rotate a Morph. If we remove it, we remove the possibility to rotate a morph. What are your positions about this behavior ? Do we considere it as a system behavior or as an eToy thing which must be removed ? Cheers, --- Jannik Laval PhD Student - Rmod Team - INRIA Certified Project Management Associate (IPMA) http://www.jannik-laval.eu http://rmod.lille.inria.fr --- _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
|
|
Hi,
I bring out a past message. And my question is more general. What do we want to keep from etoy ? Cheers, Jannik On Oct 22, 2009, at 09:33 , Laval Jannik wrote: > Hi, > > Morph>>heading is from eToy. > It is used to rotate a Morph. > If we remove it, we remove the possibility to rotate a morph. > > What are your positions about this behavior ? > Do we considere it as a system behavior or as an eToy thing which > must be removed ? > > Cheers, > > --- > Jannik Laval _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: issue 496: Morph>>heading
|
|
On Mon, Oct 26, 2009 at 11:13 AM, Laval Jannik <[hidden email]> wrote: Hi, I would said NOTHING in the core or even Pharo image. However, it would be a good idea to put all the interesting eToy stuff in an external package so that those who want to load that stuff, are able to do it.
_______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
|
|
On Oct 26, 2009, at 15:21 , Mariano Martinez Peck wrote:
I agree with you.
Is eToy maintained in Pharo ? Because, make an external package of it needs a big work... So, do we want a different package ? or maybe something which come from the etoy community, something up to date. Cheers, Jannik
--- Jannik Laval PhD Student - Rmod Team - INRIA Certified Project Management Associate (IPMA) --- _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: issue 496: Morph>>heading
|
|
2009/10/26 Laval Jannik <[hidden email]>
I don't know. Neither I care. I mean, why to put something specific in a generic language/enviroment ??? I see eToy as any other application. For example, my own (SqueakDBX), or magma, or XXX package. Why to put those specific packages in the core image? If you want, you load them. It is easy. And if they are maintained or not, it doesn't depends on Pharo developers, but in the external package developers. I decide if SqueakDBX works on Pharo or not, not Pharo developers.
I don't think so. You just need to create the package. And then, instead of removing code, you move it to that package. What can be a lot of work is to keep that package up to date and working, but that's not Pharo responsibility.
Maybe the eToy community can even touch that external package. what do you think ?
_______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: issue 496: Morph>>heading
|
|
Etoy is more complex than you think. It would be (nearly) impossible.
Marcus _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
|
|
Yes, Marcus is right. But are there some behaviors that we want to keep and integrate in Core ? For example, the Rotate functionality in the halo. Cheers, Jannik On Oct 26, 2009, at 16:22 , Marcus Denker wrote:
_______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: issue 496: Morph>>heading
|
|
In reply to this post by Marcus Denker-3
2009/10/26 Marcus Denker <[hidden email]>
Grrr Sorry, so, I may be a dreamer :( Of course I know very little about Morphic, so I totally believe you.
I was just asking as one of the Pharo goals is to be "clean". Is even that complicated to do it in little steps? For example, consider this particular case Jannik said as a step. Again, I know nothing about Morphic :(
_______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: issue 496: Morph>>heading
|
|
In reply to this post by jannik laval
jannik
you ask the right question And this is ugly. Now we could think about possible usecases. If we build a image processing system: we need it but in that case we can copy it. Stef > Yes, Marcus is right. > > But are there some behaviors that we want to keep and integrate in > Core ? > For example, the Rotate functionality in the halo. > > Cheers, > Jannik > > > On Oct 26, 2009, at 16:22 , Marcus Denker wrote: > >> >>> >>>> However, it would be a good idea to put all the interesting eToy >>>> stuff in an external package so that those who want to load that >>>> stuff, are able to do it. >>> >>> >>> >>> Because, make an external package of it needs a big work... >>> >>> I don't think so. >> >> Etoy is more complex than you think. It would be (nearly) impossible. >> >> >>> You just need to create the package. And then, instead of removing >>> code, you move it to that package. What can be a lot of work is to >>> keep that package up to date and working, but that's not Pharo >>> responsibility. >>> >> Nope. Etoy is programed in a way that makes things like this *a >> lot* of work. >> >> >> Marcus >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: issue 496: Morph>>heading
|
|
In reply to this post by jannik laval
I think a good criterium is whether the functionality is used in Pharo
today. Does anybody use rotating morphs? I don't think so. Cheers, Adrian On Oct 26, 2009, at 16:40 , Laval Jannik wrote: > Yes, Marcus is right. > > But are there some behaviors that we want to keep and integrate in > Core ? > For example, the Rotate functionality in the halo. > > Cheers, > Jannik > > > On Oct 26, 2009, at 16:22 , Marcus Denker wrote: > >> >>> >>>> However, it would be a good idea to put all the interesting eToy >>>> stuff in an external package so that those who want to load that >>>> stuff, are able to do it. >>> >>> >>> >>> Because, make an external package of it needs a big work... >>> >>> I don't think so. >> >> Etoy is more complex than you think. It would be (nearly) impossible. >> >> >>> You just need to create the package. And then, instead of removing >>> code, you move it to that package. What can be a lot of work is to >>> keep that package up to date and working, but that's not Pharo >>> responsibility. >>> >> Nope. Etoy is programed in a way that makes things like this *a >> lot* of work. >> >> >> Marcus >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
|
|
In reply to this post by Stéphane Ducasse
So,
Is anyone use the rotation in pharo-Core ? If not, I will remove it. And I will try to put it in another package, which will be loaded after. Jannik On Oct 26, 2009, at 19:11 , Stéphane Ducasse wrote: > jannik > > you ask the right question > And this is ugly. Now we could think about possible usecases. > If we build a image processing system: we need it but in that case we > can copy it. > > Stef > > >> Yes, Marcus is right. >> >> But are there some behaviors that we want to keep and integrate in >> Core ? >> For example, the Rotate functionality in the halo. >> >> Cheers, >> Jannik >> >> >> On Oct 26, 2009, at 16:22 , Marcus Denker wrote: >> >>> >>>> >>>>> However, it would be a good idea to put all the interesting eToy >>>>> stuff in an external package so that those who want to load that >>>>> stuff, are able to do it. >>>> >>>> >>>> >>>> Because, make an external package of it needs a big work... >>>> >>>> I don't think so. >>> >>> Etoy is more complex than you think. It would be (nearly) >>> impossible. >>> >>> >>>> You just need to create the package. And then, instead of removing >>>> code, you move it to that package. What can be a lot of work is to >>>> keep that package up to date and working, but that's not Pharo >>>> responsibility. >>>> >>> Nope. Etoy is programed in a way that makes things like this *a >>> lot* of work. >>> >>> >>> Marcus >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [hidden email] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
|
|
El mié, 28-10-2009 a las 07:03 +0100, Laval Jannik escribió:
> So, > > Is anyone use the rotation in pharo-Core ? > If not, I will remove it. > And I will try to put it in another package, which will be loaded after. > Remove it, please, is not a core feature. > Jannik > > > On Oct 26, 2009, at 19:11 , Stéphane Ducasse wrote: > > > jannik > > > > you ask the right question > > And this is ugly. Now we could think about possible usecases. > > If we build a image processing system: we need it but in that case we > > can copy it. > > > > Stef > > > > > >> Yes, Marcus is right. > >> > >> But are there some behaviors that we want to keep and integrate in > >> Core ? > >> For example, the Rotate functionality in the halo. > >> > >> Cheers, > >> Jannik > >> > >> > >> On Oct 26, 2009, at 16:22 , Marcus Denker wrote: > >> > >>> > >>>> > >>>>> However, it would be a good idea to put all the interesting eToy > >>>>> stuff in an external package so that those who want to load that > >>>>> stuff, are able to do it. > >>>> > >>>> > >>>> > >>>> Because, make an external package of it needs a big work... > >>>> > >>>> I don't think so. > >>> > >>> Etoy is more complex than you think. It would be (nearly) > >>> impossible. > >>> > >>> > >>>> You just need to create the package. And then, instead of removing > >>>> code, you move it to that package. What can be a lot of work is to > >>>> keep that package up to date and working, but that's not Pharo > >>>> responsibility. > >>>> > >>> Nope. Etoy is programed in a way that makes things like this *a > >>> lot* of work. > >>> > >>> > >>> Marcus > >>> > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> [hidden email] > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> [hidden email] > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > [hidden email] > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project Miguel Cobá http://miguel.leugim.com.mx _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
|
|
On Oct 28, 2009, at 16:26 , Miguel Enrique Cobá Martinez wrote: > El mié, 28-10-2009 a las 07:03 +0100, Laval Jannik escribió: >> So, >> >> Is anyone use the rotation in pharo-Core ? >> If not, I will remove it. >> And I will try to put it in another package, which will be loaded >> after. >> > > Remove it, please, is not a core feature. I like this answer :) I will do this stuff with pleasure :) Cheers, Jannik _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: issue 496: Morph>>heading
|
|
2009/10/28 Laval Jannik <[hidden email]>:
> > On Oct 28, 2009, at 16:26 , Miguel Enrique Cobá Martinez wrote: > >> El mié, 28-10-2009 a las 07:03 +0100, Laval Jannik escribió: >>> So, >>> >>> Is anyone use the rotation in pharo-Core ? >>> If not, I will remove it. >>> And I will try to put it in another package, which will be loaded >>> after. >>> >> >> Remove it, please, is not a core feature. > > I like this answer :) > I will do this stuff with pleasure :) Are you sure, this is not used anywhere ? Sometimes you need to draw a morph with a specific heading. Best regards, -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/ _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
|
|
On Oct 29, 2009, at 04:27 , Serge Stinckwich wrote: > 2009/10/28 Laval Jannik <[hidden email]>: >> >> On Oct 28, 2009, at 16:26 , Miguel Enrique Cobá Martinez wrote: >> >>> El mié, 28-10-2009 a las 07:03 +0100, Laval Jannik escribió: >>>> So, >>>> >>>> Is anyone use the rotation in pharo-Core ? >>>> If not, I will remove it. >>>> And I will try to put it in another package, which will be loaded >>>> after. >>>> >>> >>> Remove it, please, is not a core feature. >> >> I like this answer :) >> I will do this stuff with pleasure :) > > Are you sure, this is not used anywhere ? > Sometimes you need to draw a morph with a specific heading. This is an eToy thing, so in a perfect world, it should not be used :). Now, do you use, sometimes, this functionality in pharoCore ? or do you think this behavior should be offer by pharoCore ? heading is a number which is only use in the rotation behavior. I think it must be provided by eToy, not by Core. No ? Cheers, Jannik > Best regards, > -- > Serge Stinckwich > UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam > Smalltalkers do: [:it | All with: Class, (And love: it)] > http://doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: issue 496: Morph>>heading
|
|
Hi Jannik and all,
Laval Jannik a écrit : > On Oct 29, 2009, at 04:27 , Serge Stinckwich wrote: > >> Are you sure, this is not used anywhere ? >> Sometimes you need to draw a morph with a specific heading. >> ... > Now, do you use, sometimes, this functionality in pharoCore ? or do > you think this behavior should be offer by pharoCore ? > > heading is a number which is only use in the rotation behavior. > > I think it must be provided by eToy, not by Core. > This was brought by etoy but it is not etoy specific. Of course the heading message is present in the Morph class, which is not good but I see it more as a TransformationMorph /MatrixTransformationMorph functionality. As this, for now, I think it is not so bad. And what about the scaling behavior for example ? Cheers Alain > No ? > > Cheers, > Jannik > > >> Best regards, >> -- >> Serge Stinckwich >> UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam >> Smalltalkers do: [:it | All with: Class, (And love: it)] >> http://doesnotunderstand.org/ >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
«
Return to Pharo Smalltalk Developers
|
1 view|%1 views
| Free forum by Nabble | Edit this page |