< Projects Revision as of 17:41, 2 March 2008 (view source)Aseigo (talk | contribs) (→Packaging Conventions)← Older edit Revision as of 20:08, 20 March 2008 (view source) Aseigo (talk | contribs) (→Packaging Conventions)Newer edit → Line 38: Line 38: == Packaging Conventions == == Packaging Conventions == + +=== Unique Naming === + +Since your plugins and packages will co-exist with everyone else's, it is a good idea to use a naming scheme that eliminates possibility of accidental name collisions. + +In the examples below where it referse to [name], consider including an element unique to your project or organization in it. For instance, if your packages accompany an application, consider including the name of the application. Using an organizational or domain name are also possibilities. + +For example, if your plasmoid was called "SuperWidget", the [name] might be: + +* myapp_superwidget if it comes with the MyApp program +* myorg_superwidget if it is associated with the MyOrg project/company/entity +* net_myorg_foo_superwidget if the domain name associated with the plasmoid's origin is foo.myorg.net === .desktop File Naming === === .desktop File Naming === Revision as of 20:08, 20 March 2008 Contents 1 What These Guidelines (Will) Cover 2 Category Names 3 Theming 4 Animation 5 Configuration 6 Status Notifications 7 Packaging Conventions 7.1 Unique Naming 7.2 .desktop File Naming What These Guidelines (Will) Cover This document is a place to collect all the "do"s, "don't"s and "how to"s for interface elements in Plasma, particularly applets and plasmoids. Category Names The following are acceptable known entries for plasmoids and applets. If your applet does not fall within one of the following categories, leave the category field empty (it will be automatically categories under "Miscellaneous" for the time being) and contact the Plasma development team to have a suitable category added to the list (at which point you may then use that category). Application Launchers application starters and file openers. Astronomy anything to do with the night sky or other celestial bodies. Date and Time clocks, calendars, scheduling, etc Environment & Weather add-ons that display information regarding the weather or other environmentally related data Examples samples that are not meant for production systems File System anything that operates on files or the file system as it's primary purpose, such as file watchers or directory listings. Simply using a file as storage does not qualify the add-on for this category. Graphics for add-ons where displaying images, photos or graphical eye candy is the primary purpose Language add-ons whose primary purpose is language related, such as dictionaries and translators. Mapping geography and geographic data add-ons Online Services add-ons that provide an interface to online services such as social networking or blogging sites. If there is another more appropriate category for the add-on given the topic (e.g. mapping if the applet's purpose is to show maps), even if the data is retrieved from the Internet prefer that other category over this one. System Information display and interaction with information about the computer such as network activity, hardware health, memory usage, etc Windows and Tasks managers for application windows and/or tasks, such as taskbars Questions from a future plasmoid programmer. I find those categories ambiguous. For instance: Where would go "Disc Usage" applet go? File System? It's listing mount-points and how much free space is left on each... Or "System Information"? Where goes an applet that display the cover art and music information of the currently playing track in Amarok? Or any media-center related plasmoid. I propose to add a category "Multimedia". Where would go a "Live Road Traffic" plasmoid: "Environment & Weather", or "mapping"? Environment is quite vague Shouldn't "Date and Time" be renamed "Date & Time", and "Windows and Tasks" "Windows & Tasks", to keep consistency? Theming Animation Configuration Status Notifications Packaging Conventions Unique Naming Since your plugins and packages will co-exist with everyone else's, it is a good idea to use a naming scheme that eliminates possibility of accidental name collisions. In the examples below where it referse to [name], consider including an element unique to your project or organization in it. For instance, if your packages accompany an application, consider including the name of the application. Using an organizational or domain name are also possibilities. For example, if your plasmoid was called "SuperWidget", the [name] might be: myapp_superwidget if it comes with the MyApp program myorg_superwidget if it is associated with the MyOrg project/company/entity net_myorg_foo_superwidget if the domain name associated with the plasmoid's origin is foo.myorg.net .desktop File Naming Plasma uses a "general to specific" naming system for .desktop files. Following this practice makes it easy to find entries in the file system and keeps things nicely ordered. In the list below, [name] would most commonly be the plugin name as found in the file. Files autogenerated by ScriptEngines may include additional namespacing information in the file name. Animators: plasma-animator-[name].desktop Applets: plasma-applet-[name].desktop. Does not matter what language it is implemented in, it should always have the plasma-applet prefix. Containments: plasma-containment-[name].desktop DataEngines: plasma-dataengine-[name].desktop Runners: plasma-runner-[name].desktop ScriptEngines: plasma-scriptengine-[type]-[name].desktop where type may be one or more of Applet, DataEngine and/or Runner. Retrieved from "https://techbase.kde.org/index.php?title=Projects/Plasma/PIG&oldid=22356" Content is available under Creative Commons License SA 4.0 unless otherwise noted.