Re: JavaOne Session

[Vincent Hardy <vi...@eng.sun.com>]

Thierry,

OK, we can submit for both a BOF and a session. If things go well, we
will get both but there is also a possibility that we only get one.
I propose we make the submission next week. I will circulate a proposal.
V.

Thierry Kormann wrote:
> 
> 
> > As you may have heard, it is time for submission of JavaOne 2001 papers.
> > Batik would be a great topic to present at JavaOne and I think we should
> > present a paper. I suggest we present a paper collectively (there are
> > instances where there are multiple speakers on a single session).
> >
> > There are many things we could talk about. Here are two possible topics:
> >
> > a. Batik: SVG Graphics on the Java platform. What is Batik? What does it
> >    bring? Compare SVG to Java graphics (portable data/portable code).
> >    Discuss how the Java platform helped for the development. Discuss
> >    how the various imaging models helped...
> >
> > b. Batik: lessons learned from the trenches :-). Not so much on Batik
> >    itself, but more on the lessons we have learned doing the project.
> >    A kind of 'tips and tricks' session.
> 
> I am very motivated for both a JavaOne session and a BOF session. The session
> should be a good opportunity to show batik, fast graphics in java, XML and SVG
> (from an application, a Java plugin and why not a server side service).
> 
> The BOF could be (as always) a more technical session. We can present SVG,
> batik and some tips and tricks to do fast 2D graphics (dedicated to SVG?).
> 
> When can we work on the abstract? The first release of batik should be Dec.
> 4th. and the submission will end Dec. 1st.
> 
> I vote for a. (session).
> I vote for b. (BOF if possible)
> 
> Any plans?
> Thierry.
> 
> --
> Thierry Kormann
> email: Thierry.Kormann@sophia.inria.fr  http://www.inria.fr/koala/tkormann/
> Koala/Dyade/Bull @ INRIA - Sophia Antipolis
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: batik-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: batik-dev-help@xml.apache.org

Re: JavaOne Session

[Vincent Hardy <vi...@eng.sun.com>]

Thomas,

> Thomas wrote:
>
> My take on the two parts:
> 
>     I would tend to hype the XML aspect for the session: "Describe
> your whole e-commerice web-site with XML and have it translated with
> maximum fidelity to your clients capabilities" - fully buzz word
> compliant 'nonsense'.  While us coders tend to scoff at this sort of
> thing I think there is a lot to talk about here and the attendence at
> the day sessions seems to be increasingly dominated by 'IT' manager
> types.  So this should be our "target market" for the session.  Here
> we would focus more on Batik as a powerful tool for doing web
> graphics, in the context of a much larger system.
> 
>     The BOF tends to be the real coders, they want the details of what
> the architecture looks like, how data flows through the system, what
> we did to improve performance and decrease footprint.  Here we can
> focus on how Batik works, what pieces other groups might find useful,
> etc.  Perhaps talk about using Batik as a higher level imaging
> architecture/toolkit than Java2D.  Point out where/how Batik is
> designed for extension.  Basically try to recruit people into active
> Batik development.
> 
>
>     Opinions?

Yes. I like the focus you propose for the session and the BOF. I think 
it is a great idea to take a real-life example and show how Batik can be 
used. However, I think that if we chose to present that kind of topic,
we have to spend time implementing a demo that shows some of that, 
for example dynamic generation of advertisement using SVG and Batik.
In other words, we have to eat our own dog food and not just tell 
people they could do cool stuff with Batik.

Re: JavaOne Session

[Thomas E Deweese <th...@kodak.com>]

>>>>> "VH" == Vincent Hardy <vi...@eng.sun.com> writes:

VH> OK, we can submit for both a BOF and a session. If things go well,
VH> we will get both but there is also a possibility that we only get
VH> one.  I propose we make the submission next week. I will circulate
VH> a proposal.

    I'm also greatly in favor of doing a presentation for JavaONE.

    The real question I've been mulling over (and the reason I hadn't
replied yet) is how to do it without giving the audience whiplash.
There are serveral _really_ important parts to Batik (XML
parsing/handing, Event handling, Scripting language integration,
Filtering/Rendering, Interactive Rendering), each of which could be a
1 hr session (or the whole thing could be at least two 1hr sessions).

    This doesn't even begin to talk about neat things that people
could do with batik 'in the real world'...

    So I strongly support doing a BOF and a session, and I agree with
Thierry's proposal on making the Session focus on what tools like
Batik make possible, and the BOF be more how we did what we did and
what we learned from doing it.  The really hard part is going to be
figuring out what 5-10% of the total topic we want to present while
still sketching out the other 90% but still not leaving huge holes
(and now for something completely different...).

My take on the two parts:

    I would tend to hype the XML aspect for the session: "Describe
your whole e-commerice web-site with XML and have it translated with
maximum fidelity to your clients capabilities" - fully buzz word
compliant 'nonsense'.  While us coders tend to scoff at this sort of
thing I think there is a lot to talk about here and the attendence at
the day sessions seems to be increasingly dominated by 'IT' manager
types.  So this should be our "target market" for the session.  Here
we would focus more on Batik as a powerful tool for doing web
graphics, in the context of a much larger system.

    The BOF tends to be the real coders, they want the details of what
the architecture looks like, how data flows through the system, what
we did to improve performance and decrease footprint.  Here we can
focus on how Batik works, what pieces other groups might find useful,
etc.  Perhaps talk about using Batik as a higher level imaging
architecture/toolkit than Java2D.  Point out where/how Batik is
designed for extension.  Basically try to recruit people into active
Batik development.

    Opinions?