Re: [whatwg] Galleries revisited

2016-07-14 Thread Delfi Ramirez
On 2016-07-14 18:21, Domenic Denicola wrote:

>> From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of 
>> i...@hansschmucker.de
> 
>> _The remaining issue for me seems that the interaction between this "viewer" 
>> and the page is completely unspecified and that items like descriptions and 
>> copyright notices which may be required to make sense of an image may or may 
>> not be shown._
>> 
>> _ Also, an image may represent an item of any kind or offer actions on it 
>> (for example "Download the PDF", "View the subgallery", "Show related 
>> images", "Go to full description"), which the page may be unable to perform 
>> if there is no standardized way to interact with the UA._
> 
> I don't think the below proposal is a good way to address this. I'd suggest 
> creating your own library to implement the desired functionality, possibly 
> using microformats for the semantic aspects, and seeing if it gets adoption. 
> If it becomes very popular, maybe we could consider asking implementers if 
> they are interested in adding it to the platform, like they have done with 
> aspects of other popular libraries such as jQuery. But I think you are still 
> too quick to jump to asking implementers to implement a new element.

agree 

---

Delfi Ramirez -- At Work

My digital signature [1]

0034 633 589231
 del...@segonquart.net [2] 

twitter: @delfinramirez [3]
 IRC: segonquart
 Skype: segonquart [4]

http://segonquart.net

http://delfiramirez.info
 [5]
 

Links:
--
[1] http://delfiramirez.info/public/dr_public_key.asc
[2] mail:%20del...@segonquart.net
[3] https://twitter.com/delfinramirez
[4] skype:segonquart
[5] http://delfiramirez.info


Re: [whatwg] Galleries revisited

2016-07-14 Thread Domenic Denicola
> From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of 
> i...@hansschmucker.de

> The remaining issue for me seems that the interaction between this "viewer" 
> and the page is completely unspecified and that items like descriptions and 
> copyright notices which may be required to make sense of an image may or may 
> not be shown.
>
> Also, an image may represent an item of any kind or offer actions on it (for 
> example "Download the PDF", "View the subgallery", "Show related images", "Go 
> to full description"), which the page may be unable to perform if there is no 
> standardized way to interact with the UA.

I don't think the below proposal is a good way to address this. I'd suggest 
creating your own library to implement the desired functionality, possibly 
using microformats for the semantic aspects, and seeing if it gets adoption. If 
it becomes very popular, maybe we could consider asking implementers if they 
are interested in adding it to the platform, like they have done with aspects 
of other popular libraries such as jQuery. But I think you are still too quick 
to jump to asking implementers to implement a new element.