hmmm,

i agree that flash, in general is author orientated and user orientated
instead of being a viable full fledged client, no offense to flash dev or
nice people at macromedia.

though the nice strength of SOAP or even raw html, is that it is relatively
trivial to create a pseudo client within flash.

i've recently created  a flash api which communicates ( with our to be soon
to be released product... ) via raw HTTP, which translates an xml data
structure into a flash friendly data array, and does vice versa.... all done
with the xml parser built within flash. essentially it means that the
content syndication managed by our product can know have flash clients which
can add,edit, view etc....

i also remember someone implementing a flash XML-RPC client, which doesnt
work so well because of a current serious bug in flash ( i think ).

easy enough, but if flash wants to get serious, its gonna need something to
support SOAP, which means xml-schema implementation, a valid xml parser, and
possibly xslt builtin to do in client transforms instead of going back and
forth to the server for simple transforms.

even more interesting would be for flash to 'find' an xslt parser via
possibly a JAXP type interface... which is where sablotron could come in
somehow, but one must solve the JAXP conundrum within the c and c++ world
first.

subsequent post, by Miguel mentions  a few points

- Committing to XML is powerful in the sense the content is truly isolated
from the presentation

this comment is completly valid, yet reminds me of when java first came out
and people were saying 'wow, one can make cool applets in the browser',

yes seperating logic, data, and presentation is a common mantra applied to
xml and xslt; but more importantly is that meta data can be pervasive
throughout the software architecture and development is *data* centric
instead of procedurally led.

-I've learned Perl and Java, why must I again expend brain cells with the
syntax of XSL/XSLT

i think that one must expect to learn throughout their career instead of
falling into the 'golden hammer' anti pattern. More important is to not
think of a software framework as a software language; principles of
functional programming are finding their way back into commercial
programming ( read the Haskell newsgroups these days ! ), because of some
grey areas presented in current frameworks.

as for flash, the only good thing about it is that a lot of people have it,
and there seems to be very little cross browser/os issues; and lets wait
till there are some good xml/svg editors to see if flash svg becomes 'yet
another file format'.

apologies for OT

cheers, jim fuller

----- Original Message -----
From: "Antoine Quint" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, March 03, 2002 12:24 PM
Subject: OT (RE: comment on xml/flash)


> > But what if plugins like flash simply take over content geneation.
> > Is all this more than an excercise for software lovers exploring the
> > possibilities of xml for generating browser content?
>
> Although this is completely off-topic, I believe that right now it is
> impossible to really consider the Flash player as a platform for content
> generation. The Flash 5 Player indeed offers XML socket connections to
> remote servers and allow for placing dynamic content into Flash
> compositions... To a certain extent. Problem is what you will be able to
> do with the XML content you get. The Flash 5 Player does not have a
> generic API to client-side program against, you cannot generate paths on
> the fly or any fancy part of web graphics like gradient fills etc. And
> that doesn't take into account what SWF just cannot do, including
> vector/raster filter effects and the likes. What about using XML with an
> XML graphics application like SVG instead?
>
> Antoine
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>




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

Reply via email to