W3C home > Mailing lists > Public > public-hydra@w3.org > January 2015

Re: Reusable Hydra components

From: Tomasz Pluskiewicz <tomasz@t-code.pl>
Date: Wed, 28 Jan 2015 20:11:16 +0100
Message-ID: <54C93454.6060908@t-code.pl>
To: public-hydra@w3.org

On 2015-01-27 22:53, Markus Lanthaler wrote:
> On 27 Jan 2015 at 12:21, Tomasz Pluskiewicz wrote:
>> January 27 2015 12:42 AM, "Markus Lanthaler" wrote:
>> Yes, I don't like the term routing anyway in this context. Renderer is a bit better but not
>> ideal IMO. The required word is for a component that decides what view to render based
>> on an input. I guess that "render" is a logical idea but I think that "choose" is the predicate
>> here. Maybe ld-view-selector? Descriptive...
> Another term that comes to my mind is "presenter". "View controller" might also work but is probably a bit confusing in this context.

I like presenter. Concise and also a name one can find in other places, 
think MVP.

>> No, but I'd like to have the option. The problem is that a UI design may position various
>> operations available for a resource in different places on the page. In such case simply
>> rendering them next to each other could be not perfect.
> Oh I see. Perhaps you should also explore the option to make that configuration simply more (linked) data. Basically you would define a simple vocabulary being able to express those things, merge it with the data you get from the API you are interacting with and consume it the same way as that data.

Of course. I'll cross that bridge when I get there but I'll keep that 
idea in mind.

Received on Wednesday, 28 January 2015 19:12:19 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 28 January 2015 19:12:20 UTC