You are here: welcome » wiki » iconmenuinfo

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
wiki:iconmenuinfo [2011/04/18 07:25] – external edit 127.0.0.1wiki:iconmenuinfo [2015/08/18 22:44] (current) – [Menu Entries and Icons] opera10 gordon64
Line 1: Line 1:
- 
- 
 ====== Menu entries, icons, setup scripts, .info and .dep files ====== ====== Menu entries, icons, setup scripts, .info and .dep files ======
  
Line 6: Line 4:
  
  
-===== Menu entries ===== +===== Menu Entries and Icons===== 
-These are added to the submenu "Applications", which is empty by default. Entries created automatically by the system at the time extension loaded, based on freedesktop.org compliant menu definitions (.desktop files) in +Menu Entries and Icons are provided by a .desktop file stored at  
 +^/usr/local/share/applications^ 
 +The .desktop file must have the same base name as the application package. (e.g. the desktop file for homebank.tcz must be named homebank.desktop)
  
-/usr/local/share/applications +A deskop file must begin with 
 +^[Desktop Entry]^ 
 +For the full specifications see [[http://standards.freedesktop.org/desktop-entry-spec/latest/]] 
 + ===Menu Entries=== 
 +These are added to the submenu "Applications", which is empty by default. Entries are created automatically by the system at the time the extension is loaded. In order to have a menu entry the .desktop file needs, at the least, this line: 
 +^Name=^  
 +followed, on the same line, by the name you want to appear in the menu. 
 +Note: The default wbar setup provided in TinyCore 4.1 will not keep any spaces in the the value of "Name=".  (e.g. "Name= Battle for Wesnoth" will have the label "BattleforWesnoth".) Of course, this only matters your .desktop file also has an icon referenced as instructed below.
  
-directory provided by the extension. +You'll also need this line: 
- +^Exec=^ 
-===== Icons ===== +followed, on the same line, by the executable to be run when the item is clicked.
-Icons are shown in the bar, in the bottom of the screen. They are added to the right side. +
- +
-The icon should be a 48x48 PNG, and defined in the .desktop file by+
  
 +===Icons===
 +Icons are shown in the wbar, which can be positioned on any edge of the screen (bottom by default). In order to have an icon you will need the things mentioned above as well as 
 ^X-FullPathIcon=^ ^X-FullPathIcon=^
 +followed, on the same line,  by the absolute path to the icon you want to be displayed.
  
-field. Proper directory to store icon is+Please note, that X-FullPathIcon= field is not part of the .desktop file provided by applications; it is TC specific and must be added by the extension creator.
  
 +The icon should be a 48x48 PNG, and  the preferred location for storing icons is  
 ^/usr/local/share/pixmaps/^ ^/usr/local/share/pixmaps/^
- 
 For example icon for Opera10 defined as For example icon for Opera10 defined as
- 
 ^/usr/local/share/pixmaps/opera10.png^ ^/usr/local/share/pixmaps/opera10.png^
  
-Please note, that X-FullPathIcon= field is not part of the .desktop file provided by applications; it is TC specific and must be added by extension creator.+so for opera, example line becomes  
 + 
 +^X-FullPathIcon=/usr/local/share/pixmaps/opera10.png^
  
  
Line 34: Line 42:
 When an extension is loaded, an executable file of the same name as the extension in **/usr/local/tce.installed/** will be called, if it exists. This is optional. When an extension is loaded, an executable file of the same name as the extension in **/usr/local/tce.installed/** will be called, if it exists. This is optional.
  
-For details see [[http://wiki.tinycorelinux.com/tiki-index.php?page=Creating+Extensions#Adding_Custom_Startup_Scripts|Adding Custom Startup Script]] section in the Wiki.+For details see [[http://wiki.tinycorelinux.net/wiki:creating_extensions?s[]=startup&s[]=script#adding_custom_startup_scripts|Adding Custom Startup Scripts]] section in the Wiki.
  
  
 ===== .info files ===== ===== .info files =====
-They are named like the extension, with .info added, for example kmaps.tce.info. Use all parts, even if your extension does not match; in that case, put n/a for example to the unneeded field. Please do not forget a proper description of your software! An example .info file: +They are named like the extension, with .info added, for example kmaps.tce.info. Use all parts, even if your extension does not match; in that case, put n/a for example to the unneeded field. Please do not forget a proper description of your software!
- +
-http://tinycorelinux.com/files/tce/ace-of-penguins.tczl.info+
  
 +[[http://tinycorelinux.net/5.x/x86/tcz/ace-of-penguins.tcz.info|View an example .info file]]
  
 +At Tiny Core version 5, .info files should include 12 sections:
 +  -Title
 +  -Description
 +  -Version
 +  -Author
 +  -Original-site
 +  -Copying-policy
 +  -Size
 +  -Extension-by
 +  -Tags
 +  -Comments
 +  -Change-log
 +  -Current
 ===== .dep files: dependency handling ===== ===== .dep files: dependency handling =====
-Tinycore handles dependencies only when using tce-load or the graphical appbrowser to get extensions from the repository, both when installing and only downloading. The .dep files have no effect for manual downloads, or local extensions. It's named as the extension + .dep, for example extension1.tcz.dep.+Tiny Core handles dependencies only when using ''tce-load'' or the graphical appbrowser ''apps'' to either (1) install local extensions or (2) download extensions from the repository. The .dep files have no effect for manual downloads (using ''wget'' or any other tool) or local extensions. 
 + 
 +The dependency file is named by appending .dep to the extension file name. For example extension1.tcz.dep is the dependency list for exension1.tcz.
  
-For dependencies, there are recursive resolutions (implemented as of version 2.10). Previously, the extension would contain the full names of all extensions it depends on, and all they depend on. This previous method is still compatible, but the recursive approach is the current standard.+Dependency lists are recursively resolved as of Tiny Core 2.10. It is only necessary to list first-level dependencies. Before 2.10, the dependency list would include all dependents, //their// dependents, etc. This method is still compatible, but the recursive approach is now standard.
  
-The format is one extension per line with **no empty lines**. For example, an extension.tcz.dep might have:+The list file format is one extension per line with //no empty lines//. For example, an extension.tcz.dep might have:
  
-^a.tcz +<code>a.tcz 
-b.tcz^ +b.tcz</code> 
-where a.tcz.dep might contain +where a.tcz.dep might contain only 
-^c.tcz^+<code>c.tcz</code>
  
 +Please see also [[wiki:creating_extensions]]
Print/export
QR Code
QR Code wiki:iconmenuinfo (generated for current page)