Separed at birth
Here are two screenshots of Microblog plasmoids. There are two nice novelties that can be noted here (due respectively to KDE Plasma Workpace 4.6 and 4.7) are the support of "reply to message id" in the twitter API, so in Identica conversations will appear correctly threaded (sadly there is still no way to retrieve that threading information from the API) and the support for marking messages as favorites, that will appear in 4.7
What's nice is that in two days of development that plasmoid reached about 90% of the features the C++ counterpart gained in well, ages ;) so I'm quite confident the development speed in Plasma will get a dramatic boost.
All of that code in in KDE svn playground repository, I will give more info when all will move to git together with the rest of KDE software.
well,good for me .sito Hogan http://www.scarpahogan.com/
I want to buy a computer but I have no idea which brand to choose. sito hogan http://www.scarpahogan.com
air max on sale
RE: no configuration
@Jonathan Riddell: yes, it's a good feature indeed, i will include it in the QML version.
but please, for the patch you have now, do a reviewboard request ;)
Working without Configuration
We have a patch in Kubuntu kubuntu_02_microblog_default_configuration.diff which makes it work without configuration (reads a default feed, in our case kubuntu) on the principle that it's much better to do something useful without configuration where possible. If you're rewriting it in Qt Quick please include such a feature.
you are ogro
I will port Plasma to C#/GTK#
I'm using this beautiful new version with Twitter
It's smooth, stays updated, and allows for @theirnamehere
and full re-tweets.
Thanks for the great work!
virtually all of the code actually running in that plasmoid is C++: the widgets, the SVG painting, the DataEngine, the network access, all that stuff.
moreover, if we move everything to QML (probably a 2 year project) then we can then move to the fully OpenGL accelerated Qt scene graph written for QML. the performance difference is absolutely _staggering_. to do such a thing, it requires a declarative rather than an imperative approach to painting, so a tool like QML becomes necessary. and since the tool already exists (QML + the scene graph), it is where we are heading.
add in the new abilities like being able to switch UI at runtime depending on the device it is on, and having an as-good-or-better UI experience now is already worth it. being able to use the accelerated scene graph in the future, which depends on this QML work, will make it a no brainer.
Juan Antonio has a point...
"I'm quite confident the development speed in Plasma will get a dramatic boost"
What about Plasma performance? We all know that it was somewhat bad with C++ (not language's fault), so, in JS it will be even worse!