[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-panel-devel
Subject:    Re: Question about C++ vs. Python/Ruby/JS plasmoids
From:       Arne Babenhauserheide <arne_bab () web ! de>
Date:       2008-09-01 6:37:02
Message-ID: 200809010837.07848.arne_bab () web ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Am Mittwoch 27 August 2008 18:38:05 schrieb Aaron J. Seigo:
> this is a feature also provided by ECMA Script. the question is "why $LANG"
> instead of just stickign to ECMA Script.
>
> the reasons i see are:
>
> * you know $LANG, or the project your are integrating with is written in
> $LANG
>
> * in the cases you need access to more system libraries, but don't want to
> write in C++ (Ruby/Python have bindings for pretty much everything)

* in the cases where the languages are just better suited to the task. For 
example String operations, using anything from the standard library (if "it 
does the task for you" counts as being better suited :) ) or glueing things 
together in Python. 


How about using Kross to enable Plasmoids scripted in any language? 
- http://kross.dipe.org/
- http://techbase.kde.org/Development/Tutorials/Kross/Introduction

A possible first step could be a Plasmoid which takes its data from a Kross 
script. 

Best wishes, 
Arne
-- 
-- My stuff: http://draketo.de - stories, songs, poems, programs and stuff :)
-- Infinite Hands: http://infinite-hands.draketo.de - singing a part of the 
history of free software.
-- Ein Würfel System: http://1w6.org - einfach saubere (Rollenspiel-) Regeln.

-- PGP/GnuPG: http://draketo.de/inhalt/ich/pubkey.txt

["signature.asc" (application/pgp-signature)]

_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


[prev in list] [next in list] [prev in thread] [next in thread]