>>>>> "Jim" == Jim Ley <[EMAIL PROTECTED]> writes:

Jim> I've recently been working on an svg application - foafnaut -
Jim> http://foafnaut.org/ (based on work by Dean Jackson, and with
Jim> considerable help from Liz Turner) 

     Cool!

Jim> It's a complicated SVG application, relying on a lot of
Jim> javascript, whilst I've managed to get it not to error, and be
Jim> basically usable in Batik 1.5b4, there are a number of things I
Jim> am not able to do, most are not using core SVG or ECMAScript, but
Jim> are using Adobe extensions, or similar, and I was wondering if
Jim> the elements I was using are likely to be supported in 1.5
Jim> release, of it there's a likely alternative strategy

Jim> The things I need are:

Jim> Access to the query string client-side, done in ASV via the
Jim> getSrc() method.  

     On what?  this might be easy to fix...

Jim> Whilst for the online version I could use serverside scripting to
Jim> duplicate it into the client, my aim is to have a clientside
Jim> version as the data being loaded from the server makes the user
Jim> experience generally unacceptable.

---

Jim> Addition of javascript properties to SVG objects.  Normally in
Jim> javascript, you can add properties/methods dynamically to objects
Jim> with foo.bar="jim" and this includes Document Objects in all
Jim> other implementations I know of, so I can go:

Jim> cEl=document.createElement('circle') 
Jim> cEl.chicken="jim"

     Hmm... We more or less just use the Rhino engine which proxies
the Java DOM objects in ECMAScript.  Unless this is some sort of
configuration option for Rhino I doubt we can help you here.
     
Jim> and attach the chicken property to my cElement, this is very
Jim> useful, for simple objects I could use DOM methods and set an
Jim> attribute or child, however for javascript objects I'd need to
Jim> serialise the object, which is hardly desirable, any chance of
Jim> coming into line with other implementations (I realise this
Jim> probably isn't simple unfortunately, however making it not a java
Jim> error, but a script error that could be try/catch'd away would
Jim> help.)

     Sounds generally useful, any idea if this is part of ECMAScript
or just a common extension?

Jim> Lastly my problem is the with zoom and pan, I want to have
Jim> certain elements immune to zooming and panning (despite not
Jim> liking it, the application is not considered to be acceptable,
Jim> alternative HTML views of the data are available for that), which
Jim> means that I need to access the current scale and zoom of the
Jim> elements - this may be simply my syntax at fault here.

     Nope, this has not been implemented... It should be :) I don't
even think it's incredibly hard but I don't know enough about the
script binding to fix it.

Jim> Another things I've noticed but not diagnosed as being an error,
Jim> is that parseXML never works in the context of a document other
Jim> than the svg document.

     This is fixed at least in CVS.

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

Reply via email to