[Xerte] Xerte3: Hide Play/Stop/Tracker on VideoIcon

[Julian Tenney]

Your code may be assuming myIcon.videoDisplay: now you can simply
address myIcon.

-----Original Message-----
From: Tenney Julian 
Sent: 30 June 2010 16:19
To: 'Xerte discussion list'
Subject: RE: [Xerte] Xerte3: Hide Play/Stop/Tracker on VideoIcon

Can you make a new piece with just a video object in there and it works
OK?

The old synch events stuff might be breaking it? The only properties you
should need are the x / y and the .controls and .source.

There is no 'synch' event to listen for anymore, as you can listen for
'progress'.

-----Original Message-----
From: xerte-bounces at lists.nottingham.ac.uk
[mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Peter
Huppertz
Sent: 30 June 2010 16:14
To: Xerte discussion list
Subject: Re: [Xerte] Xerte3: Hide Play/Stop/Tracker on VideoIcon

Thanks for implementing this. I upgraded to the last svn, unfortunately
my piece does not compile anymore. I guess the only reason for that will
be the change of the VideoIcon. In some scripts I refer to
videoIcon.videoDisplay, I think I have to change this. Any other
thoughts why it stops compiling?


On 30.06.2010, at 17:01, Julian Tenney wrote:

> OK, now VideoDisplayIcon extends VideoDisplay. You can still turn the
> controls on or off using the .controls property, and you can also get
at
> all the native events using the usual event handlers directly on the
> icon. Think of the icon as the VideoDisplay object with controls,
rather
> than the composite object before.
> 
> Let me know if there are any hiccups,
> 
> -----Original Message-----
> From: xerte-bounces at lists.nottingham.ac.uk
> [mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Julian
Tenney
> Sent: 30 June 2010 12:13
> To: Xerte discussion list
> Subject: RE: [Xerte] Xerte3: Hide Play/Stop/Tracker on VideoIcon
> 
> Yes, but that's going to take a bit more work.
> 
> I've made it so that you can now use the .controls property [defaults
to
> true] to turn off the controls if you want to, and then make your own
> controls.
> 
> I'd still like to make it easier to get at the all the native events
> though...
> 
> 
> -----Original Message-----
> From: xerte-bounces at lists.nottingham.ac.uk
> [mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Peter
> Huppertz
> Sent: 30 June 2010 11:57
> To: Xerte discussion list
> Subject: Re: [Xerte] Xerte3: Hide Play/Stop/Tracker on VideoIcon
> 
> I think you had once the idea to have the raw VideoIcon and an extra
> ControlbarIcon. That would be perfect for me. Than you have the free
> choice where to put it (above the video, below, over). Ideally the
> ControlbarIcon would have properties like pauseButton:
> "media/myPauseButton", pauseButtonOver: "media/myPauseButtonOver". The
> question remains on how to tie VideoIcon and ControlbarIcon together.
> I'm not a big fan of giving IconIDs to all the icons. Perhaps it would
> be possible that the ControlbarIcon detects if it has a parent
> VideoIcon?
> 
> On 30.06.2010, at 12:48, Julian Tenney wrote:
> 
>> I was going to add a .controls property so you could turn them off by
>> setting it to false; alternatively you could have a different icon,
>> which inherited directly from VideoDisplay so you can access all the
>> events as you wanted. There would be two icons:
>> 
>> VideoIcon //the raw video display object
>> VideoDisplayIcon //what we have now with the controls
>> 
>> What do you think?
>> 
>> -----Original Message-----
>> From: xerte-bounces at lists.nottingham.ac.uk
>> [mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Peter
>> Huppertz
>> Sent: 30 June 2010 11:45
>> To: Xerte discussion list
>> Subject: [Xerte] Xerte3: Hide Play/Stop/Tracker on VideoIcon
>> 
>> I'm not sure what the status of the VideoIcon is. I think you thought
>> about changing it ... For some of my videos it would be nice to have
> the
>> possibility to hide the controlbar completely. At the moment I think
>> it's not possible because the buttons and the tracker are declared
>> private. Perhaps it would make sense to create a new public
>> (Sprite/Shape/Canvas?) controlbar as a parent of the buttons and the
>> tracker and which could either turned on and off by a property or at
>> least using .getChildAt(1).visible = false.
>> What do you think?
>> 
>> Peter
>> ==================================
>> Peter Huppertz
>> E-learning and IT Specialist
>> International Centre for Asset Recovery
>> Basel Institute on Governance
>> Phone: +41 61 205 55 18
>> Fax: +41 61 267 55 19
>> 
>> _______________________________________________
>> Xerte mailing list
>> Xerte at lists.nottingham.ac.uk
>> http://lists.nottingham.ac.uk/mailman/listinfo/xerte
>> _______________________________________________
>> Xerte mailing list
>> Xerte at lists.nottingham.ac.uk
>> http://lists.nottingham.ac.uk/mailman/listinfo/xerte
> 
> ==================================
> Peter Huppertz
> E-learning and IT Specialist
> International Centre for Asset Recovery
> Basel Institute on Governance
> Phone: +41 61 205 55 18
> Fax: +41 61 267 55 19
> 
> _______________________________________________
> Xerte mailing list
> Xerte at lists.nottingham.ac.uk
> http://lists.nottingham.ac.uk/mailman/listinfo/xerte
> _______________________________________________
> Xerte mailing list
> Xerte at lists.nottingham.ac.uk
> http://lists.nottingham.ac.uk/mailman/listinfo/xerte
> _______________________________________________
> Xerte mailing list
> Xerte at lists.nottingham.ac.uk
> http://lists.nottingham.ac.uk/mailman/listinfo/xerte

==================================
Peter Huppertz
E-learning and IT Specialist
International Centre for Asset Recovery
Basel Institute on Governance
Phone: +41 61 205 55 18
Fax: +41 61 267 55 19

_______________________________________________
Xerte mailing list
Xerte at lists.nottingham.ac.uk
http://lists.nottingham.ac.uk/mailman/listinfo/xerte