use File::DesktopEntry; my $entry = File::DesktopEntry->new('firefox'); print "Using ".$entry->Name." to open http://perl.org\n"; $entry->run('http://perl.org');
For this module version 1.0 of the specification was used.
This module was written to support File::MimeInfo::Applications.
Please remember: case is significant for the names of Desktop Entry keys.
The global variable $File::DesktopEntry::LOCALE tells you what the default locale being used is. However, changing it will not change the default locale.
When a name is given (a string without '"/"', '"\"' or '"."') a lookup is done using File::BaseDir. If the file found in this lookup is not writable or if no file was found, the XDG_DATA_HOME path will be used when writing.
The child process fails when this is not a Desktop Entry of type Application or if the Exec key is missing or invalid.
If the desktop entry specifies that the program needs to be executed in a terminal the $TERMINAL environment variable is used. If this variable is not set "xterm -e" is used as default.
(On Windows this method returns a Win32::Process object.)
On Windows this method doesn't always work the way you want it to due to the "fork()" emulation on this platform. Try using "run()" or "system()" instead.
It supports the following fields:
%f single file %F multiple files %u single url %U multiple urls %i Icon field prefixed by --icon %c Name field, possibly translated %k location of this .desktop file %% literal '%'
If necessary this method tries to convert between paths and URLs but this is not perfect.
Fields that are deprecated, but (still) supported by this module:
%d single directory %D multiple directories
The fields %n, %N, %v and %m are deprecated and will cause a warning if $VERBOSE is used. Any other unknown fields will cause an error.
The fields %F, %U, %D and %i can only occur as separate words because they expand to multiple arguments.
Also see ``LIMITATIONS''.
When KEY does not contain a language code you get the translation in the current locale if available or a sensible default. The request a specific language you can add the language part. E.g. "$entry->get('Name[nl_NL]')" can return either the value of the 'Name[nl_NL]', the 'Name[nl]' or the 'Name' key in the Desktop Entry file. Exact language parsing order can be found in the spec. To force you get the untranslated key use either 'Name[C]' or 'Name[POSIX]'.
Unlike the "get()" call languages are not handled automatically for "set()". KEY should include the language part if you want to set a translation. E.g. "$entry->set("Name[nl_NL]" => "Tekst Verwerker")" will set a Dutch translation for the Name key. Using either ``Name[C]'' or ``Name[POSIX]'' will be equivalent with not giving a language argument.
When setting the Exec key without specifying a group it will be parsed and quoted correctly as required by the spec. You can use quoted arguments to include whitespace in a argument, escaping whitespace does not work. To circumvent this quoting explicitly give the group name 'Desktop Entry'.
If you gave a file, text buffer or name to the constructor this method will be called automatically.
The keys Name and Type are required. Type can be either "Application", "Link" or "Directory". For an application set the optional key "Exec". For a link set the "URL" key.
Please note that the specification is targeting Unix platforms only and will only have limited relevance on other platforms. Any platform-dependent behavior in this module should be considered an extension of the spec.
The values of the various Desktop Entry keys are not parsed (except for the Exec key). This means that booleans will be returned as the strings ``true'' and ``false'' and lists will still be ``;'' separated.
If the icon is given as name and not as path it should be resolved for the %i code in the Exec key. We need a separate module for the icon spec to deal with this.
According to the spec comments can contain any encoding. However since this module read files as utf8, invalid UTF-8 characters in a comment will cause an error.
There is no support for Legacy-Mixed Encoding. Everybody is using utf8 now ... right ?
Maintained by Michiel Beijen <michielb@cpan.org>
Copyright (c) 2005, 2007 Jaap G Karssenberg. All rights reserved.
File::BaseDir and File::MimeInfo::Applications
X11::FreeDesktop::DesktopEntry