feature request

View: New views
3 Messages — Rating Filter:   Alert me  

feature request

by Robert Raleigh :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Is this something I should put in JIRA? I'd like to be able to have some text, even if it's just a document include, change based on some contextual parameter. It's essentially what's called conditional text in many publishing systems. To give an example, I may have two products that are very similar, but have different performance characteristics. Therefore, I'd like to be able to add a conditional that says, at book publishing time, if some field or metadata is set to A, then include section X at this point, but if the field or metadata is set to B, include section Y at that point instead of section X. Make sense?

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

Re: feature request

by Karel Vervaeke :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hm, this would require some investigation and development,
but I suppose you could achieve it using includes in the book
publication styles.

Alternatively try solving it using custom publisher requests. You can
code 'switch'
statements both in the mapping file and in the publisher requests - I
suppose the latter would be more useful for you.

http://www.daisycms.org/daisydocs-2_3/373-cd/194-cd/418-cd.html
http://www.daisycms.org/daisydocs-2_3/373-cd/194-cd/429-cd.html

HTH,
Karel

On Mon, Sep 14, 2009 at 9:56 PM, Robert Raleigh <rraleigh@...> wrote:

> Is this something I should put in JIRA? I'd like to be able to have some
> text, even if it's just a document include, change based on some contextual
> parameter. It's essentially what's called conditional text in many
> publishing systems. To give an example, I may have two products that are
> very similar, but have different performance characteristics. Therefore, I'd
> like to be able to add a conditional that says, at book publishing time, if
> some field or metadata is set to A, then include section X at this point,
> but if the field or metadata is set to B, include section Y at that point
> instead of section X. Make sense?
>
> 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

Re: feature request

by Karel Vervaeke :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Oh, and to make my post complete: You might want to put the conditionally
included data in a <p:group> and do the formatting in the publication style.

On Tue, Sep 15, 2009 at 9:20 AM, Karel Vervaeke <karel@...> wrote:

> Hm, this would require some investigation and development,
> but I suppose you could achieve it using includes in the book
> publication styles.
>
> Alternatively try solving it using custom publisher requests. You can
> code 'switch'
> statements both in the mapping file and in the publisher requests - I
> suppose the latter would be more useful for you.
>
> http://www.daisycms.org/daisydocs-2_3/373-cd/194-cd/418-cd.html
> http://www.daisycms.org/daisydocs-2_3/373-cd/194-cd/429-cd.html
>
> HTH,
> Karel
>
> On Mon, Sep 14, 2009 at 9:56 PM, Robert Raleigh <rraleigh@...> wrote:
>> Is this something I should put in JIRA? I'd like to be able to have some
>> text, even if it's just a document include, change based on some contextual
>> parameter. It's essentially what's called conditional text in many
>> publishing systems. To give an example, I may have two products that are
>> very similar, but have different performance characteristics. Therefore, I'd
>> like to be able to add a conditional that says, at book publishing time, if
>> some field or metadata is set to A, then include section X at this point,
>> but if the field or metadata is set to B, include section Y at that point
>> instead of section X. Make sense?
>>
>> 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