Author Topic: Blog: KDE Plasma Miscellaneous stuff  (Read 1648 times)

Offline menotu

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 15316
  • ┌∩┐(◕_◕)┌∩┐
Re: Blog: KDE Plasma Stuff
« Reply #15 on: March 20, 2013, 07:27:27 AM »
PCLinuxOS 32bit KDE 4.10.1; kernel-3.4.11-pclos1.bfs & 64bit 3.2.18bfs; NVidia GeForce 8400GS 1GB 310.19 driver

Sony Vaio SVE1513A4ESI Laptop, Intel Core i5, 2.6GHz, 6GB RAM, 750GB, 15.6" Intel HD Graphics 4000

Offline menotu

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 15316
  • ┌∩┐(◕_◕)┌∩┐
Re: Blog: KDE Plasma Stuff
« Reply #16 on: March 28, 2013, 06:56:35 AM »
By grulja - March 27, 2013

Plasma-nm (NetworkManager) preview

I’d like to show you what we are doing for network management in KDE. With Lukáš Tinkl we started to write a new plasma applet for managing your network connections.

It’s a long road to have some stable release or something for daily usage, but we have already wired and wireless connections and some basic functionality for other connection types. The entire applet is written in QML except for C++ model and some classes for working with NetworkManager. For that purpose we are using libnm-qt library which is Qt library for NetworkManager. We are also working on a new connection editor which will be as a standalone application. This editor uses some components from the old Plasma NM applet but it’s redone to use libnm-qt library.

If you want to try it, you can get it from our git repository git://anongit.kde.org/plasma-nm.git and you should disable the kded module from the old Plasma NM applet but we are not supporting secrets for VPN connections for now.

You will have to also compile libmm-qt git://anongit.kde.org/libmm-qt.git and libnm-qt (settings branch) git://anongit.kde.org/libnm-qt.git

And please note that this is not a stable version and a lot of functionality is missing.

There is also one problem with secrets, because the old Plasma NM applet stores secrets into KWallet and there are “agent owned”. We are storing secrets into the NetworkManager and when your secrets are “agent owned”, there will be problem with getting them from NetworkManager. For that you will have to edit your connection with our new editor or create them from nm-connection-editor (from NetworkManager). But it can be used together with the old Plasma NM for now if you want to have full functionality of getting secrets.

And picture how will look the new editor



Here is a video of the plasma-nm in action

plasma-nm


http://grulja.wordpress.com/2013/03/27/plasma-nm-preview/
PCLinuxOS 32bit KDE 4.10.1; kernel-3.4.11-pclos1.bfs & 64bit 3.2.18bfs; NVidia GeForce 8400GS 1GB 310.19 driver

Sony Vaio SVE1513A4ESI Laptop, Intel Core i5, 2.6GHz, 6GB RAM, 750GB, 15.6" Intel HD Graphics 4000

Offline menotu

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 15316
  • ┌∩┐(◕_◕)┌∩┐
Re: Blog: KDE Plasma Miscellaneous stuff
« Reply #17 on: April 03, 2013, 08:12:58 AM »
The following may help in setting, or at least understanding, some of the options within KDE Plasma/KWin etc.

The link is at the bottom
=================================================================

b]KDE Wiki: Desktop Effects Performance[/b]

Items covered are listed below

    1 Desktop Effect Performance
    2 Selecting the correct driver
        2.1 Determining the used driver
        2.2 Available Drivers
            2.2.1 AMD/ATI
            2.2.2 Intel
            2.2.3 NVIDIA
        2.3 Installing the Driver
    3 OpenGL Version
        3.1 kwin_gles
    4 Thumbnail Scaling
    5 General Speed of Animations
    6 Qt Graphics System
    7 Window Decorations
    8 Blur Effect
    9 Advanced Desktop Effects Settings
        9.1 Compositing type
        9.2 Keep window thumbnails
        9.3 Suspend desktop effects for fullscreen windows
        9.4 OpenGL mode
        9.5 Enable direct rendering
        9.6 Use VSync

http://userbase.kde.org/Desktop_Effects_Performance/en
« Last Edit: April 20, 2013, 09:06:23 AM by menotu »
PCLinuxOS 32bit KDE 4.10.1; kernel-3.4.11-pclos1.bfs & 64bit 3.2.18bfs; NVidia GeForce 8400GS 1GB 310.19 driver

Sony Vaio SVE1513A4ESI Laptop, Intel Core i5, 2.6GHz, 6GB RAM, 750GB, 15.6" Intel HD Graphics 4000

Offline menotu

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 15316
  • ┌∩┐(◕_◕)┌∩┐
Blog: KDE Plasma Miscellaneous stuff
« Reply #18 on: April 09, 2013, 05:28:12 AM »
by David Edmundson - 9 April 2013

New KDE Telepathy brings Better Text Editing and Improved Notifications

Good news, everyone! Today the KDE Telepathy team released version 0.6.0 of KDE Telepathy (KTp), KDE's instant messaging suite. This version brings a number of new features as well as a large amount of bug fixes.

About KDE Telepathy

KDE Telepathy is an instant messaging suite built upon the Telepathy framework. KDE Telepathy provides text chat, video calls and file transfer services over many popular instant messaging platforms including Facebook Chat and Google Talk. In addition KTp provides libraries for embedding instant messaging or real-time collaboration inside your application.

New Features

This release brings in a number of major new features. An overview:

Kopete log migration

KTp now imports logs from Kopete accounts into our log format. For new KTp users this will be asked if they wish to import when they create an account, existing users can also import logs by opening the log viewer.



Clearer message notifications

KTp had some feedback to improve the notifications of new messages. KTp now shows an icon in the contact list when a new message arrives, change the icon in the system tray, and for group chats show who is typing.

Better text editing
The chat window now features tab completion for group chats, as well as text navigation for editing messages.

KTp has made adding emoticons easier too, with a new optional emoticon toolbar.

Advanced notifications

KTp now supports setting different notifications for each of your contacts. This means it is possible to set an optional notification if your favourite friends come online, or play sounds when messages arrive from certain contacts but not others.

Improved password and security management

KTp is now able to connect to password protected jabber rooms, a much requested feature. We have also improved our connection certificate handling, now using KDE SSL certificates manager and allowing the user to override invalid certificates.

Under the hood changes and cleanups

A lot of our effort has been spent in a big refactoring under the hood, getting ourselves ready for the future as well as bringing speed and stability closing over 85 bug reports in 0.6.

0.6.0 features completely redone connection error notifications and other important UI areas.

Core filtering plugins

KTp has an extended range of message plugins to make chatting more dynamic and interactive.

Text messages can be formatted in bold or italics

Full blog and images
« Last Edit: April 20, 2013, 09:06:03 AM by menotu »
PCLinuxOS 32bit KDE 4.10.1; kernel-3.4.11-pclos1.bfs & 64bit 3.2.18bfs; NVidia GeForce 8400GS 1GB 310.19 driver

Sony Vaio SVE1513A4ESI Laptop, Intel Core i5, 2.6GHz, 6GB RAM, 750GB, 15.6" Intel HD Graphics 4000

Offline menotu

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 15316
  • ┌∩┐(◕_◕)┌∩┐
Re: Blog: KDE Plasma Miscellaneous stuff
« Reply #19 on: April 20, 2013, 09:22:17 AM »
By Martin Gräßlin (graesslin) 20 April 2013 (Martin’s Blog From the land of wobbly windows)

The relationship between Plasma and KWin in Workspaces 2
   
Yesterday during the Tokamak 6 sprint in Nuremberg we discussed the role of KWin in Plasma Workspaces 2. At the moment in Plasma Workspaces 1 KWin is of course the recommended window manager and compositor, but it’s also possible to use a different window manager. Back in the days there were quite a lot of users who run Plasma with Compiz. In theory that shouldn’t matter because everything is standardized with EWMH and ICCCM. Over the years we added more and more extensions to EWMH. It’s all open source so anyone can implement these extensions (Compiz used to do so), nevertheless right now there is probably no other window manager available to offer the full experience except KWin.

Plasma Workspaces 2 will be released at an interesting point of time. We don’t want to do the transition to Qt 5 and Wayland at the same time, so it will still be X based. But we all agree that our future will be on Wayland and even if we use X as the windowing system our primary focus is on Wayland. With Wayland quite a few things will change. KWin will play a more important role as it will be the Wayland compositor – we do not plan to use Weston.

Given that we know that the Wayland shell interface only covers part of what Plasma needs and some of our needs are extremely Plasma specific (for example Activities) it would be tempting to say that we tie KWin to Plasma. Let’s face it: which other compositor will be there to replace KWin? The reference compositor will probably never accept Plasma specific patches for things like Activities, Compiz won’t be ported to Wayland and GNOME Shell will probably never be a solution for Plasma. For the small window managers we do not know whether they will go to Wayland at all, but I expect rather not, though I expect that we will see Weston forks/extensions for substitutions of tiling window managers.

We decided to resist the temptation to go the easy road, but instead will develop all our integration bits in a way that one could replace KWin by a different Wayland compositor, even if that is just a theoretical option. Of course we will not do any fallback modes for the case that one is using e.g. Weston without Plasma integration bits. So the features which we need might then just be disabled. Adding fallback modes would most likely just result in bit rotting code as nobody would use it.

Of course to make it possible that others can provide compatibility features we need to properly document our extensions and additional interfaces. Luckily Wayland implicitly forces us to do so. The general plan is to publish our extensions and also try to standardize what makes sense to be standardized and we hope that this would also benefit other projects. What we especially had in mind is of course Razor-Qt which already supports using KWin. By properly documenting all our Plasma-KWin communication channel, they can also use what is useful to them and it ensures that we don’t break KWin in a way that it gets unusable for Razor-Qt.

http://blog.martin-graesslin.com/blog/2013/04/the-relationship-between-plasma-and-kwin-in-workspaces-2/
PCLinuxOS 32bit KDE 4.10.1; kernel-3.4.11-pclos1.bfs & 64bit 3.2.18bfs; NVidia GeForce 8400GS 1GB 310.19 driver

Sony Vaio SVE1513A4ESI Laptop, Intel Core i5, 2.6GHz, 6GB RAM, 750GB, 15.6" Intel HD Graphics 4000

Offline menotu

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 15316
  • ┌∩┐(◕_◕)┌∩┐
Re: Blog: KDE Plasma Miscellaneous stuff
« Reply #20 on: April 22, 2013, 09:48:23 AM »
By Martin Gräßlin (graesslin) 21 April 2013 (Martin’s Blog From the land of wobbly windows)

The History on Wayland Support inside KWin

Ever since a certain free software company decided to no longer be part of the larger ecosystem, I have seen lots of strange news postings whenever one of the KDE workspace developers mentioned the word “Wayland”. Very often it goes in the direction of “KDE is now also going on Wayland”. Every time I read something like that, I’m really surprised.

For me Wayland support has been the primary goal I have been working on over the last two years. This doesn’t mean that there is actual code for supporting Wayland (there is – the first commit for Wayland support in our git repositories is from June 11, 2011 (!)).

The Wayland research projects two years ago had been extremely important for the further development of KWin since then. First of all it showed that adding support for Wayland surfaces inside KWin’s compositor is rather trivial. Especially our effect system did not care at all about X11 or Wayland windows. So this is not going to be a difficult issue.

The more important result from this research project was that it’s impossible to work against an always changing target. At that time Wayland had not yet seen the 1.0 release, so the API was changing. Our code broke and needed adjustments for the changing API. It also meant that we could not merge the work into our master branch (distributions would kill us), we needed to be on a different branch for development. Tracking one heavily changing project is difficult enough, but also KWin itself is changing a lot. So the work needed to be on top of two moving targets – it didn’t work and the branch ended in the to be expected state. Now with Wayland 1.0 and 1.1 releases the situation changed completely.

The next lesson we learned from that research project was that the window manager part is not up to the task of becoming a Wayland compositor. It was designed as an X11 window manager and the possibility that there would not be X11 had never been considered. We started to split out functionality from the core window manager interface to have smaller units and to be able to add abstractions, where needed, to support in future more than just X11. That had been a huge task and is still ongoing and it comes with quite some nice side-effects like the rewrite of KWin scripting (helped to identify the interface of a managed Client inside KWin), the possibility to run KWin with OpenGL on EGL since 4.10, the new screen edge system in 4.11 and many many more. All these changes were implemented either directly or indirectly with Wayland in mind. That means we have been working on it for quite some time even if it is not visible in the code.

Full blog
PCLinuxOS 32bit KDE 4.10.1; kernel-3.4.11-pclos1.bfs & 64bit 3.2.18bfs; NVidia GeForce 8400GS 1GB 310.19 driver

Sony Vaio SVE1513A4ESI Laptop, Intel Core i5, 2.6GHz, 6GB RAM, 750GB, 15.6" Intel HD Graphics 4000

Offline menotu

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 15316
  • ┌∩┐(◕_◕)┌∩┐
Re: Blog: KDE Plasma Miscellaneous stuff
« Reply #21 on: April 24, 2013, 10:29:01 AM »
From Aaron Seigo - April 24, 2013

A Plasma Workspaces 2 Milestone

http://aseigo.blogspot.co.uk/2013/04/tokamak-6-plasma-workspaces-2-milestone.html
PCLinuxOS 32bit KDE 4.10.1; kernel-3.4.11-pclos1.bfs & 64bit 3.2.18bfs; NVidia GeForce 8400GS 1GB 310.19 driver

Sony Vaio SVE1513A4ESI Laptop, Intel Core i5, 2.6GHz, 6GB RAM, 750GB, 15.6" Intel HD Graphics 4000

Offline menotu

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 15316
  • ┌∩┐(◕_◕)┌∩┐
Re: Blog: KDE Plasma Miscellaneous stuff
« Reply #22 on: April 24, 2013, 10:42:47 AM »
by Sebastian Kügler - 24 April 2013

Plasma Pow-wow Produces Detailed Plans for Workspace Convergence

Last week, members of the Plasma team met in Nürnberg, Germany to discuss open questions on the road to Plasma Workspaces 2. The meeting was kindly hosted by SUSE and supported by the KDE e.V.. For the Plasma team, the meeting came at a perfect point in time: porting of Plasma to a new graphics has commenced, is in fact well under way, and has raised some questions that are best discussed in a high-bandwidth setting in person.
Graphics Stack Options

The developers laid out the plans for an eventual release of Plasma Workspaces 2, based on KDE Frameworks 5 and Qt5. Wayland is also part of this plan.

Starting with Plasma Worskpaces 2, Wayland will join X11 as a supported windowing environment, and all new development is taking this into consideration. Wayland is a replacement for most of the functionality which is today offered by Xorg. Wayland simplifies the graphics stack significantly with the goal of making every frame shown on screen perfect, something that is hard to achieve reliably with X11.

Wayland's leaner graphics stack and improved security model also make it more appropriate for use on modern devices. As such, it is widely seen as the successor to X11 in the Free software ecosystem. Most of the gruntwork needed for this transition is already offered in Qt, however, there are still quite some X11-dependent code pathes in the KDE Frameworks, especially in KWin and the Oxygen widget style. While KWin is making excellent progress towards being able to be used as Wayland compositor, the future of the Oxygen widget style is still an unsolved problem.

The idea is to not introduce a new user interface, but streamline the design language of the current workspace. Common and consistent elements for the user experience will be defined, and made available as packages. This goes along with less granularity in the workspace setup options, but fear not: The user will be able to mix and mash these elements to create a customized user experience. To this end, the hackers introduced a new type of Plasma packages: Look and Feel. A look and feel package combines code for UI elements such as the application switcher, activity switcher, splash screen, logout dialog and lock screen into a single package. The Look and Feel package can be swapped, either along with the shell package, or independently, allowing for great freedom in the choice of UI while delivering a great deal of consistency. This way of organizing the "vocabulary of the workspaces design language" will allow quick changes of the entire theme and allow downstream partners to ensure greater consistency at lower effort for their products. For a highly customized user experience, a tool will allow the user to easily remix the Look and Feel of the workspace.

One Shell to Rule All Devices

A generic shell is one of the things that is already in place. Rather than having one binary per workspace, with slightly different mechanics, the Plasma developers have merged these code bases into one. Elements of the shell such as default configuration, setup of panels, toolbox, containments et cetera are now defined in a so-called shell package. The generic shell itself does not hold any assumption about the target device, or use case. The UI elements are all defined in QtQuick-based code. This makes the shell easier to hack on and more maintainable, while allowing for greater flexibility for both, users and developers.

One aspect of Plasma's device convergence strategy is transparent switching of the workspace User Interface. While Plasma does offer different workspaces as it is already (Plasma Desktop, Plasma Netbook, Plasma Active, Plasma Mediacenter), these pieces are still distinctive programs right now. The plan is to move all these different user experiences into Plasma packages, which can be switched at runtime. The switching itself can be manually invoked, but also based on heuristics such as input and output devices plugged in.

A user could, for example, plug a keyboard and a mouse into her tablet, and the workspace would automatically be switched from a Tablet and touch-focused UI to a more traditional Desktop setup. Connecting a TV to the device could swap the workspace to a media center interface.

Some of the code taking care of this is already in place, but not in a state yet where it could be demonstrated.

Quicker

The way for doing UI in Plasma Workspaces 2 is to use QtQuick. This allows us to offload graphics rendering to the GPU, making better use of graphics hardware, freeing the CPU for other tasks and conserving battery life, as the GPU is much more efficient in these operations.

It does not require OpenGL drivers, however. Graphics on systems that do not support OpenGL can fall back to XRender or fully CPU based rendering. The worst case scenario is that the rendering will be done on the CPU, which is how the desktop layer is rendered today and so have the performance as it does now. To achieve performance parity even on systems which lack properly accelerated graphics drivers, usage of "heavyweight" graphics effects will be kept to a minimum. In the end, a system that is capable of running the current version of Plasma will also be able to run Plasma Workspaces 2, most likely with even better performance.

http://dot.kde.org/2013/04/24/plasma-pow-wow-produces-detailed-plans-workspace-convergence
PCLinuxOS 32bit KDE 4.10.1; kernel-3.4.11-pclos1.bfs & 64bit 3.2.18bfs; NVidia GeForce 8400GS 1GB 310.19 driver

Sony Vaio SVE1513A4ESI Laptop, Intel Core i5, 2.6GHz, 6GB RAM, 750GB, 15.6" Intel HD Graphics 4000

Offline menotu

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 15316
  • ┌∩┐(◕_◕)┌∩┐
Re: Blog: KDE Plasma Miscellaneous stuff
« Reply #23 on: April 26, 2013, 04:27:49 AM »
by David Edmundson - 25 April 2013

A Sneak Peek at KTp Active

No tablet would be complete without instant messaging. Thanks to awesome bachelor thesis work we had a non-working mockup of an active client. This active client remains separate from our desktop work.

In recent weeks I've been transforming this code to go from a non-working prototype to something working with real contact lists and text chats



How to set up the latest ktp-active

Install the latest version of plasma-mobile-components. Personally I use project-neon for this to keep a separate environment.

Install the latest (git master, not 0.6.1) of ktp-common-internals

You will need to open system settings and change your workspace theme to "Air Mobile".

git clone git://anongit.kde.org/ktp-active

Change directory to application/package and run "plasmoidviewer"

You will need to set up your accounts using either our desktop Accounts KCM Module, or manually using the mc-tool command line tool.

This sounds awesome, how can I get involved?

See our KTp wiki page http://community.kde.org/KTp/Getting_Involved

Blog and links
PCLinuxOS 32bit KDE 4.10.1; kernel-3.4.11-pclos1.bfs & 64bit 3.2.18bfs; NVidia GeForce 8400GS 1GB 310.19 driver

Sony Vaio SVE1513A4ESI Laptop, Intel Core i5, 2.6GHz, 6GB RAM, 750GB, 15.6" Intel HD Graphics 4000

Offline menotu

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 15316
  • ┌∩┐(◕_◕)┌∩┐
Re: Blog: KDE Plasma Miscellaneous stuff
« Reply #24 on: May 04, 2013, 08:51:39 AM »
Published on 16 Apr 2013

open-slx Screencast: Installing Skype in Plasma Active

You can download the skype-installer script with: curl --output skype-installer

http://saigkill.homelinux.net/pub/sky...

https://www.youtube.com/watch?feature=player_embedded&v=z_HV0n4QLQA
PCLinuxOS 32bit KDE 4.10.1; kernel-3.4.11-pclos1.bfs & 64bit 3.2.18bfs; NVidia GeForce 8400GS 1GB 310.19 driver

Sony Vaio SVE1513A4ESI Laptop, Intel Core i5, 2.6GHz, 6GB RAM, 750GB, 15.6" Intel HD Graphics 4000

Offline menotu

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 15316
  • ┌∩┐(◕_◕)┌∩┐
Re: Blog: KDE Plasma Miscellaneous stuff
« Reply #25 on: May 04, 2013, 08:56:01 AM »
The video colour isn't very good- too gray/darkish
===============================

Published on 24 Apr 2013

In this Screencast we showing you, how to add your Owncloud Contacts & Calendar to Plasma Active and how it looks like in Kontact Touch

https://www.youtube.com/watch?feature=player_embedded&v=xY8NBx1zB8g
PCLinuxOS 32bit KDE 4.10.1; kernel-3.4.11-pclos1.bfs & 64bit 3.2.18bfs; NVidia GeForce 8400GS 1GB 310.19 driver

Sony Vaio SVE1513A4ESI Laptop, Intel Core i5, 2.6GHz, 6GB RAM, 750GB, 15.6" Intel HD Graphics 4000

Offline menotu

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 15316
  • ┌∩┐(◕_◕)┌∩┐
Re: Blog: KDE Plasma Miscellaneous stuff
« Reply #26 on: May 22, 2013, 05:32:02 AM »
by David Edmundson - 21 May 2013

KTp 0.6.2 Released

We have just released version 0.6.2 of KDE Telepathy, KDE's instant messaging client.

This new minor release brings some important fixes on some crashes that occurred in rare conditions that we hadn't found before our initial release.

Crash Fixes

    304085: Contact list crashed after unlocking screen
    Git Commit

    318793: contact list crashes when closing the settings dialog
    Git Commit

    319040: crash on startup
    Git Commit

Bug Fixes

    318663: Esc key when filtering contacts does not reset filter model
    Git Commit

    318751: Groupwise logs imported from Kopete are displayed with HTML tags in chat window.
    Git Commit

    319162: Contact tooltips miss presence icon since model porting
    Git Commit

http://www.sharpley.org.uk/blog/ktp-0-6-2
PCLinuxOS 32bit KDE 4.10.1; kernel-3.4.11-pclos1.bfs & 64bit 3.2.18bfs; NVidia GeForce 8400GS 1GB 310.19 driver

Sony Vaio SVE1513A4ESI Laptop, Intel Core i5, 2.6GHz, 6GB RAM, 750GB, 15.6" Intel HD Graphics 4000

Offline menotu

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 15316
  • ┌∩┐(◕_◕)┌∩┐
Re: Blog: KDE Plasma Miscellaneous stuff
« Reply #27 on: May 22, 2013, 07:05:15 AM »
Posted by Mike Ratcliffe on 26 Mar 2013

Moving your Contacts and Calendar Away from Google (and into ownCloud)

Exporting Contacts from Google Contacts

At the time of writing, exporting contacts from Google Contacts as a .vcf file only exports one name, phone number and email address per contact. Fortunately, if you export your contacts from an Android phone you will keep all of your contact information including mugshots. To do this:

    From a Home or All Apps screen, touch the People icon.
    Select Menu > Import / Export.
    Select "Export to storage."
    Touch "OK" to confirm.

A file with the .vcf extension will be saved to the root directory of your phone's internal storage. This file contains all of your contacts including their photos. Transfer this file to your computer via a USB cable or email.

    Go to http://yourdomain.com/owncloud/
    Click Contacts -> Import.
    Select the file .vcf file that you copied to your computer and click OK to import.

Importing Calendar to ownCloud

    Go to http://www.google.com/calendar/
    Click settings -> Settings -> Calendars -> Export Calendar.
    Save the .ics file to your computer.
    Go to http://yourdomain.com/owncloud/
    Click Files and drag the .ics file into the files window in order to upload it.
    Click on the .ics file.
    In the Import calendar dialog that appears select "Default calendar" and click import.
    When the calendar has been imported close the dialog and delete the .ics file.

Configure Thunderbird
Calendar

    Uninstall the Provider for Google Calendar add-on.
    Install SOGo Connector.
    Install MoreFunctionsForAddressBook.
    Install the Lightning extension.
    In your owncloud calendar copy your calendar's CalDAV link.
    Back in Thunderbird open the calendar.
    Click File -> New Calendar -> On the Network -> Next -> CalDAV.
    Type the following into the location field:
        https://yourdomain/owncloud/remote.php/caldav/calendars/USERNAME/CALENDARNAME (the default calendar name is defaultcalendar).
    Check Offline Support.
    Click Next
    Give your calendar a name and an email address. The email address is used for email notifications.

Contacts

    Uninstall the Google Contacts addon.
    Install SOGo Connector.
    In Thunderbird open the Address Book.
    File -> New -> Remote Address Book.
    Give your address book a name.
    Type the following into the URL field:
        http://your domain/owncloud/remote.php/carddav/addressbooks/username/contacts/
    Click okay and synchronize and your contacts should download.

Configure Android Phone
Contacts

    Go to People.
    Choose Settings -> Accounts -> Your Google account.
    Clear the checkbox so that Google Contacts are no longer synchronized.
    Install CardDAV from the Google Play Store. There is a free version CardDav-Sync free beta and a paid version called CardDav-Sync beta. The paid version syncs more contact fields. You can start with the free and upgrade later.
    Run CardDAV-Sync and use these settings:
        Server URL: /owncloud/remote.php/carddav/
        Use SSL: check accordingly.
        Username: your login name.
        Password: your password.
    Click OK.
    Go back to People.
    Choose Settings -> Contacts to display -> Customize.
    Expand your Google account and clear all of it's checkboxes.
    Expand your CardDav account and check all of of it's checkboxes.
    Click OK and your contacts will be synchronized.

Calendar

    Install CalDAV from the Google Play Store. There is a free version called CalDav-Sync free beta and a paid version called CalDav-Sync beta, both written by Marten Gajda.
    Open Calendar.
    Choose Settings -> Settings -> Your Google account.
    Clear the checkbox so that Google Calendar is no longer synchronized.
    Click Add Account -> CalDav and use these settings.
        Server URL: <servername>/owncloud/remote.php/caldav/
        Use SSL: check accordingly.
        Username: your login name.
        Password: your password.
        Click Next.
    Under "Select accounts to sync" select all appropriate calendars.
    Click Next.
    Enter the email address. The email address is used for email notifications.
    Click OK and your calendar(s) will be synchronized.
    Go to phone Settings -> Accounts -> Google -> Select the Google account with the sync icon next to it -> Uncheck calendar.

Congratulations, you now no longer need an external service to synchronize your contacts and calendar. As a bonus there are a bunch of ownCloud add-ons that give you much more power than you previously had.

http://flailingmonkey.com/moving-contacts-calendar-google
PCLinuxOS 32bit KDE 4.10.1; kernel-3.4.11-pclos1.bfs & 64bit 3.2.18bfs; NVidia GeForce 8400GS 1GB 310.19 driver

Sony Vaio SVE1513A4ESI Laptop, Intel Core i5, 2.6GHz, 6GB RAM, 750GB, 15.6" Intel HD Graphics 4000