From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-03v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:35]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 87DED783A6 for ; Sat, 19 Sep 2015 23:01:10 -0700 (PDT) Received: from resomta-ch2-15v.sys.comcast.net ([69.252.207.111]) by resqmta-ch2-03v.sys.comcast.net with comcast id KJ491r0022Qkjl901J491d; Sun, 20 Sep 2015 06:04:09 +0000 Received: from eklhad ([IPv6:2601:405:4002:b0a:21e:4fff:fec2:a0f1]) by resomta-ch2-15v.sys.comcast.net with comcast id KJ491r0040GArqr01J497K; Sun, 20 Sep 2015 06:04:09 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: edbrowse/3.5.4.2+ Date: Sun, 20 Sep 2015 02:04:09 -0400 Message-ID: <20150820020409.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1442729049; bh=jc9GhIeLI1T6zv1mmzMTcR3Zm7Q2X/rDzVL7V50gX/g=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=pie+FOxM3CPlIc++KYTmoVKdKP77bkcuumf3hRKjE3cNFLdEZI+CPSNxMqyYFCQVq KyTbixkZpyRdBv8UN4PoXfIfC4YTeBQd99txjIUI5gBu8JJoV3MGu/PKkIvDGIJMdz 3g486UmM+4Qc90eym4agmAnzpF2DfFF6419O7qKVyhYSCefMNkrTaLEz6VCjRY0Sl7 2YPwWdYYXCalS29+hRPR96fDpJSnjZDOW6H6M1gLxvQXUYheC6E3tV9VbrbR0i7fAA P+r0ImSDvfGbCCmAx9ea7DhghfcGw9eXdEKvqNPMg8ZN9TISr61uB8gfaAyJa/bJM0 khVlbEAwZIO2Q== Subject: [Edbrowse-dev] Notify and Rerender X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.20 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Sep 2015 06:01:11 -0000 I was going to document the rerender command, which I obviously need to do, and I realize I'm not even sure how I want it to work. The command itself is fine, update the buffer if the active web page has changed out from under you - but the question is, should the rerender ever just run ffor you on its own? You may have no idea that the page is changing. This is where it gets very very hard to shoehorn the page, obviously made for sighted users, into our world. A more accessible web page would be better, but we might not have that option. Well I can't just update and notify you every time there is a change. Recall my earlier example, where the page updates once a second. We can't be spewing out "line 12 has been updated" once a second. And it could be more than that. A page shoing stock prices in realtime - I don't know how many updates per second that is. On the other hand, should I just never tell you there has been a change, and hope you someday invoke some javascript, which will force the rerender, or type rr? That doesn't seem right either. I'm pretty confident that I shouldn't notify you of changes to background screens (pushed onto the stack) or screens in other sessions. You'll see those changes when you switch over to them. This question is only for the current screen. I'm wondering if I should mark the time of the first change, that perhaps you don't know about, and if a rerender hasn't happened in one minute, or some such time interval, then I force the rerender and tell you what lines have changed. That might be the best compromise between reporting every single asynchronous change and never saying a word. Karl Dahlke