There is no different than using FrodoDVD in RR and MPC in RR. That is what I try to avoid.Originally Posted by Enforcer
Why is it people always want every thing to be integratedOriginally Posted by MatrixPC
I think using dedicated plugin or external program is often better than be limited with quickly coded extension... (as long as both frontend and external program both have enough communication interface and skinning facilities to make them work together seamlessly ofcourse)
Thanks for all the encouragement... it's great to know I have a lot of supporters!
The DVD feature is going to be tough. I will integrate it if I can find a DLL or OCX to use with my project. Most likely, though, it's going to involve the use of an external DVD player. However, I don't know of any freeware DVD players, and all the DVD players I have used are bloatware in my opinion.
As it stands now, DVD functionality most likely will not be included in the first beta release. I am currently experimenting with a DVD plugin for Winamp, but it's very buggy at the moment.
Don't know how difficult this will be, but are you able to write some code to make a Live Playlist. I could help you write some code but it probably wont be for a while...waiting for parts for my carputer right now.
I dont know if u have anykind of plugin infrastructure in mind, but if u plan to do one, i would like to suggest that if u could model it so that my upcoming PervTalk backend program would be nicely integradable.
PervTalk is not published yet anywhere, but i have it pretty much working on my computer. Public release is going to be in next few weeks. PervTalk is originally modelled for Xlobby HTPC frontend, but it is general, whole point of it is that it can be fitted to any frontend with suitable plugin infrastucture, PervTalk as it self is just communication media for different software which purpose is make integration of different software easier and crosstalk between them possible. I have also almost ready PervTalk plugins (called devices) for Zoom Player (called ZPd) and kX driver controls (called kXd). Idea of pervtalk is simple, instead of making one plugin between every pair of software, which needs to be redone each time either one of software is changed, pervtalk only reguires one plugin for each software and after that they can communicate together...
I know this is bit early and im sure u have thousand of other things to think first and PervTalk is not ready for release just yet. I just thought to give advance warning before u decide type of your plugininfrastructure...
EDIT: also this could make including DVD as walk in park... since PervTalk makes it possible to control Zoom player through ZPd... only thing that would be left for fronend would be embedding Zoom Player window... have to say though, that im not sure if that solution would be lightweight enough for carpc... since i have only experimented it in HTPC.
I'm not 100% sure what PervTalk does, but from what I gather, a plugin can talk to PervTalk, which can then talk to various frontends, thus allowing "universal" plugins (any plugin -> PervTalk -> Centrafuse or RR or Freeway, etc.)Originally Posted by P3rv3rt B3ar
Is this correct? If so, then that's a pretty cool idea. I've not experimented with a plugin interface at all as of yet.
P.S... why did you choose the name PervTalk?
Yes, u understanded absolutely correct.
Name PervTalk comes from my screenname and common way here to name similar interfaces (for example MonkeyTalk from Ninja Monkey's Map Monkey). Actually PervTalk is just name of the communication protocol, name of software which implements it is PervHub.