Re: JAVA Fork to C#?
by Arne Vajhøj on 10/31/2007 6:17:00 PM
E2CMonkeyBoy@gmail.com wrote:
> Quick Intro: was thumbing through a book on Programming Windows in C#
> and was wondering if I shouldnt fork my developement: I've written a
> program in windows script, and now a more robust version in Java
> (using eclipse). I've hit the wall - in that the UI portions of
> eclipse are still manual - as VE (visual editor) is now 2 versions out
> of date (and I subsequently can't get it to work - where it used to on
> my code).
I think it is only 1 version behind.
And the following unofficial port is said to work:
http://www.ehecht.com/eclipse_ve/ve.html
> So I picked up a C# book and downloaded the MS Express C# and was
> smitten by the ease of which I was able to implement some of the
> functionality. I used to do MS Studio 6.0 and MFC but I can not for
> the life of me see any reference to it (MFC) on the MS website - I
> don't know what the official UI "foundation classes" are - there are
> so many - is it Windows Forms? Or .Net or - anyhow - the meat of the
> matter is:
Windows Forms or WPF.
> Do you recommend C# for development (specifically for the windows
> platform) or is good ol' C++ and "X" (X was MFC now its? - what does
> the Word 2007 UI use?) I was relying heavily on Java to do heavy
> lifting in data base areas, Regular expressions and the like. I was
> smitten with Java+SWT but find Eclipse/SWT is developing at a snails
> pace. I read the intro to a "Charles Petzold Programming Windows C#"
> book at the book store and C# seems like a "better" java and "easier" C
> ++. I'd rather "fork" my project now that wait till I sit back and
> admire a complete project and find that C# might have been the better
> answer.
Almost anything is better than traditional X or Win32 GUI programming.
> Wish list: A level of abstraction like Java (C#?), with the power to
> create a snazzy program with MS Office 2007 UI elements. I'm willing
> to brush up on C++ do do the work if need be - I'm just so confused
> with what "windows" is programmed in these days. MFC was so hard at
> first but powerful. I've seen windows forms, windows PFC, wxWidnows
> and a myriad of other things referenced on the net. My audience
> (should I get the gumption to release the program) will be mainly
> windows. I don't plan on porting it to anything.
You can stick with Java or you can go for C# and .NET.
Depends on what you prefer (and to some extent how far you are
with the project).
Arne
Re: JAVA Fork to C#?
by Arne Vajhøj on 10/31/2007 6:19:00 PM
Chris Shepherd wrote:
> I'm all for switching to C# when it makes sense, but taking an existing
> application and porting it to a new language generally involves
> rewriting all of it.
It is often very easy to port Java to C#.
But SWT to Win Forms or WPF will be a rewrite from scratch.
Arne
Re: JAVA Fork to C#?
by Samuel R. Neff on 11/1/2007 12:48:00 PM
If converting the whole project is not an option, then you can use
IKVM to convert the java bytecode for the business logic / data stuff
to .NET and then only rewrite the UI stuff.
Then you can gradually move the rest over to .NET as time allows.
http://www.ikvm.net/
IKVM is very impressive and works great for middleware/backend stuff
(not designed for UI).
HTH,
Sam
------------------------------------------------------------
We're hiring! B-Line Medical is seeking .NET
Developers for exciting positions in medical product
development in MD/DC. Work with a variety of technologies
in a relaxed team environment. See ads on Dice.com.
>E2CMonkeyBoy@gmail.com wrote:
>> Quick Intro: was thumbing through a book on Programming Windows in C#
>> and was wondering if I shouldnt fork my developement: I've written a
>> program in windows script, and now a more robust version in Java
>> (using eclipse). I've hit the wall - in that the UI portions of
>> eclipse are still manual - as VE (visual editor) is now 2 versions out
>> of date (and I subsequently can't get it to work - where it used to on
>> my code).
>
Re: JAVA Fork to C#?
by E2CMonkeyBoy@gmail.com on 11/1/2007 4:54:00 PM
Thanks you all for your comments.
1. The "level of abstraction" was to indicate that it feels nice to
say "JPanel().add(new Button("Press ME"))" than say - the 20 or so
lines of MFC code...
or any number of other Object manipulations inside Java I use (which
I'm sure exists in C#)
2. No flame war - please - I used to like Assembly Language (when I
programmed MFC code) so - don't go there!
3. Lastly the project I have is nowhere near complete. I must confess
that it is usable and saves me HOURS and HOURS of time but I do want
to press forward and C# seems to be the answer - I suppose I'm just so
OUT OF THE LOOP on all this stuff that I want a warm a fuzzy that C#
will do all that I want before "wasting" my time and realizing that VC+
+ might have been the better choice (and hunker down and learn to do
things....manually again). Again "manually" as in malloc(ing) and
newing and deleting and - Message mapping and - you get the idea?
4. The one thing I did use to like about MFC and VC++ was that it
produced AN executable that almost all windows could run - but alas -
even my old MFC program wouldn't run recently (after dusting off the
cobwebs on it) and had to download some old MFC DLL's off the net to
get it to turn over the engine again..(on XP). it was the 4.2 verisons
and I see MFC 8.0's running around. I just don't see that many folks
talking about it anymore... mostly folks talk about WPF and Forms....
5. Thanks for your pointers - as right now - I'm rudderless and
staring at all of this with "deer in the headlights."
-Dave