[IAEP] TA v9

Walter Bender walter.bender at gmail.com
Sat Jan 31 21:22:33 EST 2009

Broadening the discussion.

I guess my preference is to use Pippy for Python. The TA example is
just to get people interested in digging deeper. I think it would be
better to put effort into importing more of the TA environment into
Pippy than making TA yet another Python editing environment.



Regarding alt-tab, the behavior I am familiar with is to use alt-tab
to cycle between all open activities and shift-alt-tab to reverse

On Sat, Jan 31, 2009 at 9:01 PM,  <forster at ozonline.com.au> wrote:
>> I can import a Pippy file into TA, but:
> I would rather see python code typed directly onto a ta block, there may be technical reasons why you prefer to import a file.
> (which reminds me of another issue i have with the sugar ui, when you alt tab in windows you go to the last window, and can quickly swap between two apps, in Sugar you dont and need to alt tab alt tab alt tab...)
>> (1) you cannot do much debugging inside of Pippy itself since you
>> don't have access to the lc (logo code) globals or the canvas.
> agreed the pippy ide is of little use here
>> (2) you must name your function myblock and pass it two arguments or
>> you'll get an error.
> no prob
>> When actually running your code within TA, you can view the log file
>> to see any error messages, which is probably OK (this is how I debug
>> in the general case).
> it would be better if errors showed on the canvas, off the cuff i dont know where to find the log, and would have to alt tab alt tab.. and refresh a viewer to see if there were errors,
> thanks

Walter Bender
Sugar Labs

More information about the IAEP mailing list