Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
KDE GUI

Qt Script For Applications 1.0 Released Today 33

hpj writes "Trolltech today released QSA. An ECMA based scripting extension to Qt (On which KDE is based) which allows easily adding scripting support to Qt (And in extension KDE applications). It is licensed like Qt under GPL as well as commercial licenses for Windows, Mac and X11 for those GPL is not suitable."
This discussion has been archived. No new comments can be posted.

Qt Script For Applications 1.0 Released Today

Comments Filter:
  • by Andy_R ( 114137 ) on Wednesday July 02, 2003 @09:40AM (#6349448) Homepage Journal
    I can't seem to find the 'stop showing me every damn press release that trolltech makes' button in my preferences.
  • Redundant (Score:2, Informative)

    by Anonymous Coward
    KJS (KDE JavaScript) already provides full ecma script for any applications that choose to make themselves scriptable. The KDE controls all have basic scriptability provided, so this is redundant for KDE.


    Looks like TrollTech is once again stealing KDE's ideas.

    • Re:Redundant (Score:5, Informative)

      by Anonymous Coward on Wednesday July 02, 2003 @12:07PM (#6351013)
      Looks like TrollTech is once again stealing KDE's ideas.

      I guess by "stealing" you are referring to the
      fact that trolltech hired the KDE
      developer who wrote KJS and paid him to improve
      the library, then released it as open source?
      • Re:Redundant (Score:1, Interesting)

        by Anonymous Coward
        Nice try, troll. Apple has been using KJS as part of their JavaScriptCore framework for over a year now, and have been silently adding changes back without fanfare or press releases. Next thing you know, TrollTech will have hired the KHTML programmers and put it under a free license too.


        It's reasons like this that I prefer BSD licenses.

    • Looks like TrollTech is once again stealing KDE's ideas.

      What - you mean, they're implementing a publicly available standard again?

      How dare they do something that... that... that immoral!

      Why, next thing you know, they'll be claiming they did it to provide an implementation of a uniform cross-platform scripting environment for Qt users. As if we're foolish enough to believe that!

      Well, too bad, Trollies - thank's to good ol' Anonymous Coward, we're on to you now!!

    • Re:Redundant (Score:3, Insightful)

      by valkadesh ( 450943 )
      AFAIK, KJS is based on ECMAScript Edition 3 (implemented in JavaScript 1.5 and JScript 5.5). QSA is based on the forthcoming Edition 4, which is way different from the previous version. (Edition 4 is implemented in JScript.NET and the yet-to-be-released JavaScript 2.0).
      To learn more on ECMAScript v. 4, see here [mozilla.org].
  • GPL (Score:1, Funny)

    by P145M4 ( 454133 )
    [...]Windows, Mac and X11 for those GPL is not suitable[...]

    bullshit
    Why should the GPL not be suitable for Windows ?

    I'll stick to GTK+/Gnome
    • Re:GPL (Score:2, Informative)

      by rmull ( 26174 )
      It should probably read "for those for whom the GPL is not suitable."
    • Re:GPL (Score:3, Informative)

      by PhilHibbs ( 4537 )
      They have released the full source to Qt on Linux under the GPL.

      They have implemented a Windows graphics layer that allows Qt applications to run on Windows. They have not released this under the GPL, which is their right.

      I wonder how much work would be involved in implementing a Windows graphics layer for Qt.
      • They have implemented a Windows graphics layer

        Actually, they implemented all of Qt for windows, and mac, and linux. Not just the graphics parts. The whole point of Qt is cross platform developement, not linux development. As for implementing Qt in windows, it makes sense that you could take the GPL'd unix version, and port it to windows. That port would also be under the GPL... and thus windows users would have a Qt without having to pay so much for the devel license. As for how much work, the code

        • Actually, they implemented all of Qt for windows, and mac, and linux. Not just the graphics parts.
          Sure, I meant that the Windows graphics layer was not GPL'd.
          • Sure, I meant that the Windows graphics layer was not GPL'd.

            And I meant that none of Qt for windows, including the threading, the networking, the database, etc is GPL'd. My point is that you'd need to do more than port the graphics components over :-)

  • MacOSX Compile (Score:4, Informative)

    by Dave9876 ( 591025 ) on Wednesday July 02, 2003 @11:25AM (#6350611)
    I'm not too sure if it's going to happen to anyone else or it was just my bad luck. But if if bitches about not having a license when trying to compile it under OSX, try "touch LICENSE.GPL" before running "./configure".
  • scripting framework (Score:4, Informative)

    by vinsci ( 537958 ) on Wednesday July 02, 2003 @11:36AM (#6350714) Journal
    Why add just one scripting language, when you can get them all? If you're lucky enough ;-) to develop in Java, you'll be interested in the open source Bean Scripting Framework [ibm.com] from IBM.
    The Bean Scripting Framework (BSF) is an architecture for incorporating scripting into Java applications and applets. Scripting languages such as Netscape Rhino (Javascript), VBScript, Perl, Tcl, Python, NetRexx and Rexx are commonly used to augment an application's function or to script together a set of application components to form an application.

    There are many scripting languages implemented in Java, including Netscape's Rhino implementation of ECMAScript, Jacl and JPython. While each of these is embeddable in Java and provides the ability to interact with Java from the language, using a specific scripting language binds an application to that single language.

    The Java world currently does not have a well-defined scripting architecture that allows Java applications to incorporate scripting easily - BSF is such an architecture. The BSF architecture allows an application to be scripted from any BSF supported language, without any scripting language dependencies.

    BSF supports both directions of scripting: in one case where the Java-side is in charge and runs/evaluates scripts at will, and in the other case the script runs and controls Java beans. Notice that while we use the word "bean", it is used loosely - BSF works with any Java object and not just a true bean.

    • Most environment have one, if not several, options for adding "scripting hooks" to an application -- Apple's AEOSA/AppleScript, Microsoft's Windows Scripting Host, the GIMP's PDB, etc. That one should exist for Java is not really a surprise.

      However, it would be nice to see someone develop a portable system of this sort, which could just be used as a common bit of infrastructure on any platform. PDB (procedural database), as used in the GIMP, probably has a good chance of being the most portable, as I think
      • Which runs on Linux, Mac OS X and MS-Windows (CygWin). And because it's such a sloppy language, it's eminently suited to MS-Windows.

        My real favourite all-weather candidate is Ruby.

  • Dependant on Qt? (Score:2, Interesting)

    I would assume this is dependant on Qt, but I'm curious to what extent... right now I'm working on a system in which I use SWIG to bind python to c++ (and visa vera) on Mac OSX -- there's nothing wrong with the current system, but I'm eager to explore alternative mechanisms, for ... you know... time wasting and just-in-case paranoia.

    If Qt Script can be made to be freestanding language binding system and interpreter, but with no GUI I'd be happy as a clam.

    But, the info on the trolltech page was inadequate.

"The following is not for the weak of heart or Fundamentalists." -- Dave Barry

Working...