Its a text-fading linking ticker type applet that will fade text of any color over any color background. It features rollover color feedback, and will pause when rolled over so the user doesn t have to "chase" links. It uses very lIttle processor power and source is included! Now supports frames!
The project Adventure is a simple text-based adventure game. The game, as given, involves the hero trying to find his way from a deep dark forest to home and his true love. There s very lIttle else the player can do apart from moving from place to place. It s not really very interesting.
This project can be of use beyond the given, rather boring forest adventure though. You can use it as a basis for developing your own adventure game with different, more interesting commands, areas, items, people and so on.
The package ope.adventure contains classes to describe the game world.
- Convert file (plain text) or clipboard content among the following
encodings: big5, gbk, hz, shift-jis, jis, euc-jp, unicode big-endian,
unicode lIttle-endian, and utf-8.
- Batch files conversion
- Preview file content and converted result before actual conversion.
This practical, roll-up-your-sleeves guide distills years of ingenious XML hacking into a complete set of tips, tricks, and tools for web developers, system administrators, and programmers who want to leverage the untapped power of XML. If you want more than the average XML user--to explore and experiment, discover clever shortcuts, and show off just a lIttle (and have fun in the process)--this invaluable book is a must-have.
Developers use algorithms and data structures every day of their working lives. Having a good under-standing of these algorithms and knowledge of when to apply them is essential to producing softwarethat not only works correctly, but also performs efficiently.
This book aims to explain those algorithms and data structures most commonly encountered in day-to-day software development, while remaining at all times practical, concise, and to the point, with lIttle orno verbiage to distract from the core concepts and examples.
UCOS/II for ICCAVR
- The version of UCOS/II is 2.04
- the original port was done by Ole Saether for the IAR compiler. Jens E.
Holtegaard ported one version using ICCAVR. Joerg Meyer did another port
(using Jens port as a start?). This is basically Joerg s port plus a
lIttle bit of changes and documentation by me.
- YOU MUST DOWNLOAD THE MAIN PART OF THE UCOS/II FROM THE UCOS/II WEBSITE
http://www.ucos-ii.com . The supplied project file assumes the portable
source is in the ..\source directory.
- Joerg has written couple document showing the stack frames etc. but it
is in German :-) They are included in this directory.
- The Timer2 overflow interrupt is used for Timer Tick. If you want to
change that, modify os_cpu_c.c and os_cpu_a.s
- I have tested this using ATMega103 with and without external RAM
using AVR Studio simulator. See test1.c test program. Both Code
Compressed (PRO) and STD versions have been tested.
The latest release, ver 1.16 of the ARM (7TDMI, 720T, 920T) port for uC/OS-II V2.61 (and higher) includes ports for the following platforms:
1. S3c2410x ( ARM920T from Samsung ) on SMDK2410 eval board.
2. LPC2xxx - LPC210x & LPC213x ( ARM7TDMI-S from Philips ) on IAR s Kickstart & OLIMEX boards.
3. EP7312 ( ARM720T from CIRRUS ) on CDK238 eval board. Should also work on boards based on the CS89712.
Tool-chains: GCC 3.3.2, ADS 1.2 & SDT 2.51.
Op-modes: Pure ARM & ARM-THUMB interworked.
Endianess: Big endian & lIttle endian modes
Standard-Library Exception Safety
Bjarne Stroustrup
Texas A&M University
(and AT&T Labs – Research)
http://www.research.att.com/~bs
Introduction to the C++ exception handling mechanisms and “resource acquisition is initialization” for people with lIttle experience with exceptions
This the second tutorial of the Writing Device Drivers series. There seems to be a lot of interest in the topic, so this article will pick up where the first left off. The main focus of these articles will be to build up lIttle by lIttle the knowledge needed to write device drivers. In this article, we will be building on the same example source code used in part one. In this article, we will expand on that code to include Read functionality, Handle Input/Ouput Controls also known as IOCTLs, and learn a bit more about IRPs.
This the third edition of the Writing Device Drivers articles. The first article helped to simply get you acquainted with device drivers and a simple framework for developing a device driver for NT. The second tutorial attempted to show to use IOCTLs and display what the memory layout of Windows NT is. In this edition, we will go into the idea of contexts and pools. The driver we write today will also be a lIttle more interesting as it will allow two user mode applications to communicate with each other in a simple manner. We will call this the “poor man’s pipes” implementation.
