By Paul Murray on Monday, 08 February 2016
Replies 15
Likes 0
Views 1.1K
Votes 0
Hi Support

I hope that you all had a well needed break.
And wish you all a great new year of the ape!

I would like customisations (adding plugins) that I make to the video.js frame work to be ES update proof.

I am looking at plugins that I would like to test here:

http://videojs.com/plugins/

As of now any new video.js plugins that I install will be overwritten when I do the next ES update.

Would there be a way to implement this so that ES updates do not break video.js added plugins?

thanks

Paul
Hey Paul,

Thank you Unfortunately right now there's no way to add additional plugins as we actually ride on our MVC framework to render videojs
·
Monday, 08 February 2016 21:24
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Mark

If I understand you correctly:
In other words even if I wanted to add plugins there would be no way to do so as of now?
To be perfectly honest it does seem a little odd not being able to extend a video component?
Here is a link to something that I believe has been built with video.js and some plugins:

http://ted.clarify.io/

It seems to be built with this video.js plugin amongst others:

https://github.com/Clarify/videojs-clarify-annotations

Do you think that it would be possible to change this situation and allow for video.js plugins?

best

Paul
·
Monday, 08 February 2016 22:02
·
0 Likes
·
0 Votes
·
0 Comments
·
The only way for you to add additional modules:

1. Turn on development mode
2. Load up the videojs library in /media/foundry/4.0/
3. Add additional plugins into the videojs library
4. Recompile the javascript again
·
Monday, 08 February 2016 22:37
·
0 Likes
·
0 Votes
·
0 Comments
·
This is over my head.
Bbbbbbut I might be able to find some one who could help me do this.
Assuming that I succeed with steps 1-4.
And then update ES after step 1-4.
Will the plugins that I installed during steps 1-4 still be there?
·
Monday, 08 February 2016 22:46
·
0 Likes
·
0 Votes
·
0 Comments
·
It depends if we update Foundry on the next version If we did, it would overwrite files.
·
Monday, 08 February 2016 22:49
·
0 Likes
·
0 Votes
·
0 Comments
·
So if the current Foundry folder version is this here:

JOOMLA/media/foundry/4.0/scripts/videojs.js

Added plugins would still work after every ES upgrade using Foundry 4 and using your 1-4 method above.
Things would break down again the moment first time an ES upgrade uses Foundry 5?

In the moment that ES uses Foundry 5...
Can I move my files/plugins from the Foundry 4 folder to Foundry 5 folder?
Again using the 1-4 method if necessary that you outlined above.
And have every thing work again for every ES upgrade using Foundry 5!

Plugins here after first ES update including Foundry upgrade:
JOOMLA/media/foundry/5.0/scripts/videojs.js
·
Monday, 08 February 2016 23:12
·
0 Likes
·
0 Votes
·
0 Comments
·
EasySocial is riding on 4.0.41. If we have some updates, 4.0.42, and it will overwrite the changes.
·
Monday, 08 February 2016 23:25
·
0 Likes
·
0 Votes
·
0 Comments
·
So in a way I am playing Russian roulette every time I update ES?

Things might or might not break depending on whether or not you are updating the Foundry version in the background!

Is there any way I can follow on what foundry version you are on in advance?
e.g. in ES version change logs?
·
Monday, 08 February 2016 23:45
·
0 Likes
·
0 Votes
·
0 Comments
·
In a way, yes Therefore, it's best to not perform these hacks
·
Tuesday, 09 February 2016 00:00
·
0 Likes
·
0 Votes
·
0 Comments
·
Is there any way I can follow on what foundry version you are on in advance?
Other stuff that I should keep an eye on?
For me adding plugins to a video tool is normal and not a hack.
Just saying
·
Tuesday, 09 February 2016 00:15
·
0 Likes
·
0 Votes
·
0 Comments
·
Sorry but we do not have a changelog for this.
·
Tuesday, 09 February 2016 00:20
·
0 Likes
·
0 Votes
·
0 Comments
·
Mark I understand that you are trying to protect me from myself.
I would never attempt any of this stuff with out professional help.
There must be some way of checking what the foundry version is?
e.g. downloaded the latest ES Launcher and search for “Foundry 4.0.41” or similar?
Once I know where to look I can check this before pulling the trigger?
i.e. check the Foundry level manually before updating.
I have some one who can help me with stuff like this.

But I need to be able to point him in the right direction.
·
Tuesday, 09 February 2016 00:44
·
0 Likes
·
0 Votes
·
0 Comments
·
The only way to check for the foundry version is at /media/foundry/4.0/version
·
Tuesday, 09 February 2016 13:54
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Mark

Thanks for this.

best

Paul
·
Tuesday, 09 February 2016 16:15
·
0 Likes
·
0 Votes
·
0 Comments
·
No problem
·
Tuesday, 09 February 2016 16:19
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post