40-character limit

[nielmclaren]

Dat 40-character limit is making people crazy.

Especially when you get into flow state and your fast typing triggers the alert. If we queue updates for every 3-5 characters changed then we could do away with the warning altogether. People following along would see the code being written out as expected.

[furiousgreencloud]

Yes it's annoying.

the pop up alert is the worst too (my BAD), a "status line" type message would be better.

How/Where would the updates be queued. I like the direction you're going in i'm just not sure I understand the solution, which shouldn't stop you.

• Brady

On Wed, Jun 10, 2015 at 1:23 PM, Niel notifications@github.com wrote:

Dat 40-character limit is making people crazy.

Especially when you get into flow state and your fast typing triggers the alert. If we queue updates for every 3-5 characters changed then we could do away with the warning altogether. People following along would see the code being written out as expected.

— Reply to this email directly or view it on GitHub https://github.com/furiousgreencloud/PermanentDeviation/issues/6.

[nielmclaren]

It's a great minimally-viable solution so nobody's bad. (-;

I need to look to see what's actually going on in the code but we can send a request every few characters rather than over some time interval. Just need to make sure cases are handled where the requests don't go through immediately or they don't go in order. But this way the full history will be sent to the server without having to get the coder to slow down. Asynchronicity!

[furiousgreencloud]

Ah, yes I get it.

On Wed, Jun 10, 2015 at 2:24 PM, Niel notifications@github.com wrote:

It's a great minimally-viable solution so nobody's bad. (-;

I need to look to see what's actually going on in the code but we can send a request every few characters rather than over some time interval. Just need to make sure cases are handled where the requests don't go through immediately or they don't go in order. But this way the full history will be sent to the server without having to get the coder to slow down. Asynchronicity!

— Reply to this email directly or view it on GitHub https://github.com/furiousgreencloud/PermanentDeviation/issues/6#issuecomment-110919434 .

[furiousgreencloud]

the whole thing could be diff based, using git!?

On Wed, Jun 10, 2015 at 5:05 PM, Brady Marks furiousgreencloud@gmail.com wrote:

Ah, yes I get it.

On Wed, Jun 10, 2015 at 2:24 PM, Niel notifications@github.com wrote:

It's a great minimally-viable solution so nobody's bad. (-;

I need to look to see what's actually going on in the code but we can send a request every few characters rather than over some time interval. Just need to make sure cases are handled where the requests don't go through immediately or they don't go in order. But this way the full history will be sent to the server without having to get the coder to slow down. Asynchronicity!

— Reply to this email directly or view it on GitHub https://github.com/furiousgreencloud/PermanentDeviation/issues/6#issuecomment-110919434 .

[nielmclaren]

I'd normally agree but we'd have an epic number of commits if we're tracking changes of 1-5 characters. If we're okay with just seeing a diff of what was added/removed during each 4-minute session then this becomes viable. Loses the feeling of being able to watch how the coder codes, but.

Maybe let's see what the diffs look like and we can decide which is more useful for learning and for watching. Maybe for live coding we can show character-by-character updates and then for the archives we just show diffs.

On Wed, Jun 10, 2015 at 6:57 PM, Brady Marks notifications@github.com wrote:

the whole thing could be diff based, using git!?

On Wed, Jun 10, 2015 at 5:05 PM, Brady Marks furiousgreencloud@gmail.com wrote:

Ah, yes I get it.

On Wed, Jun 10, 2015 at 2:24 PM, Niel notifications@github.com wrote:

It's a great minimally-viable solution so nobody's bad. (-;

I need to look to see what's actually going on in the code but we can send a request every few characters rather than over some time interval. Just need to make sure cases are handled where the requests don't go through immediately or they don't go in order. But this way the full history will be sent to the server without having to get the coder to slow down. Asynchronicity!

— Reply to this email directly or view it on GitHub < https://github.com/furiousgreencloud/PermanentDeviation/issues/6#issuecomment-110919434

.

— Reply to this email directly or view it on GitHub https://github.com/furiousgreencloud/PermanentDeviation/issues/6#issuecomment-110967676 .