Plugins

[msm]

Don't quote me on this (ok do if you want but i will deny everything and edit this post to make you look wrong) but any language that supports .net managed code should work. This is, currently, C#, vb.net and managed c++.net. The latter is truely horrible, IMO, 'cos nothing is really out there to help. Of the three, c# is the most featured, although there is probably a strong argument for VB, but i've never used it so i wont bother.

Matt

[CodeMonkey]

Actually the managed extentions for C++ really aren't that bad.  They take getting used to, but aren't any worse than learning the .NET framework in any of the other supported languages.

I also believe you can use any language that supports the .NET managed code stuff.  If there are any languages outside of the three Visual Studio .NET supports (C#, C++, VB) I am unaware of them.

Though I did hear a rumor that somebody is going to get the visual cobol stuff working with .NET

[sub]

Yes, msm's right. You need to write any plugins as a .net .DLL, so you are current limited to C#, VB.NET, managed C++ and J++ languages. I think there is also .net cobol compiler (really)

[CodeMonkey]

Here you go

I double dog dare someone to write a gbpvr plugin in visual cobol .NET

[gplasky]

One other thing we need to think about is the Main Screen. As more and more plugins are developed (I like the email reader plugin idea) we are going to run out of button room. We need to look at: do we do multi-column button. (That will mess up the icons showing on the right side) Or do we have a special button which is actually a group that will take it to another screen/page. Food for thought.

Gerry

[paulrking]

What about a menu of plugins - maybe a tree view type arrangement

PK

[AndyCherry]

Quote[/b] (paulrking @ April 21 2004,20:30)]What about a menu of plugins - maybe a tree view type arrangement

PK

Need to think about how you'd navigate whatever is put in place with only a remote control, and also how it would look on the "10 foot" interface....

Cheers,
Andy

[MC001]

####, I wish we'd moved from VB6 to .Net at work... I feel like I'm in the stone age here.

[paulrking]

Go for it the jump from VB to VB.Net or even C# isn't that IMHO

PK

[AndyCherry]

I was a VB5 person myself - I bought the cheapo version of C# and learnt from scratch (string handling is the bit I really struggle with) - it's fairly easy to do... the biggest issue is getting into the object oriented mindset instead of the psuedo object-based procedural approach of VB5.

The .NET framework is very cool - it makes things very easy to do (processes, threads, http, etc.).

Cheers,
Andy