Tag Archives: KDE

The Mobile Concept

Reading this post you were able to watch a video about Plasma Mobile (actually, Plasma on all kind of devices) and see some screenshots. But if you don’t know the ideas and concepts behind that, you are just going to bash it as it’s just the bootstrap of the project and a lot needs to be done.

And if for some reason you are wondering about the future of the netbook project, don’t worry πŸ™‚ Plasma Netbook and Plasma Mobile, besides being oriented for smaller form factors than a regular Desktop / Notebook, have different concepts as they’re serving for different purposes.Β  Marco (notmart) and all the Plasma team will still keep working on the netbook shell and if you read this post you can see the netbook shell running on Intel’s Jax10 devices. This was done toΒ  give us an idea about how the netbook interface would behave on touchscreen devices and helped Marco to do a lot of bug fixing and improvements.

Back to the mobile shell, this interface presented here was created for the same Jax10 device but the architecture was designed to support different “Views” (as in MVC) for even smaller devices (N900 anyone?) , while still sharing the same concepts though. Even if the interface was not designed for the N900 for example, we were able to run it with great performance and the usability was very good. What means that we’ll just need to slightly tweak the view to make it perfect for the N900. And all of this can be done by designers as the View is 100% done in QML πŸ™‚

So our first step was to brainstorm about launching menus (and how regular grid views seems to be so boring) and how different contexts affects the way you use your mobile. I mean, we are making desktops aware of contexts more and more and it’s silly to think that you don’t use this concept on your other devices.

We thought about having regular activities so the user would be able to have different set of plasmoids for each context that he’s working on. However it still needs to be very easy to do some stuff like:

  • Going to your dialer if it’s a phone;
  • Change between activities (later we can make the shell location aware so it’s possible to auto switch);
  • Launch applications easily and context aware (presenting the applications related to that context);

In order to achieve these goals we came with this idea: having a regular containment and a kind of panel that auto hides itself after some seconds. Important to say that right now this panel is 100% QML and is not like the desktop’s panel (that is a containment in another view). This makes the shell use less memory and be faster as it’s just playing with pixmaps in the end. After hiding, it shows a collapsed representation of the panel at the bottom that the user can either click on it or drag it up to show back the panel. This makes it really easy to change between one activity to another one while keeping the user interface clean enough so the user can play with his applets πŸ˜‰

First Mockup by Nuno

The panel while in it's collapsed mode

But then you ask me: “I want to launch applications ? How can I do that ?”. One solution is to add an application launcher as one of the main activities and the other one is to enable context aware application launchers. So, looking at the pictures above think that you are at the “Internet Activity” and you want to launch your applications. You can always launch the application related to one plasmoid from it so if you have an RSS Feed plasmoid you are able to launch your feeds reader using this plasmoid.Β  But if the applications doesn’t have a related applet, in our concept you can just flip horizontally the current activity and you’ll find on it’s backside a context aware launcher that have shortcut icons for your applications and it’s size is proportional to the times that you launched the application and how much related to that activity the application is. This way it’s easy to find the most important applications for that activity.

Activity flipping to show...

...the context aware application launcher that right now is just a gradient πŸ˜›

It’s not there right now but the idea is that at the top we will have this small bar (that will be a containment) to show the status related widgets like battery, signals strength and other stuff very plasma, like clocks! It’s not there yet, but it will be!

Regarding the transitions from one activity to another we thought about sliding the activities up and down so there is the idea that we are throwing the current activity somewhere else and bringing the new one.

Throwing away the current activity....

...bringing the new one and fading out the panel....

...and the switch is done!

\Basically this is the concept behind the Plasma Mobile shell and after this it was just a matter of thinking about nice animations that would make sense, tweaking it’s timers and polishing icons πŸ™‚ It’s clear to us that during the development we’ll find flaws in this ideas and we will need to fix them, as well as that the implementation right now is a little bit dirty due to time constraints (Tokamak doesn’t last forever unfortunately). Next steps ? Fix all the ugly code, finish implementing the launch menu, polishing and bug fixing…what means that we just bootstrapped!

Ah, if you are wondering: the Plasma Netbook project still keeps up to speed and is not sharing this backend (besides sharing a lot from libplasma). The deal is that the Netbook really needs it’s own concept and implementation while Plasma Mobile is really meant to be used on smaller devices than netbooks πŸ˜‰


Plasma Mobile before deploying


Plasma Mobile on Jax10

I would like to thanks all tokamakers for providing great ideas and also INdT’s designers that gave me great ideas along the last years that I could apply for this concept.

YATP: Yet Another Tokamak Post

So, I just prepared a nice post about the job we have been doing during Tokamak 4 and what happened this days but I really don’t want to spoil cool stuff before we can at least give you some screenshots and videos πŸ˜‰ Keep reading this blog as the next two posts will explain all of this and give some pretty and nice screenshots and videos!

First of all I would like to thank Will Stephenson, openSUSE and KDE e.V. (and of course everybody who supports the KDE e.V.) for hosting this developer sprint. It was awesome to put together people from three different teams that develop stuff that have a huge overlap area (Plasma + KWin + Oxygen). Really, thank you very much. I’m proud that you’re part of the KDE community!

Weather has been good (compared to Oslo and Finland where I was spending the last weeks) and the office is really good to work on. We have a lot of different devices to hack on (big computers with touchscreens, small devices from Intel and Nokia and the regular notebooks and netbooks) and we were able to expose a little bit more of our work to the local community (as well as see some old pictures of a sprint that happened at this same place in 2002).

From my side I was planning to bump the Pastebin applet with some new ideas and work on Plasmate and shell mobile but it seems that in the end I was able to just stick with one of these three targets. Anyway I hope that I can finish at least one more of then until the release of KDE SC 4.5.

Here is everybody that joined our developer sprint and keep watching this blog because tomorrow I’ll have some cool stuff to show everybody! Again: thanks to our hosts and to the Plasma, KWin and Oxygen teams for being so great!

The Desktop Konquering Germany

Tokamak Group Photo: Plasma, KWin and Oxygen teams

Google Chrome OS. Or, how to miss the shot.

Recently there was a lot of noise regarding the new coolest guy on the street: Google Chrome OS. I was traveling and just today I could read all my feeds, emails and put everything on the right place πŸ™‚

Some people talked about it but I usually don’t pay attention or even read some articles but unluckily I was doing some reviews of Palm Pre, the new Zune and other devices and it’s software and for some reason I landed in the article of Free Software Magazine regarding Google Chrome OS and how KDE and GNOME shot each other on the head. I really don’t pay attention to any flame wars or trolls and usually just ignore these topics as they don’t take us anywhere. But this one got my attention (unluckily, again).

I’m writing about it for a few reasons: first the (lack) of technical background present in the article (I really don’t know the author and I’m not judging his technical skills besides the ones shown in the article), second due the fact of being a “Free Software” magazine (as it points out in the domain name at least) and third due the fact that people just love hype :).

First Act

Let’s talk about technical facts. If I remember correctly the author says that Chrome OS will use a “GNU/Linux” kernel. There is no such thing. The kernel is Linux: period. If it will use a GNU/Linux system is another history. Then there is this talk about Pulseaudio and this is a “hot topic” in the Linux audio system world.

There are people who like it and (from what I hear everyday in mailing lists and IRC channels) more people who doesn’t like it. Personally I don’t use it as I don’t have the need and my distro (slackware) does not ship it by default. The excuse of the author for the fact that Chrome OS was not using GNOME/KDE and/or GNU Linux was that none of them provides what Google wants and because there were too many options and none of them was good enough. If none of them is good enough I’ll let for the reader to decide about it but that is not why Google didn’t use it.

First of all Chrome OS will have the help of Canonical to build it’s stuff so probably behind the Webkit stuff that the user will see as the “workspace” it will just be a regular Linux distribution (probably Ubuntu based) behind the scenes. In the end it is a GNU/Linux based system.

One could argue about Android not using a GNU/Linux based system and people often confuse Android with Chrome OS (even Google doesn’t have an answer for it yet and Googlers says that probably in the future they will converge to the same thing). Android not using GNU/Linux is true and they don’t even use some common systems like HAL to handle hardware making some (ugly?) hacks to do what HAL would solve out of the box for them. But I understand their side and probably they had reasons to do that (dead lines, licenses, etc…).

Well, I’ll not talk about Google’s work right now. They are doing their job in the sense that they are presenting the world a new way of looking at the desktop. But some arguments like: “there are too many ‘desktops’ libraries” and this is due the fact GNU/Linux has two different desktop environments are just…how can I say…ah! these are arguments that comes from people with no technical background. I don’t write about economic stuff, do you know why ? Because I surely have an opinion, but I don’t have the technical background to write about it and I’ll probably just create more noise and confuse people instead of helping them understand something.

I’ll not extend myself more on this section as it can get too long: but arguments saying that applications have dependencies of .so and this is harmful to the user and proposing solutions that are already out there in ANY Linux distribution (bundle of libraries are packages and it’s dependencies if anybody has questions regarding this), etc.. just make noise and have no technical background.

Sometimes journalists/bloggers are the ones that write about everything without knowing anything and this leads to at least confusion.

Second act

I’m not sure if everybody knows that but Google is just arriving at Free Software world (as much other companies, like Nokia for example). The first approach of Google was being open source friend but not free software. And there is a huge difference.

Thanks to many people Google is changing this and becoming closer and closer to free software with initiatives such as Google Summer of Code, when they fund students to work on free software projects and much other initiatives.

But the point is that a “Free Software” magazine has an article attacking the free software community (I say attacking because there is no constructive feedback or review inside an article without technical background). Ok, you may be thinking that I’m beating too much in the “technical background” key, but even from the user’s point of view there are almost no valid arguments there besides the fact that we need to improve sound on Linux (big news here ;)).

So, we have a free software magazine, pushing a non free software initiative and talking about non sense stuff. Google has a great product on it’s hands and no doubt about it. But come on: if you want to compare KDE, GNOME and Chrome Workspace do it the proper way.

Third Act

Hype. It’s all about hype. Google Wave was the brand new silver bullet in the world. Everybody that is not a fan boy and seriously tried to used it know what I’m talking about. But the hype was so big because it was a Google’s product (and usually Google has great products) that everybody started creating use cases, theories and etc.. just due to that. No real use case, no real innovation. Just hype.

Again, Google has great products: GMail, Google Docs, Google Analytics, Google AdSense/AdWords, etc… But sometimes people start talking and expecting things just because of the hype. Trolls and fan boys are species that walks together in the world.

The same is happening with Chrome OS here. It’s not ready yet but people are already saying that it will be the best thing ever. Or even that very solid COMMUNITIES and the software around them are dead just because in one year somebody will bring a new product.

Examples from the past ? ‘Virtual reality’ (being used on browsers with VRML and videogames with those horrible goggles), ‘Java Applets’ (who don’t remember it being the final solution for dynamic web pages ???) or even ‘Director’ who was the killer application for multimedia stuff and would kill Flash ?

Final Act: Summary

Let’s just calm down and learn with each other. Gnome and KDE learned a lot of things with each other and with it’s own communities, Linux and the GNU/Linux distributions too.

Google has great products and can really create expectations on it’s users. Google search, maps, Android…all great products but all of them (as any other software) have problems and bugs (anyone using GMail’s imap?).

So please, for the next ones writing about the brand new thing that will kill all the others out there, calm down, write your opinion but just don’t start saying that projects are going to die if you don’t have any clue about it and don’t start guessing stuff. Want to write a user review ? Write it as a user review and about what is bad (maybe what is good too). But writing guessing articles tending to be a user review but pretending to be a technical article is not good for anybody.

Avoid shooting yourself in the foot.

How is the weather in Qt 4.6 ?

Hmm…it looks sunny πŸ™‚ Take a look at this video. This is a demo we did using Qt 4.6 for S60 and the N900. You can find the source code in the same place where you can get Qt’s source code.

This is a “making of” video from the designers perspective, that shows from where they started and where they are right now in terms of design and of course, the implementation of the demo by the end of the video :). It also shows a little bit the work flow of INdT’s designers when designing new products.

Nice weather application. We didn’t have time to improve KDE’sΒ  one but for KDE 4.5 we’ll abuse so much of Qt 4.6! Performance improvements and features added. Who can imagine what’s coming in Qt 4.7 and 4.8 ???? (ok ok, maybe we know that and Thiago for sure knows that….but come on…you too can take a look at the repos and know what’s coming ;). Enjoy the video!

Changing the weather from Ian Moreira on Vimeo.

Post Latinoware Post :)

Latinoware was a nice conference held in the south of the country last week, from the 22nd to the 24th of October. It was a really nice conference and we had a lot of KDE exposure there as we had our logo on the main website of the conference, a booth and also a lot of talks KDE/Qt related.

It was really awesome that Ade and Annma could go there. It shows that Brazil and South America are not “3rd class citizens” in the community. A lot of people here in Brazil tend to think that we are not that special in the world besides our beaches and carnival. So, specially for students this is really important. Probably it’s also important for those that are at the beginning of their free software careers as they think ‘ow, a foreigner came here for KDE…this project must be important’. Ah, of course: it was also really a pleasure to have them here. Great great great people :).

Ade explaining what is KDE

Ade explaining what is KDE

During my talk we had some people really interested in netbook stuff and it was nice to give this presentation as I did a similar one during GCDS but the one during GCDS didn’t have too much demos as everything was at the first steps. Now, with Marco working full time on this and some others that will join the team, I had a LOT of cool stuff to show off, not just the ideas behind everything.

During GCDS I talked about the base ideas and research we did for Plasma Netbook. It was nice from a concepts point of view but I had no demos, just screenshots of pre-alpha versions and nothing fancy to show off. But this “pre-alpha” stage for the project was important so we could create a vision for the project and stick with it. Now, after some (few) months we have done a lot of things and the vision starts to show off.

Instead of going on through all the details I’ll just explain the final demo of my talk: I had a netbook (with Plasma Netbook of course), running Amarok and playing some Cold Play song (bonus points for Cold Play that released a 5 songs live album for free on their website – funny fact: the music playing was ‘Viva La Vida’ , life is really great in KDE world, isn’t it πŸ™‚ ? I had the now playing plasmoid on my Newspaper desktop and just shared it. TookΒ  an N900 from my pocket and showed how far KDE can go: using our technology I was able to ‘get’ the shared plasmoid, and remote control Amarok from my mobile phone (btw, thanks to Vudentz to let me use his N900 as I don’t have one yet).

As you may already have seen in other posts on Planet KDE there is already a KDE-Maemo effort going on and yes, we have the power an can go everywhere, just as Qt. And we will deliver a really rich user experience for our end users. More to come, keep following…. πŸ˜‰

The KDE Latinoware Booth

The KDE Latinoware Booth

PS: really awesome to meet the KDE-MG people during latinoware. Kudos to them and of course to Live Blue guys. You Rock! πŸ™‚

User Experience with Different Devices

It has been some time that I had some ideas regarding different devices. My first try was with the so famous “Mysterious Device” that we had during Tokamak 3 and later I played a little bit with my N85 and QtS60.

Qt Everywhere: yes, this means a lot of things. For Nokia it means that the same framework will be available for different platforms, for users that they will have more software being developed and for us, developers, that we can bring our software for all the devices that Qt is ported to.

Let’s also talk a little bit about platforms: Nokia has been playing with Maemo for some time now and the platform itself is pretty mature. Of course it will have problems but it’s pretty mature and compared to a lot of others out there it’s much better. But Maemo was “confined” to internet tablets…a device that was not good enough to be a netbook and not small enough to be a phone. It was “just” a pocket computer.

However the scenario changed and now we have a mobile phone running Maemo out there (N900) and Nokia learned the lesson about how to attract open source developers (just think that while Apple charge developers to get the full SDK and deploy their software, Nokia gives big discounts on new devices for developers).

I was pretty sad that I couldn’t go to Maemo Summit and show my ideas to everybody out there and it became worse when I saw that everybody there had their N900 and would be able to create awesome stuff for the device. This is one of the downsides of living in Brazil: it’s almost impossible to get/buy new hardwares without paying huge taxes and the developers program always helped on this matter. Too sad =/. BUT it seems that today was my lucky day! I (and some others) received a mail saying that we would receive a discount on an N900! Awesome! So now it will be possible to do all the stuff I was planning to do!

Plasma Netbook is one of my main objectives for the short/mid term (take a look here for the last news). It has a lot of potential and a lot of great ideas around it. We already received good reviews even in “less than alpha” state and we’re looking for companies that want to sell their stuff with something that will provide a unique user experience. If you are interested, contact us…we can explain our ideas and provide details about it. Also know we have Marco working full time on this, while I’m working full time on Qt and others are keeping plasma up to shape.

And probably you’re asking yourself why you should be interested in what I said above. The reason is just below. Take a look at the pictures and at the videos.

Shared Plasmoid on N900

Shared Plasmoid on N900

I didn’t use Plasma netbook for this demo because I needed to recompile some stuff and it’s much better in a real netbook. This demo I’ll do during my talk on Latinoware. But for those that can’t go, I’ll talk a little bit: user experience is more than what the user does in front of his computer. It’s all about tasks. Recently, Rob integrated into KDE 4.4 his wonderful SoC called Remote Widgets. This enables two machines to share Plasma content in a very nice and easy way (I don’t even need to say that developers using libplasma get this feature for free, do I ?).

Original Plasmoid on Desktop

Original Plasmoid on Desktop (written using Javascript)

For me it was a pretty clear path to go. I want to share my widgets (that helps me during my day-to-day tasks) between different devices, so I can “take” them with me even if I leave my computer. This can be applied to many plasmoids and this is just a demo. I get a plasmoid that is in my desktop and share it with my mobile phone (in this case an N900 that a friend that went to Maemo Summit led me for this weekend). Pretty simple and easy to achieve (ok, it was hard to record the movie, talk and do all the stuff at the same time hehe). For security reasons it asks for pin codes between the two devices (just like bluetooth pairing – and you can have trusted devices too) and you can even save your passwords using KWallet :).

(if you can’t see the video above, try going here: http://www.youtube.com/watch?v=F1qxdYAUBbk)

Thanks to Mek and Darktears for sharing Qt/KDE compile problems in scratchbox, Vudentz for the device and Aaron and work mates for calming me down when I was compiling all the stuff πŸ™‚ Any questions are welcome and remember that we can extend this a lot! (preempting one question: yes, it’s possible to share the “now playing” plasmoid and control your Amarok from the device πŸ˜‰ ).

Cheers!

White as Snow

Well, last day of Tokamak. It’s sad that I must say goodbye to all of these people that actually lived with me for one week. It was so intense that I almost didn’t realize that we were together for one week. But let’s talk about what we did during the sprint.

During the first days I talked with everybody I could about anchor layouts, animated layouts and Qt stuff. It was great as it’s hard to explain the stuff and get feedback from a lot of great hackers at once and as fast as we can get when we are in this kind of developer sprints. We had great discussions about Qt, regarding bugs, features, future and everything else we could talk about. I really can see that every time that we put all these great hackers in the same room, we save some months (maybe years?) of development. All of that to make you take less time to code πŸ˜‰

Plasma Developers

Plasma Developers

While everybody else was merging their brand new stuff on trunk, commiting bug fixes and new features I was fighting with cross compiling KDE to the “mysterious device” that Aaron brought to us. What I could achieve ? We have KDE 4.2.X working PERFECTLY on this device, with all the features and beauty that KDE could bring to you. It runs really really fast on this ARM device. We were all impressed!

And then came the second part of the experiment: run trunk on it. While it was ok to compile stuff on scratchbox using Maemo SDK, the lack of a proper SDK for the device gave us some headache: some bug on qmake prevented it to detect correct paths and made me find out each library that was not properly added to cmake’s links.txt file and correctly add it. By the end of kdebase compilation I already had almost all the names and did a script to fix that, but until the time I found out all the libraries it was compiling and stopping all the time (I don’t need to tell that it was really slow to compile and due to this problem, it was even slower).

After some days I finally had kdelibs + plasma-destkop and plasma-netbook compiled. However when we put all this stuff on the hardware we faced a problem with Svg files not being show. So althoughf we have plenty new stuff full of new features running on the device, it looks a little bit “ugly” without the proper background, etc.. we just have white background…white as snow. But come on…we just had a few days with the device…we can do MUCH more with it and imagine if we had a proper SDK ? We can make this hardware AWESOME with our software and I can only hope that we’ll have some more time with it in the next months…(we would need less than 1 month with a proper SDK to make it really really really ROCK!).

Ah, meanwhile it was compiling kdelibs I created the pastebin dataengine/service, migrated the pastebin applet to use that and also fixed some bugs on other applets…

Talking about snow, today was the first day I saw snow in my life πŸ™‚ It was a unique experience for me :). It’s really hard to describe with words how happy I was and how beautiful it was in the top of that mountain. Thanks Mario for this trip…it was one of those moments in our lifes that you never forget.

Tomorrow morning I’m heading to Brazil again. It was an awesome sprint. If someone asks me what comes next from my point of view, I would answer: running plasma-netbook on the “mysterious device” (please, I just need one week with a proper SDK πŸ˜‰ ), finishing and optimizing anchor layout for Qt 4.6 (I really hope this will help people out there to create rich UIs with Qt) and of course: keep all the stuff we have discussed during Tokamak going on!

Randa View

Randa View

Thank you Mario, thank you Plasma developers, thank you Qt/INdT and thank you KDE πŸ™‚ What a wonderful personal and professional experience.

Tokamak 3

I’m at Tokamak 3 in Randa where Mario is hosting us. First of all, thanks to Mario: everything is perfect!

Great landscape surrounding us

Great landscape surrounding us

During the last days we had presentations, meetings and talks. The GSoC projects are being merged in trunk (a lot of great features coming: new widgets explorer, mouse plugins, remote widgets, plasmate), the netbook stuff is going on, Qt stuff being solved, etc..

I talked about QGraphicsAnchorLayout, the new layout engine that will be present on Qt 4.6 and even did a small demo about that. We are nailing down the remaining bits (API, bugs) and hopefully we’ll have an awesome layout engine to create rich UIs when Qt 4.6 comes to “the streets” !

I’m also working with Alexis (darktears) to debug some problems that we’re facing with the raster engine on embedded devices. The thing is that the performance was not so good as it was in 4.5.0 and we’re tracking down where is the regression. Besides that we already tested Qt 4.6 on some hardware that we have here and the performance is much better than 4.5.X (regarding GraphicsView). While we wait Qt cross compiling, I’m also updating the pastebin applet to provide a nice dataengine/service so other plasmoids/applications can take advantage of this.

Until now, it has been a great sprint with lot of work being done on Plasma and on Qt 4.6. It’s awesome how much our speed increases when we are together! πŸ˜‰

The theory behind the code

I’ll not talk about GCDS on this post: others said everything one could tell about the conference! πŸ™‚ It was really awesome: meeting KDE people is just an awesome experience. It was good also to see more brazilians in the conference (after FISL, the brazilian kde community seems to have started to grow or at least organize more itself) . Ah, during GCDS I joined for the first time the e.V. assembly and it’s really good the feeling that I’m helping the KDE community a little bit more. KDE is all about it’s community and it’s community is great! Well, enough with the sentimental part. Let’s talk about the theory behind the code of plasma-netbook.

Newspaper Activity ready for the presentation

Newspaper Activity ready for the presentation

During GCDS I did a presentation about this project, explaining a little bit our ideas and why we had them. I also used the time to definetely fix the name of the project to plasma-netbook (instead of plasma-mid). This was done to reflect the objective of the project. We created the project to avoid the idea of putting a full desktop inside a netbook (using concepts that don’t fit well on the device), and we can’t fall into the same problem trying to have something for MID devices also.

It was good to see the interest of the community around the project and also to see that some vendors are already contacting us to ship their devices with our netbook shell. Great also to see that the Kubuntu team will have a “Kubuntu Netbook Remix” project and if we can deliver in time our stuff, they want to use it on their project.

One thing that is also really important about the project is the fact that we want to create a new user experience on these devices. KDE is not about a specific project anymore, it’s all about the user experience: starting on the desktop shell and going far away on social interaction, media, etc. Thinking about this we want to improve this experience by delivering great features such as the open Social plasmoid, the new wikipedia runner and others that will come with the time. This way, when some random user buys his brand new netbook, running KDE he will enter our world, he’ll start to fell part of something more and that was the strategy that saved a fruit company that makes computers and devices (they create a new experience around their devices). I really hope that the community and also vendors can see the potential that we have in our hands and start helping us on this journey and to believe that it’s possible.

If you want to read the paper that I wrote about this, download it here and also my presentation here. You can also check Marco’s last post about the current status of the project.

During my presentation I announced the Qt Labs America project and I hope to give more news for you really soon….ah, and the talk about Qt layouts (including live demos of anchor layouts and animated layouts) by my fellows Caio and Eduardo was also great. If you couldn’t watch it, stay tuned to the videos that the conference will publish (I hope so πŸ˜› ).

Now I’m really looking forward Tokamak3. I hope I can go but I have a lot of “ifs”. Let’s see what happens next weeks.

New Pastebin feature and change of names…

Now you can just drop an http URL on the pastebin plasmoid and it’ll give you a tiny url πŸ™‚ Nice and small feature…

Also I just committed the change of name from plasma-mid to plasma-netbook to avoid problems, confusions and all questions regarding mid devices that are not the focus right now.

Later I’ll post more news about GCDS and about my presentation/paper.