Rob's Lab - rob's wild ideas and software

[img[9ne Logo|assets/9ne_logo.png]]



9ne (pronounced "nine") is an online code editor based on Emacs (Copyright 2006 Rob Rohan). 9ne is a recursive acronym and joke, and means "9ne is not Emacs".

9ne's design goal is to provide an all purpose text editor similar to Emacs but web based. The first step is to assist in code editing (specifically HTML, CSS, and Javascript), but to also add hooks for any type of editing (mail reader, configuration files, etc). It currently supports XML and Javascript syntax highlighting modes (Evoked with M+X XML MODE and M+X JAVASCRIPT MODE respectively)

!Demo

<html>
<object width="425" height="350"><param name="movie" value="http://www.youtube.com/v/iVhDxCaCyU4"></param><embed src="http://www.youtube.com/v/iVhDxCaCyU4" type="application/x-shockwave-flash" width="425" height="350"></embed></object> 
</html>

!Download

9ne is released under the GPL.

[img[Download 9ne|assets/arrowdisk.png][http://robrohan.com/projects/download.php?file=9ne/9ne_0.9b.zip]]

!Source

9ne uses the [[Git]] distributed source control program (the one the Linux kernel uses). To check out my version of the source code into your own distributed repository, use the following command after installing Git:

{{{
$ cd my_projects_folder
$ git clone http://robrohan.com/projects/9ne/repo/9ne.git/
}}}

!Help

* [[9ne API|http://robrohan.com/projects/9ne/doc]]
* KeyBindingsFormat
* SyntaxColoringFormat
* LifeCycleHooks
* ExtensionExample


!Current State
9ne currently works the best on Mac OS X with Safari, Firefox, Flock or Camino. It also works on Windows with Firefox or IE6 and 7 with a few hiccups here and there. It has been mildly tested on Linux with varying degrees of success.

!Screenshots

[img[Shot 1|assets/9neOnIE.jpg.jpeg]]
[img[Shot 2|assets/9neLinux.png]]
[img[Shot 3|assets/9neFirefox.jpg.jpeg]]
[img[Shot 4|assets/9neSafari.jpg.jpeg]]

1. Write the Rules file using the xmode.dtd in {plugins}/com.rohanclan.afae_X.X.X/modes/
NOTE: you can use afae to do this by simply creating an XML document and adding
{{{
<!DOCTYPE MODE SYSTEM "xmode.dtd">
}}}
to the top of the file. However, the easiest way to make a new language is to use an already existing language definition as a base.

2. Add the mode file to the {plugins}/com.rohanclan.afae_X.X.X/modes/ directory, and add an entry into the catalog file (located in the same directory). The entry will need to looks something like the following:
{{{
<MODE NAME="hex"	FILE="hex.xml" 
	FILE_NAME_GLOB="*.{hex,other}"
/>
}}}
Where FILE_NAME_GLOB is the extension of the file, FILE is your new language file name, and NAME is the unique name of the language.

3. Add the file extension to the plugin.xml file (located in {plugins}/com.rohanclan.afae_X.X.X/) so Eclipse knows Afae can handle the file. Search the file for the word "extensions" and add it to the end of the comma separated list (should be around line 67).

You can now restart Eclipse and the file will be opened in Afae using your rules.
''Note:'' if you've opened the file before in a different editor (i.e. the default editor), you might have to right click (control click on Mac) on the file and choose Open With>Afae Editor

An All-purpose Editor for Eclipse

In one line: Afae's goal is to be a [[Textmate|http://macromates.com/]] like editor in Eclipse.

Afae stands for Another Freebooter's All-purpose Editor. It is a group of plugins for Eclipse that do the following:

* Syntax highlighting for many types of files.
* MetaWeblog plugin for posting to your blog
* Keystroke comments
* An image viewer and basic re-sizer for GIF, JPG, ICO, and PNG
* Snippets inserter with trigger text and variable replacement.
* A while-you-edit XML DTD and XML Schema validator
* Much more...

This is the editor I've used for most applications I've written. Afae is heavily influenced by both [[jEdit|http://jedit.org/]] and [[Textmate|http://macromates.com/]] - both of which are fantastic editors. Aside from [[Xcode|http://www.apple.com/macosx/features/xcode/]], TextMate, and [[Aquamacs|http://aquamacs.org/]] this is the only development environment / editor I use.

''Note'': All Afae plugins now require at least Eclipse 3.2 and Java version 1.5 (aka 5.0).

!Licenses & Contributors

Afae uses libraries, icons, and mode files from a lot of different places and projects. Afae would not be possible without the hard work of a lot of people. Here is a short list of some of the entities who's open source code help make Afae possible:

It should be noted that none of these entities endorse Afae (except for my name of course). Their names appear here only for attribution.

Rob Rohan, Stephen Milligan, Oliver Tupman, IBM Corporation, Klaus Hartlage, Sebastian Davids, Christopher Lenz, Chris Grindstaff, The Apache Software Foundation, David Vignoni (icons), Everaldo Coelho (icons), Chengdong Li, Jef Poskanzer, Mark Drew, Ben Glazer (mode file), Andre Kaplan (mode file), Kris Kopicki (mode file), Marc Rummel (mode file), Helge Böhme (mode file), Kristian Ovaska (mode file), Matthias Schneider (mode file), Mirco Bova (mode file), Nils Krahnstoever (mode file), Slava Pestov (mode file), Artur Biesiadowski (mode file), Mike Dillon (mode file), Juha Lindfors (mode file), Will Sargent (mode file), Ingmar Stein (mode file), Marcio Marchini (mode file), Rick Beton (mode file), Lionel Fiol (mode file), Barry Carr (mode file), Ralf Engels (mode file), Romain Guy (mode file), Jan Schaefer (mode file), Patrick Tingen (mode file), Giulio Piancastelli (mode file), Ed Stewart (mode file), Jonathan Revusky (mode file), Ian Maclean (mode file), Will Sargent (mode file), Richard F. Ashwell III (mode file), Michael Jacobson (mode file), Wojciech Stryjewski (mode file), Dante Fabrizio (mode file), Nitsan Vardi (mode file), Ron Stewart (mode file)

By downloading and installing the following plugins, you are agreeing to the following terms:

* [[Afae Editor License]]
* [[Afae Blogger License]]
* [[Afae Image Viewer License]]
* [[Afae Snippets License]]
* [[Afae Xml Compiler License]]

!Plugin Downloads

{{{
Update site: http://robrohan.com/projects/afae
}}}

To install Afae, in Eclipse select Help > Software Updates > Find and Install.... Select Search for new features to install, and then click Next.

On the next screen select New Remote Site..., name the site anything you like (Afae is apropos), and use the url http://robrohan.com/projects/afae. Then follow the on screen instructions.

''Note:'' If you have used the beta update site (used the update site prior to 2008-05-04), you will need to remove the old installed plugins before trying to use the update site. You can remove the old plugins by going into Help > Software Updates > Manage Configuration, and right clicking on the afae related features and choosing Uninstall. You will then need to restart Eclipse and re-access the update site.

!Help

* How to [[Add a language in Afae]]
* How to go about [[Using Snippet Variables]]
* What are the [[Supported File Types]]
* All you ever wanted to know about the [[Syntax Files]]
* [[Afae's Minimum System Requirements]]
* [[Using Afae With Model Glue]]

!Source

To get the Afae source, you'll need to use the [[Git]] version control system.

Once you have git installed, you can clone a repository by doing one of the following (depending on which plugin you're interested in):

{{{
$ git clone http://robrohan.com/projects/afae/repo/AfaeEditor.git
$ git clone http://robrohan.com/projects/afae/repo/AfaeEditorBlogger.git
$ git clone http://robrohan.com/projects/afae/repo/AfaeImageViewer.git
$ git clone http://robrohan.com/projects/afae/repo/AfaeSnippets.git
$ git clone http://robrohan.com/projects/afae/repo/AfaeXMLCompiler.git
$ git clone http://robrohan.com/projects/afae/repo/AfaeExtras.git
$ git clone http://robrohan.com/projects/afae/repo/AfaeFeature.git
$ git clone http://robrohan.com/projects/afae/repo/AfaeUpdateSite.git
}}}

!Screenshots

[img[Windows shot|assets/afae-windows.jpg.jpeg]]
[img[Studio shot|assets/studio.jpg.jpeg]]
[img[Plastic|assets/new-plastic.jpg.jpeg]]
[img[Blackboard|assets/new-blackboard.jpg.jpeg]]
[img[Image Viewer|assets/image-viewer.jpg.jpeg]]
[img[Ubuntu Shot|assets/ubuntu_shot.png]]
[img[Blogging|assets/newafae.jpg.jpeg]]

{{{

}}}

The blogging plugin uses the Apache XMLRPC library which is released under the following license:

{{{

Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.

"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.

"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.

"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:

(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and

(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and

(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and

(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.

You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work.

To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
}}}

It also uses Icons from the Crystal Clear icons set, by Everaldo Coelho, which are released under the following license:

{{{
GNU LESSER GENERAL PUBLIC LICENSE

Version 2.1, February 1999

Copyright (C) 1991, 1999 Free Software Foundation, Inc.
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.

[This is the first released version of the Lesser GPL. It also counts
as the successor of the GNU Library Public License, version 2, hence
the version number 2.1.]

Preamble

The licenses for most software are designed to take away your freedom
to share and change it. By contrast, the GNU General Public Licenses are
intended to guarantee your freedom to share and change free software--to
make sure the software is free for all its users.

This license, the Lesser General Public License, applies to some specially
designated software packages--typically libraries--of the Free Software
Foundation and other authors who decide to use it. You can use it too,
but we suggest you first think carefully about whether this license or
the ordinary General Public License is the better strategy to use in any
particular case, based on the explanations below.

When we speak of free software, we are referring to freedom of use, not
price. Our General Public Licenses are designed to make sure that you have
the freedom to distribute copies of free software (and charge for this
service if you wish); that you receive source code or can get it if you want
it; that you can change the software and use pieces of it in new free
programs; and that you are informed that you can do these things.

To protect your rights, we need to make restrictions that forbid distributors
to deny you these rights or to ask you to surrender these rights. These
restrictions translate to certain responsibilities for you if you distribute
copies of the library or if you modify it.

For example, if you distribute copies of the library, whether gratis or for
a fee, you must give the recipients all the rights that we gave you. You
must make sure that they, too, receive or can get the source code. If you
link other code with the library, you must provide complete object files
to the recipients, so that they can relink them with the library after
making changes to the library and recompiling it. And you must show them
these terms so they know their rights.

We protect your rights with a two-step method: (1) we copyright the library,
and (2) we offer you this license, which gives you legal permission to
copy, distribute and/or modify the library.

To protect each distributor, we want to make it very clear that there is
no warranty for the free library. Also, if the library is modified by
someone else and passed on, the recipients should know that what they have
is not the original version, so that the original author's reputation will
not be affected by problems that might be introduced by others.

Finally, software patents pose a constant threat to the existence of any
free program. We wish to make sure that a company cannot effectively
restrict the users of a free program by obtaining a restrictive license
from a patent holder. Therefore, we insist that any patent license
obtained for a version of the library must be consistent with the full
freedom of use specified in this license.

Most GNU software, including some libraries, is covered by the ordinary
GNU General Public License. This license, the GNU Lesser General Public
License, applies to certain designated libraries, and is quite different
from the ordinary General Public License. We use this license for certain
libraries in order to permit linking those libraries into non-free
programs.

When a program is linked with a library, whether statically or using a
shared library, the combination of the two is legally speaking a combined
work, a derivative of the original library. The ordinary General Public
License therefore permits such linking only if the entire combination
fits its criteria of freedom. The Lesser General Public License permits
more lax criteria for linking other code with the library.

We call this license the "Lesser" General Public License because it does
Less to protect the user's freedom than the ordinary General Public
License. It also provides other free software developers Less of an advantage
over competing non-free programs. These disadvantages are the reason
we use the ordinary General Public License for many libraries. However,
the Lesser license provides advantages in certain special circumstances.

For example, on rare occasions, there may be a special need to encourage
the widest possible use of a certain library, so that it becomes a de-facto
standard. To achieve this, non-free programs must be allowed to use the
library. A more frequent case is that a free library does the same job as
widely used non-free libraries. In this case, there is little to gain by
limiting the free library to free software only, so we use the Lesser
General Public License.

In other cases, permission to use a particular library in non-free programs
enables a greater number of people to use a large body of free software.
For example, permission to use the GNU C Library in non-free programs
enables many more people to use the whole GNU operating system, as well
as its variant, the GNU/Linux operating system.

Although the Lesser General Public License is Less protective of the users'
freedom, it does ensure that the user of a program that is linked with
the Library has the freedom and the wherewithal to run that program using
a modified version of the Library.

The precise terms and conditions for copying, distribution and modification
follow. Pay close attention to the difference between a "work based on
the library" and a "work that uses the library". The former contains code
derived from the library, whereas the latter must be combined with the
library in order to run.
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License Agreement applies to any software library or other program
which contains a notice placed by the copyright holder or other authorized
party saying it may be distributed under the terms of this Lesser General
Public License (also called "this License"). Each licensee is addressed as
"you".

A "library" means a collection of software functions and/or data prepared
so as to be conveniently linked with application programs (which use some
of those functions and data) to form executables.

The "Library", below, refers to any such software library or work which
has been distributed under these terms. A "work based on the Library" means
either the Library or any derivative work under copyright law: that is to say,
a work containing the Library or a portion of it, either verbatim or with
modifications and/or translated straightforwardly into another language.
(Hereinafter, translation is included without limitation in the term
"modification".)

"Source code" for a work means the preferred form of the work for making
modifications to it. For a library, complete source code means all the source
code for all modules it contains, plus any associated interface definition
files, plus the scripts used to control compilation and installation of the
library.

Activities other than copying, distribution and modification are not covered
by this License; they are outside its scope. The act of running a program
using the Library is not restricted, and output from such a program is covered
only if its contents constitute a work based on the Library (independent of
the use of the Library in a tool for writing it). Whether that is true
depends on what the Library does and what the program that uses the Library
does.

1. You may copy and distribute verbatim copies of the Library's complete
source code as you receive it, in any medium, provided that you conspicuously
and appropriately publish on each copy an appropriate copyright notice and
disclaimer of warranty; keep intact all the notices that refer to this License
and to the absence of any warranty; and distribute a copy of this License
along with the Library.

You may charge a fee for the physical act of transferring a copy, and you
may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Library or any portion of it,
thus forming a work based on the Library, and copy and distribute such
modifications or work under the terms of Section 1 above, provided that you
also meet all of these conditions:

* a) The modified work must itself be a software library.
* b) You must cause the files modified to carry prominent notices stating
that you changed the files and the date of any change.
* c) You must cause the whole of the work to be licensed at no charge to
all third parties under the terms of this License.
* d)

If a facility in the modified Library refers to a function or a table
of data to be supplied by an application program that uses the facility, other
than as an argument passed when the facility is invoked, then you must make a
good faith effort to ensure that, in the event an application does not supply
such function or table, the facility still operates, and performs whatever
part of its purpose remains meaningful.

(For example, a function in a library to compute square roots has a purpose
that is entirely well-defined independent of the application. Therefore,
Subsection 2d requires that any application-supplied function or table used by
this function must be optional: if the application does not supply it, the square
root function must still compute square roots.)

These requirements apply to the modified work as a whole. If identifiable
sections of that work are not derived from the Library, and can be reasonably
considered independent and separate works in themselves, then this License, and its
terms, do not apply to those sections when you distribute them as separate works.
But when you distribute the same sections as part of a whole which is a work based
on the Library, the distribution of the whole must be on the terms of this License,
whose permissions for other licensees extend to the entire whole, and thus to each
and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights
to work written entirely by you; rather, the intent is to exercise the right to
control the distribution of derivative or collective works based on the Library.

In addition, mere aggregation of another work not based on the Library with the
Library (or with a work based on the Library) on a volume of a storage or distribution
medium does not bring the other work under the scope of this License.

3. You may opt to apply the terms of the ordinary GNU General Public License instead
of this License to a given copy of the Library. To do this, you must alter all the
notices that refer to this License, so that they refer to the ordinary GNU General
Public License, version 2, instead of to this License. (If a newer version than version
2 of the ordinary GNU General Public License has appeared, then you can specify that
version instead if you wish.) Do not make any other change in these notices.

Once this change is made in a given copy, it is irreversible for that copy, so the
ordinary GNU General Public License applies to all subsequent copies and derivative
works made from that copy.

This option is useful when you wish to copy part of the code of the Library into a
program that is not a library.

4. You may copy and distribute the Library (or a portion or derivative of it, under
Section 2) in object code or executable form under the terms of Sections 1 and 2
above provided that you accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange.

If distribution of object code is made by offering access to copy from a designated
place, then offering equivalent access to copy the source code from the same place
satisfies the requirement to distribute the source code, even though third parties
are not compelled to copy the source along with the object code.

5. A program that contains no derivative of any portion of the Library, but is
designed to work with the Library by being compiled or linked with it, is called a
"work that uses the Library". Such a work, in isolation, is not a derivative work of
the Library, and therefore falls outside the scope of this License.

However, linking a "work that uses the Library" with the Library creates an executable
that is a derivative of the Library (because it contains portions of the Library),
rather than a "work that uses the library". The executable is therefore covered by
this License. Section 6 states terms for distribution of such executables.

When a "work that uses the Library" uses material from a header file that is part
of the Library, the object code for the work may be a derivative work of the
Library even though the source code is not. Whether this is true is especially
significant if the work can be linked without the Library, or if the work is
itself a library. The threshold for this to be true is not precisely defined by law.

If such an object file uses only numerical parameters, data structure layouts
and accessors, and small macros and small inline functions (ten lines or less
in length), then the use of the object file is unrestricted, regardless of whether
it is legally a derivative work. (Executables containing this object code plus
portions of the Library will still fall under Section 6.)

Otherwise, if the work is a derivative of the Library, you may distribute the
object code for the work under the terms of Section 6. Any executables containing
that work also fall under Section 6, whether or not they are linked directly
with the Library itself.

6. As an exception to the Sections above, you may also combine or link a "work
that uses the Library" with the Library to produce a work containing portions of
the Library, and distribute that work under terms of your choice, provided that
the terms permit modification of the work for the customer's own use and reverse
engineering for debugging such modifications.

You must give prominent notice with each copy of the work that the Library is used
in it and that the Library and its use are covered by this License. You must supply
a copy of this License. If the work during execution displays copyright notices,
you must include the copyright notice for the Library among them, as well as a
reference directing the user to the copy of this License. Also, you must do one
of these things:

* a) Accompany the work with the complete corresponding machine-readable
source code for the Library including whatever changes were used in the work (which
must be distributed under Sections 1 and 2 above); and, if the work is an executable
linked with the Library, with the complete machine-readable "work that uses the
Library", as object code and/or source code, so that the user can modify the
Library and then relink to produce a modified executable containing the modified
Library. (It is understood that the user who changes the contents of definitions
files in the Library will not necessarily be able to recompile the application to
use the modified definitions.)
* b) Use a suitable shared library mechanism for linking with the Library. A
suitable mechanism is one that (1) uses at run time a copy of the library already
present on the user's computer system, rather than copying library functions into
the executable, and (2) will operate properly with a modified version of the library,
if the user installs one, as long as the modified version is interface-compatible with
the version that the work was made with.
* c) Accompany the work with a written offer, valid for at least three years, to
give the same user the materials specified in Subsection 6a, above, for a charge no
more than the cost of performing this distribution.
* d) If distribution of the work is made by offering access to copy from a
designated place, offer equivalent access to copy the above specified materials from
the same place.
* e) Verify that the user has already received a copy of these materials or that
you have already sent this user a copy.

For an executable, the required form of the "work that uses the Library" must include
any data and utility programs needed for reproducing the executable from it. However,
as a special exception, the materials to be distributed need not include anything that
is normally distributed (in either source or binary form) with the major components
(compiler, kernel, and so on) of the operating system on which the executable runs,
unless that component itself accompanies the executable.

It may happen that this requirement contradicts the license restrictions of other
proprietary libraries that do not normally accompany the operating system. Such a
contradiction means you cannot use both them and the Library together in an executable
that you distribute.

7. You may place library facilities that are a work based on the Library side-by-side in
a single library together with other library facilities not covered by this License, and
distribute such a combined library, provided that the separate distribution of the work
based on the Library and of the other library facilities is otherwise permitted, and
provided that you do these two things:

* a) Accompany the combined library with a copy of the same work based on the Library,
uncombined with any other library facilities. This must be distributed under the terms
of the Sections above.
* b) Give prominent notice with the combined library of the fact that part of it
is a work based on the Library, and explaining where to find the accompanying uncombined
form of the same work.

8. You may not copy, modify, sublicense, link with, or distribute the Library except as
expressly provided under this License. Any attempt otherwise to copy, modify, sublicense,
link with, or distribute the Library is void, and will automatically terminate your
rights under this License. However, parties who have received copies, or rights, from you
under this License will not have their licenses terminated so long as such parties remain
in full compliance.

9. You are not required to accept this License, since you have not signed it. However,
nothing else grants you permission to modify or distribute the Library or its derivative
works. These actions are prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Library (or any work based on the Library), you indicate your
acceptance of this License to do so, and all its terms and conditions for copying,
distributing or modifying the Library or works based on it.

10. Each time you redistribute the Library (or any work based on the Library), the
recipient automatically receives a license from the original licensor to copy, distribute,
link with or modify the Library subject to these terms and conditions. You may not impose
any further restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties with this License.

11. If, as a consequence of a court judgment or allegation of patent infringement or
for any other reason (not limited to patent issues), conditions are imposed on you
(whether by court order, agreement or otherwise) that contradict the conditions of
this License, they do not excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this License and any
other pertinent obligations, then as a consequence you may not distribute the Library
at all. For example, if a patent license would not permit royalty-free redistribution
of the Library by all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to refrain entirely
from distribution of the Library.

If any portion of this section is held invalid or unenforceable under any particular
circumstance, the balance of the section is intended to apply, and the section as a
whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other
property right claims or to contest validity of any such claims; this section has the
sole purpose of protecting the integrity of the free software distribution system which
is implemented by public license practices. Many people have made generous contributions
to the wide range of software distributed through that system in reliance on consistent
application of that system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of
the rest of this License.

12. If the distribution and/or use of the Library is restricted in certain countries either
by patents or by copyrighted interfaces, the original copyright holder who places the
Library under this License may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among countries not thus
excluded. In such case, this License incorporates the limitation as if written in the body
of this License.

13. The Free Software Foundation may publish revised and/or new versions of the Lesser
General Public License from time to time. Such new versions will be similar in spirit to the
present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Library specifies a version
number of this License which applies to it and "any later version", you have the option of
following the terms and conditions either of that version or of any later version published
by the Free Software Foundation. If the Library does not specify a license version number,
you may choose any version ever published by the Free Software Foundation.

14. If you wish to incorporate parts of the Library into other free programs whose
distribution conditions are incompatible with these, write to the author to ask for
permission. For software which is copyrighted by the Free Software Foundation, write to
the Free Software Foundation; we sometimes make exceptions for this. Our decision will be
guided by the two goals of preserving the free status of all derivatives of our free software
and of promoting the sharing and reuse of software generally.

NO WARRANTY

15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO
THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY
SERVICING, REPAIR OR CORRECTION.

16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT
HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE,
BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL
DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO
LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR
A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER
PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Libraries

If you develop a new library, and you want it to be of the greatest possible use to the public,
we recommend making it free software that everyone can redistribute and change. You can do so
by permitting redistribution under these terms (or, alternatively, under the terms of the
ordinary General Public License).

To apply these terms, attach the following notices to the library. It is safest to attach them
to the start of each source file to most effectively convey the exclusion of warranty; and each
file should have at least the "copyright" line and a pointer to where the full notice is found.

one line to give the library's name and an idea of what it does.
Copyright (C) year name of author

This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) any later version.

This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.

You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA

Also add information on how to contact you by electronic and paper mail.

You should also get your employer (if you work as a programmer) or your school, if any, to
sign a "copyright disclaimer" for the library, if necessary. Here is a sample; alter the
names:

Yoyodyne, Inc., hereby disclaims all copyright interest in
the library `Frob' (a library for tweaking knobs) written
by James Random Hacker.

signature of Ty Coon, 1 April 1990
Ty Coon, President of Vice

That's all there is to it!
}}}

{{{
Copyright (c) 2004-2007 Rob Rohan

Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

}}}

----

{{{
Copyright (c) 2004-2005 Stephen Milligan

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.

}}}

----

{{{
Copyright (c) 2004-2005 Oliver Tupman

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.

}}}

----

{{{
Copyright (c) 2000, 2004 IBM Corporation and others.
All rights reserved. This program and the accompanying materials
are made available under the terms of the Common Public License v1.0
which accompanies this distribution, and is available at
http://www.eclipse.org/legal/cpl-v10.html

Contributors:
IBM Corporation - initial API and implementation
Klaus Hartlage - www.eclipseproject.de
Sebastian Davids <sdavids@gmx.de> - initial API and implementation
Christopher Lenz - initial API and implementation
}}}
----
{{{
cbg.editor Eclipse plugin
Copyright(c) 2002, Chris Grindstaff

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.

DOM4j and RegExp

{{{
============================================================================
The Apache Software License, Version 1.1
============================================================================

Redistribution and use in source and binary forms, with or without modifica-
tion, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.

3. The end-user documentation included with the redistribution, if any, must
include the following acknowledgment: "This product includes software
developed by the Apache Software Foundation (http://www.apache.org/)."
Alternately, this acknowledgment may appear in the software itself, if
and wherever such third-party acknowledgments normally appear.

4. The names "log4j" and "Apache Software Foundation" must not be used to
endorse or promote products derived from this software without prior
written permission. For written permission, please contact
apache@apache.org.

5. Products derived from this software may not be called "Apache", nor may
"Apache" appear in their name, without prior written permission of the
Apache Software Foundation.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLU-
DING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This software consists of voluntary contributions made by many individuals
on behalf of the Apache Software Foundation. For more information on the
Apache Software Foundation, please see <http://www.apache.org/>.
}}}

The Icons:

{{{
TITLE: NUVOLA ICON THEME for KDE 3.x
AUTHOR: David Vignoni
SITE: http://www.icon-king.com
MAILING LIST: http://mail.icon-king.com/mailman/listinfo/nuvola_icon-king.com

GNU LESSER GENERAL PUBLIC LICENSE
Version 2.1, February 1999

Copyright (C) 1991, 1999 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.

[This is the first released version of the Lesser GPL. It also counts
as the successor of the GNU Library Public License, version 2, hence
the version number 2.1.]

Preamble

The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.

This license, the Lesser General Public License, applies to some
specially designated software packages--typically libraries--of the
Free Software Foundation and other authors who decide to use it. You
can use it too, but we suggest you first think carefully about whether
this license or the ordinary General Public License is the better
strategy to use in any particular case, based on the explanations below.

When we speak of free software, we are referring to freedom of use,
not price. Our General Public Licenses are designed to make sure that
you have the freedom to distribute copies of free software (and charge
for this service if you wish); that you receive source code or can get
it if you want it; that you can change the software and use pieces of
it in new free programs; and that you are informed that you can do
these things.

To protect your rights, we need to make restrictions that forbid
distributors to deny you these rights or to ask you to surrender these
rights. These restrictions translate to certain responsibilities for
you if you distribute copies of the library or if you modify it.

For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that we gave
you. You must make sure that they, too, receive or can get the source
code. If you link other code with the library, you must provide
complete object files to the recipients, so that they can relink them
with the library after making changes to the library and recompiling
it. And you must show them these terms so they know their rights.

We protect your rights with a two-step method: (1) we copyright the
library, and (2) we offer you this license, which gives you legal
permission to copy, distribute and/or modify the library.

To protect each distributor, we want to make it very clear that
there is no warranty for the free library. Also, if the library is
modified by someone else and passed on, the recipients should know
that what they have is not the original version, so that the original
author's reputation will not be affected by problems that might be
introduced by others.

Finally, software patents pose a constant threat to the existence of
any free program. We wish to make sure that a company cannot
effectively restrict the users of a free program by obtaining a
restrictive license from a patent holder. Therefore, we insist that
any patent license obtained for a version of the library must be
consistent with the full freedom of use specified in this license.

Most GNU software, including some libraries, is covered by the
ordinary GNU General Public License. This license, the GNU Lesser
General Public License, applies to certain designated libraries, and
is quite different from the ordinary General Public License. We use
this license for certain libraries in order to permit linking those
libraries into non-free programs.

When a program is linked with a library, whether statically or using
a shared library, the combination of the two is legally speaking a
combined work, a derivative of the original library. The ordinary
General Public License therefore permits such linking only if the
entire combination fits its criteria of freedom. The Lesser General
Public License permits more lax criteria for linking other code with
the library.

We call this license the "Lesser" General Public License because it
does Less to protect the user's freedom than the ordinary General
Public License. It also provides other free software developers Less
of an advantage over competing non-free programs. These disadvantages
are the reason we use the ordinary General Public License for many
libraries. However, the Lesser license provides advantages in certain
special circumstances.

For example, on rare occasions, there may be a special need to
encourage the widest possible use of a certain library, so that it becomes
a de-facto standard. To achieve this, non-free programs must be
allowed to use the library. A more frequent case is that a free
library does the same job as widely used non-free libraries. In this
case, there is little to gain by limiting the free library to free
software only, so we use the Lesser General Public License.

In other cases, permission to use a particular library in non-free
programs enables a greater number of people to use a large body of
free software. For example, permission to use the GNU C Library in
non-free programs enables many more people to use the whole GNU
operating system, as well as its variant, the GNU/Linux operating
system.

Although the Lesser General Public License is Less protective of the
users' freedom, it does ensure that the user of a program that is
linked with the Library has the freedom and the wherewithal to run
that program using a modified version of the Library.

The precise terms and conditions for copying, distribution and
modification follow. Pay close attention to the difference between a
"work based on the library" and a "work that uses the library". The
former contains code derived from the library, whereas the latter must
be combined with the library in order to run.

GNU LESSER GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License Agreement applies to any software library or other
program which contains a notice placed by the copyright holder or
other authorized party saying it may be distributed under the terms of
this Lesser General Public License (also called "this License").
Each licensee is addressed as "you".

A "library" means a collection of software functions and/or data
prepared so as to be conveniently linked with application programs
(which use some of those functions and data) to form executables.

The "Library", below, refers to any such software library or work
which has been distributed under these terms. A "work based on the
Library" means either the Library or any derivative work under
copyright law: that is to say, a work containing the Library or a
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language. (Hereinafter, translation is
included without limitation in the term "modification".)

"Source code" for a work means the preferred form of the work for
making modifications to it. For a library, complete source code means
all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control compilation
and installation of the library.

Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it). Whether that is true depends on what the Library does
and what the program that uses the Library does.

1. You may copy and distribute verbatim copies of the Library's
complete source code as you receive it, in any medium, provided that
you conspicuously and appropriately publish on each copy an
appropriate copyright notice and disclaimer of warranty; keep intact
all the notices that refer to this License and to the absence of any
warranty; and distribute a copy of this License along with the
Library.

You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for a
fee.

2. You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

a) The modified work must itself be a software library.

b) You must cause the files modified to carry prominent notices
stating that you changed the files and the date of any change.

c) You must cause the whole of the work to be licensed at no
charge to all third parties under the terms of this License.

d) If a facility in the modified Library refers to a function or a
table of data to be supplied by an application program that uses
the facility, other than as an argument passed when the facility
is invoked, then you must make a good faith effort to ensure that,
in the event an application does not supply such function or
table, the facility still operates, and performs whatever part of
its purpose remains meaningful.

(For example, a function in a library to compute square roots has
a purpose that is entirely well-defined independent of the
application. Therefore, Subsection 2d requires that any
application-supplied function or table used by this function must
be optional: if the application does not supply it, the square
root function must still compute square roots.)

These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Library,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Library, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Library.

In addition, mere aggregation of another work not based on the Library
with the Library (or with a work based on the Library) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

3. You may opt to apply the terms of the ordinary GNU General Public
License instead of this License to a given copy of the Library. To do
this, you must alter all the notices that refer to this License, so
that they refer to the ordinary GNU General Public License, version 2,
instead of to this License. (If a newer version than version 2 of the
ordinary GNU General Public License has appeared, then you can specify
that version instead if you wish.) Do not make any other change in
these notices.

Once this change is made in a given copy, it is irreversible for
that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy.

This option is useful when you wish to copy part of the code of
the Library into a program that is not a library.

4. You may copy and distribute the Library (or a portion or
derivative of it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you accompany
it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange.

If distribution of object code is made by offering access to copy
from a designated place, then offering equivalent access to copy the
source code from the same place satisfies the requirement to
distribute the source code, even though third parties are not
compelled to copy the source along with the object code.

5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library". Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.

However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library". The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.

When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library. The
threshold for this to be true is not precisely defined by law.

If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work. (Executables containing this object code plus portions of the
Library will still fall under Section 6.)

Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.

6. As an exception to the Sections above, you may also combine or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.

You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License. You must supply a copy of this License. If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License. Also, you must do one
of these things:

a) Accompany the work with the complete corresponding
machine-readable source code for the Library including whatever
changes were used in the work (which must be distributed under
Sections 1 and 2 above); and, if the work is an executable linked
with the Library, with the complete machine-readable "work that
uses the Library", as object code and/or source code, so that the
user can modify the Library and then relink to produce a modified
executable containing the modified Library. (It is understood
that the user who changes the contents of definitions files in the
Library will not necessarily be able to recompile the application
to use the modified definitions.)

b) Use a suitable shared library mechanism for linking with the
Library. A suitable mechanism is one that (1) uses at run time a
copy of the library already present on the user's computer system,
rather than copying library functions into the executable, and (2)
will operate properly with a modified version of the library, if
the user installs one, as long as the modified version is
interface-compatible with the version that the work was made with.

c) Accompany the work with a written offer, valid for at
least three years, to give the same user the materials
specified in Subsection 6a, above, for a charge no more
than the cost of performing this distribution.

d) If distribution of the work is made by offering access to copy
from a designated place, offer equivalent access to copy the above
specified materials from the same place.

e) Verify that the user has already received a copy of these
materials or that you have already sent this user a copy.

For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it. However, as a special exception,
the materials to be distributed need not include anything that is
normally distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies
the executable.

It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system. Such a contradiction means you cannot
use both them and the Library together in an executable that you
distribute.

7. You may place library facilities that are a work based on the
Library side-by-side in a single library together with other library
facilities not covered by this License, and distribute such a combined
library, provided that the separate distribution of the work based on
the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:

a) Accompany the combined library with a copy of the same work
based on the Library, uncombined with any other library
facilities. This must be distributed under the terms of the
Sections above.

b) Give prominent notice with the combined library of the fact
that part of it is a work based on the Library, and explaining
where to find the accompanying uncombined form of the same work.

8. You may not copy, modify, sublicense, link with, or distribute
the Library except as expressly provided under this License. Any
attempt otherwise to copy, modify, sublicense, link with, or
distribute the Library is void, and will automatically terminate your
rights under this License. However, parties who have received copies,
or rights, from you under this License will not have their licenses
terminated so long as such parties remain in full compliance.

9. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Library or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Library (or any work based on the
Library), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Library or works based on it.

10. Each time you redistribute the Library (or any work based on the
Library), the recipient automatically receives a license from the
original licensor to copy, distribute, link with or modify the Library
subject to these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties with
this License.

11. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Library at all. For example, if a patent
license would not permit royalty-free redistribution of the Library by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Library.

If any portion of this section is held invalid or unenforceable under any
particular circumstance, the balance of the section is intended to apply,
and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

12. If the distribution and/or use of the Library is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Library under this License may add
an explicit geographical distribution limitation excluding those countries,
so that distribution is permitted only in or among countries not thus
excluded. In such case, this License incorporates the limitation as if
written in the body of this License.

13. The Free Software Foundation may publish revised and/or new
versions of the Lesser General Public License from time to time.
Such new versions will be similar in spirit to the present version,
but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Library
specifies a version number of this License which applies to it and
"any later version", you have the option of following the terms and
conditions either of that version or of any later version published by
the Free Software Foundation. If the Library does not specify a
license version number, you may choose any version ever published by
the Free Software Foundation.

14. If you wish to incorporate parts of the Library into other free
programs whose distribution conditions are incompatible with these,
write to the author to ask for permission. For software which is
copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this. Our
decision will be guided by the two goals of preserving the free status
of all derivatives of our free software and of promoting the sharing
and reuse of software generally.

NO WARRANTY

15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Libraries

If you develop a new library, and you want it to be of the greatest
possible use to the public, we recommend making it free software that
everyone can redistribute and change. You can do so by permitting
redistribution under these terms (or, alternatively, under the terms of the
ordinary General Public License).

To apply these terms, attach the following notices to the library. It is
safest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.

<one line to give the library's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>

You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

Also add information on how to contact you by electronic and paper mail.

You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the library, if
necessary. Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the
library `Frob' (a library for tweaking knobs) written by James Random Hacker.

<signature of Ty Coon>, 1 April 1990
Ty Coon, President of Vice

That's all there is to it!
}}}

This Plugin also uses Mode files from JEdit. JEdit, and the mode files are licensed under either the BSD License or GNU General Public License (GPL) depending on what Mode file is in question. If you are going to close source a distribution of Afae, please see that mode files, and further infomation can be found at: http://sourceforge.net/projects/jedit/

{{{
Copyright (c) 2004-2007 Rob Rohan

Permission is hereby granted, free of charge, to any person obtaining a 
copy of this software and associated documentation files (the "Software"), 
to deal in the Software without restriction, including without limitation 
the rights to use, copy, modify, merge, publish, distribute, sublicense, 
and/or sell copies of the Software, and to permit persons to whom the Software 
is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in 
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 
SOFTWARE.
}}}

----

{{{
Copyright (c) 2004 Oliver Tupman

Permission is hereby granted, free of charge, to any person obtaining a 
copy of this software and associated documentation files (the "Software"), 
to deal in the Software without restriction, including without limitation 
the rights to use, copy, modify, merge, publish, distribute, sublicense, 
and/or sell copies of the Software, and to permit persons to whom the Software 
is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in 
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 
SOFTWARE.
}}}

----


{{{
Copyright (c) 2004 Chengdong Li : cdli@ccs.uky.edu
All rights reserved. This program and the accompanying materials 
are made available under the terms of the Common Public License v1.0
which accompanies this distribution, and is available at
http://www.eclipse.org/legal/cpl-v10.html
}}}

----

{{{
Some Code and Gif creating:
 Transparency handling and variable bit size courtesy of Jack Palevich.

 Copyright (C)1996,1998 by Jef Poskanzer <jef@acme.com>. All rights reserved.

 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions
 are met:
 1. Redistributions of source code must retain the above copyright
    notice, this list of conditions and the following disclaimer.
 2. Redistributions in binary form must reproduce the above copyright
    notice, this list of conditions and the following disclaimer in the
    documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.

Visit the ACME Labs Java page for up-to-date versions of this and other
fine Java utilities: http:Created-By:www.acme.com/java/
}}}

{{{
Copyright (c) 2004-2007 Rob Rohan

Permission is hereby granted, free of charge, to any person obtaining a 
copy of this software and associated documentation files (the "Software"), 
to deal in the Software without restriction, including without limitation 
the rights to use, copy, modify, merge, publish, distribute, sublicense, 
and/or sell copies of the Software, and to permit persons to whom the Software 
is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in 
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 
SOFTWARE.
}}}

----

{{{
Copyright (c) 2004 Stephen Milligan

Permission is hereby granted, free of charge, to any person obtaining a 
copy of this software and associated documentation files (the "Software"), 
to deal in the Software without restriction, including without limitation 
the rights to use, copy, modify, merge, publish, distribute, sublicense, 
and/or sell copies of the Software, and to permit persons to whom the Software 
is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in 
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 
SOFTWARE.
}}}


----

{{{
Copyright (c) 2004 Mark Drew

Permission is hereby granted, free of charge, to any person obtaining a 
copy of this software and associated documentation files (the "Software"), 
to deal in the Software without restriction, including without limitation 
the rights to use, copy, modify, merge, publish, distribute, sublicense, 
and/or sell copies of the Software, and to permit persons to whom the Software 
is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in 
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 
SOFTWARE.
}}}


----


Code examples taken from an article by Chris Grindstaff

{{{
TITLE:	NUVOLA ICON THEME for KDE 3.x
AUTHOR:	David Vignoni
SITE:	http://www.icon-king.com
MAILING LIST: http://mail.icon-king.com/mailman/listinfo/nuvola_icon-king.com

Copyright (c)  2003-2004  David Vignoni.

		  GNU LESSER GENERAL PUBLIC LICENSE
		       Version 2.1, February 1999

 Copyright (C) 1991, 1999 Free Software Foundation, Inc.
     59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.

[This is the first released version of the Lesser GPL.  It also counts
 as the successor of the GNU Library Public License, version 2, hence
 the version number 2.1.]

			    Preamble

  The licenses for most software are designed to take away your
freedom to share and change it.  By contrast, the GNU General Public
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.

  This license, the Lesser General Public License, applies to some
specially designated software packages--typically libraries--of the
Free Software Foundation and other authors who decide to use it.  You
can use it too, but we suggest you first think carefully about whether
this license or the ordinary General Public License is the better
strategy to use in any particular case, based on the explanations below.

  When we speak of free software, we are referring to freedom of use,
not price.  Our General Public Licenses are designed to make sure that
you have the freedom to distribute copies of free software (and charge
for this service if you wish); that you receive source code or can get
it if you want it; that you can change the software and use pieces of
it in new free programs; and that you are informed that you can do
these things.

  To protect your rights, we need to make restrictions that forbid
distributors to deny you these rights or to ask you to surrender these
rights.  These restrictions translate to certain responsibilities for
you if you distribute copies of the library or if you modify it.

  For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that we gave
you.  You must make sure that they, too, receive or can get the source
code.  If you link other code with the library, you must provide
complete object files to the recipients, so that they can relink them
with the library after making changes to the library and recompiling
it.  And you must show them these terms so they know their rights.

  We protect your rights with a two-step method: (1) we copyright the
library, and (2) we offer you this license, which gives you legal
permission to copy, distribute and/or modify the library.

  To protect each distributor, we want to make it very clear that
there is no warranty for the free library.  Also, if the library is
modified by someone else and passed on, the recipients should know
that what they have is not the original version, so that the original
author's reputation will not be affected by problems that might be
introduced by others.

  Finally, software patents pose a constant threat to the existence of
any free program.  We wish to make sure that a company cannot
effectively restrict the users of a free program by obtaining a
restrictive license from a patent holder.  Therefore, we insist that
any patent license obtained for a version of the library must be
consistent with the full freedom of use specified in this license.

  Most GNU software, including some libraries, is covered by the
ordinary GNU General Public License.  This license, the GNU Lesser
General Public License, applies to certain designated libraries, and
is quite different from the ordinary General Public License.  We use
this license for certain libraries in order to permit linking those
libraries into non-free programs.

  When a program is linked with a library, whether statically or using
a shared library, the combination of the two is legally speaking a
combined work, a derivative of the original library.  The ordinary
General Public License therefore permits such linking only if the
entire combination fits its criteria of freedom.  The Lesser General
Public License permits more lax criteria for linking other code with
the library.

  We call this license the "Lesser" General Public License because it
does Less to protect the user's freedom than the ordinary General
Public License.  It also provides other free software developers Less
of an advantage over competing non-free programs.  These disadvantages
are the reason we use the ordinary General Public License for many
libraries.  However, the Lesser license provides advantages in certain
special circumstances.

  For example, on rare occasions, there may be a special need to
encourage the widest possible use of a certain library, so that it becomes
a de-facto standard.  To achieve this, non-free programs must be
allowed to use the library.  A more frequent case is that a free
library does the same job as widely used non-free libraries.  In this
case, there is little to gain by limiting the free library to free
software only, so we use the Lesser General Public License.

  In other cases, permission to use a particular library in non-free
programs enables a greater number of people to use a large body of
free software.  For example, permission to use the GNU C Library in
non-free programs enables many more people to use the whole GNU
operating system, as well as its variant, the GNU/Linux operating
system.

  Although the Lesser General Public License is Less protective of the
users' freedom, it does ensure that the user of a program that is
linked with the Library has the freedom and the wherewithal to run
that program using a modified version of the Library.

  The precise terms and conditions for copying, distribution and
modification follow.  Pay close attention to the difference between a
"work based on the library" and a "work that uses the library".  The
former contains code derived from the library, whereas the latter must
be combined with the library in order to run.

		  GNU LESSER GENERAL PUBLIC LICENSE
   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

  0. This License Agreement applies to any software library or other
program which contains a notice placed by the copyright holder or
other authorized party saying it may be distributed under the terms of
this Lesser General Public License (also called "this License").
Each licensee is addressed as "you".

  A "library" means a collection of software functions and/or data
prepared so as to be conveniently linked with application programs
(which use some of those functions and data) to form executables.

  The "Library", below, refers to any such software library or work
which has been distributed under these terms.  A "work based on the
Library" means either the Library or any derivative work under
copyright law: that is to say, a work containing the Library or a
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language.  (Hereinafter, translation is
included without limitation in the term "modification".)

  "Source code" for a work means the preferred form of the work for
making modifications to it.  For a library, complete source code means
all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control compilation
and installation of the library.

  Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope.  The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it).  Whether that is true depends on what the Library does
and what the program that uses the Library does.
  
  1. You may copy and distribute verbatim copies of the Library's
complete source code as you receive it, in any medium, provided that
you conspicuously and appropriately publish on each copy an
appropriate copyright notice and disclaimer of warranty; keep intact
all the notices that refer to this License and to the absence of any
warranty; and distribute a copy of this License along with the
Library.

  You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for a
fee.

  2. You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

    a) The modified work must itself be a software library.

    b) You must cause the files modified to carry prominent notices
    stating that you changed the files and the date of any change.

    c) You must cause the whole of the work to be licensed at no
    charge to all third parties under the terms of this License.

    d) If a facility in the modified Library refers to a function or a
    table of data to be supplied by an application program that uses
    the facility, other than as an argument passed when the facility
    is invoked, then you must make a good faith effort to ensure that,
    in the event an application does not supply such function or
    table, the facility still operates, and performs whatever part of
    its purpose remains meaningful.

    (For example, a function in a library to compute square roots has
    a purpose that is entirely well-defined independent of the
    application.  Therefore, Subsection 2d requires that any
    application-supplied function or table used by this function must
    be optional: if the application does not supply it, the square
    root function must still compute square roots.)

These requirements apply to the modified work as a whole.  If
identifiable sections of that work are not derived from the Library,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works.  But when you
distribute the same sections as part of a whole which is a work based
on the Library, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Library.

In addition, mere aggregation of another work not based on the Library
with the Library (or with a work based on the Library) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

  3. You may opt to apply the terms of the ordinary GNU General Public
License instead of this License to a given copy of the Library.  To do
this, you must alter all the notices that refer to this License, so
that they refer to the ordinary GNU General Public License, version 2,
instead of to this License.  (If a newer version than version 2 of the
ordinary GNU General Public License has appeared, then you can specify
that version instead if you wish.)  Do not make any other change in
these notices.

  Once this change is made in a given copy, it is irreversible for
that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy.

  This option is useful when you wish to copy part of the code of
the Library into a program that is not a library.

  4. You may copy and distribute the Library (or a portion or
derivative of it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you accompany
it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange.

  If distribution of object code is made by offering access to copy
from a designated place, then offering equivalent access to copy the
source code from the same place satisfies the requirement to
distribute the source code, even though third parties are not
compelled to copy the source along with the object code.

  5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library".  Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.

  However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library".  The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.

  When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library.  The
threshold for this to be true is not precisely defined by law.

  If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work.  (Executables containing this object code plus portions of the
Library will still fall under Section 6.)

  Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.

  6. As an exception to the Sections above, you may also combine or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.

  You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License.  You must supply a copy of this License.  If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License.  Also, you must do one
of these things:

    a) Accompany the work with the complete corresponding
    machine-readable source code for the Library including whatever
    changes were used in the work (which must be distributed under
    Sections 1 and 2 above); and, if the work is an executable linked
    with the Library, with the complete machine-readable "work that
    uses the Library", as object code and/or source code, so that the
    user can modify the Library and then relink to produce a modified
    executable containing the modified Library.  (It is understood
    that the user who changes the contents of definitions files in the
    Library will not necessarily be able to recompile the application
    to use the modified definitions.)

    b) Use a suitable shared library mechanism for linking with the
    Library.  A suitable mechanism is one that (1) uses at run time a
    copy of the library already present on the user's computer system,
    rather than copying library functions into the executable, and (2)
    will operate properly with a modified version of the library, if
    the user installs one, as long as the modified version is
    interface-compatible with the version that the work was made with.

    c) Accompany the work with a written offer, valid for at
    least three years, to give the same user the materials
    specified in Subsection 6a, above, for a charge no more
    than the cost of performing this distribution.

    d) If distribution of the work is made by offering access to copy
    from a designated place, offer equivalent access to copy the above
    specified materials from the same place.

    e) Verify that the user has already received a copy of these
    materials or that you have already sent this user a copy.

  For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it.  However, as a special exception,
the materials to be distributed need not include anything that is
normally distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies
the executable.

  It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system.  Such a contradiction means you cannot
use both them and the Library together in an executable that you
distribute.

  7. You may place library facilities that are a work based on the
Library side-by-side in a single library together with other library
facilities not covered by this License, and distribute such a combined
library, provided that the separate distribution of the work based on
the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:

    a) Accompany the combined library with a copy of the same work
    based on the Library, uncombined with any other library
    facilities.  This must be distributed under the terms of the
    Sections above.

    b) Give prominent notice with the combined library of the fact
    that part of it is a work based on the Library, and explaining
    where to find the accompanying uncombined form of the same work.

  8. You may not copy, modify, sublicense, link with, or distribute
the Library except as expressly provided under this License.  Any
attempt otherwise to copy, modify, sublicense, link with, or
distribute the Library is void, and will automatically terminate your
rights under this License.  However, parties who have received copies,
or rights, from you under this License will not have their licenses
terminated so long as such parties remain in full compliance.

  9. You are not required to accept this License, since you have not
signed it.  However, nothing else grants you permission to modify or
distribute the Library or its derivative works.  These actions are
prohibited by law if you do not accept this License.  Therefore, by
modifying or distributing the Library (or any work based on the
Library), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Library or works based on it.

  10. Each time you redistribute the Library (or any work based on the
Library), the recipient automatically receives a license from the
original licensor to copy, distribute, link with or modify the Library
subject to these terms and conditions.  You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties with
this License.

  11. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License.  If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Library at all.  For example, if a patent
license would not permit royalty-free redistribution of the Library by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Library.

If any portion of this section is held invalid or unenforceable under any
particular circumstance, the balance of the section is intended to apply,
and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices.  Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

  12. If the distribution and/or use of the Library is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Library under this License may add
an explicit geographical distribution limitation excluding those countries,
so that distribution is permitted only in or among countries not thus
excluded.  In such case, this License incorporates the limitation as if
written in the body of this License.

  13. The Free Software Foundation may publish revised and/or new
versions of the Lesser General Public License from time to time.
Such new versions will be similar in spirit to the present version,
but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number.  If the Library
specifies a version number of this License which applies to it and
"any later version", you have the option of following the terms and
conditions either of that version or of any later version published by
the Free Software Foundation.  If the Library does not specify a
license version number, you may choose any version ever published by
the Free Software Foundation.

  14. If you wish to incorporate parts of the Library into other free
programs whose distribution conditions are incompatible with these,
write to the author to ask for permission.  For software which is
copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this.  Our
decision will be guided by the two goals of preserving the free status
of all derivatives of our free software and of promoting the sharing
and reuse of software generally.

			    NO WARRANTY

  15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
LIBRARY IS WITH YOU.  SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

  16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.

		     END OF TERMS AND CONDITIONS

           How to Apply These Terms to Your New Libraries

  If you develop a new library, and you want it to be of the greatest
possible use to the public, we recommend making it free software that
everyone can redistribute and change.  You can do so by permitting
redistribution under these terms (or, alternatively, under the terms of the
ordinary General Public License).

  To apply these terms, attach the following notices to the library.  It is
safest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.

    <one line to give the library's name and a brief idea of what it does.>
    Copyright (C) <year>  <name of author>

    This library is free software; you can redistribute it and/or
    modify it under the terms of the GNU Lesser General Public
    License as published by the Free Software Foundation; either
    version 2.1 of the License, or (at your option) any later version.

    This library is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
    Lesser General Public License for more details.

    You should have received a copy of the GNU Lesser General Public
    License along with this library; if not, write to the Free Software
    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

Also add information on how to contact you by electronic and paper mail.

You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the library, if
necessary.  Here is a sample; alter the names:

  Yoyodyne, Inc., hereby disclaims all copyright interest in the
  library `Frob' (a library for tweaking knobs) written by James Random Hacker.

  <signature of Ty Coon>, 1 April 1990
  Ty Coon, President of Vice

That's all there is to it!
}}}

{{{
Copyright (c) 2005-2007 Rob Rohan

Permission is hereby granted, free of charge, to any person obtaining a 
copy of this software and associated documentation files (the "Software"), 
to deal in the Software without restriction, including without limitation 
the rights to use, copy, modify, merge, publish, distribute, sublicense, 
and/or sell copies of the Software, and to permit persons to whom the Software 
is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in 
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 
SOFTWARE.
}}}

Requires: Apache Xerces software. xml-apis.jar, xercesImpl.jar, resolver.jar

{{{
                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.
}}}

Basically, you need a system capable of running Eclipse (http://www.eclipse.org Eclipse 3.1 recommended, but it should run on older 3.x versions).

'''OS''': Mac OS X, Linux, AIX, HP/UX, Solaris or Windows.

'''RAM''': Somewhere in the gig range is good (But would probably run fine on 512MB).

'''Processor''': G4 or PIII or higher (But would probably run fine on a 500MHZ Celron too).

'''Java''': 1.5 (5.0) for snippets to work correctly and for the Image Viewer to work on Mac you need the latest Java (1.5.0_06). You can run just the editor Afae in the 1.4.x JVM however.

'''Screen Resolution''': 1024 x 768 (The larger the better)

----

For reference my system specs are:

'''OS''': Mac OS X 10.4.6 

'''Processor''': 1.33 GHZ PowerPC G4

'''RAM''': 1.25 GB

'''Java''': 1.5.0_06

'''Screen Resolution''': 1280 x 854

AppList is a simple program of Mac OS X that creates an HTML file out of the contents of your /Applications directory (complete with Application icons). The file can then be mailed around or posted to your blog.

It is quite common for people to have lists of their favorite Mac OS X applications on their blog, and this tool just makes that a bit easier.

AppList is written in Applescript and released under the Apple Public Source License.

!Download

[img[Download|assets/arrowdisk.png][http://robrohan.com/projects/download.php?file=AppList/AppList.dmg.zip]]

AppList uses the [[Git]] distributed source control program (the one the Linux kernel uses). To check out my version of the source code into your own distributed repository, use the following command after installing Git:

{{{
$ cd my_projects_folder
$ git clone http://robrohan.com/projects/AppList/repo/AppList.git
}}}

!Screenshots

[img[Shot 1|assets/AppList1.jpg.jpeg]]
[img[Shot 2|assets/TextMate.jpg.jpeg]]
[img[Shot 3|assets/TextEditList.jpg.jpeg]]

Ashpool is a lightweight XML Database written in Java™. It's goal is to use standard SQL92 syntax to query, add, update, and delete XML documents via a JDBC driver. The XML documents must hold to a table like structure. The reason for the table structure restriction is that SQL was designed to query table data not hierarchical data.

The Ashpool engine via JDBC drivers can be used to query any XML document; however, it is best used with documents that have a table like structure for the first three levels. The "column" section of the table structure can contain integer, float, string, dateTime or XML fragments. Ashpool can be used to search for XML documents inside of an XML document (for example, as a serialized bean store), or used as a lightweight relational database.

All the while Ashpool's "tables" are XML, so transmitting them over HTTP, running them through FOP, or editing them with a text editor are all possible - it other words you do not loose the power of XML.

Along with SQL, Ashpool also can use the Bean Scripting Framework to create stored procedures and scripts.

Not everything is roses though. Because Ashpool is querying XML, Ashpool can get slow when large amounts of information are involved. Ashpool uses SAX (unlike some other products) so it can handle somewhat larger documents then others, but do not expect Enterprise Database performance. Performance issues do not show their head unless you are using encrypted documents or the documents contain a "large" amount of data.

Ashpool defines a "table like structure" to mean an XML document like the following:

{{{
<any_root_node>
	<any_row_node>
		<column_node_a>data</column_node_a>
		<column_node_b/>
		[...]
	</any_row_node>
	[...]
</any_root_node>
}}}
			
where all <any_row_node> elements have the same named and number of child elements. If the 'column' being queried contains child nodes instead of simple data (int, string, dateTime, etc) the returned column contains the document fragment.

!Help

* [[Ashpool Users Guide]]
* [[Ashpool Command Guide]]

!Download

[img[Download|assets/arrowdisk.png][http://robrohan.com/projects/ashpool/Ashpool_036b2.zip]]

!Source

Source

This project uses the [[Git]] version control system. You can clone any of the repositories using the following:

{{{
$ git clone http://robrohan.com/projects/ashpool/repo/Ashpool.git
}}}

!Test Databases

Here are some test databases to play with. Simply unzip them and point Ashpool to the folders. For example, $./Ashpool.sh northwindXML.

* [[Northwind|http://robrohan.com/projects/download.php?file=ashpool/testdb/northwindXML.zip]] - the typical MS demo database in XML form (the demo one on Access and MSSQL)
* [[Factbook|http://robrohan.com/projects/download.php?file=ashpool/testdb/factbook.xml.gz]] - the CIA publishes facts about all the countries on earth. This is an XML version. (Note: this is a single xml file not a datastore)
* [[The King James Bible|http://robrohan.com/projects/download.php?file=ashpool/testdb/bible_kjv.tar.gz]]
* [[The Quran|http://robrohan.com/projects/download.php?file=ashpool/testdb/quran_shakir.tar.gz]]

!Archives

[[Ashpool_0.3.6b.zip|http://robrohan.com/projects/download.php?file=ashpool/archives/Ashpool_0.3.6b.zip]]

!Screenshot

[img[Shot 1|assets/commandline.png]]
[img[Shot 2|assets/SQuirreL.png]]
[img[Shot 1|assets/wincmd.png]]

BlogCFC Atom is an add on to [[Ray Camden's BlogCFC|http://ray.camdenfamily.com/projects/blogcfc]] that will allow you to use the [[Atom Publishing Protocol (atompub or APP)|http://www.ietf.org/html.charters/atompub-charter.html]] with your blog. This will allow you to use clients like [[Flock|http://www.flock.com/]] or [[Ecto|http://ecto.kung-foo.tv/]] to post entries to your blog.

See the readme.txt for more information and installation instructions.

!License
{{{
Copyright 2006 Rob Rohan

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
}}}
				
!Download

[[Git]] Repository Checkout:
{{{
$ git clone http://robrohan.com/projects/BlogCFCAtom/repo/BlogCFCAtom.git
}}}

[img[download|assets/arrowdisk.png][http://robrohan.com/projects/download.php?file=BlogCFCAtom/blogcfcatom_0.5beta_src.zip]]
[[Download blogcfcatom_0.5beta_src.zip||http://robrohan.com/projects/download.php?file=BlogCFCAtom/blogcfcatom_0.5beta_src.zip]]

!Howtos

[[Add blog to Flock|http://robrohan.com/projects/BlogCFCAtom/assets/addToFlock.mov]] (.mov 1.5 MB)
[[Add blog to Ecto|http://robrohan.com/projects/BlogCFCAtom/assets/addToEcto.mov]] (.mov 2.0 MB)

!Archives

[[blogcfcatom_0.4beta_src.zip|http://robrohan.com/projects/download.php?file=BlogCFCAtom/archives/blogcfcatom_0.4beta_src.zip]]
[[blogcfcatom_0.3beta_src.zip|http://robrohan.com/projects/download.php?file=BlogCFCAtom/archives/blogcfcatom_0.3beta_src.zip]]

!Screenshots

[img[Screen shot 1|assets/Flock_Mac.jpg.jpeg]]
[img[Screen shot 2|assets/ecto_mac.jpg.jpeg]]
[img[Screen shot 3|assets/ecto_windows.JPG.jpeg]]
[img[Screen shot 4|assets/flock_windows.JPG.jpeg]]

The Chinese Word Widget will show a new Chinese Word daily (or at least frequently). The word is shown in pinyin, simplified, and traditional characters. When you flip the widget over you can see the English translation so the widget can be used in a flash card like manner.

[img[Chinese words widget|assets/ChineseWidget.png][http://cn.robrohan.com]]

It's a fun tool if you are learning Chinese.

[[Download Chinese Word of the Day Widget|http://cn.robrohan.com]]

[[StartPage]]

[[Uml|http://robrohan.com/projects/demos/uml]]

[[Snoop|http://robrohan.com/projects/demos/snoop]]

9ne can be extended by using normal javascript functions. To add functions to the editor, just include new javascript files to the HTML file that start 9ne. Once the functions are in the same runtime enviroment, they can be called in a number of ways.

!The Run Command

The easiest way is to use ''run'' command. This is the key stroke that puts the focus on the MiniBuffer and allows you to simply type a function name to invoke it. For example, on Safari on Mac you would type ALT+X, type a function name, and then hit enter to run that function. If a function name has underscores in the name (run_my_command() for example) when typing the function a dash (-) should be used instead of an underscore. In addition hitting the space bar will automacially add the -. So in the previous example, you would type "ALT+X run my command", which would be displayed as "ALT+X run-my-command".

Any function in the 9ne runtime space can be invoked using this method. Simply include the javascript file with the extension functions, and use the run command to execute them.

!Key Bindings

You can also bind your extension functions to key strokes. Once you have your extension function included in the 9ne runtime, you add a key chord to the BINDINGS variable that specify what key stroke your function should be invoked with, and how to call your function. The keys are defined using the KeyBindingsFormat rules, and to call your function you'll need to use the function ''run_minibuffer_command''. Note that ''run_minibuffer_command'' takes the function name as a string, not as a function.

Here is an example of a key binding:

{{{
BINDINGS["CTRL+ALT+SHIFT+E"] = "run_minibuffer_command('RobsExampleExtension')";

function RobsExampleExtension(params) {
	this.cue = "Enter items in object form, like { A:1, B:2 }";
	
	for(i in params) {
		addStringToCurrentPosition(i + " ~> " + params[i]);
		editor_new_line();
	}
}
}}}

The bindings portion should be pretty clear, but I'd like to point out a few things about the function itself.

!Function Extras

It's often a good idea to write the extension functions in such a way to not need any parameters. This is not always possible however. goto_line for example requires the client to input the line number they wish to jump to.

When the function needs client input, you can attach a property to the function named ''cue'', and add a single parameter to the function. When the function is called the ''cue'' property is check for existence, and if it exists, the client is prompted for input using the text in the ''cue'' property.

Once the client fills in the cue dialog, the information is then passed to the function. 

!Including Functions Into The 9ne Runtime

Just to be clear, in the above paragraphs, when it says "include in the 9ne runtime" that simply means adding another <script src=""> to the 9ne.html document so that when 9ne is run, your extension functions are included.

The FTP Uploader widgets allows you to use drag and drop to upload a file to an FTP server. You can setup several FTP servers, and you don't need to buy anything to get it to work. The software is made available under the terms of the LGPL.

[img[FTP Widget|assets/ftp.png][http://robrohan.com/projects/download.php?file=widgets/Uploader.wdgt.zip]]

''Release 1.1:'' just optimizes some of the code, updates to Neuromancer 0.6.0, adds the version number to the widget, and fixes the password as text error.

''Release 1.2:'' added the ability to specify a default server by setting the variables in """PresetServerSetting""".js

!Download

[img[download|assets/arrowdisk.png][http://robrohan.com/projects/download.php?file=widgets/Uploader.wdgt.zip]]
[[Download FTP Widget|http://robrohan.com/projects/download.php?file=widgets/Uploader.wdgt.zip]]

!Help

* [[FTP Widget Server Setup]]
* [[FTP Widget Server Select]]
* [[FTP Widget Server Delete]]
* [[FTP Widget Default Server Setting]]

If you redistribute the widget, you may want to setup a server by default. For example, and ISP could pre-configure the widget to upload to a users home directory.

To setup a default server, view the widget code by right clicking the widget (or command click) and choose ''Show Package Contents''

Within that directory there is a file called """PresetServerSettings.js"""' - open this file in a text editor.

There are a few variables that can be set in this file. Here is the file contents:
{{{
//the nickname of the server (i.e. My Service)
var PRE_MARKNAME = "";
//the host (i.e. ftp.mysite.com)
var PRE_HOST = "";
//the target directory after login (i.e. htdocs/)
var PRE_TARGET = "";
//the user name to use for login
var PRE_USER = "";
//the password to use for login
var PRE_PASSWORD = "";
}}}

The variables should be self explanatory. Once they are set, the first time the widget is started these setting will be in effect. The client can, however, delete or edit the server setting in the normal way.

To delete a server do the following:

Click the (i) to flip the widget over

Highlight the server you wish to remove, and click the [-] button on the upper right.

Click Done

If you have more than one server setup for uploading, you can select which server the file gets up loaded to by doing the following:

Click the (i) to flip the widget over.

In the upper part of the widget, highlight the server you wish to upload to.

Click Done.

When the widget flips back over you'll see ''Server: [Server Name]'' at the top of the widget - where ''[Server Name]'' will be the server you've selected.

To setup a server, begin by clicking the (i) in the lower right hand corner of the widget (the i will become visible when your cursor enters the widget area).

After you click the (i) the widget will flip over to expose the widget settings. If you are setting up your first server, simply begin by filling out the form. If you are adding a second or third server click the [+] button on the upper right of the widget. Here is a brief description and example of what each field means:

''Name'': This is a name for the server. This is anything you'd like it to be. Any text that will help you remember this group of settings. For example, ''My Work Server'' or ''Blog Number 1''. The only rule is the name must be unique, you can not have two groups of settings named the same. After you have that filled out the Name field, hit TAB to go to the next field (the Server name will now appear in the list above)

''Host'': This is the FTP server address. It can either be in text form (ftp.host.com for example), or in IP form (192.168.1.333 for example). This setting should only be the server name without any """ftp://""" or path information. For example these are all '''incorrect'''

"""ftp://ftp.myhost.com"""

"""ftp://user@host:192.168.1.4/test/test"""

For those example """URIs""" you would put """ftp.myhost.com""" and "192.168.1.4" in the Host field and nothing more.

''Host Directory'': If after login you have to navigate to a subdirectory, enter the path here. For example, using """ftp://user@host:192.168.1.4/test/test""" the Host Directory would be "test/test". Often you'll have something like "www" or "main_html" on your account you'll want the files to upload to. If you want the files to upload into the main directory use "." for this setting.

''User Name'': is your account's user name

''Password'': is your accounts password

To get started with this blank TiddlyWiki, you'll need to modify the following tiddlers:
* SiteTitle & SiteSubtitle: The title and subtitle of the site, as shown above (after saving, they will also appear in the browser title bar)
* MainMenu: The menu (usually on the left)
* DefaultTiddlers: Contains the names of the tiddlers that you want to appear when the TiddlyWiki is opened
You'll also need to enter your username for signing your edits: <<option txtUserName>>

HexCalculator Widget - Hex Calculator Widget can do calculations in base 2, 10 and 16 with the most common features implemented. It has key bindings for most everything, and is designed to be a coder's calculator. It is based around a signed 32-bit integer.

[img[HexCalculator|assets/HexCalc.png][http://robrohan.com/projects/download.php?file=widgets/HexCalculator.wdgt.zip]]

''Release 1.5:'' UI overhaul. Updated the keybindings to use the command key instead of the ALT or option key (Sometimes the ALT key would fail to register).

[[Download HexCalculator Widget|http://robrohan.com/projects/download.php?file=widgets/HexCalculator.wdgt.zip]]

JUTest is a simple javascript unit testing / wild-wacky-idea-testing-out environment.

This movie might help explain:

<html>
<object width="425" height="344"><param name="movie" value="http://www.youtube.com/v/k5viu5CxGrU&hl=en&fs=1"></param><param name="allowFullScreen" value="true"></param><embed src="http://www.youtube.com/v/k5viu5CxGrU&hl=en&fs=1" type="application/x-shockwave-flash" allowfullscreen="true" width="425" height="344"></embed></object>
</html>

!Download

This project uses the [[Git]] version control system. You can clone any of the repositories using the following:

{{{
$ git clone http://robrohan.com/projects/JUTest/repo/JUTest.git
}}}

These are a few Java libraries I've written that I use in other projects. They are:

CryptoLibs
ImageLibs

However, they are not open source or available for download.

Must be specified in order of ''CTRL'' ''ALT'' and then ''SHIFT''

_GLOBAL_CANCEL_ will force any in-progress chord to abort. Note: You have to define the action for the stroke as well as mark it as global cancel

Define any chords beginnings by using the ''append_minibuffer_binding'' function. Note: if you want to build long chords you should define them in order.

When you have a chord and then a single note, you have to have a minibuffer message using the function ''minibuffer_message''.

Example:
{{{
var BINDINGS = {
	"_GLOBAL_CANCEL_":	"CTRL+G",
	
	"CTRL+X":		"append_minibuffer_binding('CTRL+X')",
	"CTRL+X CTRL+H":	"append_minibuffer_binding('CTRL+H')",
	
	"ENTER":		"editor_new_line()",
	"BACKSPACE":		"editor_backspace()",
	"TAB":			"keyWithRepeat(insert_tab); isdirty = true",
	"DEL":			"keyWithRepeat(delete_char); isdirty = true",
	"CTRL+E":		"end_of_line()",
	"UP":			"keyWithRepeat(previous_line);",
	"CTRL+F":		"keyWithRepeat(forward_char);",
	"RIGHT":		"keyWithRepeat(forward_char);",
	"CTRL+G":		"minibuffer_message('Quit'); leaveMiniBuffer()",
	
	"CTRL+X CTRL+F":	"run_minibuffer_command('find_file'); leaveMiniBuffer()",
	
	"CTRL+H T":		"find_file('texts/tutorial.txt'); minibuffer_message('Loading Tutorial...');",
	"CTRL+X CTRL+S":	"save();",
	
	/* example of long chord */
	"CTRL+X CTRL+H CTRL+S":	"alert('Long Chord!'); leaveMiniBuffer();"
};
}}}

The following are supported keys:
{{{
CTRL
ALT
SHIFT
A-Z
0-9
COMMA
PEROID
ENTER
BACKSPACE
TAB
DEL
UP
DOWN
LEFT
RIGHT
ESC
OPENBRACE
CLOSEBRACE
BACKSLASH
FORWARDSLASH
GRAVE
MINUS
EQUALS
SEMICOLON
QUOTE
F1
F2
F3
F4
F5
F6
F7
F8
}}}

Note: not all keys will work on all browsers / operating system combinations.

There are a few built in ways to launch and use 9ne. Some pass full control to 9ne, and some start 9ne, but hook into 9ne's callbacks to handle events.

What this means in practice is - you can either let 9ne load and save files / buffers of text, or you can load and save them yourself.

!Having 9ne Load Buffer Text

The two main ways to have 9ne control the buffer life cycle is with one of the two functions: ''lanuch9ne'' and ''launch9neWithTextarea''. The first of these functions will use XMLHttpRequest to GET a file form the server, and the second will link 9ne to a preexisting text area.

It it important to note that when 9ne loads a file with a GET request the file will be processed by the server. So, for example, if you load a PHP file with the ''launch9ne'' function no PHP statements will be in the file because it will have been processed by the server. You will only see the rendered information.

When linking to a text area, the text area is set to disabled until 9ne is closed.

!Controlling The Life Cycle Yourself

The more advanced, and powerful, way of loading text into 9ne is to do it yourself. With all the different security systems and loading styles this is often going to be the best bet for integrating 9ne.

When you control the life cycle yourself you'll want to open 9ne with the function ''launch9neWithHandle''. This function will return a pointer to the window 9ne opens and allow you to set your hooks. For example:

{{{
var hndl = launch9neWithHandle(615,620,'untitled');
}}}

Once you have a pointer to a 9ne window there are three functions you'll likely want to override: ''on9neStart'', ''on9neEnd'', and ''save''. These functions allow you to insert callback functions for when 9ne finishes loading, when the save function is called, and right before the window is closed.

When setting your callback functions, it is a good idea to pause for a few milliseconds because some browsers require a brief amount of time to actually create the window. Here is an example of launching a 9ne window and setting the main callbacks:

{{{
var hndl = launch9neWithHandle(615,620,'untitled');

//pause to make sure the window fully opens			
setTimeout(function(){
	hndl.on9neStart = function(){ 
		hndl.loadFile("test.php", hndl.guessFileType("test.php"), "test stuff\n more text\n <andstuff>"); 
		hndl.save = function(){ alert("save!") };
	};
			
	hndl.on9neEnd = function() { 
		if(hndl != null) {
			alert(hndl.buffer_name + " \n " + hndl.get_editor_text());
			hndl = null;
		}
	};
}, 500);
}}}

The above fragment set the text of 9ne using the ''loadFile'' 9ne function, it then sets it's own callback for when 9ne's ''save'' function is called. It then adds a callback for when the client quits 9ne and alerts the buffer name (file name) and the editors current text.

Using these callback functions you can set 9ne's startup text, perform your own save operations by using ''get_editor_text'', and provide any cleanup needed after 9ne has been closed.

[[9ne]]
[[Afae]]
[[AppList]]
[[Ashpool]]
[[BlogCFCAtom]]
[[Demos]]
[[JavaLibs]]
[[JUTest]]
[[Mvc]]
[[Neuromancer]]
[[PaperClip]]
[[PICKitBurner]]
[[PIConOSX]]
[[Sortie]]
[[Thoth]]
[[WebArchiveExtractor]]
[[Widgets]]
[[XiaoCiDian]]

<<closeAll>><<permaview>><<newTiddler>><<newJournal 'DD MMM YYYY'>><<saveChanges>><<slider chkSliderOptionsPanel OptionsPanel 'options »' 'Change TiddlyWiki advanced options'>>

"""MvCphp""" and """MvCasp""" are very simple, easy to understand frameworks for PHP and ASP. They are simple Model View Controller / Front Controller frameworks for small web applications. I use them for very simple sites that need a bit of modularity or have components I'll use in other projects.

These are not do-it-all full-on frameworks like """CakePHP""" or what have you, they are intended for simple single purpose sites like a landing page, standalone RSS feeder, or maybe an embedded device application.

The PHP version is released under the GPL (version 2), and the ASP version is in the public domain.

!Source

This project uses the [[Git]] version control system. You can clone any of the repositories using the following:

{{{
$ git clone http://robrohan.com/projects/mvc/repo/MvCasp.git
$ git clone http://robrohan.com/projects/mvc/repo/MvCphp.git
$ git clone http://robrohan.com/projects/mvc/repo/MvCphpTest.git
}}}

''Note:'' Neuromancer is being replaced with the project [[Sortie]]. If you are using Neuromancer, it is recommended you migrate to Sortie.

Neuromancer is a set of javascript libraries that provide a common interface between browsers and allow for javascript remoting (Ajax calls). The Neuromancer core is released under the LGPL license; however, some of the graphics libraries are under a different license. Unless otherwise noted in the source code (see the documentation), the libraries are under the LGPL.

Note For web service unmarshalling, 0.5.0Beta and higher require Coldfusion MX 7.0.1 (Merrimack) - they may work with any Axis 1.2 implementation but is untested.

!License

LGPL

This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version.

This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.

You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

!Download

[img[Download|assets/arrowdisk.png][http://robrohan.com/projects/download.php?file=neuromancer/releases/neuromancer_0.6.5.zip]]

!Help

* [[API|http://robrohan.com/projects/neuromancer/doc]]

Last Updated: 
Copyright © Rob Rohan
All Rights Reserved

If you own a USB PICKit 1 Flash Starter Kit (with firmware version 2), and you are trying to burn your HEX files to the board in Mac OS X, but can't find a program to do it with - your search is over.

[img[My PIC Kit|assets/Photo1.jpg.jpeg]]

Or, on the flip side, if you want to try your hand at programming PICs using Mac OSX, this tool chain works (as of Feb 28, 2008).

* HI-TECH's [[PICC-Lite C complier|http://microchip.htsoft.com/products/compilers/PICClite.php]]. Free.
* Microchip's [[Flash Starer Kit|http://www.microchipdirect.com/ProductDetails.aspx?Catalog=BuyMicrochip&Category=Getting%20Started%20Programmers&mid=1&treeid=6]]. Part Number: DV164101. $USD36.00.
* An Editor - I recommend [[TextMate (€39)|http://macromates.com/]], [[Afae (Free)|http://robrohan.com/projects/afae/]], or [[Aquamacs (Free)|http://aquamacs.org/]]
* This Application. Free.
!Features

* Finder integration. Double clicking a Hex file launches the burner application
* Reload before burn. When you click "Write", before it burns the Hex file to the board, the application will reload the hex file so you don't have to (for example, after a recompile)
* Cleaned up UI

!Known Issues

* Sometimes you have to click "Write" twice for burn to happen properly
* The "Verify" button doesn't work properly (don't bother using it)
* Currently Intel Macs Only. However you can use the older version on PPC
* Leopard (Mac OS 10.5) Only. Again, the older version should work if you need it on older systems

!Download

PICKit Burner uses the [[Git]] distributed source control program (the one the Linux kernel uses). To check out my version of the source code into your own distributed repository, use the following command after installing [[Git]]:

{{{
$ git clone http://robrohan.com/projects/PICKitBurner/repo/PICKitBurner.git
}}}

!Screenshots

[img[Screen shot 1|assets/PICKit%20BurnerScreenSnapz002.png]]
[img[Screen shot 2|assets/FinderScreenSnapz001.jpg.jpeg]]
[img[Screen shot 3|assets/PICKitBurnerScreenSnapz001.jpg.jpeg]]

I've been getting into PIC programming, and I like to use Mac OS X. While finding tools for PIC programming on OS X is getting easier, it's still kind of a pain to track down all the pieces for a good tool chain.

PIC on OS X is an attempt to gather all the basic tools into one place so anyone starting out with """PIC"""s on OS X wont have as hard a time as I did :)

I am focused on finding:

* Compiler and linker for C (and ASM)
* Program to program the chips over USB (using Microchip PICKit 1)
* A good IDE or Editor

Currently I am using (and therefore the tools are for) the Microchip PICKit 1 Flash Starter Kit (with firmware version 2)

!Download

The download contains (for PPC only):

* gputils. Compiler, linker, etc for making ASM files to HEX files.
* """UsbPicKit""".app. Program used to program the HEX files to the chips. You also might want to try http://ww1.microchip.com/downloads/en/DeviceDoc/pickit.tgz the official Microchip app that does the same thing.
* """PicExample""". An Example project for the Eclipse platform that has a build script that invokes the compiler.

[img[Download|assets/arrowdisk.png][http://robrohan.com/projects/download.php?file=PIConOSX/PIConOSX.dmg.zip]]

<!--{{{-->
<div id='header' class='header'>
<div class='headerShadow'>
<span class='searchBar' macro='search'></span>
<span class='siteTitle' refresh='content' tiddler='SiteTitle'></span>&nbsp;
<span class='siteSubtitle' refresh='content' tiddler='SiteSubtitle'></span>
</div>

</div>
<div id='mainMenu'>
<span refresh='content' tiddler='MainMenu'></span>
<span id='noticeBoard' refresh='content' tiddler='NoticeBoard'></span>

</div>
<div id='sidebar'>
<div id='sidebarOptions' refresh='content' tiddler='MochaSideBarOptions'></div>
<div id='sidebarTabs' refresh='content' force='true' tiddler='SideBarTabs'></div>
</div>
<div id='displayArea'>
<div id='messageArea'></div>
<div id='tiddlerDisplay'></div>
</div>
<div id='contentFooter' refresh='content' tiddler='contentFooter'></div>
<!--}}}-->

PaperClip is a simple operating system that I've been writing on and off for a few years. It's very basic, and currently just boots. One fun thing about it is it has a clean room implementation of the standard C library (about 60% complete).

[img[PaperClip Booting|assets/screen.jpg.jpeg]]

Simple regular expression tester. Useful when trying out regexs for Javascript code, and somewhat useful when trying to build regular expressions for other languages (like sed, ruby, or perl).

[img[Regex Widget|assets/regex.png][http://robrohan.com/projects/download.php?file=widgets/RegexWidget.wdgt.zip]]

The match area at the bottom shows the array of matches and the index. It is running the match through the Javascript code Array = String.match([your regex]).

''Release 1.7:'' Support for multiline regular expressions (for example ^[0-3]$), and made using the start and end "/" optional in the regex testing area.

''Release 1.6.1:'' There was a slight bug in the HTML fix. This fixes the fix.

''Release 1.6:'' Updated the matching area to better support HTML matches. HTML matches were rendering in the match window which is not likely what people want.

''Release 1.5:'' UI overhaul. The widget looks much nicer

!License

The software is made available under the terms of the LGPL. By downloading or using the software you agree to the terms of the LGPL.

!Download

[img[download|assets/arrowdisk.png][http://robrohan.com/projects/download.php?file=widgets/RegexWidget.wdgt.zip]]
[[Download Regex Widget|http://robrohan.com/projects/download.php?file=widgets/RegexWidget.wdgt.zip]]

Shakespearean-like insult generator. It is inspired by the site http://www.pangloss.com/seidel/Shaker/. This widget was a gift for my wife (it was her idea, and she asked me if I could write it for her).

[img[ShakeASpear|assets/shakeaspear.jpg.jpeg][http://robrohan.com/projects/download.php?file=widgets/ShakeASpear.wdgt.zip]]

ShakeASpear is made available under the terms of the LGPL so enjoy, you vain pottle-deep devil-monk.

[img[Download ShakeASpear|assets/arrowdisk.png][http://robrohan.com/projects/download.php?file=widgets/ShakeASpear.wdgt.zip]]
[[Download ShakeASpear|http://robrohan.com/projects/download.php?file=widgets/ShakeASpear.wdgt.zip]]

rob's wild ideas and software

[img[Rob Rohan dot com Lab|assets/RobRohan.comLogosm.png]] Rob's Lab

Sortie is a set of javascript libraries that provide a common interface between browsers and javascript libraries. While Sortie itself has built in libraries (such as XMLHttpRequest wrappers and some UI functions), it's goal is to allow the use of any libraries. Meaning you could use Spry widgets or Yahoo! widgets or fragments of the Dojo framework from within the same application. The interaction and inclusion of the libraries being control by Sortie.

All of Sortie's code is within the Sortie Namespace.

Sortie has a preprocessor that allows you to include javascript libraries from within javascript code, and also lets you set required dependencies from within your libraries. The dependency checker can check version as well as simply existence.

For example, to include libraries into your application on your main entry point you would use code like the following at the very top of the library file:

{{{
Sortie.Core.$({
     include:new Array(
         "Code/Util/Cookie.js",
         "Code/Util/Search.js"
     )
});
}}}
			
This would include those javascript files into the runtime. After the files are included, any library dependency checks are performed. You can register a dependency in your library by using code similar to the following:

{{{
Sortie.Core.$({
     require:new Array(
         { c:"Sortie.Util.Collections", v:"0.2"},
         { c:"Some.Other.Class" }
     )
});
}}}
			
Where c stands for Class and v stands for version (optional)

!Help

* [[API|http://robrohan.com/projects/sortie/doc/]]
* [[Current Build Unit Test|http://robrohan.com/projects/sortie/tests/]]

!Source

{{{
$ git clone http://robrohan.com/projects/sortie/repo/Sortie.git
}}}

''Welcome to my Lab!''

This is where I host most of my projects.  On the left is a list of all the projects I have attached to this wiki.  Feel free to peruse the projects and source code, use the search at the top of the page, are the tag / timeline listing on the right of the page.

/*{{{*/
/*Mocha TiddlyWiki Theme*/
/*Version 1.0*/
/*Design and CSS originally by Anthonyy, ported to TiddlyWiki by Saq Imtiaz.*/
/*}}}*/
/*{{{*/
 #contentWrapper{
margin: 0 3.4em;

			font-family: Lucida Grande, Tahoma, Arial, Helvetica, sans-serif; /* Lucida Grande for the Macs, Tahoma for the PCs */
font-size: 11px;
			line-height: 1.6em;
			color: #666;
}

.header {
 background: #fff; 
			padding-top: 10px;
			clear: both;

border-bottom: 4px solid #948979;
}

.headerShadow {	padding: 2.6em 0em 0.5em 0em; }

.siteTitle {
			font-family: 'Trebuchet MS' sans-serif;
			font-weight: bold;
			font-size: 32px;
			color: #CC6633;
			margin-bottom: 30px;
			background-color: #FFF;
}

.siteTitle a{color:#CC6633; border-bottom:1px dotted #cc6633;}

.siteSubtitle {
	font-size: 1.0em;
        display: block;
        margin: .5em 3em; color: #999999;
}

#mainMenu {
position:relative;
float:left;
margin-bottom:1em;
display:inline;
text-align:left;
padding: 2em 0.5em 0.5em 0em;
width:13em;
font-size:1em;
}

#sidebar{
position:relative;
float:right;
margin-bottom:1em;
padding-top:2em;
display:inline;

}

#displayArea {
	margin: 0em 17em 0em 15em;
}

.tagClear {clear:none;}

#contentFooter {background:#575352; color:#BFB6B3; clear: both; padding: 0.5em 1em;}

		
		#contentFooter a {
			color: #BFB6B3;
			border-bottom: 1px dotted #BFB6B3;
		}
		
		#contentFooter a:hover {
			color: #FFFFFF;
			background-color:#575352;
		}

		a,#sidebarOptions .sliderPanel a{
			color:#CC6714;
			text-decoration: none;
		}

		a:hover,#sidebarOptions .sliderPanel a:hover {
			color:#CC6714;
			background-color: #F5F5F5; 
		}

.viewer .button, .editorFooter .button{
	color: #666;
	border: 1px solid #CC6714;
}

.viewer .button:hover, 
.editorFooter .button:hover{
	color: #fff;
	background: #CC6714;
	border-color: #CC6714;
}

.viewer .button:active, .viewer .highlight,.editorFooter .button:active, .editorFooter .highlight{color:#fff; background:#575352;border-color:#575352;}


		#mainMenu a {
			display: block;
			padding: 5px;
			border-bottom: 1px solid #CCC;
		}

		#mainMenu a:link, #navlist a:visited {
			color:#CC6714;
			text-decoration: none;
		}
		
		#mainMenu a:hover {
			background: #000000 url(arrow.gif) 96% 50% no-repeat;
			background-color: #F5F5F5;
			color:#CC6714;
		}
		
		#mainMenu a:hover, #mainMenu a:active, #mainMenu .highlight, #mainMenu .marked {
			background: #000000 url(arrow.gif) 96% 50% no-repeat;
			background-color: #F5F5F5;
			color:#CC6714;
		}

#mainMenu span {position:relative;}

#mainMenu br {display:none;}

#sidebarOptions a {
			color:#999;
			text-decoration: none;
		}

#sidebarOptions	a:hover {
			color:#4F4B45;
			background-color: #F5F5F5;border:1px solid #fff;
		}

#sidebarOptions {line-height:1.4em;}

		.tiddler {
			padding-bottom: 40px;
			border-bottom: 1px solid #DDDDDD; 
		}
.title {color:#CC6633;}
.subtitle, .subtitle a { color: #999999; font-size: 1.0em;margin:0.2em;}
.shadow .title{color:#948979;}

.selected .toolbar a {color:#999999;}
.selected .toolbar a:hover {color:#4F4B45; background:transparent;border:1px solid #fff;}

.toolbar .button:hover, .toolbar .highlight, .toolbar .marked, .toolbar a.button:active{color:#4F4B45; background:transparent;border:1px solid #fff;}

 .listLink,#sidebarTabs .tabContents {line-height:1.5em;}
 .listTitle {color:#888;}

#sidebarTabs .tabContents {background:#fff;}
#sidebarTabs .tabContents .tiddlyLink, #sidebarTabs .tabContents .button{color:#999;}
#sidebarTabs .tabContents .tiddlyLink:hover,#sidebarTabs .tabContents .button:hover{color:#4F4B45;background:#fff}

#sidebarTabs .tabContents .button:hover, #sidebarTabs .tabContents .highlight, #sidebarTabs .tabContents .marked, #sidebarTabs .tabContents a.button:active{color:#4F4B45;background:#fff}

.tabSelected{color:#fff; background:#948979;}

.tabUnselected {
 background: #ccc;
}

 .tabSelected, .tabSelected:hover {
 color: #fff;
 background: #948979;
 border: solid 1px #948979;
padding-bottom:1px;
}

 .tabUnselected {
 color: #999;
 background: #eee;
 border: solid 1px #ccc;
padding-bottom:1px;
}

#sidebarTabs .tabUnselected { border-bottom: none;padding-bottom:3px;}
#sidebarTabs .tabSelected{padding-bottom:3px;}


#sidebarTabs .tabUnselected:hover { border-bottom: none;padding-bottom:3px;color:#4F4B45}

#sidebarOptions .sliderPanel {
	background: #fff; border:none;
	font-size: .9em;
}
#sidebarOptions .sliderPanel a {font-weight:normal;}
#sidebarOptions .sliderPanel input {border:1px solid #999;}

.viewer blockquote {
	border-left: 3px solid #948979;
}

.viewer table {
	border: 2px solid [[ColorPalette::TertiaryDark]];
}

.viewer th, thead td {
	background: #948979;
	border: 1px solid #948979;
	color: #fff;
}
.viewer pre {
	border: 1px solid #948979;
	background: #f5f5f5;
}

.viewer code {
	color: #2F2A29;
}

.viewer hr {
	border-top: dashed 1px #948979;
}

.editor input {
	border: 1px solid #948979;
}

.editor textarea {
	border: 1px solid #948979;
}

.popup {
	background: #948979;
	border: 1px solid #948979;
}

.popup li.disabled {
	color: #000;
}

.popup li a, .popup li a:visited {
	color: #eee;
	border: none;
}

.popup li a:hover {
	background: #575352;
	color: #fff;
	border: none;
}

.tagging, .tagged {
	border: 1px solid #eee;
	background-color: #F7F7F7;
}

.selected .tagging, .selected .tagged {
	background-color: #eee;
	border: 1px solid #BFBAB3;
}

 .tagging .listTitle, .tagged .listTitle {
	color: #bbb;
}

.selected .tagging .listTitle, .selected .tagged .listTitle {
	color: #666; 
}

.tagging .button, .tagged .button {
		color:#aaa;
}
.selected .tagging .button, .selected .tagged .button {
		color:#4F4B45;
}

.highlight, .marked {background:transparent; color:#111; border:none; text-decoration:underline;}

.tagging .button:hover, .tagged .button:hover, .tagging .button:active, .tagged .button:active {
		border: none; background:transparent; text-decoration:underline; color:#000;
}

h1,h2,h3,h4,h5 { color: #666; background: transparent; padding-bottom:2px; font-family: Arial, Helvetica, sans-serif; }
h1 {font-size:18px;}
h2 {font-size:16px;}
h3 {font-size: 14px;}

#messageArea {
	border: 4px solid #948979;
	background: #f5f5f5;
	color: #999;
        font-size:90%;
}

#messageArea a:hover { background:#f5f5f5;}

#messageArea .button{
	color: #666;
	border: 1px solid #CC6714;
}

#messageArea .button:hover {
	color: #fff;
	background: #948979;
	border-color: #948979;
}


* html .viewer pre {
	margin-left: 0em;
}

* html .editor textarea, * html .editor input {
	width: 98%;
}

.searchBar {float:right;font-size: 1.0em;}
.searchBar .button {color:#999;display:block;}
.searchBar .button:hover {border:1px solid #fff;color:#4F4B45;}
.searchBar input {			
                        background-color: #FFF;
			color: #999999;
			border: 1px solid #CCC;		margin-right:3px;
}

#sidebarOptions .button:active, #sidebarOptions .highlight {background:#F5F5F5;}

*html #contentFooter { padding:0.25em 1em 0.5em 1em;}

#noticeBoard {font-size: 0.9em; color:#999; position:relative;display:block;background:#fff; clear: both; margin-right:0.5em; margin-top:60px; padding:5px; border-bottom: 1px dotted #CCC; border-top: 1px dotted #CCC;}
#mainMenu #noticeBoard a,#mainMenu #noticeBoard .tiddlyLink {display:inline;border:none;padding:5px 2px;color:#DF9153 }
#noticeBoard a:hover {border:none;}	

#noticeBoard br {display:inline;}

#mainMenu #noticeBoard  .button{
	color: #666;
	border: 1px solid #DF9153;padding:2px;
}

#mainMenu #noticeBoard  .button:hover{
	color: #fff;
	background: #DF9153;
	border-color: #DF9153;
}

.searchbar {position:relative; width:11em;}
.searchbar .button{margin:0; width:11em;}
#header {display:inline-block;}
/*}}}*/

The following is a list of file types Afae supports. The list format is: language or format name and then a list of extensions for that type. The list is not in alpha order, so please use your browsers search function to see if a file format or extension is supported. If you do not see your language listed here, you can submit a bug to get support for the language built into Afae. If you are working on your own language see [[Add a language in Afae]] for instructions on how to add your own language or file format.

{{{
XQuery:
	xq
	xquery
	
Log:
	log

4gl:
	4gl

Actionscript:
	as

ada95:
	ada
	adb
	ads
	
Applescript:
	applescript
	scpt

ASP:
	asp
	asa
	aspx
	asax

Assembly-r2000:
	mips

Assembly-x86:
	asm
	inc
	dbg

Awk Scripts:
	awk

B:
	imp
	ref
	mch

Batch Scripts:
	bat

BBj:
	bbj
	

Beanshell:
	bsh

BibteX:
	bib

C:
	c
	h

COBOL:
	cbl
	cob

C++:
	cc
	cpp
	hh
	hpp
	cxx

C#:
	cs

CSS:
	css

DSSSL:
	dsl

Eiffel:
	e

FORTH:
	f
	4th

Foxpro:
	prg

Haskell:
	hs

HTML:
	html
	htm
	xhtml

IDL:
	idl

INI:
	ini
	reg

Java:
	java

Javascript:
	js

JHTML:
	jhtml

JMK:
	jmk 

JSP:
	jsp
	jsf
	jspf

Lisp:
	lisp
	lsp
	el

Makefile:
	Makefile
	mak

ML:
	sml
	ml

Modula3:
	i3
	m3

Netrexx: 
	nrx

Objective-c:
	m
	h

Objectrexx:
	rex
	orx

Occam:
	.icc

Omnimark:
	xom
	xin

Pascal:
	pas
	dpr
	dpk

Patch:
	diff
	patch

Perl:
	pl
	pm

PHP:
	php3
	php4
	php
	phtml

PL-SQL
	pls

Postscript
	ps
	eps

Povray
	pov
	povray

Prolog:
	pro

Progress:
	p
	i
	w
	f

Properties:
	properties
	props
	strings

Pvwave:
	jou

Python:
	py
	pyw

Rebol:
	r

RPM-spec:
	spec
	
Ruby (and Ruby on Rails):
	Rakefile
	rb
	rbw
	rake
	rhtml
	yml

Rview:
	rvw

Scheme:
	scm

SGML:
	sgml
	sgm

Shellscript:
	csh
	sh

SHTML:
	shtml
	shtm

Smalltalk:
	st
	sources
	changes

SQR:
	sqr
	sqc

TCL:
	tcl
	tsh

TEX:
	tex
	sty
	ltx

Texinfo:
	texi

Text:
	txt

Transact-SQL:
	sql

Visual Basic:
	vbs
	bas
	cls
	vb

Velocity:
	vm

Verilog:
	ver
	v

Vhdl:
	vh

XSLT:
	xsl
	xslt
	thx
	xdf

DTD:
	dtd
	mod

Flex:
	mxml

XML:
	project
	classpath
	xml
	xhtml
	config
	lzx
	plist
	xsd
	xmi
	wsdl
	rss
	resx
	rng
	ixml
	wsdd
	(modelglue)
	(mach-ii)
	
Apache Configuration:
	htaccess

GIF:
	gif

JPG:
	jpg
	jpeg

Bitmap:
	bmp

Icon:
	ico

Blog:
	blog

Coldfusion:
	cfml
	cfm
	cfc
}}}

The syntax files Afae uses are based on the JEdit format or Mode files. Afae does not support the full rule set that JEdit does.

!PROPS

The root element of the mode files is MODE. Within MODE the first element should be PROPS. You can define several PROPERTIES in the PRPOS section, but only ''commentStart'' and ''commentEnd'' are used at present. 

{{{
#!xml
<MODE>
	<PROPS>
		<PROPERTY NAME="commentStart" VALUE="=begin" />
		<PROPERTY NAME="commentEnd" VALUE="=end" />
	<PROPS>
	...
}}} 

These two properties control what characters are used when you use "Wrap text in a comment" (ctrl+c ctrl+k on the Mac).

!RULES

After the PROPS section there are one or more RULES sections. The RULES sections describe how to colorize the document. For example the following rule has a SPAN command to do HTML style comments:

{{{
#!xml
...
	<PROPS>
	
	<RULES IGNORE_CASE="TRUE">
		<SPAN TYPE="COMMENT1">
			<BEGIN>&lt;!--</BEGIN>
			<END>--&gt;</END>
		</SPAN>
		
		...
}}}

RULES can take several attribute parameters they are the following:

{{{
SET : [NAME] : Name used when referring to the rule from commands
HIGHLIGHT_DIGITS : [TRUE or FALSE] : Should this rule highlight digits
IGNORE_CASE : [TRUE or FALSE] : Should this rule ignore case
ESCAPE : [SINGLE CHAR] : A character that allows the rule to be escaped. For example \ in a C string "This is a \"quote\" in a quote"
DEFAULT : [PARTITION NAME] : The default color to make the partition, or blank for plain text
}}}

----

There are several commands that can be put into RULES. Each command will take at least a TYPE attribute that says what partition to use when the command is satisified. Here are the supported commands in Afae, and at the bottom of the page are the supported partition types.

!SEQ

The SEQ command allows you to define a group of characters for partitioning.

{{{
#!xml
<SEQ TYPE="OPERATOR">:</SEQ>
}}}

That defines the colon character to get the OPERATOR partition type.

{{{
AT_LINE_START : [TRUE or FALSE] :
* AT_WHITESPACE_END : [TRUE or FALSE] :
* AT_WORD_START : [TRUE or FALSE] :
TYPE
DELEGATE
}}}

!SPAN

The span rule allows you to define an area to apply a partition to. For example:

{{{
#!xml
<SPAN TYPE="COMMENT1">
	<BEGIN>(</BEGIN>
	<END>)</END>
</SPAN>
}}}

Defines an area between (), and says to apply the COMMENT1 partition type to the area. SPAN can also use a DELEGATE attribute to call a named RULE somewhere else in the file. When you do this the TYPE must be set to null. For example:

{{{
#!xml
<SPAN TYPE="NULL" DELEGATE="LITERAL">
	<BEGIN>(</BEGIN>
	<END>)</END>
</SPAN>
...
<RULES SET="LITERAL" DEFAULT="LITERAL1" ESCAPE="\">
	<SEQ TYPE="OPERATOR">:</SEQ>
</RULES>
}}}

That SPAN command uses the commands within the LITERAL rule set to do it's partitioning. It is important to note that Afae does not allow nested rule set jumping. Meaning that if a SPAN delegates to a RULES set, that RULES set cannot have a SPAN that also delegates to a different RULE set.

The SPAN command can take the following attributes:

{{{
TYPE : [PARTITION TYPE] 
AT_LINE_START : [TRUE or FALSE] : The span can only start at the beginning of a line
EXCLUDE_MATCH : [TRUE or FALSE] : The span should or should not include the markers in the coloring
NO_LINE_BREAK : [TRUE or FALSE] : Are newlines allowed with in the span
NO_WORD_BREAK : [TRUE or FALSE] : Are word breaks allowed within the span (only a space is a word break at present)
DELEGATE : [TRUE or FALSE] : Forward to another defined rule set
IGNORE_CASE : [TRUE or FALSE] : Should this rule ignore case (overrides the RULE setting)
ESCAPE : A string of chars that can be used to keep the span from ending (a list with no delimiters). A single char could be \ in a C string for example.
}}}

!MARK_FOLLOWING

'''MARK_FOLLOWING has been deprecated and should not be used. See SPAN_REGEXP'''

'''Warning''' MARK_FOLLOWING is buggy in the current release (0.9.98). It can cause the editor to fail to start and result in an error like:

{{{
java.lang.IllegalArgumentException: Argument not valid
at org.eclipse.swt.SWT.error(SWT.java:3358) at 
org.eclipse.swt.SWT.error(SWT.java:3297) at 
org.eclipse.swt.SWT.error(SWT.java:3268) at
...
}}}

//The only workaround at present is to not use the tag//

//The mark following command marks an area after the defined text. For example://

{{{
#!xml
<MARK_FOLLOWING TYPE="KEYWORD2" EXCLUDE_MATCH="FALSE">#</MARK_FOLLOWING>
}}}

//would use the KEWORD2 partition on everything after the # symbol.//

{{{
* AT_LINE_START : [TRUE or FALSE] :
* AT_WHITESPACE_END : [TRUE or FALSE] :
EXCLUDE_MATCH : [TRUE or FALSE] :
* AT_WORD_START : [TRUE or FALSE] :
TYPE : [NAME]
DELEGATE : [NAME]
}}}

!MARK_PREVIOUS

'''MARK_PREVIOUS has been deprecated and should not be used. See SPAN_REGEXP'''

{{{
#!xml
<MARK_PREVIOUS TYPE="LABEL" EXCLUDE_MATCH="TRUE" AT_LINE_START="TRUE">:</MARK_PREVIOUS>
}}}

{{{
* AT_LINE_START : [TRUE or FALSE] :
* AT_WHITESPACE_END : [TRUE or FALSE] :
EXCLUDE_MATCH : [TRUE or FALSE] :
* AT_WORD_START : [TRUE or FALSE] :
TYPE : [NAME]
DELEGATE : [NAME]
}}}

!EOL_SPAN

{{{
#!xml
<EOL_SPAN TYPE="KEYWORD2">#</EOL_SPAN>
}}}

{{{
TYPE : [PARTITION TYPE] 
AT_LINE_START : [TRUE or FALSE] : The span can only start at the beginning of a line
* EXCLUDE_MATCH : [TRUE or FALSE] : The span should or should not include the markers in the coloring
DELEGATE : Forward to another defined rule set
}}}

!SPAN_REGEXP

Regular expression rule. The regular expression must be anchored at both sides. Here it is anchored to the start of the string and ends at the first white space outside of a &gt; symbol. The IGNORE_CASE attribute is used only on the END part of the span.

The HASH_CHAR attribute is another anchor marker and is required. It is the single character that will cause this rule to fire. The character is repeated in the actual regular expression as seen in the example below. HASH_CHAR can take a string - each char in the string should be a char that fires off the rule. There can only be one SPAN_REGEXP HASH_CHAR per Rule set - meaning you can't have 2 SPAN_REGEXP that have the same HASH_CHAR value. 

EXCLUDE_MATCH will keep the END match from color coding. This is useful when the END is being used as a stabilizing anchor. 

{{{
#!xml
<SPAN_REGEXP HASH_CHAR="&lt;" TYPE="LITERAL1" AT_LINE_START="FALSE" 
	EXCLUDE_MATCH="FALSE" NO_WORD_BREAK="FALSE" IGNORE_CASE="TRUE">
	<BEGIN>^(&lt;[sS][cC][rR][iI][pP][tT] .*&gt;)\s</BEGIN>
	<END>&lt;/script&gt;</END>
</SPAN_REGEXP>
}}}

{{{
TYPE : [PARTITION TYPE] 
AT_LINE_START : [TRUE or FALSE] : The span can only start at the beginning of a line
EXCLUDE_MATCH : [TRUE or FALSE] : The span should or should not include the markers in the coloring
NO_LINE_BREAK : [TRUE or FALSE] : Are newlines allowed with in the span
NO_WORD_BREAK : [TRUE or FALSE] : Are word breaks allowed within the span (only a space is a word break at present)
DELEGATE : [TRUE or FALSE] : Forward to another defined rule set
IGNORE_CASE : [TRUE or FALSE] : Should this rule ignore case (overrides the RULE setting)
ESCAPE : A string of chars that can be used to keep the span from ending (a list with no delimiters). A single char could be \ in a C string for example.
}}}

!KEYWORDS

{{{
#!xml
...
<KEYWORDS IGNORE_CASE="FALSE">
	<KEYWORD1>auto</KEYWORD1>
	<KEYWORD2>asm</KEYWORD2>
	<KEYWORD3>char</KEYWORD3>	
	<LITERAL2>true</LITERAL2>
<KEYWORDS>
...
}}}

!PARTITION TYPES

{{{
NULL
COMMENT1
COMMENT2
LITERAL1
LITERAL2
LABEL
KEYWORD1
KEYWORD2
KEYWORD3
FUNCTION
MARKUP
OPERATOR
DIGIT
METHOD
}}}

* = Not fully implemented

Syntax coloring uses regular expressions and a style sheet. The rules are defined in a ''properties'' files. They are also not loaded by 9ne until they are needed. Meaning something has to start the mode call, then using Ajax the correct property file is loaded, and finally the rules are applied to the document.

There are four parts to a rule: the key, ''regex'', ''regexmod'', and ''replace''.

The key can be anything you'd like, but there can be only one key per mode.

The ''regex'' portion of the rule defines how the rule should find the thing it is supposed to color. It is important to note that these rules are applied one line at a time so there is no way at present to span multiple lines.

The ''regexmod'' are any modification parameters that should be used in the regular expression. For example, /[1bc]/text/ig. "ig" is the regexmod in that example.

''replace'' is an html fragment that will be used when the regex is found. This will often contains a back reference.

Example (the Javascript syntax file):
{{{
literal.regex=([\"\'].*?[\"\'])
literal.regexmod=ig
literal.replace=<span class='literal1'>$1</span>

keywords.regex=([\W])(function|var|for|if|while|do|new|case|switch|return|else)([\W])
keywords.regexmod=gm
keywords.replace=$1<span class='keyword1'>$2</span>$3

keywordsstart.regex=(^)(function|var|for|if|while|do|new|case|switch|return|else)(\W)
keywordsstart.regexmod=gm
keywordsstart.replace=<span class='keyword1'>$2</span>$3

keywordsend.regex=(\W)(function|var|for|if|while|do|new|case|switch|return|else)($)
keywordsend.regexmod=gm
keywordsend.replace=$1<span class='keyword1'>$2</span>

label.regex=([\W])(this|true|false|null)([\W])
label.regexmod=gm
label.replace=$1<span class='label'>$2</span>$3

comment.regex=(\/\/.*$)
comment.regexmod=gm
comment.replace=<span class='comment1'>$1</span>
}}}

There is also a mode to extension Map object that 9ne checks on file load.

{{{
var mode_ext_map = new Map();

mode_ext_map.put("html","HTML");
mode_ext_map.put("xhtml","HTML");
mode_ext_map.put("xml","XML");
mode_ext_map.put("rss","XML");
mode_ext_map.put("xsl","XML");
mode_ext_map.put("txt","Text");
mode_ext_map.put("js","Javascript");
mode_ext_map.put("css","CSS");
...
}}}

When 9ne loads a file, it checks the extension against the map keys, and if it finds a match it will call the function "[value_to_lowercase]_mode()" to handle the file type. For example, loading a file test.xhtml will automatically call the function "html_mode()". It will also display [value] in the status bar to show which mode is currently active.

Javascript and System terminal. In other words, it is an interactive javascript shell and a bash shell emulator. The javascript shell contains all of the Neuromancer libraries.

[img[Terminal Widget|assets/terminal.png][http://robrohan.com/projects/download.php?file=widgets/Terminal.wdgt.zip]]

''Release 1.1:'' Updated to the new Neuromancer 0.6.0 libraries, and added a PATH variable so when you are in system mode you no longer have to type the full path to the application. For example "ls -alFh" is no longer "/bin/ls -alFh". By default it looks in /usr/bin /usr/local/bin and /sbin for applications.

Thoth is a 2.3 and 2.4 servlet, that you can run in your favorite servlet container. It gives you the ability to use XSLT as a scripting language within web pages. Thoth can create HTML and PDF output on the fly from any XML (or no XML at all), and it can use XML as storage.

!Download

[img[Download|assets/arrowdisk.png][http://robrohan.com/projects/download.php?file=thoth/thoth_nightly.zip]]

!Source

[[Git]] Repository Download:

{{{
git clone http://robrohan.com/projects/thoth/repo/ThothServlet.git
}}}

!Screenshots

[img[Shot 1|assets/Jetty4Run.jpg.jpeg]]
[img[Shot 2|assets/BasicThothScript.jpg.jpeg]]
[img[Shot 3|assets/ThothWindows.jpg.jpeg]]

Download the XML Compiler, add the plugin, and then do the following:

1. Right click on the project and make sure ''XML Nature'' is on 

2. At the top of the file, use either 

{{{
#!xml
<!DOCTYPE modelglue SYSTEM "modelglue.dtd"> 
}}}

or 

{{{
#!xml
<!DOCTYPE modelglue PUBLIC "-//MODEL-GLUE COM//DTD MODEL-GLUE//EN" "modelglue.dtd">
}}}

I just made up the identifiers because there didn't seem to be a real one. I suppose the best one to use is the <!DOCTYPE modelglue SYSTEM "modelglue.dtd"> one as it'll likely never change.

{{{
$${DATE}
$${MONTH}
$${TIME}
$${DATETIME}
$${DAYOFWEEK}
$${CURRENTFILE} - Current file name (just the file)
$${CURRENTFOLDER} - Current folder (The path to the containing folder)
$${CURRENTPATH} - Current path (full file name)
$${CURRENTPRJPATH} - Just the folder
$${USERNAME} - Current user
$${MONTHNUMBER} - Month as a number
$${DAYOFMONTH} - Day of month as a number
$${DAYOFWEEKNUMBER} - Day of week (the week starts on Sunday)
$${DATETIME24} - DateTime24 - a 24 hour clock version of datetime.
$${YEAR} - Current year.
$${YEAR2DIGIT} - Current two digit year. 
}}}

WebArchive Extractor is a utility that can take Apple's WebArchive file format, and turn the file into a "normal" directory structure.

WebArchive files can be created by saving a web page in Safari (saving all the graphics, css, and images) or you can create one with TextEdit.

This utility's focus is on helping you to create simple HTML pages with images using TextEdit. For example, after you create a document with images in TextEdit, you can save the file as WebArchive, use this utility to convert the file into a directory structure, and then upload the extracted directory structure to a web server. This process can be used to create help files for web applications or very simple web sites.

[img[Universal Binary|assets/macuniversal20070611.gif]]

!Screenshots

[img[Shot 1|assets/Extractor2.jpg.jpeg]]
[img[Shot 1|assets/Extractor1.jpg.jpeg]]
[img[Shot 1|assets/Extractor3.jpg.jpeg]]

!Download

[img[Download|assets/arrowdisk.png][http://robrohan.com/projects/download.php?file=WebArchiveExtractor/WebArchiveExtractor.dmg.zip]]

!Source Code

To get the WebArchiveExtractor source, you'll need to use the free and open source git version control system. Once you have git installed, you can clone the repository by doing the following:

{{{
$ git clone http://robrohan.com/projects/WebArchiveExtractor/repo/WebArchiveExtractor.git
}}}

!Licenses & Contributors

This version of WebArchiveExtractor is forked from Vitaly Davidenko's Web Archive Extractor utility which can be found on Sourceforge.

Copyright 2006 Vitaly Davidenko (2006-10-12) Apple Public License
Copyright 2007 Rob Rohan (2007-09-18)
Icons Copyright:
TITLE:	Crystal Project Icons
AUTHOR:	Everaldo Coelho
SITE:	http://www.everaldo.com
CONTACT: everaldo everaldo com
Copyright (c) 2006-2007 Everaldo Coelho.
http://everaldo.com/crystal/?action=license

I also got some help from the great web site:
http://cocoadevcentral.com/

[[FTP Uploader Widget]]
The FTP Uploader widgets allows you to use drag and drop to upload a file to an FTP server.

[[Regex Widget]]
Simple regular expression tester.

[[Chinese Word Widget]]
The Chinese Word Widget will show a new Chinese Word daily 

[[ShakeASpear]]
Shakespearean-like insult generator.

[[HexCalculator Widget]]
Hex Calculator Widget can do calculations in base 2, 10 and 16 with the most common features implemented.

[[Terminal Widget]]
Javascript and System terminal.

小词典 (xiǎo cídiǎn) are a few a small Chinese to English dictionary applications that are powered by CC-CEDICT. There are currently two versions of the dictionary application - the Desktop version and the iPhone™ / iPod™ touch version.

[[小词典 Web Site|http://xiaocidian.com]]

[[TiddlyWiki|http://www.tiddlywiki.com]] © Osmosoft

//{{{
//This ensures that the footer sticks to the bottom of the screen when there are no tiddlers open. If that is not desirable, it can be deleted.
function setFooter() {
         if (document.getElementById && document.getElementById("contentFooter") ) {
            var windowHeight=findWindowHeight();
         if (windowHeight>0) {
            var contentHeight= document.getElementById('mainMenu').offsetHeight + document.getElementById("header").offsetHeight + document.getElementById("contentFooter").offsetHeight;
            var menu= document.getElementById('mainMenu');
            if (windowHeight-(contentHeight)>=0) {
               menu.style.position='relative';
               menu.style.marginBottom=(windowHeight-(contentHeight))+'px';
               }
            else {
                 menu.style.position='';
                 menu.style.marginBottom='';
                 }
            }
         }
}
window.onresize = function() {
  setFooter();
}

Story.prototype.refreshTiddler_footerhack=Story.prototype.refreshTiddler;
Story.prototype.refreshTiddler = function (title,template,force)
{    
var theTiddler = Story.prototype.refreshTiddler_footerhack.apply(this,arguments);
setFooter();
   return theTiddler;}

//}}}