Jump to content

User:Diggy/Calligra Sprint 2011.2 presentation

From KDE Community Wiki
< User:Diggy
Revision as of 00:44, 8 November 2011 by Diggy (talk | contribs) (Calligra Sprint 2011.2 presentation)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

My Plans

  • Need for Interoperability between Calligra apps
  • UI perspective from a non developer
  • Promoting Calligra
  • Plug-ins K.I.S.S. proposal
  • Calligra and DTP (ideas)
  • Kexi Documentation / Making documentation roadmaps

Outline

Where does Calligra stand as a suite?

Calligra is currently more a pack of applications sharing a common vision and reusing code rather than a tightly integrated application suite.

  • Average user expectations from an office suite
    • Stability / Data Integrity
    • Reusing Docs made with other applications / Exporting to other formats
    • UI Homogenity
    • Interoperability between apps of the suite

Promoting Calligra

As Calligra is a new suite (name-wise at least) we should put an extra effort to "sell" this as efficiently as we can.

  • Finalize Calligra Logo / Guidelines
  • Prepare homogenous splash screens for all apps
  • Advertise using any means at hand:
    • Add more content on calligra-suite.org
    • On KDE domain websites
    • Social networking services
  • Create "made with Calligra" watermark to be used on documents

Modular, modular, modular

Most office suites in order to achieve better sales volume or user's acceptance, quickly become bloated with features an average user almost never uses. How to deal with that efficiently without sacrificing features? PLUGINS! Pros making Calligra apps as modular as possible:

  • Plug ins can be added after installation when needed
  • Most likely some of them will work between versions
  • Reduced overhead. No need to reserve several MBs of memory for someone who uses Tables to keep a shopping list :)
  • Porting to other architectures is simplified as the main app is ported first, providing basic functions, plugins later.
  • Better code organization. No need to have preprocessor instructions in the main files just to seperate build cases. eg No one is ever going to do What-If analysis using Tables on a mobile device.

Ideas for new Calligra apps / modules

  • Authoring / Completing forms (as suggested by jstaniek) using Words and Kexi Form editor
  • DeskTop Publishing. Currently we can't fit Calligra in a DTP workflow because we're missing on that one.

Kexi Documentation / Making documentation roadmaps

Retrieved from "https://community.kde.org/index.php?title=User:Diggy/Calligra_Sprint_2011.2_presentation&oldid=15850"