.Net FrontEnd - Page 2

YukonSUT · 01-07-2006, 02:49 PM

I've been investigating doing this exact project in C# for about a year now, and I even started prototyping a MediaPlayer app on DirectX 9, but just didn't have the time to dedicate to developing a full fledged app.

All of the other app's here are really well intentioned, and people did really great jobs with what they had to work with, but C# and the .Net platform have really opened up some great tools that I think could be used to make a great front end.

I can't wait to contribute to this project in some form or another. Whenever you're comfortable with releasing this project, I look forward to seeing it.

dorgan1983 · 01-07-2006, 04:24 PM

Would you like any help on this project, I know both vb.net and C# and would be willing to help.

zzachattack2 · 01-07-2006, 08:33 PM

Thank you both for your interest in helping.

Dorgan... if you'd like to contribute you could start developing some of the plugins when the sdk is released, which should be pretty soon, as the base is pretty much done.

FMode · 01-08-2006, 09:01 AM

Quote: Originally Posted by zzachattack2

...All running plugins are inside a pluginhost. And every plugin inherits the Plugin class. So interacting with a plugin can be as simple as invoking a known member on a select plugin using reflection. Or... if you know the interface to a specific plugin, you can cast the select plugin to its known type and interact directly with it.
....

...to its known type at compiletime (=early binding) ? The "Intellisense" feature is a MUST IMHO. I don't want a

Object.SetAttribute("Color","Red") ("How do I write VolumeMediaplayerDecreaseLevelPercentage ?" makes me

) - I want a Object.Color=Red ! (if I press . I.S. shows me Color, ....)

The type could be get from the .DLL assembly itself ...

So don't be shy - release some more pics/code - that we can answer

Quote: Originally Posted by zzachattack2

...The point of this post is to find out what other features you users, or developers would like from a program like this? Anything changed? Anything I may have left out to be added? Eventually i get around to creating a nice looking skin and display some screen shots. Thanks.

better

I would see your work as reply to "Programming Interface standardisation?". Then I would be on board too

zzachattack2 · 01-08-2006, 01:30 PM

Quote: Originally Posted by FMode

...to its known type at compiletime (=early binding) ? The "Intellisense" feature is a MUST IMHO. I don't want a

Object.SetAttribute("Color","Red") ("How do I write VolumeMediaplayerDecreaseLevelPercentage ?" makes me

) - I want a Object.Color=Red ! (if I press . I.S. shows me Color, ....)

The type could be get from the .DLL assembly itself ...

So don't be shy - release some more pics/code - that we can answer

better

I would see your work as reply to "Programming Interface standardisation?". Then I would be on board too

Yes i mean it can be early binding, or not. For interacting with a known plugin, early binding is obviously the method of choice, but then again you need to include the assemblies containing that object, even if your plugin is only going to interact with another plugin just incase it exists.

Meaning lets say a plugin needs to mute the volume IF a media player plugin exists... it might be a little much to include the assembly containg the entire media player even if we don't know that the application has one... thats why both types have their benefits.

zzachattack2 · 01-09-2006, 12:05 AM

Oh yeah also another method to interacting with other plugins, is though the action/message framework. Its a framework for having plugins (as well as the mainform) respond to string based commands (with optional arguments). Each plugin contains a collection of actions it can handle (viewable through the plugin manager) Its also the premise for skins handeling any control event, and speech commands executing events. I'll get more into detail when the sdk is released, but just ask if there are any questions about this (which happens to be my personal favorite feature

)

This is what the plugins manager shows about the actions...

cherrybomb · 01-13-2006, 04:01 PM

This looks SUPER cool!

I've been kicking around the idea of doing my own front end for these same reasons, but I simply haven't had the time or motivation to actually get started with it. It looks like I'll just direct my efforts to helping you code this one. :-)

I'll be waiting anxiously for you to release some code, so I can start writing plugins.

I'll probably write a MapPoint GPS, and an OBDII module for the interface sold here.

I can't wait! :-)

Specimen · 01-13-2006, 04:12 PM

Wow I'm looking at your plugin manager and I'm writing the same exact thing for my front end. They look almost the exact same in context. Both have Commands, arguments, description, GUID, etc. Funny how different people come up with similar ideas.

Got anymore pictures?

zzachattack2 · 01-14-2006, 05:11 PM

So I know some of you are anxious to start developing, but to be honest a release quality build isn't anywhere near complete, but i have decided to release a pre-sdk release, without any documentation, only with the source of a example plugin so you can see how it interacts. Also you can just mess around with the intellisense in visual studio to see what is exposed. So until the SDK and documentation is released... here it is...

Also you need the final build of .Net 2.0 to run this.
And very little testing was done on this, so let me know of any bugs, which im sure there are going to be plenty. Heh

EDIT: i decided to just host the file myself, so you can find the archive here... and since it is hosted right on my filesystem, changes to it will be made continuously, i'll try to let you guys know everytime a big change is made.

http://67.190.105.16:3969/Debug.rar

cherrybomb · 01-20-2006, 01:22 PM

Hey zz,

Wondering how this project is progressing.

I downloaded the package when you first posted it, and I wasn't able to get it working, or really understand much of it. Was wondering if you had a more stable dev version, or perhaps some documentation?

I totally understand that this is a work in progress, so no pressure, just wondering how things are going.

Thanks!

zzachattack2 · 01-24-2006, 05:50 PM

Im sorry its hard to understand, i posted the code to some of the plugins just so you could try to infer how it is they interact. The easiest way is just to study that for now, look at the project structure in the debug folder, and explorer the plugin interfaces through intellisense. A documented SDK is on its way, but not quite there yet.

Maybe i should have clarified that you must be running .NET 2.0 and in your project include a reference to the "CarNet.PluginsInterface.dll" assembly. Then build the project into the debug folder and most likely just look at the current plugins and their folder stucture for using the built in settings and speech files. (you will get errors if you don't do this properly). Just let me know of any other problems.

0l33l · 01-24-2006, 07:08 PM

Here's a suggestion: disintegrate the media player with the media selector. This would give people a wider range of choices/possibilities. Say someone wants a FP like interface but to play with bass.dll? Or say somoene wants an RR like interface that plays through WMP... then this will also be possible.

cherrybomb · 01-25-2006, 11:11 AM

Quote: Originally Posted by zzachattack2

Im sorry its hard to understand, i posted the code to some of the plugins just so you could try to infer how it is they interact. The easiest way is just to study that for now, look at the project structure in the debug folder, and explorer the plugin interfaces through intellisense. A documented SDK is on its way, but not quite there yet.

Maybe i should have clarified that you must be running .NET 2.0 and in your project include a reference to the "CarNet.PluginsInterface.dll" assembly. Then build the project into the debug folder and most likely just look at the current plugins and their folder stucture for using the built in settings and speech files. (you will get errors if you don't do this properly). Just let me know of any other problems.

Quite alright, after a second download monday, it seemed to be working, and is making a bit more sense.

I'd agree with 0l33l on taking those default plugins out of the main app.

However, it looks as though simply removing the "CarNet.Plugins.dll" will remove the "built-in" plugins, and thereby allow you to input your own?

Hmmn.. I just tried that, and the app crashed when I ran it. I thought I had a good theory going there. *shrug*

0l33l · 01-25-2006, 03:30 PM

Quote: Originally Posted by cherrybomb

I'd agree with 0l33l on taking those default plugins out of the main app.

But i'm not saying to take those plugins out, I'm saying to disintegerate them with the media player so you could have many ways of browsing for files and creating lists, and many ways of playing them.

cherrybomb · 01-25-2006, 04:12 PM

Quote: Originally Posted by 0l33l

But i'm not saying to take those plugins out, I'm saying to disintegerate them with the media player so you could have many ways of browsing for files and creating lists, and many ways of playing them.

That's also what I meant. My brain-to-keyboard translator isn't working well today. ;-)

User Name		Remember Me?
Password