OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cgmo-webcgm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [cgmo-webcgm] Flow of electricity


[...copying the TC list...]

At 03:23 PM 10/1/2007 -0700, Galt, Stuart A wrote:
>My reply is embedded below :)
>
> > -----Original Message-----
> > From: Lofton Henderson [mailto:lofton@rockynet.com]
> > Sent: Monday, October 01, 2007 3:10 PM
> > To: Galt, Stuart A; cgmo-webcgm@lists.oasis-open.org
> > Subject: Re: [cgmo-webcgm] Flow of electricity
> >
> > Stuart --
> >
> > Good stuff!  Again, we should be looking to put your examples
> > (and anyone
> > else's) of 2.0 capabilities somewhere on the Web site.  So,
> > aside from technical (and 2.1 rqts questions), there is the
> > Education/Outreach
> > question:  when and where can we put these up and direct
> > people to them?
>
>I meant to mail the examples to the list but Dave informed me that
>kavi ate the html.... I think I will have to zip them up or something.

I'm not sure I understand.  I got them via the list, and both the .cgm and 
the .htm attachments were intact.

On the other hand, if you look at the message in the Kavi archive,
http://lists.oasis-open.org/archives/cgmo-webcgm/200709/msg00087.html ,
then you will notice that Kavi seems to have put the HTML in-line and 
dropped the attachment.

All hail to Kavi !!!  (What a piece of junk.)

>It will be ironic that the firewall here will eat my message :)
>I am not sure where is a good place to put these out so people can
>see what can be done with 2.0... One problem is that you need to
>get a viewer before you can see the files.  While everyone on the
>planet has a PDF viewer... CGM viewers are on far fewer desktops.
>If I had a viewer that didn't require people to download a viewer
>I would be able to reach a far wider audience.

That's a good topic for discussion (telecon).  A couple of practical 
(short-term) ideas come to mind:

1.) our proposed examples page could have one-jump links to every vendor's 
viewer that works on the examples; and these should be trivial to download, 
install, and run.

2.) maybe we could make a "cartoon strip" composite that shows what one 
will see with an enabled viewer?


> >
> > Technical questions...
> >
> > At 01:46 PM 9/28/2007 -0700, Galt, Stuart A wrote:
> > >[..]
> > >As I start making more complex images/applications I am
> > finding myself
> > >wishing I had a either getStyleProperty() or removeStyleProperty()
> >
> > Is the "get" an inquiry function?  Do you actually want both
> > "get" and "remove", or did you really mean "either...or"?
> >
> > Do you propose that these be added to the 2.1 wish list?
>
>I don't really care!  I would take which ever is easier to
>implement.  I think the get would be easier but you might
>get "false" results if you change the style property within the
>APS.

Explain?  What does it mean to "change the style property within the 
APS"?  You can change a Style Property through DOM for a whole APS, or 
through XCF for a whole APS.  But "within the APS", you can only change CGM 
primitive attributes (or ApsAttrs in the APS header).

>I know how I could implement the remove functionality in
>my conceptual viewer but I have no idea if other viewers use
>the same model.
>
> >
> > >method
> > >(I realize that this is difficult to implement) and the
> > ability to make
> > >several DOM changes without waiting for a redraw between each one.
> >
> > I guess this has now been added to the 2.1 wish list.
>
>I think the "delay redraw" will be more important as the
>animations/DOM control become more complex.  My script I
>changed the color and stroke-width so I had twice as many
>redraws as necessary.
>
>I apologize for being part of the feature creep problem but
>I was just talking about things that would make some of these
>simple examples better/more efficient.

I don't think feature creep is a big problem at this stage.  The entire 
collection of endorsed 2.1 extensions is pretty small at this point.  On 
the other hand, here is an item that proves useful to people actually 
writing WebCGM applications.

-Lofton.




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]