Free agenda software for linux

Agendaroids is an "Asteroids" clone for the Agenda VR3 PDA.
Agendaroids is a game where you maneuver a space ship in a field of asteroids, and shoot at them to break them into smaller pieces.
It uses vector-based graphics with fixed-point trigonometry, so it runs well even on the FPU-less VR3, but it also runs on any other Xlib-based system.
Main features:
- Smooth vector graphics
- Dark-on-light display; better for greyscale LCD screens
- Light-on-dark display for monitors and color LCDs
- Looks really cool with the backlight on!
- Rotating asteroids
- Fast, table-based trigonometric functions
- Agenda-friendly key controls (as well as PC keyboard alternative)
- Sound effects (via piezo buzzer)
- Pause and resume (even if you quit)
- ... and more!

Ovidentia is a professional collaborative/groupware portal generator featuring an administrable management tool with a workflow for the approval to publish articles, comments, files, or vacation requests.
It also features an agenda (shareable), an integrated directory, charts, an LDAP directory interface, add-ons support, a mail interface, and a WYSIWYG HTML editor to publish articles, news, posts, or write email. The project supports LDAP, Ovidentia, and Active Directory authentication.
Enhancements:
- Bugs correction
- Security corrective measures
- Vacation requests management evolutions

GoWeather graphically displays current conditions and 5-day forecast for a location.
It displays an attractive representation the current weather conditions for a particular location, along with upcoming weather forecasts.
The source of the data are small, text-based reports in a standard format (METAR and Zone Forecast (ZFP)) made available from an unchanging, reliable source (the National Weather Service (NWS)).
GoWeather is FLTK-based, has a small form-factor, and the data files are very small and can be accessed offline.
This means GoWeather is suitable for Linux handhelds (like the Agenda VR3 PDA).
Enhancements:
- Initial upload to SourceForge CVS CHANGES.txt created
- Added some "uploading to Agenda" info. to "INSTALL.txt"
- Updated GoWeather URL in documents and files
- References to "Go Weather" changed to "GoWeather"
- "About" dialog window created

AspectES is an implementation of Aspect-Oriented Programming in JavaScript 1.5, as standardized by EcmaScript Specification 262.
AspectES project contains core classes that enable software engineers to gracefully develop JavaScript applications that have clear, well-documented designs that incorporate Aspect Oriented Programming.
This project only uses standardized Web technologies: JavaScript 1.5, with no proprietary extensions. The framework is documented with JavaScriptdoc.
Mission:
Produce a superior implementation of Aspect-Oriented Programming in JavaScript v1.5, as standardized by EcmaScript Specification 262.
Scope: A package framework that contains core classes that enable software engineers to gracefully develop JavaScript applications that have clear, well-documented designs incorporating Aspect Oriented Programming.
Agenda:
Current:
- This framework powers the drag-and-drop capability in the (open-source) Gigapan Explorer Application, delivered to the United States NASA in late 2005.
- This project only uses standardized web technologies: JavaScript 1.5, with no proprietary extensions.
- Enjoy complete JavaScriptdoc as you develop this codebase.
- See the Coding Standard.
- See the tips on Debugging JavaScript.
Immediate Future:
- Develop a test suite that completely exercises the existing functionality.
- Log and fix bugs on said functionality.
- Identify additional desired functionality.
- Build a pluggable module for generating JavaScriptdoc from AspectES aspects and their associated yarn.
Enhancements:
- This version is now contained in its own tigris.org project, separate from the Gigapan Explorer application for which it was originally developed.

perlhack is a Perl module that will show you how to hack at the Perl internals.

This document attempts to explain how Perl development takes place, and ends with some suggestions for people wanting to become bona fide porters.
The perl5-porters mailing list is where the Perl standard distribution is maintained and developed. The list can get anywhere from 10 to 150 messages a day, depending on the heatedness of the debate. Most days there are two or three patches, extensions, features, or bugs being discussed at a time.

A searchable archive of the list is at either:

http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/

or

http://archive.develooper.com/perl5-porters@perl.org/

List subscribers (the porters themselves) come in several flavours. Some are quiet curious lurkers, who rarely pitch in and instead watch the ongoing development to ensure theyre forewarned of new changes or features in Perl. Some are representatives of vendors, who are there to make sure that Perl continues to compile and work on their platforms. Some patch any reported bug that they know how to fix, some are actively patching their pet area (threads, Win32, the regexp engine), while others seem to do nothing but complain. In other words, its your usual mix of technical people.

Over this group of porters presides Larry Wall. He has the final word in what does and does not change in the Perl language. Various releases of Perl are shepherded by a "pumpking", a porter responsible for gathering patches, deciding on a patch-by-patch, feature-by-feature basis what will and will not go into the release. For instance, Gurusamy Sarathy was the pumpking for the 5.6 release of Perl, and Jarkko Hietaniemi was the pumpking for the 5.8 release, and Rafael Garcia-Suarez holds the pumpking crown for the 5.10 release.
In addition, various people are pumpkings for different things. For instance, Andy Dougherty and Jarkko Hietaniemi did a grand job as the Configure pumpkin up till the 5.8 release. For the 5.10 release H.Merijn Brand took over.

Larry sees Perl development along the lines of the US government: theres the Legislature (the porters), the Executive branch (the pumpkings), and the Supreme Court (Larry). The legislature can discuss and submit patches to the executive branch all they like, but the executive branch is free to veto them. Rarely, the Supreme Court will side with the executive branch over the legislature, or the legislature over the executive branch. Mostly, however, the legislature and the executive branch are supposed to get along and work out their differences without impeachment or court cases.

You might sometimes see reference to Rule 1 and Rule 2. Larrys power as Supreme Court is expressed in The Rules:

Larry is always by definition right about how Perl should behave. This means he has final veto power on the core functionality.

Larry is allowed to change his mind about any matter at a later date, regardless of whether he previously invoked Rule 1.

Got that? Larry is always right, even when he was wrong. Its rare to see either Rule exercised, but they are often alluded to.

New features and extensions to the language are contentious, because the criteria used by the pumpkings, Larry, and other porters to decide which features should be implemented and incorporated are not codified in a few small design goals as with some other languages. Instead, the heuristics are flexible and often difficult to fathom. Here is one persons list, roughly in decreasing order of importance, of heuristics that new features have to be weighed against:

Does concept match the general goals of Perl?

These havent been written anywhere in stone, but one approximation is:

1. Keep it fast, simple, and useful.
2. Keep features/concepts as orthogonal as possible.
3. No arbitrary limits (platforms, data sizes, cultures).
4. Keep it open and exciting to use/patch/advocate Perl everywhere.
5. Either assimilate new technologies, or build bridges to them.

Where is the implementation?

All the talk in the world is useless without an implementation. In almost every case, the person or people who argue for a new feature will be expected to be the ones who implement it. Porters capable of coding new features have their own agendas, and are not available to implement your (possibly good) idea.

Backwards compatibility

Its a cardinal sin to break existing Perl programs. New warnings are contentious--some say that a program that emits warnings is not broken, while others say it is. Adding keywords has the potential to break programs, changing the meaning of existing token sequences or functions might break programs.

Could it be a module instead?

Perl 5 has extension mechanisms, modules and XS, specifically to avoid the need to keep changing the Perl interpreter. You can write modules that export functions, you can give those functions prototypes so they can be called like built-in functions, you can even write XS code to mess with the runtime data structures of the Perl interpreter if you want to implement really complicated things. If it can be done in a module instead of in the core, its highly unlikely to be added.

Is the feature generic enough?

Is this something that only the submitter wants added to the language, or would it be broadly useful? Sometimes, instead of adding a feature with a tight focus, the porters might decide to wait until someone implements the more generalized feature. For instance, instead of implementing a "delayed evaluation" feature, the porters are waiting for a macro system that would permit delayed evaluation and much more.

Does it potentially introduce new bugs?

Radical rewrites of large chunks of the Perl interpreter have the potential to introduce new bugs. The smaller and more localized the change, the better.

Does it preclude other desirable features?

A patch is likely to be rejected if it closes off future avenues of development. For instance, a patch that placed a true and final interpretation on prototypes is likely to be rejected because there are still options for the future of prototypes that havent been addressed.

Is the implementation robust?

Good patches (tight code, complete, correct) stand more chance of going in. Sloppy or incorrect patches might be placed on the back burner until the pumpking has time to fix, or might be discarded altogether without further notice.

Is the implementation generic enough to be portable?

The worst patches make use of a system-specific features. Its highly unlikely that nonportable additions to the Perl language will be accepted.

Is the implementation tested?

Patches which change behaviour (fixing bugs or introducing new features) must include regression tests to verify that everything works as expected. Without tests provided by the original author, how can anyone else changing perl in the future be sure that they havent unwittingly broken the behaviour the patch implements? And without tests, how can the patchs author be confident that his/her hard work put into the patch wont be accidentally thrown away by someone in the future?

Is there enough documentation?

Patches without documentation are probably ill-thought out or incomplete. Nothing can be added without documentation, so submitting a patch for the appropriate manpages as well as the source code is always a good idea.

Is there another way to do it?

Larry said "Although the Perl Slogan is Theres More Than One Way to Do It, I hesitate to make 10 ways to do something". This is a tricky heuristic to navigate, though--one mans essential addition is another mans pointless cruft.

Does it create too much work?

Work for the pumpking, work for Perl programmers, work for module authors, ... Perl is supposed to be easy.

Patches speak louder than words

Working code is always preferred to pie-in-the-sky ideas. A patch to add a feature stands a much higher chance of making it to the language than does a random feature request, no matter how fervently argued the request might be. This ties into "Will it be useful?", as the fact that someone took the time to make the patch demonstrates a strong desire for the feature.

If youre on the list, you might hear the word "core" bandied around. It refers to the standard distribution. "Hacking on the core" means youre changing the C source code to the Perl interpreter. "A core module" is one that ships with Perl.

dvdbackup you can do a 1:1 copy of a DVD-video.

Installation

Download dvdbackup version 0.1 - you will also need libdvdread version 0.9.3 or later.

Compile dvdbackup.c in the src dir like this gcc -o dvdbackup
-I/my/prefix/to/libdvdread/include -L/my/prefix/to/libdvdread/lib
-ldvdread dvdbackup.c

NOTE: The "" indicates that its one line - i.e. remove the "" from the command
line

Usage:

If your backup directory is /my/dvd/backup/dir/ specified with the "-o" flag. Then dvdbackup will create a DVD-Video structure under /my/dvd/backup/dir/TITLE_NAME/VIDEO_TS.

Since the title is "uniq" you can use the same dir for all your DVD backups. If it happens to have a generic title dvdbackup will exit with a return value of 2. And you will need to specify a title name with the -n switch.

dvdbackup will always mimic the original DVD-Video structure. Hence if you e.g. use the -M (mirror) you will get an exact duplicate of the original. This means that every file will be have the same size as the original one. Like wise goes also for the -F and the -T switch.

However the -t and (-t -s/-e) switch is a bit different the titles sectors will be written to the original file but not at the same offset as the original one since they may be gaps in the cell structure that we dont fill.

To backup the whole DVD

dvdbackup -M -i/dev/dvd -o/my/dvd/backup/dir/

This action creates a valid DVD-Video structure that can be burned to a DVD-/+R(W) with help of mkisofs version 1.11a27 or later

To backup the main feature of the DVD

dvdbackup -F -i/dev/dvd -o/my/dvd/backup/dir/

This action creates a valid DVD-Video structure of the feature title set
dvdbackup defaults to get the 16:9 version of the main feature if a 4:3 is also present on the DVD. To get the 4:3 version use -a 0.

dvdbackup makes it best to make a inteligent guess what is the main feature of the DVD - in case it fails please send a bug report.

To backup a title set

dvdbackup -T 2 -i/dev/dvd -o/my/dvd/backup/dir/

where "-T 2" specifies that you want to backup title set 2 i.e. all VTS_02_X.XXX files.

This action creates a valid DVD-Video structure of the specified title set

To backup a title

dvdbackup -t 1 -i/dev/dvd -o/my/dvd/backup/dir

This action backups all cells that forms the specified title. Note that there can be sector gaps in between one cell and an other. dvdbackup will backup all sectors that belongs to the title but will skip sectors that arent a part of the title.

To backup a specific chapter or chapters from a title

dvdbackup -t 1 -s 20 -e 25 -i/dev/dvd -o/my/dvd/backup/dir

This action will backup chapter 20 to 25 in title 1, as with the backup of a title there can be sector gaps between one chapter (cell) and on other.dvdbackup will backup all sectors that belongs to the title 1 chapter 20 to 25 but will skip sectors that arent a part of the title 1 chapter 20 to 25.

To backup a single chapter e.g. chapter 20 do -s 20 -e 20
To backup from chapter 20 to the end chapter use only -s 20
To backup to chapter 20 from the first chapter use only -e 20

You can skip the -t switch and let the program guess the title although its not recomened.

If you specify a chapter that his higher than the last chapter of the title dvdbackup will turncate to the highest chapter of the title.

Return values

0 on success
1 on usage error
2 on title name error
-1 on failur

Todo - i.e. whats on the agenda

Make the main feature guessing algoritm better. Not that it doesnt do its job, but its implementation its that great. I would also like to preserve more information about the main feature since that would let me preform better implementations in other functions that depends on the titles_info_t and title_set_info_t strcutures.
Make it possible to extract cells in a title not just chapters (very easy so it will definitly be in the next version).

Make a split mirror (-S) option that divides a DVD-9 to two valid DVD-5 video structures. This is not a trivial hack and its my main goal the next month or so. It involves writing ifoedit and vobedit libraries in order to be able to manipulate both the IFO structures and the VOB files. Out of this will most probably also come tscreate and vtscreate which will enable you to make a very simple DVD-Video from MPEG-1/2 source.

PDA Maze project is a first-person 3D maze game with PDAs in mind.
PDA Maze is a first-person 3D maze game written in Xlib. Its small and fast and runs nicely on the Agenda VR3 Linux-based PDA. It has options for game timers, maze sizes, and different map modes.
Main features:
- 3D, first-perspective view (prerendered for speed)
- Screen scrolls when you rotate
- Walls colored differently on different sides
- Four background (skyline) photos
- Button (keyboard) and stylus (mouse) controls
- Game timer
- Different maze sizes
- Modes for partial (build as you go), total and no overview maps
- Sound effects
Enhancements:
- Added "input" windowmanager hint and title, so program will appear in VRSM window lists (VR->Windows menu, and Statusbar app windowlist). This works around a current bug in VRSM.