User:Dcecile: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
(unrelated development schedule: [[Schedules/KDE4/4.0_Release_Beta_Goals]]) | (unrelated development schedule: [[Schedules/KDE4/4.0_Release_Beta_Goals]]) | ||
every part of the KDE libraries needs tutorial documentation. this is a survey. (note: the lists of modules could be taken from a release doc or something.....) tutorials should answer: "why would I use KDE over just QT?" | |||
===KDE glue=== | |||
what defines a KDE app? | |||
* localization | |||
* consistent menus, accelerators, toolbars, chrome, icons | |||
* transparent file access | |||
* simple, cross-platform build system | |||
* shared technology | |||
* testing | |||
* documentation | |||
* open source | |||
* inviting for new users and developers | |||
===pillars of KDE=== | ===pillars of KDE=== | ||
| Line 23: | Line 35: | ||
* CMake: how to create your own app; and plug in other libraries | * CMake: how to create your own app; and plug in other libraries | ||
* KActions: setting up menus, toolbars, and accelerators | * KActions: setting up menus, toolbars, and accelerators | ||
* Internationalization and localiazation | |||
* QT Designer: designing a widget-based interface | * QT Designer: designing a widget-based interface | ||
* KConfigXT: persistent app config data. making the settings dialog. using the settings | * KConfigXT: persistent app config data. making the settings dialog. using the settings | ||
* KPixmapCache: | * KPixmapCache: | ||
* KIO: tranparent file access. how does it work with the QT libraries? | * KIO: tranparent file access. how does it work with the QT libraries? | ||
* ThreadWeaver: performs "jobs" that can be scheduled on non-UI threads | |||
===other=== | ===other=== | ||
Revision as of 22:06, 12 October 2007
(unrelated development schedule: Schedules/KDE4/4.0_Release_Beta_Goals)
every part of the KDE libraries needs tutorial documentation. this is a survey. (note: the lists of modules could be taken from a release doc or something.....) tutorials should answer: "why would I use KDE over just QT?"
KDE glue
what defines a KDE app?
- localization
- consistent menus, accelerators, toolbars, chrome, icons
- transparent file access
- simple, cross-platform build system
- shared technology
- testing
- documentation
- open source
- inviting for new users and developers
pillars of KDE
- Solid: getting info about hardware
- extra info
- API
- contact: Kevin Ottens
- status: tutorial
- Phonon: use audio and video in your app
- Strigi: find data. also how to let strigi use your filetype
- Plasma: creating a new desktop paradigm
- Nepomuk: relation to Strigi? file metainfo, relationships
- Decibel: connecting to other people
- Akonadi: communcations storage backend
- Oxygen: devs need to know how to access all of the icon and sound that this team has put together. (and maybe know how to give feedbacks or make commissions.) there should be doc about doing for yourself what the Oxygen team does
- Sonnet
everyday tech
- Hello World: this is the simplest KDE app; proves your dev environment is working and gives you confidence to continue coding!
- There is a dialog
- CMake: how to create your own app; and plug in other libraries
- KActions: setting up menus, toolbars, and accelerators
- Internationalization and localiazation
- QT Designer: designing a widget-based interface
- KConfigXT: persistent app config data. making the settings dialog. using the settings
- KPixmapCache:
- KIO: tranparent file access. how does it work with the QT libraries?
- ThreadWeaver: performs "jobs" that can be scheduled on non-UI threads
other
- job progress
- D-Bus
PIM stuff
- Khalkhi: contacts framework
- KitchenSync
- syndication etc.