On Sat, Jun 7, 2014 at 4:37 PM, Scott Robison sc...@casaderobison.com
wrote:
On Jun 7, 2014 1:27 PM, Ron Wilson ronw.m...@gmail.com wrote:
On Sat, Jun 7, 2014 at 2:23 PM, Stephan Beal sgb...@googlemail.com
wrote:
For the local UI case, sure, i can see it being useful, but people
would
Is it reasonable to ask that the 'autosync' setting cause artifacts created
from the GUI to also be autosynced?
I know this would likely increase the latency of the GUI, and would
possibly create a series of error cases and/or user interactions that do
not need to be handled in the GUI today.
On Sat, Jun 7, 2014 at 3:44 PM, Eric Rubin-Smith eas@gmail.com wrote:
I know this would likely increase the latency of the GUI, and would
possibly create a series of error cases and/or user interactions that do
not need to be handled in the GUI today. But I believe that today's
behavior
Stephan Beal wrote:
I know this would likely increase the latency of the GUI, and would
possibly create a series of error cases and/or user interactions that do
not need to be handled in the GUI today. But I believe that today's
behavior nevertheless violates the principle of least
On Sat, Jun 7, 2014 at 1:26 PM, Eric Rubin-Smith eas@gmail.com wrote:
Two of Fossil's self-proclaimed major benefits are: (a) its GUI and
(b) its autosync feature. That the GUI does not attempt to implement
autosync at all *is* surprising.
Note that in non-tiny teams, there is often a
On Sat, Jun 7, 2014 at 2:23 PM, Stephan Beal sgb...@googlemail.com wrote:
For the local UI case, sure, i can see it being useful, but people would
also expect it to work remotely, and it often wouldn't.
When running the local UI, that is seen as part of the local client, but
when accessing a
On Jun 7, 2014 1:27 PM, Ron Wilson ronw.m...@gmail.com wrote:
On Sat, Jun 7, 2014 at 2:23 PM, Stephan Beal sgb...@googlemail.com
wrote:
For the local UI case, sure, i can see it being useful, but people would
also expect it to work remotely, and it often wouldn't.
When running the local UI,
7 matches
Mail list logo
