GSoC 2012: Make Plasmate ready for release, report 3

As I mentioned in my previous report my second task is to implement a remote installer. This week I have fixed the ui and a few things in the logic code, from now on the remote installer doesn’t ask the user to specify a temporary directory. So this is how remote installer looks like right now,

the remote installer as a plasmate plugin

the remote installer as a standalone application

Advertisements

GSoC 2012: Make Plasmate ready for release, report 2

This is my second report for my GSoC 2012 project. This week and the next two coming weeks my task is to implement a remote installer. Except from adding the feature into plasmate we also decided to make the remote installer a standalone application.

So far I have implemented the remote installer both as a standalone application and as a plasmate plugin, but the logic code doesn’t work properly yet.

the remote installer as a plasmate plugin

the remote installer as a standalone application

When the remote installer will be finished you will be able to access the remote installer

  • from plasmate via the publish dialog
  • and as a standalone application named plasmaremoteinstaller

So what’s next?
I don’t really like the ui, so I will try to come up with something nicer 🙂 and of course to fix the logic code which doesn’t work properly.

Also, this week I had to integrate the remote installer inside plasmate’s Publish dialog, so I fixed  some bugs that Publisher had.