xngr-development

[xngr-dev] XElementType

[Vishal B. <vbh...@gm...>]

Hi everyone!

I got the latest code from HEAD for xngr module this morning and I
discovered that org.xngr.XElementType class has been completely removed. Now
I am getting compilation errors. Any clues as to why it was removed? Or am I
doing something wrong?

Cheers,
Vishal

Re: [xngr-dev] XElementType

[Vishal B. <vbh...@gm...>]

Sorry for the multiple posts. I found that XElementType.java was removed in
the last commit (6/28/07):

$ cvs log XElementType.java

RCS file: /cvsroot/xngr/xngr/src/org/xngr/Attic/XElementType.java,v
Working file: XElementType.java
head: 1.3
branch:
locks: strict
access list:
symbolic names:
        V011: 1.2
        V08: 1.2
        V06: 1.2
        V05: 1.1.1.1
        V02: 1.1.1.1
        Initial_V01: 1.1.1.1
        Cladonia: 1.1.1
keyword substitution: kv
total revisions: 4;     selected revisions: 4
description:
----------------------------
revision 1.3
date: 2007/06/28 13:14:19;  author: edankert;  state: dead;  lines: +2 -2
Clean up, removed dom4j, use generics and security manager stuff.
----------------------------
revision 1.2
date: 2002/08/19 20:08:09;  author: edankert;  state: Exp;  lines: +3 -3
Handle universal names without namespaces correctly. {}
----------------------------
revision 1.1
date: 2002/02/16 16:12:49;  author: edankert;  state: Exp;
branches:  1.1.1;
Initial revision
----------------------------
revision 1.1.1.1
date: 2002/02/16 16:12:49;  author: edankert;  state: Exp;  lines: +0 -0
Initial import
=============================================================================

Looks like it was removed by mistake. Also, I am not sure why dom4j.jar was
removed. I had to use a local copy of dom4j.jar to compile.

Cheers.

Re: [xngr-dev] XElementType

[Edwin D. <eda...@gm...>]

I'm sorry for the unexpected code changes but I wasn't aware that
people were using the current code, I have created a version tag
V101 for people that want to get the code for the 1.1 version.

I have started work on the new 2.0 version of the XML browser, this
will involve major changes to both the services APIs as the browser
part.

At the moment I have the following changes in mind:

The main idea of the XML browser will stay the same but the services
API will become simpler and will be more based on open standards,
using JAXP functionality instead of dom4j functionality.

The API will also look more like it does in eclipse with the use of
multiple extension-points and some of the terminology might also
change to be more in line with eclipse.

The idea is that people for version 2.0 of the XML browser can provide
any number of services but can also easily provide new browser
implementations.

I am planning to release 2 different browser implementations:
- one that allows users to browse and explore directories
- and one that allows to browse and bookmark xml documents

But it should also be easy enough to create a browser implementation
which is build into eclipse and one that allows to browse a xml database.
All these browsers (although not sure about the eclipse version yet)
should be able to use the same services.

This means that there will be 2 different APIs, one for Service providers
and one for Browser providers. I will try to get beta versions of these
new APIs ready as soon as possible to get some feedback.

This is currently still in design phase, so any suggestions are very
welcome.

Kind regards,
Edwin
-- 
http://www.edankert.com/