TiddlyTweeter wrote:
"Very good case example (http://cultconv.com/  [footnote---on mobile its 
too minuscule!])."

yes, I know of the sizing issue on mobile devices. Not sure how to handle 
that other than a redesign which I am loathe to do given usage stats 
(~8,000 per month over last calendar year). The basic design is for 
multiple synchronous channels of information, in this case four 
(video/audio, transcript, table of contents and images with captions). 
Altogether too much for a small screen. Plus on iPhone, the video takes 
over the whole screen anyway.

bobj

On Tuesday, 1 December 2020 at 03:50:57 UTC+11 TiddlyTweeter wrote:

> Ciao bobj
>
> Very good case example (http://cultconv.com/  [footnote---on mobile its 
> too minuscule!]).
>
> BTW, I really took to your last point ...
>
> Throughout all of my research career, the issue that continually crops up 
>> is context. I think this is the crucial component to keep things 
>> understandable. Yet no agreed understanding of context exists yet we all 
>> use it ...
>>
>
> Right. In terms of information design issues there is no algorithm for 
> accurately deriving either "scope of meaning" or "scope of inference 
> (context implying)". Though it is pretty clear on net that within "fields 
> of interest" context is ALWAYS playing an implicit role in successful sites.
>
> I thought the site you gave access to excellent. *Very honed to purpose*. 
> It is an unusual (uplifting) thing seeing such a "schematization" work so 
> well.
> I think that is the point. You have to "sniff/tease" out context and back 
> generate (derive) schema from that first-felt understanding that isn't 
> otherwise derivable.
>
> Best wishes
> TT
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/587ed5db-e27b-4d5a-820f-7497652d30fdn%40googlegroups.com.

Reply via email to