So the proposal is to

a) to move all from category '*Etoys-geometry* to category *geometry
eToy* and then the two methods

rotationCenter and rotationCenter:

to category 'rotate scale and flex'

-- HJH


On 6/11/18, Chris Cunningham <cunningham.cb at gmail.com> wrote:
> On Mon, Jun 11, 2018 at 9:27 AM, K K Subbu <kksubbu.ml at gmail.com> wrote:
>
>> On Monday 11 June 2018 06:24 PM, David T. Lewis wrote:
>>
>>> These two methods are sent by CircleMorph>>extent: in package
>>> Morphic-Basic,
>>> so moving them from Etoys to Morphic seems the the right thing to do.
>>> Does
>>> anyone disagree?
>>>
>>
>> rotationCenter is an optional not an intrinsic geometric property like
>> bounds, extent etc. So should it be moved into the category "rotate scale
>> and flex"?
>>
>> rotationCenter also works with other properties like forwardDirection
>> etc.
>> They should also be considered for merging into Morphic. In fact, all the
>> methods in Etoys-geometry could be moved to Morph as they don't use
>> anything specific to Etoys (player).
>>
>> Regards .. Subbu
>>
>> Looking at the definitions in the image, there are 4 definitions of these
> methods.  The 3 definitions NOT in Etoys are in the method category
> 'geometry etoy'.  So I'd suggest putting them there to at least have all of
> them in the same place.
>
> -cbc
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: category_geometry_etoy_Screenshot_2018-06-11.png
Type: image/png
Size: 225449 bytes
Desc: not available
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20180611/793f16b7/attachment-0001.png>