Skip to content

Ideas for PlexyDesk

Siraj Razick edited this page Feb 22, 2015 · 6 revisions

New Features and Ideas for PlexyDesk.

PlexyDesk aims to be modular. The core functionalities include loading extensions and platform support to render widget in a toolkit independent way. So we are equally happy to support HTML5 widgets as well as C++ widgets, but as extensions. This leaves room for us to support various types of widgets using the same desktop framework. This will help vendors to support their own layout engines or widgets within plexydesk without having to redo and fork the project. These new ideas are always derived following this key concept of modularity.

HTML5 Widgets.

  • Add support for loading HTML5 widgets from a zipped widget pack.
  • Create a new Desktop controller for handling HTML5 widgets.
  • Support loading Apple dashboard widgets on OS X.
  • Inject plexydesk API into the web context.

Qt independent Layout manager.

  • Current code dependents on Qt QGraphicsLayout for widget layouts, ideally it would be perfect if we can have a toolkit independent layout manager written in C++.
  • Support animated layout updates.
  • Dynamic Grid layout.
  • New types of layout and the support for extending these layouts.

Add support for DBus on Unix.

  • Write a desktop controller to support IPC over DBUS if detected during runtime.
  • Expose Workspace and space specific methods to DBus.
  • Support SocialKit interactions over DBUS.

Improve window management. [Linux/X11]

  • Support Wayland and write a compositor. name it plexydesk-session-shell.
  • Improve window management functions in Space class or write a new class to handle window hierarchy.
  • Note that the current space classes does not support window a hierarchy.
  • Improve session management.

Addressbook.

  • Create address book data models to aggregate contacts from various sources.
  • Local storage support to store contacts and meta contact information. We should be able to store contacts using various backends. such as XML/sqlite/ or even RDF databases with proper meta contact relationships and linkages.
  • Unified UI components to browse, search, edit, and discover contacts which connects to address book models using an unified API.
  • Contact card UI with details about the contact
  • Concept of Self Contact
  • Card Editor. Start a form editor to edit contact details.
  • Contact Chooser Activity. Quick contact selector to pick contacts from other widgets/applications.

Note Editor

  • Context aware notes - Read the title and fetch meta information about the title online.
  • Add Weather information to notes.
  • Button to add notes,
  • Share button to share a note between users from the address book.
  • Share notes over social media (twitter/facebook/Google+)
  • Add note tags
  • Note browser with search

File Manager.

  • Ability to add a folder to the desktop
  • Desktop Trash can
  • Mounted Disk Volumes.
  • File search
  • File tags and meta information
  • Easy sharing over social media (facebook/twitter/Google+).

Social Integration.

  • Social activity widgets for sharing, uploading and downloading content for various social services from Google+/Facebook/Twitter.
  • WebCam and WebRTC integration.
  • Meta data extraction and RDF database integration to store allowed data with plexydesk SocialKit.
  • Social status updates. Google+/Facebook/twitter.
  • Coding Guidelines

Clone this wiki locally