Hi,
I attached a new version of the step button. This one uses Karl's bug picture, it resets the etoys debugger, and it keeps the visual feedback.
A few remarks, though:
* I modified PhraseTileMorph>>#try to use the top editor's player when possible. I don't think it could be dangerous, but I'm not sure so I thought you should know...
* I had to make a HighlightMorph class to make the rectangle follow the highlighted tile. While writing this I realized a lot of Etoys mechanisms could be made much simpler if we make all morphs trigger events whenever one of its properties change. This way we could avoid a lot of stepping morphs (for instance, all the Updating___Morphs). What do you think?
Cheers,
Richo
P.S. I borrowed the "salmon sniff" project for the example... I'm not feeling very creative today :)
On Wed, Nov 16, 2011 at 7:23 AM, karl ramberg
<karlramberg@gmail.com> wrote:
On Wed, Nov 16, 2011 at 1:12 AM, Ricardo Moran
<richi.moran@gmail.com> wrote:
Yes, you're right. One thing I was thinking was to move the "timesToRepeat" property from the TimesRepeatTile to the EtoysDebugger, and when hiting the try button or the tick clock, reinitialize the EtoysDebugger altogether.
This sounds right. Once you press other buttons the debugger should be reinitialized.
Also, maybe it would be a good idea to leave the visual feedback instead of deleting after a short while, what do you think?¨
I think this could be tested.
Karl
On Tue, Nov 15, 2011 at 8:00 PM, karl ramberg
<karlramberg@gmail.com> wrote:
One issue or maybe feature I found with the TimesRepeatTile is that the Try button does not reset the timesToRepeat property.
So the debug button jumps into the TimesRepeatTile and you press the Try button, the debug button will hi-light the same tile you left before clicking the Try button.
KarlOn Tue, Nov 15, 2011 at 11:34 PM, karl ramberg
<karlramberg@gmail.com> wrote:
Hi I think this code looks quite nice and I think it does what it should.
I can't see how it could be much simpler either.
Others chime in here.
I made a drawing of a bug that maybe could be used as the debug button.
Karl
On Mon, Nov 14, 2011 at 9:21 PM, Ricardo Moran
<richi.moran@gmail.com> wrote:
This version works with the repeat tile, and I replaced the red button with the "next page" button from books. It's more intention revealing, don't you think? :)
Although it seems to work fine, I think the code should be examined before inclusion because I have the feeling the code is too complex for what it does and I'm not sure how to improve it...
To make it easy for review, I put all the code in a package called "Etoys-Debugger" (except for the code adding the button to the row editor). I don't mean we should upload them as separate packages but it might help to review the code.
Thanks!
Richo
On Mon, Nov 14, 2011 at 4:15 AM, karl ramberg
<karlramberg@gmail.com> wrote:
This is really nice, Richo.So very useful. We must add this to the image :-)
Maybe enhance the look of the red button a little.
KarlOn Mon, Nov 14, 2011 at 5:39 AM, Scott Wallace
<scott.wallace@squeakland.org> wrote:
Yay, Richo! Outstanding!
-- Scott
On Nov 12, 2011, at 12:33 PM, Ricardo Moran wrote:
> Hi,
>
> I've added a simple "step over" button in the script editor. I attached a project to demonstrate. For now, it's an ugly red circle because I don't have a nice image, but it should work as expected.
>
> Limitation: it doesn't work with the repeat tile yet. And it could probably be coded more nicely.
>
> Cheers,
> Richo
_______________________________________________
etoys-dev mailing list
etoys-dev@squeakland.org
http://lists.squeakland.org/mailman/listinfo/etoys-dev