Re: JS - inside or out?

Today, yes. In the future? Not necessarily.

That's why we need something flexible and modular.

2016-11-17 17:59 GMT+01:00 Leonard Rosenthol <lrosenth@adobe.com>:

> I would expect that a standard OWP UA is assuming that all UX is provided
> by the content…
>
>
>
> But again, this is going to be one of our biggest debates as we move
> towards the technical aspects of the work.
>
>
>
> Leonard
>
>
>
> *From: *Hadrien Gardeur <hadrien.gardeur@feedbooks.com>
> *Date: *Thursday, November 17, 2016 at 11:33 AM
> *To: *Laurent Le Meur <laurent.lemeur@edrlab.org>
> *Cc: *W3C Digital Publishing IG <public-digipub-ig@w3.org>
> *Subject: *Re: JS - inside or out?
> *Resent-From: *<public-digipub-ig@w3.org>
> *Resent-Date: *Thursday, November 17, 2016 at 11:34 AM
>
>
>
> That's true for a RS but not for a standard OWP UA, which is what I also
> have in mind.
>
>
>
> 2016-11-17 17:31 GMT+01:00 Laurent Le Meur <laurent.lemeur@edrlab.org>:
>
> The advantage of having such Content JS features given explicitly as
> metadata is that the RS software implementation becomes really easy. And
> for the Content author, giving the information is not a big deal (he should
> know what he's programming as part of his Content).
>
>
>
> Laurent Le Meur
>
> EDRLab
>
>
>
>
>
>
>
> Le 17 nov. 2016 à 16:54, Hadrien Gardeur <hadrien.gardeur@feedbooks.com>
> a écrit :
>
>
>
> I wasn't thinking about including that information in the manifest and/or
> metadata, but that's roughly the idea.
>
>
>
> 2016-11-17 16:37 GMT+01:00 Laurent Le Meur <laurent.lemeur@edrlab.org>:
>
> If we use the dichotomy Reading System vs Content, do you mean that the
> Content metadata should contain information meaning e.g. "I'm dealing with
> the pagination" or "I'm dealing with the reader mode" (following your list
> of "JS features"), forcing the RS to turn these features off and lets the
> Content JS dealing with them?
>
>
>
> Laurent Le Meur
>
> EDRLab
>
>
>
>
>
>
>
>
>
> Le 17 nov. 2016 à 16:03, Hadrien Gardeur <hadrien.gardeur@feedbooks.com>
> a écrit :
>
>
>
> I'm going to repeat myself, but I strongly believe that we can figure out
> a way to handle both:
>
>
>
> We just need to figure out a way to:
>
>    - identify that a JS provides such progressive enhancements in order
>    to turn it off eventually
>    - make sure that each progressive enhancement can be tested
>    individually, this way we can have a much more fine grained approach for
>    such a "Web Publication Polyfill"
>
> I've listed a few of the progressive enhancements that could be supported
> at: https://github.com/HadrienGardeur/webpub-
> manifest/wiki/Web-Publication-JS-Features
>
>
>
>
>
>
>
> --
>
> Hadrien Gardeur
>
> Co-founder, Feedbooks
>
> http://www.feedbooks.com
>
> T: +33.6.63.28.59.69
>
> E: hadrien.gardeur@feedbooks.com
>
> 54, rue de Paradis
>
> 75010 Paris, France
>
>
>
>
>
>
>
> --
>
> Hadrien Gardeur
>
> Co-founder, Feedbooks
>
> http://www.feedbooks.com
>
> T: +33.6.63.28.59.69
>
> E: hadrien.gardeur@feedbooks.com
>
> 54, rue de Paradis
>
> 75010 Paris, France
>



-- 
Hadrien Gardeur
Co-founder, Feedbooks
http://www.feedbooks.com
T: +33.6.63.28.59.69
E: hadrien.gardeur@feedbooks.com
54, rue de Paradis
75010 Paris, France