Slashdot Mirror
Developing Applications with KJSEmbed
Rich writes "Ian Geiser of SourceXtreme has released an interesting HOWTO showing how you can use KDE's embedded JavaScript tool to write quick-and-dirty apps. The apps can use the features of Qt and KDE to pack a lot of punch for a small amount of code. You can find it on his website."
The current problems with using DCOP right now for scripting and macros type stuff are:
* There is very little documentation about what DCOP interfaces programs like Kate have, and how they can be used for writing small scripts and macros.
* The existing DCOP interfaces are not designed for the ease of use by scripters/powerusers. They are built directly on top of the C++ implementation.
* The DCOP interfaces are often not complete enough to make it possible to script everything that can be done via the GUI.
--
Simon
Most unix apps arn't event driven (or even GUI) so an event driven language like VB (ok i know it can be non event driven but thats not its raison
d'etre) is not much use as an all purpose solution. Tcl/Tk was good at this sort of thing but it seems to have gone below the radar in the last 5 years or so.
If you hate it so much, then don't use it.
I can't stand it when people bitch and moan about a some technology being too <negative_adjective> when it comes to open source. (Especially when people like you make complaints and don't even bother to substantiate them in any way. What you offer is purely opinion.) If you're in a position to use KDE, then you are not using Windows. If you are not using Windows, then you are in a position of choice.
And that's really the whole point, isn't it?
KDE is a desktop environment, not a window manager like you are asking for. In this case, KDE is trying to provide a platform that is both easy to use and serves the needs of rapid application development. These are things that will help make it a more viable alternative to Windows and tools like VisualBASIC which can be great for quick prototyping. Of course, I don't know what the point is of defending it on these grounds. It's a tool, one of many, well suited to certain tasks and perhaps not so well suited to others.
Join Tor today!
Well if it weren't for the requirement "can take VB and convert", you would have a lot of options. VB needs to go away. People didn't use VB because of the language, they used it because you could write crappy throwaway programs and prototypes quickly. Using Python, Perl, Ruby, Delphi, Java and or even C++ underneath makes no difference, because 99% of the time the RAD developer isn't touching any code.
.NET. Without arguing one way or the other on the merits of .NET, one of the rationales for the decision was so that it would be easier to use Visual Basic. Huh?
Frankly, the whole "programming for non-programmers" approach needs to be seriously rethought. It's good that marketing types can quickly make a mockup of an app, but they should never be led to believe that they can do the work of developers. One quarter million dollar realtime embedded product I work on was spec'd by marketing to use
Don't blame me, I didn't vote for either of them!