codaland
Saturday, March 15, 2003
       
htmlArea - Turn any 'textarea' into a WYSIWYG editor

htmlArea is a WYSIWYG editor replacement for any 'textarea' field. Instead of teaching your software users how to code basic HTML to format their content, they can use htmlArea to:
o Format text to be bold, italicized, or underlined.
o Change the face, size and colour.
o Left, centre, or right-justify paragraphs.
o Make bulleted or numbered lists.
o Indent or un-indent paragraphs
o Insert a horizontal line.
o Insert hyperlinks and images.
o Insert tables
o View the raw HTML source of what they're editing.

You can also create your own buttons to insert custom blocks of HTML code and images.

htmlArea is provided by interactivetools.com completely free.

Please note: because htmlArea is available for free, we can't provide any support. Post a question to our Forum if you're having a problem and someone may be able to help you there.
#




Tuesday, March 11, 2003
       
Sarissa Documentation
Sarissa is a JavaScript meta-API. It bridges the gap of DOM XML extentions between Internet Explorer and Mozilla (or Moz-based) browsers. It is an effort to provide a common interface for those extentions, bringing them closer to eachother. It was originally created to protect my sanity ;-)

Sarissa implements some of IE extentions for Mozilla. These are:

* The xml property, which gives the serialized XML String of a DOM Object.
* The HTMLElement.innerText property, which gives the text of a node with the tags stripped out
* The DOMDocument.async property, which controls synchronous/asynchronous loading of XML documents.

Sarissa provides some usefull, cross-browser factory methods

* The Sarissa.getDomDocument() method returns a DOM Document object
* The Sarissa.getXmlHttpRequest() method returns a XML HTTP Request object
* The Sarissa.setXslParameter() method manipulates XSLT parameters

Also, Sarissa adds the missing node-type constants of the Node interface (DOM 1 Core) to Internet Explorer. For example, if you include Sarissa in your page, the folowing will alert true...
#




Monday, March 10, 2003
       
Skaringa
S karinga is a framework for Java and XML language binding. Its core component is an Object Transformer, which is able to transform Java objects into XML documents and vice versa.
It consists of the parts:

* Serializer: Marshalls Java objects into XML documents.
* Deserializer: Creates Java objects from XML documents.
* XML schema generator: Generates XML schema definitions (XSD) from Java classes. The XML documents created by the serializer can be validated against those schemas.
* Transformer: Transforms Java objects of different types into each other by using XSLT instructions.

It is designed for simplicity, supporting a wide range of types, and speed.
#


       
Re: JUnit classloading [long]\
First, apologies to Scott for blogging in insufficient detail. Hopefully this post will be better. I intend to argue that

1. The "Ant classloader problem" is tricky but is mostly fixable without violating the class loader delegation model.

2. The "XML classloader problem" is caused by bad library design both in JAXP and the XML parsers and there is no way for class loading to cleanly undo the damage that these libraries inflict. I'll also propose a simple solution.

3. As far as the future of classloading is concerned, the XML issue is not a special case--it is the prototypical and important case.


Whew, thankfully I found this. Eric mentioned this a little while ago but I forgot to mark it. It's a real problem with Google doesn't index sites recently. This is why specialized search engines must exist.

From this message:

Here is what I believe any reliable custom classloader should do in loadClass(String name)....
#


       
Classpath Ordering (in Tomcat): Questions, and possible contrib.
I've been having a peek at the Tomcat main CVS branch in respect of its classloading behaviour. Apologies if I have missed any discussion - I have only just subscribed, and I did not find much in the tomcat-dev archives a couple of days ago.

It appears to me that ClassLoading is not quite right in a couple of respects ( ie. not working 'as advertised' ), and if you're willing, I'd like to have a go at a couple of patches for it.

Here's the list of things that I consider to be broken, based on the understandings that:
#


       
FastXMLDB
FastXMLDB is not an attempt to replace full featured servers such as Xindice. Rather, it allows the developer to quickly implement a native XML database with a very light weight implementation.

FastXMLDB does not support XPath querying, and currently, provides no persistence mechanism.
#


       
PERST: Simple, Fast, Convenient Object Oriented Database
PERST is just an embedded object-oriented database for applications that need to deal with persistent data. It is easy to use and provides high performance. The main advantage of PERST is its tight integration with the programming language. There is no gap between the database and application data models - PERST directly stores data in language objects. Thus, there is no need of packing/unpacking code, which has to be written for traditional relational databases. Unlike many other OODBMS, PERST does not require a special compiler or pre-processor. Yet, it is able to provide high level of transparency. The PERST API is convenient, flexible and easy to use. PERST is a very compact database - only 5 thousand lines of code and 50Kb of the resulting JAR (Java implementation). Its requirements of system resources are also very small. Moreover, PERST does not require any administration efforts whatsoever. Despite to its simplicity, PERST supports normal ACID transactions with very fast recovery after a runtime error.
#


       
J2ME Ant Tasks and MIME Types
Of course, if I were working on a project in a production situation, I would probably use Antenna, a collection of ant tasks for Ant 1.5.x that allows you to build, preverify, create JADs, and do all the other stuff that all the cool kids are doing. It's released under the LGPL.
#




blogroll:

winer
slashdot
javalobby
the server side
developerWorks
news.com
dotnet247
dotnet junkies
gotdotnet
sam gentile
sam ruby
paul prescod
.net guy
0xdecafbad
jon udell
john robb
dj's
rebelutionary
blogging roller
desktop fishbowl
servlets.com
cafe au lait
be blogging
kevin burton
paradox1x
james strachan
the truth is out there
brett morgan
blogging roller #2
joe's jelly
psquad's corner
zopen-x
rickard oberg
the saturn times
russel beattie
gerhard froelich
pete drayton
clemens vaster
weakliem
reinacker
drew
wagner
ingo rammer
ken rawlings
system.error.emit
tomas
simon fell
bit working
justin rudd
chris sells
john lam
jim murphy
brian jepson
john burkhardt
matt pope
better living through software
windley
caetano
kulchenko
loosely coupled
understanding software engineering
rest lst,rdf-interest lst,tag lst ucapi lst
archives:


A man, his puppy, and a double barreled shotgun.

Powered by Blogger