Slashdot Mirror

← Back to Stories (view on slashdot.org)

Coding with KParts

Posted by Hemos on from the how-to-make-better-programs dept.

wrinkledshirt writes "IBM DeveloperWorks has an article here about coding with KParts, KDE's component architecture. It's a little thin, but given that no single component technology has claimed victory yet for Linux, just thought this might be an interesting read for some. It also might lead to some good discussion comparing people's experiences with KParts, ORBit ? , Bonobo ? , or Kylix ? 's CLX..."

2 of 119 comments (clear)

  1. Refreshing Attitude by Karma+Sucks · · Score: 5, Insightful

    After all the hype and noise about .NET, tomorrow's technology tomorrow, I'm glad there is now a little focus on some of the great technologies we have *today*.

    KParts is modest. It doesn't not try to solve all the problems of the programming community. But it's *damn* good at what it's good at.

    Like they say, the right tool for the right job. Only rarely will you find a one-size-fits-all solution.

    --
    (Please browse at -1 to read this comment.)
  2. KParts won't dominate by markj02 · · Score: 3, Insightful
    no single component technology has claimed victory yet for Linux, just thought this might be an interesting read for some

    And no single component technology will "claim victory". Different applications have different needs. For some applications, CORBA interoperability is absolute essential.

    KParts in particular is further held back by the fact that it is covered by the GPL: commecial developers do not like being nickled-and-dimed just to put their software on Linux, in particular since the industry standard is free. And KParts is (at least perceived to be) biased towards C++.

    It's nice what the people over at KDE are doing. But don't expect world domination.

    All these "component architectures" are really mostly driven by limitations of C and C++ anyway. In the long run, the issue of component architectures will largely go away, as desktop software development shifts to Java and C#. Yes, Java and C# still require some conventions for components, but they already have most of the hard parts implemented as part of the language.