cvs commit: xml-site/targets/batik faqs.html

2001-12-18 Thread vhardy
vhardy  01/12/18 01:10:48

  Modified:targets/batik faqs.html
  Log:
  Reflects entry added by Thomas about MacOS X support.
  
  Revision  ChangesPath
  1.16  +35 -0 xml-site/targets/batik/faqs.html
  
  Index: faqs.html
  ===
  RCS file: /home/cvs/xml-site/targets/batik/faqs.html,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- faqs.html 2001/12/06 13:52:25 1.15
  +++ faqs.html 2001/12/18 09:10:48 1.16
  @@ -88,6 +88,9 @@
   fails on the org.w3c.xxx packages. What is happening?
   /A/LILIA href=#faq-24
   How do I checkout the latest CVS version of Batik?
  +/A/LILIA href=#faq-25
  +I'm using Mac OS X, and some of the SVG files I view are messed up 
(things
  +appear clipped or out of place).  What do I need to do to fix this?
   /A/LI/UL/BLOCKQUOTE/FONT/TD/TR/TABLE/DIVBRDIV 
align=rightTABLE border=0 cellpadding=0 cellspacing=0 
width=98%TRTD align=right height=7 valign=bottom width=9IMG 
border=0 height=7 hspace=0 src=resources/bar-top-left.gif vspace=0 
width=9/TDTD background=resources/bar-border-top.gifIMG border=0 
height=5 hspace=0 src=resources/void.gif vspace=0 width=1/TDTD 
align=left height=7 valign=bottom width=9IMG border=0 height=7 
hspace=0 src=resources/bar-top-right.gif vspace=0 
width=9/TD/TRTRTD background=resources/bar-border-left.gif 
width=9IMG border=0 height=1 hspace=0 src=resources/void.gif 
vspace=0 width=9/TDTD bgcolor=#0086b2 width=100%FONT 
color=#ff face=arial,helvetica,sanserif size=+1IMG border=0 
height=5 hspace=0 src=resources/void.gif vspace=0 
width=5BAnswers/B/FONT/TDTD 
background=resources/bar-border-right.gif width=9IMG border=0 
height=1 hspace=0 src=resources/void.gif vspace=0 
width=9/TD/TRTRTD align=right height=12 valign=top 
width=9IMG border=0 height=12 hspace=0 
src=resources/bar-bottom-left.gif vspace=0 width=9/TDTD 
background=resources/bar-border-bottom.gifIMG border=0 height=12 
hspace=0 src=resources/void.gif vspace=0/TDTD align=left 
height=12 valign=top width=9IMG border=0 height=12 hspace=0 
src=resources/bar-bottom-right.gif vspace=0 
width=9/TD/TR/TABLETABLE border=0 cellpadding=0 cellspacing=0 
width=98%TRTDFONT color=#00 face=arial,helvetica,sanserifA 
name=faq-1!--anchor--/ADIV align=rightTABLE border=0 
cellpadding=0 cellspacing=0 width=95%TRTD align=right height=7 
valign=bottom width=9IMG border=0 height=7 hspace=0 
src=resources/bar-top-left.gif vspace=0 width=9/TDTD 
background=resources/bar-border-top.gifIMG border=0 height=5 hspace=0 
src=resources/void.gif vspace=0 width=1/TDTD align=left height=7 
valign=bottom width=9IMG border=0 height=7 hspace=0 
src=resources/bar-top-right.gif vspace=0 width=9/TD/TRTRTD 
background=resources/bar-border-left.gif width=9IMG border=0 height=1 
hspace=0 src=resources/void.gif vspace=0 width=9/TDTD 
bgcolor=#0086b2 width=100%FONT color=#ff 
face=arial,helvetica,sanserifIMG border=0 height=5 hspace=0 
src=resources/void.gif vspace=0 width=5BWhat is 
Batik?/B/FONT/TDTD background=resources/bar-border-right.gif 
width=9IMG border=0 height=1 hspace=0 src=resources/void.gif 
vspace=0 width=9/TD/TRTRTD align=right height=12 valign=top 
width=9IMG border=0 height=12 hspace=0 
src=resources/bar-bottom-left.gif vspace=0 width=9/TDTD 
background=resources/bar-border-bottom.gifIMG border=0 height=12 
hspace=0 src=resources/void.gif vspace=0 width=1/TDTD align=left 
height=12 valign=top width=9IMG border=0 height=12 hspace=0 
src=resources/bar-bottom-right.gif vspace=0 
width=9/TD/TR/TABLETABLE border=0 cellpadding=0 cellspacing=0 
width=95%TRTDFONT color=#00 face=arial,helvetica,sanserif
   
   
  @@ -573,6 +576,38 @@
 P align=leftYou just have to follow the instructions posted on the
 A href=http://xml.apache.org/cvs.html;XML Apache CVS page/A.
 /P
  +
  +/FONT/TD/TR/TABLE/DIVBRA name=faq-25!--anchor--/ADIV 
align=rightTABLE border=0 cellpadding=0 cellspacing=0 
width=95%TRTD align=right height=7 valign=bottom width=9IMG 
border=0 height=7 hspace=0 src=resources/bar-top-left.gif vspace=0 
width=9/TDTD background=resources/bar-border-top.gifIMG border=0 
height=5 hspace=0 src=resources/void.gif vspace=0 width=1/TDTD 
align=left height=7 valign=bottom width=9IMG border=0 height=7 
hspace=0 src=resources/bar-top-right.gif vspace=0 
width=9/TD/TRTRTD background=resources/bar-border-left.gif 
width=9IMG border=0 height=1 hspace=0 src=resources/void.gif 
vspace=0 width=9/TDTD bgcolor=#0086b2 width=100%FONT 
color=#ff face=arial,helvetica,sanserifIMG border=0 height=5 
hspace=0 src=resources/void.gif vspace=0 width=5B
  +I'm using Mac OS X, and some of the SVG files I view are messed up 
(things
  +appear clipped or out of place).  What do I need to do to fix this?
  +/B/FONT/TDTD background=resources/bar-border-right.gif 
width=9IMG border=0 height=1 hspace=0 src=resources/void.gif 
vspace=0 

cvs commit: xml-site/targets/batik faqs.html

2001-12-18 Thread vhardy
vhardy  01/12/18 05:09:00

  Modified:targets/batik faqs.html
  Log:
  Added entry on Java Web Start problem on Mac OS X.
  
  Revision  ChangesPath
  1.17  +18 -0 xml-site/targets/batik/faqs.html
  
  Index: faqs.html
  ===
  RCS file: /home/cvs/xml-site/targets/batik/faqs.html,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -r1.16 -r1.17
  --- faqs.html 2001/12/18 09:10:48 1.16
  +++ faqs.html 2001/12/18 13:09:00 1.17
  @@ -91,6 +91,9 @@
   /A/LILIA href=#faq-25
   I'm using Mac OS X, and some of the SVG files I view are messed up 
(things
   appear clipped or out of place).  What do I need to do to fix this?
  +/A/LILIA href=#faq-26
  +I cannot run the Batik demo on Mac OS X (10.1.1). The Batik splash 
screen hangs.
  +What is happening?
   /A/LI/UL/BLOCKQUOTE/FONT/TD/TR/TABLE/DIVBRDIV 
align=rightTABLE border=0 cellpadding=0 cellspacing=0 
width=98%TRTD align=right height=7 valign=bottom width=9IMG 
border=0 height=7 hspace=0 src=resources/bar-top-left.gif vspace=0 
width=9/TDTD background=resources/bar-border-top.gifIMG border=0 
height=5 hspace=0 src=resources/void.gif vspace=0 width=1/TDTD 
align=left height=7 valign=bottom width=9IMG border=0 height=7 
hspace=0 src=resources/bar-top-right.gif vspace=0 
width=9/TD/TRTRTD background=resources/bar-border-left.gif 
width=9IMG border=0 height=1 hspace=0 src=resources/void.gif 
vspace=0 width=9/TDTD bgcolor=#0086b2 width=100%FONT 
color=#ff face=arial,helvetica,sanserif size=+1IMG border=0 
height=5 hspace=0 src=resources/void.gif vspace=0 
width=5BAnswers/B/FONT/TDTD 
background=resources/bar-border-right.gif width=9IMG border=0 
height=1 hspace=0 src=resources/void.gif vspace=0 
width=9/TD/TRTRTD align=right height=12 valign=top 
width=9IMG border=0 height=12 hspace=0 
src=resources/bar-bottom-left.gif vspace=0 width=9/TDTD 
background=resources/bar-border-bottom.gifIMG border=0 height=12 
hspace=0 src=resources/void.gif vspace=0/TDTD align=left 
height=12 valign=top width=9IMG border=0 height=12 hspace=0 
src=resources/bar-bottom-right.gif vspace=0 
width=9/TD/TR/TABLETABLE border=0 cellpadding=0 cellspacing=0 
width=98%TRTDFONT color=#00 face=arial,helvetica,sanserifA 
name=faq-1!--anchor--/ADIV align=rightTABLE border=0 
cellpadding=0 cellspacing=0 width=95%TRTD align=right height=7 
valign=bottom width=9IMG border=0 height=7 hspace=0 
src=resources/bar-top-left.gif vspace=0 width=9/TDTD 
background=resources/bar-border-top.gifIMG border=0 height=5 hspace=0 
src=resources/void.gif vspace=0 width=1/TDTD align=left height=7 
valign=bottom width=9IMG border=0 height=7 hspace=0 
src=resources/bar-top-right.gif vspace=0 width=9/TD/TRTRTD 
background=resources/bar-border-left.gif width=9IMG border=0 height=1 
hspace=0 src=resources/void.gif vspace=0 width=9/TDTD 
bgcolor=#0086b2 width=100%FONT color=#ff 
face=arial,helvetica,sanserifIMG border=0 height=5 hspace=0 
src=resources/void.gif vspace=0 width=5BWhat is 
Batik?/B/FONT/TDTD background=resources/bar-border-right.gif 
width=9IMG border=0 height=1 hspace=0 src=resources/void.gif 
vspace=0 width=9/TD/TRTRTD align=right height=12 valign=top 
width=9IMG border=0 height=12 hspace=0 
src=resources/bar-bottom-left.gif vspace=0 width=9/TDTD 
background=resources/bar-border-bottom.gifIMG border=0 height=12 
hspace=0 src=resources/void.gif vspace=0 width=1/TDTD align=left 
height=12 valign=top width=9IMG border=0 height=12 hspace=0 
src=resources/bar-bottom-right.gif vspace=0 
width=9/TD/TR/TABLETABLE border=0 cellpadding=0 cellspacing=0 
width=95%TRTDFONT color=#00 face=arial,helvetica,sanserif
   
   
  @@ -608,6 +611,21 @@
 with the document enough it will often 'fix' it's self for a while, 
 then after a while it will go back to being broken (this makes me
 think the problem may be some sort of race condition in the JVM)./P
  +
  +/FONT/TD/TR/TABLE/DIVBRA name=faq-26!--anchor--/ADIV 
align=rightTABLE border=0 cellpadding=0 cellspacing=0 
width=95%TRTD align=right height=7 valign=bottom width=9IMG 
border=0 height=7 hspace=0 src=resources/bar-top-left.gif vspace=0 
width=9/TDTD background=resources/bar-border-top.gifIMG border=0 
height=5 hspace=0 src=resources/void.gif vspace=0 width=1/TDTD 
align=left height=7 valign=bottom width=9IMG border=0 height=7 
hspace=0 src=resources/bar-top-right.gif vspace=0 
width=9/TD/TRTRTD background=resources/bar-border-left.gif 
width=9IMG border=0 height=1 hspace=0 src=resources/void.gif 
vspace=0 width=9/TDTD bgcolor=#0086b2 width=100%FONT 
color=#ff face=arial,helvetica,sanserifIMG border=0 height=5 
hspace=0 src=resources/void.gif vspace=0 width=5B
  +I cannot run the Batik demo on Mac OS X (10.1.1). The Batik splash 
screen hangs.
  +What is happening?
  +/B/FONT/TDTD background=resources/bar-border-right.gif 
width=9IMG border=0 height=1 hspace=0 

Re: Forrest (a.k.a. xml.apache.org 2.0)

2001-12-18 Thread Sam Ruby

Stefano Mazzocchi wrote:

 Log scanner
 ===

 The log scanner is a set of scripts that scan the logs from the CVS, the
 mail lists and the web site to gather information on:

I volunteer.

 Build system
 

 The goal is to have the system running completely autonomous: this
 follows the Gump approach. [Sam, I'll need your help here, since I don't
 have an account on nagoya]

You got it.

 Just like Gump which is not a subproject on its own, Forrest doesn't
 deserve that status neither as long as it remains a single-man show (and
 my experience tells me it will very likely remain so if the above goals
 are met)

We are already up to two.  I'd like to see the build system build upon Gump
(let me rephrase that: since I'm volunteering, the build system *WILL*
build upon Gump).  Perhaps Gump itself didn't have enough technical
critical mass to become a project, but perhaps Forrest+Gump does.

- Sam Ruby


-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail:  [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: Forrest (a.k.a. xml.apache.org 2.0)

2001-12-18 Thread David Crossley

Stefano Mazzocchi wrote:

 3) layout
 -
 
 The layout previously proposed on this list was a solution to the speed
 problem but I couldn't adapt it to the depth needs identified in the
 rest of the goals.
 
 So, I resurrected my rusty web design skills and came up with the layout
 you find attached. I've tested it on IE 5.5, NS 4.78 and Moz 0.9.5 on
 win2k. 
 
 Feedback, suggestions and criticisms are appreciated.

This is really great that you have taken this on Stefano,
many thanks. We will all help where we can.

I used View source to look behind-the-scenes and i see
that there are still tables embedded within tables embedded
within other tables. I think that this will again lead to troubles
on some browsers with the larger documents.

I realise that there may be a need to use one table to achieve
the left-hand columns. However, i would like us to minimise the
need for embedded tables, especially in the main text panel.

--David Crossley

-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail:  [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: UDDI Server

2001-12-18 Thread Vivek Chopra

A correction Jason. UDDI4J V1 was developed by IBM,
however UDDI4J V2 (hosted at www.uddi4j.org) has
had code contributions from both IBM and HP. UDDI4J
is an open source project available under the
IBM Open Source licence.

- Vivek

 Jason Rutherglen wrote:
 
  Ok,
 
  JUDDI is good.  The main think that is really
 lacking from these projects
  such as JUDDI is the database connection.  The
 UDDI XML to Java object code
  can be obtained from IBM's UDDI4J.  Then there
 just needs to be made the
  objects that will go into the database and that is
 really the architecture.
  Then the 3rd remaining piece is to define a set of
 access control APIs for
  the methods on the UDDI service.  I think this
 would wrap up the project,
  and of course it would evolve.  That was my plan
 anyways.  The details are
  in the access control interface and the EJB
 modeling.  UDDI4J has the UDDI
  translation pieces.  This is about what JUDDI does
 as well.  I would rather
  use UDDI4J because IBM is maintaining it.
 
  Jason
 
  - Original Message -
  From: Davanum Srinivas [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Sent: Wednesday, December 12, 2001 4:05 PM
  Subject: Re: UDDI Server
 
   Jason,
  
   There is interest for such a project, but we
 need to begin
  somewhereFor a start do you have a
   codebase (public?) that we can take a look at?
 If not, Can you please take
  a look at JUDDI
   (http://sourceforge.net/projects/uddi/) and see
 what's missing etc?
  
   Thanks,
   dims
  
   --- Jason Rutherglen [EMAIL PROTECTED] wrote:
I would like to propose an XML Apache project.
  A Java UDDI Server,
  written to talk to a
relational database (MySQL, Oracle, etc)
 possibly with EJBs, that also
  has security hooks and
integrates with Apache SOAP or Apache AXIS,
 and uses Xerces.  Anyone
  interested in working on
such a project?
   
Thanks,
   
Jason
   
  
  
   =
   Davanum Srinivas - http://jguru.com/dims/
  
  
 __
   Do You Yahoo!?
   Check out Yahoo! Shopping and Yahoo! Auctions
 for all of
   your unique holiday gifts! Buy at
 http://shopping.yahoo.com
   or bid at http://auctions.yahoo.com
  
  

-
   In case of troubles, e-mail:
 [EMAIL PROTECTED]
   To unsubscribe, e-mail: 
 [EMAIL PROTECTED]
   For additional commands, e-mail:
 [EMAIL PROTECTED]
  
 
 

-
  In case of troubles, e-mail:
 [EMAIL PROTECTED]
  To unsubscribe, e-mail: 
 [EMAIL PROTECTED]
  For additional commands, e-mail:
 [EMAIL PROTECTED]
 
 
 
  begin:vcard 
 n:Najmi;Farrukh
 tel;work:781-442-0703
 x-mozilla-html:FALSE
 url:www.sun.com
 org:Sun Microsystems;Java Software
 adr:;;1 Network Dr. MS
 BUR02-302;Burlington;MA;01803-0902;USA
 version:2.1
 email;internet:[EMAIL PROTECTED]
 fn:Farrukh Najmi
 end:vcard
 
 
-
 In case of troubles, e-mail:
 [EMAIL PROTECTED]
 To unsubscribe, e-mail: 
 [EMAIL PROTECTED]
 For additional commands, e-mail:
[EMAIL PROTECTED]


=
email: [EMAIL PROTECTED]
web  : http://www.soaprpc.com

__
Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of
your unique holiday gifts! Buy at http://shopping.yahoo.com
or bid at http://auctions.yahoo.com

-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail:  [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: [POLL] WASP Lite on Apache?

2001-12-18 Thread Davanum Srinivas

Anne,

It's been over a month since we heard from you on WASP-Lite(Java). Can you please let 
us know
about your latest position on the proposal? 

http://marc.theaimsgroup.com/?t=10056072667r=1w=2

Thanks,
dims


=
Davanum Srinivas - http://jguru.com/dims/

__
Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of
your unique holiday gifts! Buy at http://shopping.yahoo.com
or bid at http://auctions.yahoo.com

-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail:  [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: Forrest (a.k.a. xml.apache.org 2.0)

2001-12-18 Thread Theodore W. Leung

On Sun, 2001-12-16 at 13:33, Stefano Mazzocchi wrote:
 [sorry for cross-post: this is a general issue, but I'd like the cocoon
 people to know what I'm doing so that they might give me a hand :)]
 
 I started the effort that will, hopefully, bring us a much more useful
 documentation system for xml.apache.org and, hopefully, to the entire
 ASF, even if political and ego obstacles will get in the way.
 
 I personally don't care: this effort is mainly to create a better
 documentation infrastructure following the goals outlined below. I
 started the Cocoon project three years ago exactly for this reason and
 now that has all the features I needed, I think I can attack the problem
 from a very wide angle. 
 
 The site building system will be targetted toward xml.apache.org, but
 I'll keep a very broad perspective, making it possible to adapt the
 system to other apache.org projects with very few changes.
 
 BIG DISCLAIMER: however, whether this happens or not, I personally don't
 care. For sure, don't count on me wasting my time on fighting about 'my
 DTD is better than yours' or 'my system is
 faster/smaller/cleaner/easier-to-use/more-extensible than yours'.
 
 I'll come up with a system that works and then you guys will vote on
 what to do. I consider this an exercise to present full Cocoon
 potentials (that, objectively, beat the pants out of all the other
 systems used around Apache) but nothing more than this.
 
 - o -
 
 Ok, now that I stated this, let's get into the effort goals.
 
 GOALS
 -
 
 1) Speed: current xml.apache.org is slow. Empirical studies on learning
 processes indicate that if a page takes more than 10 seconds on a 56Kbs
 modem, the cognitive experience is degrated.
 
 2) Coherence: current xml.apache.org is extremely incoherent. Again,
 it's easy to understand that lack of coherence between subprojects docs
 is perceived (and sometimes reflects!) lack of cooperation.
 
 3) Navigation: the navigation experience on current xml.apache.org is a
 nightmare. There is no way to perceive the basic elements of spatial
 navigation: where am I? where can I go? how do I go back? how do I go
 there?
 
 4) Depth: the current xml.apache.org page layout forces a flat hierarchy
 of levels. The current Cocoon documentation somewhat extends this, but
 the visual look doesn't reflect the notion. Visual codes are extremely
 important to allow a easy and immediate navigation even at the deepest
 level.
 
 5) Usefulness: xml.apache.org contains powerful software but it's not
 powerful in itself. It should be a window on the information useful for
 both users and developers, along with friendly behavior, such as
 print-friendly versions of the single pages and of the whole
 per-subproject documentation, pagination of long articles,
 site-restricted search, graphs of project-related data and so on.
 
 6) Simplicity: xml.apache.org is done by volunteers, on all levels.
 Nobody is directly paid to do this. Not even myself. So, if the above
 goals are met, but the system is not simple and immediate to use for
 those who have to maintain and update the information, the result is
 void over a short period of time.
 
 7) Extensibility, Flexibility, Modularity: web sites, just as software,
 are living entities that adapt on their environment. The build system
 must not restrict the ability to evolutionary extend the information
 architecture.
 
 8) URI Solidity and Future Compatibility: URIs are contracts between the
 publisher and the user. Human users have the ability to estimate the
 long-term validity of these contracts and 'route around' eventual broken
 links, while machine users do not. The goal is to come up with a system
 that allows to generate a web site with strong URIs.
 
 
 Design Decisions
 
 
 staticity: even if I think that the availability of a dynamic publishing
 system would be beneficial, considering the web site load, the load of
 the apache machines and the state of the JVM for FreeBSD and the
 political problems behind all this, it's *must* easier (at least for
 now) to have a static version of the site batch-produced and then placed
 into the web-serving space.
+1
 automaticity: the site will be automatically generated out of files
 stored into CVS. The idea is to have GUMP-like nagging features that
 send email to the various mail lists using XML validation to estimate
 the 'integrity' of the docs placed.
+1
 For this reason, in honor of Sam Ruby's great work, and for the
 resonation with 'forest', thus a huge number of trees (i.e. XML files),
 I call this effort Forrest.
 
 I believe that together, Forrest and Gump, will help bringing apache
 quality one step up (moreover, as in the name, forrest wraps gump and
 will publish its generated data, providing more overall coherence)
 
 - o -
 
 separation of concerns
 --
 
 There are three concern islands, here is a list of their 

Re: Forrest (a.k.a. xml.apache.org 2.0)

2001-12-18 Thread giacomo

On Sun, 16 Dec 2001, Stefano Mazzocchi wrote:

I have some experience in using cocoon to generate html sites and pdf
books with full validation turned on. So I might be of help in this
concern (yes, cocoon is able to do that out of the box with support for
CATALOG mappings to overcome the hassle of SystemID pointing into the
file system instead of using  http URLs).

Another point is (yes, guys, it comes again) shouldn't we move to a
more official DTD for our docs? The Avalon project already has parts
of their documents written in DocBook as well as XSLT stylesheets to

1. transform DocBook to html and pdf (addmittedly only a subset
   of DocBook)
2. convert the cocoon DTDs you've mentioned somewhere below
   to the DocBook DTD (for legacy reasons :).

In a documentation build system based on cocoon I'm using I've choosen
an evolutionary approach to support various DocBook elements by adding a
XSLT template like this:

 xsl:template match=node() priority=.-1
   xsl:message
 THE ELEMENT xsl:value-of select=name(.) ISN'T YET SUPPORTED
   /xsl:message
   xsl:copy
 xsl:apply-templates/
   xsl:copy
 /xsl:template

 xsl:template match=@* priority=-1
   xsl:copy
 xsl:apply-templates/
   xsl:copy
 /xsl:template

These templates lead to show during the build process each element used
in the xdocs without explicit support made available.

Giacomo

 [sorry for cross-post: this is a general issue, but I'd like the cocoon
 people to know what I'm doing so that they might give me a hand :)]

 I started the effort that will, hopefully, bring us a much more useful
 documentation system for xml.apache.org and, hopefully, to the entire
 ASF, even if political and ego obstacles will get in the way.

 I personally don't care: this effort is mainly to create a better
 documentation infrastructure following the goals outlined below. I
 started the Cocoon project three years ago exactly for this reason and
 now that has all the features I needed, I think I can attack the problem
 from a very wide angle.

 The site building system will be targetted toward xml.apache.org, but
 I'll keep a very broad perspective, making it possible to adapt the
 system to other apache.org projects with very few changes.

 BIG DISCLAIMER: however, whether this happens or not, I personally don't
 care. For sure, don't count on me wasting my time on fighting about 'my
 DTD is better than yours' or 'my system is
 faster/smaller/cleaner/easier-to-use/more-extensible than yours'.

 I'll come up with a system that works and then you guys will vote on
 what to do. I consider this an exercise to present full Cocoon
 potentials (that, objectively, beat the pants out of all the other
 systems used around Apache) but nothing more than this.

 - o -

 Ok, now that I stated this, let's get into the effort goals.

 GOALS
 -

 1) Speed: current xml.apache.org is slow. Empirical studies on learning
 processes indicate that if a page takes more than 10 seconds on a 56Kbs
 modem, the cognitive experience is degrated.

 2) Coherence: current xml.apache.org is extremely incoherent. Again,
 it's easy to understand that lack of coherence between subprojects docs
 is perceived (and sometimes reflects!) lack of cooperation.

 3) Navigation: the navigation experience on current xml.apache.org is a
 nightmare. There is no way to perceive the basic elements of spatial
 navigation: where am I? where can I go? how do I go back? how do I go
 there?

 4) Depth: the current xml.apache.org page layout forces a flat hierarchy
 of levels. The current Cocoon documentation somewhat extends this, but
 the visual look doesn't reflect the notion. Visual codes are extremely
 important to allow a easy and immediate navigation even at the deepest
 level.

 5) Usefulness: xml.apache.org contains powerful software but it's not
 powerful in itself. It should be a window on the information useful for
 both users and developers, along with friendly behavior, such as
 print-friendly versions of the single pages and of the whole
 per-subproject documentation, pagination of long articles,
 site-restricted search, graphs of project-related data and so on.

 6) Simplicity: xml.apache.org is done by volunteers, on all levels.
 Nobody is directly paid to do this. Not even myself. So, if the above
 goals are met, but the system is not simple and immediate to use for
 those who have to maintain and update the information, the result is
 void over a short period of time.

 7) Extensibility, Flexibility, Modularity: web sites, just as software,
 are living entities that adapt on their environment. The build system
 must not restrict the ability to evolutionary extend the information
 architecture.

 8) URI Solidity and Future Compatibility: URIs are contracts between the
 publisher and the user. Human users have the ability to estimate the
 long-term validity of these contracts and 'route around' eventual broken
 links, 

Re: Forrest (a.k.a. xml.apache.org 2.0)

2001-12-18 Thread giacomo

On Wed, 19 Dec 2001, David Crossley wrote:

 Stefano Mazzocchi wrote:

  3) layout
  -
 
  The layout previously proposed on this list was a solution to the speed
  problem but I couldn't adapt it to the depth needs identified in the
  rest of the goals.
 
  So, I resurrected my rusty web design skills and came up with the layout
  you find attached. I've tested it on IE 5.5, NS 4.78 and Moz 0.9.5 on
  win2k.
 
  Feedback, suggestions and criticisms are appreciated.

 This is really great that you have taken this on Stefano,
 many thanks. We will all help where we can.

 I used View source to look behind-the-scenes and i see
 that there are still tables embedded within tables embedded
 within other tables. I think that this will again lead to troubles
 on some browsers with the larger documents.

 I realise that there may be a need to use one table to achieve
 the left-hand columns. However, i would like us to minimise the
 need for embedded tables, especially in the main text panel.

Minimization is the key. Mostly you can build the initial layout using
three tables:

+--+
!   HEADER !
+--+
+---+--+
! N !  !
! A !  !
! V !  !
! - ! CONTEXT  !
! B !  !
! R !  !
! R !  !
+---+--+
+--+
!   FOOTER !
+--+

You can divide the HEADER and FOOTER table into more columns if needed.
You can also divide the NAV-BAR table into more rows as needed. But then
the CONTENT part is still where tables will be nested.

IMO this is the most seedy and portable way to support even older
browsers.

Giacomo


 --David Crossley

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, email: [EMAIL PROTECTED]






-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail:  [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: Forrest (a.k.a. xml.apache.org 2.0)

2001-12-18 Thread Martin Stricker

Sam Ruby wrote:
 
 Stefano Mazzocchi wrote:

  Just like Gump which is not a subproject on its own, Forrest doesn't
  deserve that status neither as long as it remains a single-man show
  (and my experience tells me it will very likely remain so if the
  above goals are met)
 
 We are already up to two.  I'd like to see the build system build upon
 Gump (let me rephrase that: since I'm volunteering, the build system
 *WILL* build upon Gump).  Perhaps Gump itself didn't have enough
 technical critical mass to become a project, but perhaps Forrest+Gump
 does.

OTOH since both Gump and Forrest are doing cross-project stuff, would it
be a good idea to put them into xml-commons?

Best regards,
Martin Stricker
-- 
Homepage: http://www.martin-stricker.de/
Registered Linux user #210635: http://counter.li.org/

-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail:  [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




RE: [POLL] WASP Lite on Apache?

2001-12-18 Thread Anne Thomas Manes

Dims,

We moved the discussion to axis-dev. There's a fair amount of work that we'd
need to do to clean up our code before we submit it to Apache, so before we
do this work we want to ensure that our code will be useful to you. We
talked about the possibilities of merging Axis and WASP, but considering the
differences in architecture, merger appears to be very challenging.

We've just released a new version of our C++ implementation, which we've
also offered to submit to Apache. Both implementations are based on the same
architecture. Our C++ implementation is already open source, so we've
requested that the Axis team look at this code before we proceed further. We
haven't heard much discussion since then.

Regards,
Anne

 -Original Message-
 From: Davanum Srinivas [mailto:[EMAIL PROTECTED]]
 Sent: Tuesday, December 18, 2001 10:13 AM
 To: [EMAIL PROTECTED]
 Cc: Anne Thomas Manes
 Subject: Re: [POLL] WASP Lite on Apache?


 Anne,

 It's been over a month since we heard from you on
 WASP-Lite(Java). Can you please let us know
 about your latest position on the proposal?

 http://marc.theaimsgroup.com/?t=10056072667r=1w=2

 Thanks,
 dims


 =
 Davanum Srinivas - http://jguru.com/dims/

 __
 Do You Yahoo!?
 Check out Yahoo! Shopping and Yahoo! Auctions for all of
 your unique holiday gifts! Buy at http://shopping.yahoo.com
 or bid at http://auctions.yahoo.com



-
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail:  [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]