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
cr_read(3)						     Library Functions Manual							cr_read(3)

NAME
cr_read - read from crash dump SYNOPSIS
DESCRIPTION
The function attempts to read the memory area defined by mem_page and num_pages into the buffer pointed to by buf from the crash dump opened using crash_cb. The starts at the position in the crash dump associated with the physical memory offset given by mem_page. If the physical memory page mem_page does not exist in the crash dump, sets *num_pages to 0 and returns 0. No data transfer will occur past a page of memory that does not exist in the crash dump. If the starting position, mem_page, plus the read length, *num_pages, goes past an area of memory that does not exist in the crash dump, sets *num_pages to the number of consecutive pages (starting at mem_page) actually read. RETURN VALUE
Returns zero for success. Other possible return values are described in libcrash(5). EXAMPLES
Assuming a process opened a crash dump, the following call to cr_read(3) reads the first pages from the crash dump into the buffer pointed to by mybuf: WARNINGS
may return fewer pages than requested due to implementation details. Always check the number of pages returned. If they are fewer than requested, issue a new request starting at the first page not returned. Only if that new request reads zero pages (or returns an error) can you be sure that the page was not dumped. AUTHOR
was developed by HP. SEE ALSO
cr_open(3), libcrash(5). cr_read(3)