OOo Basic crash course: Creating a simple application launcher

Tags

Special Forums News, Links, Events and Announcements UNIX and Linux RSS News OOo Basic crash course: Creating a simple application launcher

05-28-2008

Registered User

26,240, 27

Join Date: Sep 2000

Last Activity: 1 August 2008, 3:09 PM EDT

Posts: 26,240

Thanks Given: 0

Thanked 27 Times in 26 Posts

OOo Basic crash course: Creating a simple application launcher

Wed, 28 May 2008 15:00:00 GMT
In previous installments of the crash course, you've learned how to build a simple basket tool, a task manager, and even a word game. This time, let's take a look at how you can use the skills you picked up from those exercises to create a simple application launcher, which will allow you to start virtually any application without leaving the convenience of OpenOffice.org. While working on this project, you'll learn how to create and use functions, handle errors, and how to populate list boxes using records from a database table.

Source...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. HP-UX

Sudden application crash in servers

Hi, This weekend there was a sudden application crash in the server. I did not know where to start to investigate the problem, so I first looked into the /var/adm/syslog/syslog.log, and this was what I found : Dec 17 00:38:02 L28bi01 sshd: error: accept: No buffer space available Dec 17...

2. Shell Programming and Scripting

Cannot get terminal application to launch with a graphical launcher when successful in terminal

I have been having an extremely annoying problem. For the record, I am relatively new at this. I've only been working with unix-based OS's for roughly two years, mostly Xubuntu and some Kali. I am pretty familiar with the BASH language, as that's the default shell for debian. Now, I've made this...

3. Red Hat

XCB crash while Video Rendering in multithreded application

I encounter the following crash on RHEL 7.0 when I run a multithreaded video rendering application using GLFW and OpenGL. OpenGL version is 2.1 and MESA version is 9.3.0 Following is the back trace of the multi-threaded program I am working on:...

4. UNIX for Dummies Questions & Answers

Need help creating a launcher for connecting 2 computers

CentOS 5.3 I have been tasked with a project of simplifying our media process for new staff and I need some help with ideas on how to achieve this. I am not a Linux expert and have only been using it for 12 months so appreciate the help. Stage 1 Currently we are couriered once a month a...

5. OS X (Apple)

[launchd] Creating a basic firewall

Hi, I'm trying to use launchd to detect whether certain ports are opened and if they are then to take some appropriate action, e.g. close the port or, worst case scenario, down the whole net connection. Apparently, force closing a port is not possible without killing the offending binary so...

6. Programming

socket system call can not succedd right after application crash.

hello all, I have developed a server application in C for ulinux kernel 2.6.It works very fine; creating a socket, binding it to a port, listening for incoming sockets and accepting them ,all finish without any error. But there is a problem regarding application crash.After an intentionally...

LEARN ABOUT HPUX

cr_open

cr_open(3)						     Library Functions Manual							cr_open(3)

NAME

       cr_open() - open crash dump for reading

SYNOPSIS

DESCRIPTION

       The library call opens a crash dump and passes back a crash dump descriptor.

       The path argument points to a path name naming a crash dump directory or file, and must not exceed bytes in length.

       The CRASH * to which crash_cb points is set to a crash dump descriptor, which can then be passed to the other functions to access the crash
       dump.

       flags is a bitmask of zero or more of the following flag values, which affect the operation of future calls to libcrash routines  for  this
       crash dump, except for cr_verify(3), which has its own flags parameter.

       The library will not attempt to verify checksums of files in the crash
			     dump if this flag is set.

       The library will write messages to stderr during time-consuming operations
			     (decompressions and checksums) if this flag is set.

RETURN VALUE

       Returns zero for success.  Other possible return values are described in libcrash(5).

EXAMPLES

       The following call to opens crash dump contained in the directory and returns the crash dump descriptor For an example of reading the crash
       dump see the cr_read(3) manual entry.

AUTHOR

       was developed by HP.

SEE ALSO

       cr_close(3), cr_perror(3), libcrash(5).

																	cr_open(3)

UNIX and Linux RSS News