Skip to content
This repository has been archived by the owner on Jan 21, 2022. It is now read-only.

[RFC]Exposed Core.VlcMediaPlayer and Interops.VlcManager #321

Merged

Conversation

jeremyVignelles
Copy link
Collaborator

It allows users to unlock features that are not yet implemented/too low-level to be implemented in the VlcControl.
What do you think about this? Is it too dangerous to let users play with the internals of this library?
Fixes #239

@mfkl
Copy link
Contributor

mfkl commented Sep 28, 2017

If you have a use for it and other people do too apparently, I don't see why it should not be exposed.

That being said, maybe add some ALL CAPS WARNING USE AT YOUR OWN RISK! or something in the comments, so the caller knows what he/she's getting into?

@jeremyVignelles
Copy link
Collaborator Author

I do have a warning, but not all caps, should I change that?
Thanks for your answer.

@mfkl
Copy link
Contributor

mfkl commented Sep 28, 2017

I would, that way they know you mean business. But the important part is that there is a warning 👍

@jeremyVignelles jeremyVignelles force-pushed the feature/internals-exposure branch from dd3d7af to 54ea3f2 Compare October 5, 2017 08:08
Jeremy Vignelles added 2 commits October 5, 2017 12:10
It allows users to unlock features that are not yet implemented/too
low-level to be implemented in the VlcControl.
@jeremyVignelles jeremyVignelles force-pushed the feature/internals-exposure branch from 54ea3f2 to a9ad545 Compare October 5, 2017 10:10
@jeremyVignelles jeremyVignelles merged commit a7cfb88 into ZeBobo5:develop Oct 5, 2017
@jeremyVignelles jeremyVignelles deleted the feature/internals-exposure branch October 5, 2017 10:17
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants