variable graphics?

[Robert Raleigh]

I've been using the variable feature to produce some documentation for OEM versions of our product, and it works great. The problem I'm running into though now is that I also need to include graphics that are screenshots of productized versions of our software. My current approach is to duplicate the relevant documents and then insert the changed screenshots. This approach will create problems, though, when the text of the original document changes.

Ideally, I'd like to be able to use the same text but point to a different set of screenshots in a document, based on some context variable. It could be a field or a branch or whatever. I just want to be able to handle it without branching and therefore creating multiple versions of a document that must all be updated in parallel.

Any ideas on how I might be able to do this currently? And if not, ideas on how it might best be handled for purposes of a feature request?

Thanks,

Robert

CONFIDENTIAL

This document and attachments contain information from Fusion-io, Inc. which is confidential and/or legally privileged.
The information is intended only for the use of the individual or entity named on this transmission.
If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking of any
action in reliance on the contents of this emailed information is strictly prohibited, and that the documents should be returned to Fusion-io, Inc. immediately.
In this regard, if you have received this email in error, please notify us by return email immediately.


_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

[Karel Vervaeke]

Hmm, it may be a bit far fetched, but you could use an xsl template
that changes the <img> elements on your site (or in your book
publication process):

Instead of <img
src="/daisy/yoursite/123-DSY/version/last/part/ImageData/data/> have
the links rendered as

<img src="/daisy/yoursite/ext/imageswitcher/mode1/123-DSY/>

And then implement an 'imageswitcher' extension which renders a
different image based on some parameters (you get to decide how the
image selection is done and how the 'mode' is chosen)
Alternatively the stylesheet has enough input to decide which image to
render you can manage the screenshot variants using branches and add a
dynamicly chosen ?branchId=... parameter to the @src attribute.

I hope I'm making sense, I haven't slept much.
Karel

On Mon, Aug 3, 2009 at 9:50 PM, Robert Raleigh<rraleigh@...> wrote:

> I've been using the variable feature to produce some documentation for OEM
> versions of our product, and it works great. The problem I'm running into
> though now is that I also need to include graphics that are screenshots of
> productized versions of our software. My current approach is to duplicate
> the relevant documents and then insert the changed screenshots. This
> approach will create problems, though, when the text of the original
> document changes.
>
> Ideally, I'd like to be able to use the same text but point to a different
> set of screenshots in a document, based on some context variable. It could
> be a field or a branch or whatever. I just want to be able to handle it
> without branching and therefore creating multiple versions of a document
> that must all be updated in parallel.
>
> Any ideas on how I might be able to do this currently? And if not, ideas on
> how it might best be handled for purposes of a feature request?
>
> Thanks,
>
> Robert
>
> CONFIDENTIAL
>
> This document and attachments contain information from Fusion-io, Inc. which
> is confidential and/or legally privileged.
> The information is intended only for the use of the individual or entity
> named on this transmission.
> If you are not the intended recipient, you are hereby notified that any
> disclosure, copying, distribution or taking of any
> action in reliance on the contents of this emailed information is strictly
> prohibited, and that the documents should be returned to Fusion-io, Inc.
> immediately.
> In this regard, if you have received this email in error, please notify us
> by return email immediately.
>
>
> _______________________________________________
> daisy community mailing list
> Professional Daisy support:
> http://outerthought.org/en/services/daisy/support.html
> mail to: daisy@...
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy
>
>

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

[A Rocha Webmaster]

This relates to something we need -- pictures to be displayed at any dimensions.

When the page editor specifies that the image should be 200 px wide, we want to create a 200 px wide picture and use it in the page -- not transfer the 2 MB, 1600 px wide original version and scale it at the browser. :-) Using the Preview picture won't work in all occasions either -- scaling the 250 px Preview to 200 px on the browser makes for a very ugly picture.

Has anyone made such a modification / extension to Daisy?

Júlio.

Ter, 2009-08-04 às 10:14 +0200, Karel Vervaeke escreveu:

Hmm, it may be a bit far fetched, but you could use an xsl template
that changes the <img> elements on your site (or in your book
publication process):

Instead of <img
src="/daisy/yoursite/123-DSY/version/last/part/ImageData/data/> have
the links rendered as

<img src="/daisy/yoursite/ext/imageswitcher/mode1/123-DSY/>

And then implement an 'imageswitcher' extension which renders a
different image based on some parameters (you get to decide how the
image selection is done and how the 'mode' is chosen)
Alternatively the stylesheet has enough input to decide which image to
render you can manage the screenshot variants using branches and add a
dynamicly chosen ?branchId=... parameter to the @src attribute.

I hope I'm making sense, I haven't slept much.
Karel

On Mon, Aug 3, 2009 at 9:50 PM, Robert Raleigh<rraleigh@...> wrote:
> I've been using the variable feature to produce some documentation for OEM
> versions of our product, and it works great. The problem I'm running into
> though now is that I also need to include graphics that are screenshots of
> productized versions of our software. My current approach is to duplicate
> the relevant documents and then insert the changed screenshots. This
> approach will create problems, though, when the text of the original
> document changes.
>
> Ideally, I'd like to be able to use the same text but point to a different
> set of screenshots in a document, based on some context variable. It could
> be a field or a branch or whatever. I just want to be able to handle it
> without branching and therefore creating multiple versions of a document
> that must all be updated in parallel.
>
> Any ideas on how I might be able to do this currently? And if not, ideas on
> how it might best be handled for purposes of a feature request?
>
> Thanks,
>
> Robert
>
> CONFIDENTIAL
>
> This document and attachments contain information from Fusion-io, Inc. which
> is confidential and/or legally privileged.
> The information is intended only for the use of the individual or entity
> named on this transmission.
> If you are not the intended recipient, you are hereby notified that any
> disclosure, copying, distribution or taking of any
> action in reliance on the contents of this emailed information is strictly
> prohibited, and that the documents should be returned to Fusion-io, Inc.
> immediately.
> In this regard, if you have received this email in error, please notify us
> by return email immediately.
>
>
> _______________________________________________
> daisy community mailing list
> Professional Daisy support:
> http://outerthought.org/en/services/daisy/support.html
> mail to: daisy@...
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy
>
>
_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy