Re: Why GUI perl programs on Windows?

Personally, I think it depends on who is going to use the program in the end. If you are going to sell it as a commercial product, then Visual C++, Visual C# Visual Basic, etc, would be a better choise (believe it or not, Visual C++ generates the fastest executable out of all the compilers for Windows). If you are writing a quicky for yourself or a small number of users, then you could use the wxWidget package. I used it a while back, but gave up because of bugs in the package. I ended up writing GUI applications for Windows only in Visual Basic and Visual Basic .NET. :-)

I know that activestate also has Visual Perl .NET, but I haven't used it. You could take a look at that option, of course.

Comment on Re: Why GUI perl programs on Windows?

Replies are listed 'Best First'.
Re^2: Why GUI perl programs on Windows? by holli (Abbot) on Sep 03, 2005 at 17:28 UTC
Writing a GUI without a designer is a PITA. So I elaborate a bit on the Visual Perl .NET part. I have successfully created two projects that use this product. It's quit nice. You can use the whole .NET class library from "perl scripts" (.NET exe binarys), but the syntax does not look very perlish. And you can write .NET components that can be used from other .NET languages. That makes using GUI and Perla piece of cake. You click your GUI together and put the logic in the Perl .dll's. The power of the .NET library and CPAN in one program. holli, /regexed monk/	[reply] [d/l]
Re^3: Why GUI perl programs on Windows? by Anonymous Monk on Sep 03, 2005 at 18:27 UTC
"What you can do" does not equal to "what you should do". The most natural way of using .NET library is not through Perl. And if you choose to do so, you have chosen to follow not to lead. Things will always first be available through C# and polished, then Perl .NET started to take time and catch up.	[reply]


Just another Perl shrine
	PerlMonks