local dataengines and browser

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent

local dataengines and browser
by nice on Monday 21/Apr/2008, @11:08

resolution independance and OS / Browser independance , WOW

but how does a plasma applet in a browser connects to local data engines ?

Related Links

·   Articles on Developer
·   Also by nice
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: local dataengines and browser
by Aaron Seigo on Monday 21/Apr/2008, @11:19

for dataengine using plasmoids, that will require access to the scripting API. these will therefore rely on support in the web rendering kit used (khtml, webkit, gecko, ie, opera, etc), probably via a plugin not unlike, say, flash. (except open .. )

but for simpler widgets that don't use data engines, we can replicate the widgetry in plain embedded javascript.

[ Reply To This | View ]

Re: local dataengines and browser
by nice on Monday 21/Apr/2008, @11:34

are there dataengine exposed via webservice ?

with a wsdl description ? that would be great, so javascript could query via xmlHTTPrequest...

perhaps add a interface for that to plasma ?

[ Reply To This | View ]

Re: local dataengines and browser
by Aaron Seigo on Monday 21/Apr/2008, @12:46

first off, this has huge security implications. the security infrastructure for non-trusted/trustable widgets is fledgling right now (though design has been discussed) ...

with that proviso, assuming the JOLIE integration works out, that would be the most likely route for us to go.

[ Reply To This | View ]

Re: local dataengines and browser
by Riddle on Tuesday 22/Apr/2008, @08:07

That depends on whether you really want the engines to reside on the client. If not, then one could make a pure JS implementation of the API based on AJAX to get the data from the server.

[ Reply To This | View ]

Re: local dataengines and browser
by asdf on Tuesday 22/Apr/2008, @14:15

if the data to display *comes* from the client, it should reside @ the client

if the data can be produced somehow in the browser ? then it would make sense to put the dataengine in the browser too.

but i think about 99% percent of useful data comes from different clients, not outside a browser

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"The trolls are only human and make mistakes too." -- Charles Samuels
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.