OOo Basic crash course: Creating a simple application launcher


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News OOo Basic crash course: Creating a simple application launcher
# 1  
Old 05-28-2008
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...
Login or Register to Ask a Question

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... (9 Replies)
Discussion started by: anaigini45
9 Replies

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... (16 Replies)
Discussion started by: Huitzilopochtli
16 Replies

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:... (0 Replies)
Discussion started by: anuachin
0 Replies

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... (0 Replies)
Discussion started by: clistyles
0 Replies

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... (3 Replies)
Discussion started by: ASGR
3 Replies

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... (1 Reply)
Discussion started by: Sedighzadeh
1 Replies
Login or Register to Ask a Question
crashdc(8)						      System Manager's Manual							crashdc(8)

NAME
crashdc - Diagnostic data collection for a running or crashed system SYNOPSIS
/usr/bin/crashdc [system-kernel] [core-image] DESCRIPTION
The crashdc utility examines the core image of the operating system to extract critical diagnostic data. This utility is a shell script that invokes several tools and commands that extract selected parameters of a running or a crashed system (for example, system configura- tion, running processes, and panic messages). The arguments to the crashdc utility are the system kernel and the core image. The default values are /vmunix and /dev/mem, respectively. If you specify no arguments, the crashdc utility examines the running system. The system usually invokes the crashdc utility during system startup. If the most recent core dump has been saved by the savecore command, both the core image and the system kernel (respectively vmcore.n and vmunix.n, where the variable n is the crash number) are saved in the crash directory (by default, /var/adm/crash). Also, the crashdc utility saves the output as the file crash-data.n (where the variable n is the crash number) in the crash directory. The crashdc utility is invoked only if crash-data.n output in the crash directory does not exist or is not from the most recent crash. FILES
Default core image Default system image Output from crashdc SEE ALSO
Commands: dbx(1), kdbx(8), savecore(8) crashdc(8)