jxv-users — List for JXV users

[Jxv-users] Re: Building and object instantiation

[Gal B. <ga...@be...>]

Hi Kevin.

That import is some old class that is no longer used. It should have been
deleted when I removed the class, my IDE must have a bug or something. I've
fixed this on CVS.

The feature you are talking about has allready been requested in the context
of loading instances from a cache. I have it implemented locally in my CVS
working copy. I've created an "instanciator" component which is used by all
JXV readers (except FlatReader which has it's own mechanism) to instanciate
objects. You can configure your own instanciator for your classes in the JXV
config file like this:

<instanciator:root xmlns:instanciator="http://jxv.sf.net/instanciator/"
config:category="my-classes" instanciator="my-instanciator-class"/>

The instanciator class should implement the
org.jxv.instanciator.Instanciator interface.

I wasn't going to check this stuff in yet, though it's stable, because I
didn't have a chance to update the docs yet. But to help you move on with
your application and hopefully give me some feedback I've checked it in.
Keep in mind that the docs aren't up to date yet, so if you have a question
about the new stuff ask me.

Regards
Gal

----- Original Message ----- 
From: "Kevin O'Neill" <ke...@ro...>
To: <jxv...@li...>
Sent: Friday, November 14, 2003 11:49 PM
Subject: [Jxv-users] Building and object instantiation

>Hey all.
>
>I've just tried checking out the latest code and building. I get the
>following:
>
>   [javac] symbol  : class DefaultSAXWriterDelegate
>   [javac] location: package sax
>    [javac] import org.jxv.template.sax.DefaultSAXWriterDelegate;
>    [javac]                             ^
>
>The reason for checking out the code was to look at changing the object
>instantiation. I need to connect some object instances to services when
>they are created. I manage my services via PicoContainer
>(http://www.picocontainer.org/). So my question is which class/es do I
>need to override to have bean object construction done via pico?
>
>-k.
>
>-- 
>If you don't test then your code is only a collection of bugs which
>apparently behave like a working program.
>
>Website: http://blogs.codehaus.org/people/kevin/
>Pub Key: http://blogs.codehaus.org/people/kevin/public.asc

[Jxv-users] Building and object instantiation

[Kevin O'N. <ke...@ro...>]

Hey all.

I've just tried checking out the latest code and building. I get the
following:=20

    [javac] symbol  : class DefaultSAXWriterDelegate
    [javac] location: package sax
    [javac] import org.jxv.template.sax.DefaultSAXWriterDelegate;
    [javac]                             ^

The reason for checking out the code was to look at changing the object
instantiation. I need to connect some object instances to services when
they are created. I manage my services via PicoContainer
(http://www.picocontainer.org/). So my question is which class/es do I
need to override to have bean object construction done via pico?

-k.

--=20
If you don't test then your code is only a collection of bugs which=20
apparently behave like a working program.=20

Website: http://blogs.codehaus.org/people/kevin/
Pub Key: http://blogs.codehaus.org/people/kevin/public.asc

[Jxv-users] JXV and Swing

[<ha...@id...>]

Hi,

I am considering the use of jxv for building Swing GUI's. The idea is
not having to write tons of Java code to instantiate all the standard
objects that make up a Swing GUI, from top to bottom, including frames,
toolbars, menubars, panels (incl. layout), buttons, etc. Note that I'm
NOT concerned about writing out XML again, just building the structure.

It would be nice to be able to instantiate all relevant classes using
either empty constructors or factories (which I know jxv handles) and be
able to use constant strings similar to static fields that are common
e.g. horisontal-when-needed for JScrollPane.HORISONTAL_WHEN_NEEDED.

Another feature I'm interested in is the possibility of using either an
attribute or an element for specifying a value e.g. color="Color.BLUE"
or <color>Color.BLUE</color>. This is very useful when writing XML by
hand, but complicates XML output (ambiguity).

A third complicating factor is the many constraints that appear in
Swing. Although most components are JComponents and hence can have
sub-components, it makes no sense to include a generic <components> tag,
since many JComponents constrain the number (e.g. JScrollPane,
JSplitPane) or the kinds (JFrame). Instead, the Swing method to call
when seeing an element like <panel> will depend in the containing
element (parent object).

Any ideas?

Hallvard

[Jxv-users] Checking that the list is working properly...

[Gal B. <ga...@be...>]