Tele: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
Line 29: Line 29:
         UI and subsequent network events determine which state results. </blockquote>  
         UI and subsequent network events determine which state results. </blockquote>  
       </li>  
       </li>  
   </ol><center>
   </ol>
<blockquote><center>
The design intent is that the desktop legend-taskbar default state is collapsed with the desktop, an expand tab/flap and the doorbell. <br>It is draggable and when connected the doorbell illumination will track the call state.
The design intent is that the desktop legend-taskbar default state is collapsed with the desktop, an expand tab/flap and the doorbell. <br>It is draggable and when connected the doorbell illumination will track the call state.
<br>No common login/profile link for this SPA as it automatically connects for authenticated clients and ignores others other than providing a meeting passphrase usable with Jitsi meet.</center>
<br>No common login/profile link for this SPA as it automatically connects for authenticated clients and ignores others other than providing a meeting passphrase usable with Jitsi meet.</center>
</blockquote>
<blockquote>Visual cues would need currently unaffordable modifications  
<blockquote>Visual cues would need currently unaffordable modifications  
to generalized sense modalities for accessibility but down the road ... . The system itself is an integration of various of my infrastructures with a derived jigasi client, videobridge server, and as many of the jitsi tools as are useful, which sfaik is all of them.</blockquote>
to generalized sense modalities for accessibility but down the road ... . The system itself is an integration of various of my infrastructures with a derived jigasi client, videobridge server, and as many of the jitsi tools as are useful, which sfaik is all of them.</blockquote>