[etoys-notify] [JIRA] Commented: (SQ-161) Textual reference to dropped morphs/players

Karl Ramberg (JIRA) tracker at squeakland.org
Tue Dec 11 13:49:39 EST 2012


    [ http://tracker.squeakland.org/browse/SQ-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40829#action_40829 ] 

Karl Ramberg commented on SQ-161:
---------------------------------

http://source.squeak.org/etoys/Tools-kfr.13.mcz

==================== Summary ====================

Name: Tools-kfr.13
Author: kfr
Time: 11 December 2012, 7:46:58 pm
UUID: 0ea23466-cb95-f146-aad8-e9ba30466970
Ancestors: Tools-kfr.12

Insert players uniqueNameForReference when dropped on a ScriptEditor textual method pane. Simple support for objRef tiles added. Rejects most other dropped tiles at the moment.

> Textual reference to dropped morphs/players
> -------------------------------------------
>
>                 Key: SQ-161
>                 URL: http://tracker.squeakland.org/browse/SQ-161
>             Project: squeakland
>          Issue Type: Feature
>          Components: etoys
>            Reporter: team
>            Priority: Optional
>             Fix For: future release
>
>
> From TRAC  Ticket #9033 (karl, november 2008)
> (karl) A textual script do not have a reference to morphs/players in the project/World. This could be established the way it can be done in Workspaces by dropping the morph/player over the textual field.
> (scott) Unfortunately, the player-reference scheme in etoys is such that the "internal names" used within scripts compiled from tiles do not (necessarily) correspond to the external names seen in the UI, and -- most problematically -- the system sometimes changes the "internal names" automatically and behind the user's back. As long as only tile scripts are involved, there is no problem with the system automatically changing the name, because new scripts using the new names are created and compiled. For textually-code scripts, however, this doesn't work, since the user's source strings are all we have to work with, and it would be perilous to do a mindless find-and-replace of one internal name by another behind the user's back.
> A general reassessment of the way we refer to objects in scripts is in order, but probably not for the current round...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.squeakland.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the etoys-notify mailing list