Jump to content

Frameworks/Epics/New Runtime Organization: Difference between revisions

From KDE Community Wiki
Jriddell (talk | contribs)
make more complete
Jriddell (talk | contribs)
No edit summary
Line 86: Line 86:


{{FrameworkInProgress| kglobalaccel | ?? | mgraesslin|  whatever framework the global accel classes go into | }}
{{FrameworkInProgress| kglobalaccel | ?? | mgraesslin|  whatever framework the global accel classes go into | }}
{{FrameworkTodo| khelpcenter | ?? |??| needs a replacement app | }}


{{FrameworkTodo| kiconfinder | ?? |??|  kdesdk, "KDE cli" repo, or just drop; hard to say what its value really is | }}
{{FrameworkTodo| kiconfinder | ?? |??|  kdesdk, "KDE cli" repo, or just drop; hard to say what its value really is | }}
{{FrameworkTodo| kimgio | tier1/kguiaddons/src/plugins/imageformats |??|  webp plugin for qimageio. needs cmake modified so it actually gives a notice if it can't find libwebp. move into kdeframeworks with all the rest.| }}


{{FrameworkInProgress| kioclient | ?? |??| kf5 port done. the same code gets compiled into several different binaries, is this sensible? a user tool, so "KDE cli" repo | }}
{{FrameworkInProgress| kioclient | ?? |??| kf5 port done. the same code gets compiled into several different binaries, is this sensible? a user tool, so "KDE cli" repo | }}
Line 125: Line 129:
{{FrameworkTodo| kio recentdocuments | ?? | ?? |  is it used? | }}
{{FrameworkTodo| kio recentdocuments | ?? | ?? |  is it used? | }}


{{FrameworkTodo| kio remote | ?? | ?? | is it used? | }}
{{FrameworkTodo| kio remote | ?? | ?? |   | }}


{{FrameworkTodo| kio settings | ?? | ?? |  is it used? | }}
{{FrameworkTodo| kio settings | ?? | ?? |  is it used? | }}
Line 135: Line 139:
{{FrameworkInProgress| kio thumbnail | ?? | sebas |  | }}
{{FrameworkInProgress| kio thumbnail | ?? | sebas |  | }}


{{FrameworkInProgress| kio trash | ?? | various |   | }}
{{FrameworkInProgress| kio trash | ?? | various | KF5 port working  | }}
 
{{FrameworkTodo| khelpcenter | ?? |??| needs a replacement app | }}


{{FrameworkTodo| kdeui/about | ?? |??| replacement with QML, put into KDE App solution | }}
{{FrameworkTodo| kmimetypefinder | ?? | ?? | small command line app.  kde cli repo?  | }}


{{FrameworkTodo| keditfiletype | ?? |??| research replacement | }}
{{FrameworkTodo| knetattach | ?? | ?? | wizard used by remote kio  | }}


|}
|}

Revision as of 10:48, 15 November 2013

kde-runtime reorganization epic

Important Forewords

Runtime requirements of a given Framework will be included in the Framework repository, giving people a "single tarball/repo" solution to use. Even though the runtime and libraries will be housed together, attention should still be paid to ensuring that there is a clean and well engineered split and division between the runtime and libraries. Runtime components that are supposed to be background details should not bleed through the library APIs, libraries should not have build-time dependencies on runtime components, etc.

Runtime Components Planning

Definition of done:

  • A component must be migrated to its corresponding Frameworks repository OR be merged into another approriate non-frameworks module (e.g. kde-workspace)
  • All i18n and documentation (if any) must be migrated appropriately with it
  • Has been cleared by the module maintainer that it is migrated to for inclusion

A spreadsheet was prepared of each component in kde-runtime: https://docs.google.com/spreadsheet/ccc?authkey=CI_3zNMC&key=0Am2uzNh0KAtpdFVaRkMtMXZEcC00MEE0dzhrbWV2Nnc&hl=en_US&authkey=CI_3zNMC#gid=0


Status Component Destination Migrator Comments
DONE kactivitymanager kactivities Ivan Cukic
TODO kio_file KIO Framework ?? currently in kdelibs/kioslave
TODO kio_ftp KIO Framework ?? currently in kdelibs/kioslave
TODO kio_http KIO Framework ?? currently in kdelibs/kioslave
TODO kio_metainfo KIO Framework ?? currently in kdelibs/kioslave
TODO Attica KDE Plugin libattica ?? Dependency on kconfig, port to secret service
TODO Attica kcm ?? ??
TODO cmake ecm? ??
TODO desktoptheme libplasma2 Aaron Seigo
IN PROGRESS drkonqi ?? mgraesslin port to kf 5 working. bug reporting missing. belongs with a Solutions framework
IN PROGRESS kcmshell ?? mmartin, JRiddell port to kf 5 done. belongs with a Solutions framework.
TODO kcm_componentchooser kde-workspace ??
TODO kcm_dnssd kde-workspace ??
TODO kcm_emoticons Emoticons framework ?? alternatively, could go into kde-workspace
IN PROGRESS kcm_icons kde-workspace JRiddell port to KF 5 working
TODO kcm_kded kde-workspace ?? perhaps merge (in part / whole) into kinfocenter
TODO kcm_knotify KDE Notifications Frameworks ?? will probably require a rework; reference the KDE Notifications framework effort
IN PROGRESS kcm_locale kde-workspace Sebas K kdelibs should integrate with workspace being run in, klocale would be used to customize that from within a Plasma Workspace
TODO kcontrol/menus kinfocenter? ?? research what uses this category, move it there
TODO kcontrol/spellchecking sonnet ??
TODO kde4 script ?? ?? it's a barebones version of a script used in KApplication; should end up wherever KApplication does
TODO kdebugdialog kill it ?? kdebug no more
TODO kdeeject ?? ?? research what uses it; can it be removed altogether?
TODO kde-menu ?? ?? deprecate/remove
TODO kdesu ?? ?? also add kdesudo?
TODO kdontchangethehostname kded ?? deprecate the binary, move it into kded
TODO keditfiletype kded ?? library support; identify most appropriate framework; perhaps move into a "KDE cli" repository?
TODO kcm_keditfiletype kde-workspace ??
TODO kfile4 kde-kdeutils? ?? another candidate for a "KDE cli" repo?
IN PROGRESS kglobalaccel ?? mgraesslin whatever framework the global accel classes go into
TODO khelpcenter ?? ?? needs a replacement app
TODO kiconfinder ?? ?? kdesdk, "KDE cli" repo, or just drop; hard to say what its value really is
TODO kimgio tier1/kguiaddons/src/plugins/imageformats ?? webp plugin for qimageio. needs cmake modified so it actually gives a notice if it can't find libwebp. move into kdeframeworks with all the rest.
IN PROGRESS kioclient ?? ?? kf5 port done. the same code gets compiled into several different binaries, is this sensible? a user tool, so "KDE cli" repo
IN PROGRESS kioexec ?? ?? kf5 port done. KIO Framework
IN PROGRESS kio_about kde-baseapps Bhushan Shah kf5 port done. used by konqueror, move it there
TODO kio_applications kde-workspace ?? does this even get used?
TODO kio_archive ?? ?? in theory belongs with libkarchive topically, but has kio dependency
TODO kio_bookmarks kde-baseapps ?? used by konqueror, move it there
TODO kio_cgi kdesdk ??
TODO kio_desktop kde-baseapps ?? used by konq, dolpin, folderview; Plasma Workspaces is working on deprecating it
TODO kio docfilter ?? ?? is it used?
TODO kio filter ?? ?? is it used?
TODO kio finger ?? ?? is it used?
TODO kio fish ?? ?? is it used?
TODO kio floppy ?? ?? is it used?
TODO kio info ?? ?? is it used?
TODO kio man ?? ?? is it used?
TODO kioslaves/network ?? ??
TODO kio nfs ?? ?? is it used?
TODO kio recentdocuments ?? ?? is it used?
TODO kio remote ?? ??
TODO kio settings ?? ?? is it used?
TODO kio sftp ?? ??
TODO kio smb ?? ??
IN PROGRESS kio thumbnail ?? sebas
IN PROGRESS kio trash ?? various KF5 port working
TODO kmimetypefinder ?? ?? small command line app. kde cli repo?
TODO knetattach ?? ?? wizard used by remote kio