Sponsored Content
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Sun Presentation Minimizer serves purpose, but needs work Post 302162867 by Linux Bot on Wednesday 30th of January 2008 11:40:05 AM
Old 01-30-2008
Sun Presentation Minimizer serves purpose, but needs work

Wed, 30 Jan 2008 16:00:00 GMT
Sun Presentation Minimizer (SPM) represents free software's answer to PPTminimizer. Designed for OpenOffice.org 2.3 or StarOffice 8 Impress and released under the Lesser GNU General Public License, SPM is an extension that creates a wizard that guides you through reducing the size of your presentation, making it easier to transport and, on some systems, quicker to run. Those who present large slide shows -- especially graphics-heavy ones -- will find it a well-designed and effective addition, although several features require more work.


Source...
 

7 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

Using a Sun Ultra 5 at work

I wouldn't call myself exactly new to Unix. I've played with Linux before so I can get around alright. I just have never really learned the basics, like setting a user's path. How do I do that on my Sun station? Obvioulsly, I've got several different bins, but I can only use the commands in... (1 Reply)
Discussion started by: skinnell2
1 Replies

2. Solaris

Problem getting SUN trunking to work

Hi all, I am trying to setup SUN trunking per the instructions in the SUN Trunking 1.3 Installation and User's Guide. Dated June - 2007. I am setting it up in a test environment. Pretty simple test bed. 2 Sun V490s connected to a Catalyst 6500 via fiber NICs. 2 NIC's in each 490. Each is a... (9 Replies)
Discussion started by: bruhnf
9 Replies

3. Shell Programming and Scripting

common UNIX script which is to work in HP and SUN environment

I have two different UNIX scripts for updating Co-ordinate points which are working fine seperately in HP and SUN environments. But I am trying to write a common UNIX script which is to work in HP and SUN environment. The following are the scripts i am using SUN: #!/bin/ksh info () {... (6 Replies)
Discussion started by: ramkumar2yk
6 Replies

4. Solaris

Config reader module in Sun MC Agent not work in E2900

Hi men, Have you ever meet this error ? I install full Sun MC 4.0 packages (+ Add ons) exception of Sun Midrange Platform Administration because i don't know how to configure it Then all other servers are ok, only E2900 servers have Config reader module error: Data Acquisition error I... (12 Replies)
Discussion started by: tien86
12 Replies

5. Solaris

ALOM wont work when KVM connected to Sun Fire V440 server

Hi, I was asked to connect a KVM screen to a Sun Fire V440 last night so I connected it up but no joy and nothing on the KVM screen. I was told that a reboot may fix the problem so connected to the ALOM and rebooted. On the plus side, the KVM screen now works but I lost the ALOM connection. ... (0 Replies)
Discussion started by: jimmy54321
0 Replies

6. Shell Programming and Scripting

Logs Presentation

Hello All, I am trying to capture system logs for specific tools run by users. So my script create logs from 10 different server.So is there any script & tool from that i can read or present them easily ?. Regards Ankit (1 Reply)
Discussion started by: ajaincv
1 Replies

7. Red Hat

LUN Presentation

Hi, I have presented a LUN from my EVA 4400 to a RHEL server. The server sees 4 paths to the LUN which I can see from fdisk. If I want to add this LUN to my OS i.e. # fdisk /dev/sd??? ....which actual device do I run fdisk against? I am running multipath so is there... (12 Replies)
Discussion started by: Duffs22
12 Replies
OODoc::Manifest(3pm)					User Contributed Perl Documentation				      OODoc::Manifest(3pm)

NAME
OpenOffice::OODoc::Manifest - Access to document file descriptor DESCRIPTION
The OpenOffice::OODoc::manifest class is a specialist derivative of OpenOffice::OODoc::XPath allowing access to the content descriptor of an OpenDocument or OpenOffice.org file. For ordinary content processing applications, it's not absolutely necessary to control the manifest. Member imports or deletions (ex: createImageElement() in OpenOffice::OODoc::Image, raw_delete() in OpenOffice::OODoc::File) may make the real content inconsistent with the manifest. Up to now, the OpenOffice.org desktop suite don't worry about that. However, OpenOffice::OODoc::Manifest provides a few number of easy to use methods to get or set any entry in the manifest. In addition, it allows the users (at their own risks) to create or update any kind of special entry or mime type, without control. There is no automatic consistency check between the manifest and the real content (but this check and others could be easily developed with the combination of this module and the other ones). The manifest (i.e. the "META-INF/manifest.xml" part of an ODF package) is a special member that describes the MIME types and the full internal paths of the other members. Methods Constructor : OpenOffice::OODoc::Manifest->new(<parameters>) Short Form: odfManifest(<parameters>) See OpenOffice::OODoc::XPath->new The XML member loaded by default is 'META-INF/manifest.xml'. Example: $my manifest = OpenOffice::OODoc::Manifest>new ( file => 'document.odt' ); returns a new object which represents the member list of an ODF-compliant "document.odt" file. getEntry($entry) Returns the element (if any) corresponding to the given member. Example: my $element = $manifest->getEntry("content.xml"); Returns the element describing the "content.xml" member of the file, if this element is defined. getMainType() Returns the main MIME type of the document. For example, this type is "application/vnd.oasis.opendocument.text" for an OpenDocument text file or "application/vnd.oasis.opendocument.presentation" for an OpenDocument presentation, or "application/vnd.sun.xml.writer" for an OpenOffice.org 1.0 text file, etc. See the Appendix C in the OASIS OpenDocument 1.0 specification for a complete list of OpenDocument-compliant MIME types. getType($entry) Returns the media (mime) type of the given member. removeEntry($entry) Deletes the named entry. setEntry($entry, $type) Sets the mime type of an entry element. If the element was not previously existing, it's created. Returns the new element in case of success, undef otherwise. Example: my $element = $manifest->setEntry ("content.xml", "text/xml"); This instruction first creates (if needed) an entry for the member "content.xml" and sets its media type to "text/xml". setMainEntry($type) Sets the main MIME type of the document. Risky; not for ordinary use. But nobody prevents you from giving a presentation or spreadsheet MIME type to a Writer document ! Properties As for OpenOffice::OODoc::XPath Exported functions None NOTES
See OpenOffice::OODoc::Notes(3) for the footnote citations ([n]) included in this page. AUTHOR
/COPYRIGHT Developer/Maintainer: Jean-Marie Gouarne <http://jean.marie.gouarne.online.fr> Contact: jmgdoc@cpan.org Copyright 2004-2008 by Genicorp, S.A. <http://www.genicorp.com> Initial English version of the reference manual by Graeme A. Hunter (graeme.hunter@zen.co.uk). License: GNU Lesser General Public License v2.1 perl v5.14.2 2008-09-16 OODoc::Manifest(3pm)
All times are GMT -4. The time now is 10:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy