Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Vanilla and Strawberry (and Chocolate) Perl 2008 Plans 8 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • But they will be based on WxWindows, and will most likely include things like a POD Viewer, a GUI CPAN Client, and potentially an editor such as Kephra, as well as other tools as needed or available.

    Um...why ? or rather, why not the GUI toolkit that is/has supplanted all others, namely, the web browser ? Its 2008. As of about mid-2006, its become increasingly clear that, "if it doesn't run in a browser, it don't mean sh*t."

    At the risk of sounding like a buzzword bingo caller, it would be a shame to

    • The big win for browsers has always been automated deployment.

      If you want to run everything locally, there's still advantages to doing things in a GUI. Introducing a client server model and the overheads of doing things in Javascript for a process that is inherently local has it's own downsides.

      That said, it may well be that some of the client side apps ARE done in HTML/Javascript.

      The POD viewer is one example of an application that would be ideal to do browser-based. It's document focus aligns well with the HTML view of the universal.

      Conversely I've used the RedHat Satellite "GUI" for module installation and it's just plain hideous.

      I also seriously doubt there's many people that are using Javascript/HTML as a programmer's editor, or for their music player, and so on.

      There's no "right" way to do it, I'm not saying "everything must be WxWindows Win32 GUI widgets".

      I'm just suggesting that since WxWindows is suitably cross-platform, and at least LOOKS like native Win32, that wherever we use a GUI toolkit, we should use that.

      You are quite welcome to implement a HTML/Javascript CPAN client or programmer's editor and prove me wrong.

      • I don't understand implementing a "programmer's editor". There are plenty of IDEs for Perl [perl.org] already, aren't there?

        It's a good idea to make things work better on Windows, though. Languages like Python or Ruby seem to have already dealt with this better than Perl has.

        But what kind of motivation would a Windows programmer have to use Chocolate Perl instead of, say, Visual Studio [microsoft.com]?

        • ActiveState cancelled the Visual Studio Perl version of Perl.
          • I guess this is what I mean. Why would people from the Windows world even want to use Perl, when they can use for example C# or VB? Or maybe you're not trying to win over those people.
            • The best example that I can think of is in teaching -- I met someone who was taking a Perl course, and they were using Mac's TextEdit as their editor. I tried convincing the student they'd be better off at the very least using something that did text coloring (I recommended TextWrangler, being that they were a Mac user), but they didn't make the switch.

              I'd assume that making it easier for a non-programmer to pick up and program in Perl is a good thing, especially if it results in schools being more willing
            • Why would anyone on 90% of the world's desktops want to use Perl?

              Because they are forced to use Windows by corporate policy.

              Because of the CPAN... because there's so much depth to the pre-written code out there, and assembling components in Perl is SO much easier compared to Windows languages once you need to do anything even remotely esoteric or interesting.

              Because Windows + Mac + Linux == cross-platform, which is a hugely desirable feature.

              Because developers can write GUI business tools on Linux (which th
        • I'll add one more point to your original question.

          > I don't understand implementing a "programmer's editor". There are plenty of IDEs for Perl already, aren't there?

          Yes, but they all suck.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.