Thread: An Open Source, Fast and Modular, C# Front End

Wow! I'm really looking forward to seeing this form!
Just a request, if you are making it fully open (ie code and everything) could you please make sure you comment well, I briefly touched C# last year and would like to get back into it, and this sounds like the most interesting way of doing it.

Good luck with the development, I have been looking for an all in one package for a while now!

Regards

Well its going to take awhile before I have something to test....and I certainly can't do this project on my own. But now that I know I need to re-write the engine to use something like slimDX i at least have a place to start - and hopefully will find some other users with directx coding experience that can help out.

If I have a few more volunteers i'm going to put together a sourceforge project and get subversion and a wiki up and running.

joey7415963: Yea commenting shouldn't be a problem....usually i remember to do it whenever i do a svn commit. Not sure how much help were going to have but ive done some other large scale projects and we had 1-2 users just in charge of commenting and documentation.

have you tried XNA?

Originally Posted by 2k1Toaster

XNA is way too bloated for anything but gaming.

Exactly my thoughts....

Not to mention slimdx should really cut down on the loading and execution times - and give a smaller memory footprint since we don't have to deal with loading that entire part of the framework.

I also plan on using some pretty cool optimization code to ngen the entire assembly when installed or updated, and same for plugins.

I want to get a forum on here just for this so that we don't have to discuss everything in one thread. One small problem - it needs a name. I wanted something that didn't limit it to just being for car use (i've seen carputers on everything from motorcycles to segways). Best I could come up with in 5 seconds is SharpMobile - anyone have anything better?

Originally Posted by 2k1Toaster

I thought the files had to already have been ngen-ed pre-run. So if your app is skinnable, that wouldnt do any good unless everyone knows how to do it. Maybe they changed that?

Thats correct but the installation or the update program can re-run ngen. The app itself can also detect an outdated plugin and run ngen on it before its loaded. Skinning doesn't really change that - as long as the code itself doesn't change you can change the skin files as much as you want.

I'm working on the assumption that people won't mind if updates take a good minute..and installing plugins takes 20-30 seconds instead of 5-10 as long as everything loads really fast when you go to use it.