[9fans] libframe Go port

[9fans] libframe Go port

[Giles Hutton]

[-- Attachment #1: Type: text/plain, Size: 461 bytes --]

Hi All,

I'm currently in the process of porting acme to Go, and as part of that I'm
porting libframe as well. It's currently in a fully transliterated state
and needs a good refactor to make it more idiomatic Go.

However, my question is whether this is something that people would be keen
on using, and if so, what's the procedure for getting it added to the 9fans
github repo once I've finished. Is a simple pull request enough?

Thanks,

Giles

[-- Attachment #2: Type: text/html, Size: 590 bytes --]

Re: [9fans] libframe Go port

[Tharaneedharan Vilwanathan]

[-- Attachment #1: Type: text/plain, Size: 700 bytes --]

Hi,

Just wanted to let you know I am very eager to see both acme and libframe
in Go. Its a great idea.

Regards
dharani


On Sat, Oct 10, 2015 at 8:42 AM, Giles Hutton <hutton.giles@gmail.com>
wrote:

> Hi All,
>
> I'm currently in the process of porting acme to Go, and as part of that
> I'm porting libframe as well. It's currently in a fully transliterated
> state and needs a good refactor to make it more idiomatic Go.
>
> However, my question is whether this is something that people would be
> keen on using, and if so, what's the procedure for getting it added to the
> 9fans github repo once I've finished. Is a simple pull request enough?
>
> Thanks,
>
> Giles
>

[-- Attachment #2: Type: text/html, Size: 1161 bytes --]

Re: [9fans] libframe Go port

[Siarhei Zirukin]

[-- Attachment #1: Type: text/plain, Size: 601 bytes --]

why not a javascript library?

On Sat, Oct 10, 2015 at 5:42 PM, Giles Hutton <hutton.giles@gmail.com>
wrote:

> Hi All,
>
> I'm currently in the process of porting acme to Go, and as part of that
> I'm porting libframe as well. It's currently in a fully transliterated
> state and needs a good refactor to make it more idiomatic Go.
>
> However, my question is whether this is something that people would be
> keen on using, and if so, what's the procedure for getting it added to the
> 9fans github repo once I've finished. Is a simple pull request enough?
>
> Thanks,
>
> Giles
>

[-- Attachment #2: Type: text/html, Size: 997 bytes --]

Re: [9fans] libframe Go port

[Skip Tavakkolian]

[-- Attachment #1: Type: text/plain, Size: 807 bytes --]

no need. just use David Hoskin's HTML5 devdraw:

https://bitbucket.org/dhoskin/9webdraw


On Sat, Oct 10, 2015 at 10:03 AM, Siarhei Zirukin <ftrvxmtrx@gmail.com>
wrote:

> why not a javascript library?
>
> On Sat, Oct 10, 2015 at 5:42 PM, Giles Hutton <hutton.giles@gmail.com>
> wrote:
>
>> Hi All,
>>
>> I'm currently in the process of porting acme to Go, and as part of that
>> I'm porting libframe as well. It's currently in a fully transliterated
>> state and needs a good refactor to make it more idiomatic Go.
>>
>> However, my question is whether this is something that people would be
>> keen on using, and if so, what's the procedure for getting it added to the
>> 9fans github repo once I've finished. Is a simple pull request enough?
>>
>> Thanks,
>>
>> Giles
>>
>
>

[-- Attachment #2: Type: text/html, Size: 1619 bytes --]

Re: [9fans] libframe Go port

[Kurt H Maier]

On Sat, Oct 10, 2015 at 10:29:06AM -0700, Skip Tavakkolian wrote:
> no need. just use David Hoskin's HTML5 devdraw:
>
> https://bitbucket.org/dhoskin/9webdraw

that *is* a javascript library.

khm

Re: [9fans] libframe Go port

[Skip Tavakkolian]

[-- Attachment #1: Type: text/plain, Size: 400 bytes --]

it is HTML5 (which includes JavaScript) by virtue of the fact that i needs
WebSockets support.


On Sat, Oct 10, 2015 at 10:55 AM, Kurt H Maier <khm@sciops.net> wrote:

> On Sat, Oct 10, 2015 at 10:29:06AM -0700, Skip Tavakkolian wrote:
> > no need. just use David Hoskin's HTML5 devdraw:
> >
> > https://bitbucket.org/dhoskin/9webdraw
>
> that *is* a javascript library.
>
> khm
>
>

[-- Attachment #2: Type: text/html, Size: 893 bytes --]

Re: [9fans] libframe Go port

[Skip Tavakkolian]

[-- Attachment #1: Type: text/plain, Size: 555 bytes --]

(and it needs <canvas> element, etc.)

On Sat, Oct 10, 2015 at 11:05 AM, Skip Tavakkolian <
skip.tavakkolian@gmail.com> wrote:

> it is HTML5 (which includes JavaScript) by virtue of the fact that i needs
> WebSockets support.
>
>
> On Sat, Oct 10, 2015 at 10:55 AM, Kurt H Maier <khm@sciops.net> wrote:
>
>> On Sat, Oct 10, 2015 at 10:29:06AM -0700, Skip Tavakkolian wrote:
>> > no need. just use David Hoskin's HTML5 devdraw:
>> >
>> > https://bitbucket.org/dhoskin/9webdraw
>>
>> that *is* a javascript library.
>>
>> khm
>>
>>
>

[-- Attachment #2: Type: text/html, Size: 1351 bytes --]

Re: [9fans] libframe Go port

[Kurt H Maier]

On Sat, Oct 10, 2015 at 11:05:04AM -0700, Skip Tavakkolian wrote:
> it is HTML5 (which includes JavaScript) by virtue of the fact that i needs
> WebSockets support.

HTML5 does not include javascript.

khm

Re: [9fans] libframe Go port

[Skip Tavakkolian]

[-- Attachment #1: Type: text/plain, Size: 451 bytes --]

yet 9webdraw requires HTML5 features; so it *IS NOT* just javascript (i
think this was your original "contribution" to the conversation)


On Sat, Oct 10, 2015 at 11:23 AM, Kurt H Maier <khm@sciops.net> wrote:

> On Sat, Oct 10, 2015 at 11:05:04AM -0700, Skip Tavakkolian wrote:
> > it is HTML5 (which includes JavaScript) by virtue of the fact that i
> needs
> > WebSockets support.
>
> HTML5 does not include javascript.
>
> khm
>
>

[-- Attachment #2: Type: text/html, Size: 871 bytes --]

Re: [9fans] libframe Go port

[Kurt H Maier]

On Sat, Oct 10, 2015 at 11:38:15AM -0700, Skip Tavakkolian wrote:
> yet 9webdraw requires HTML5 features; so it *IS NOT* just javascript (i
> think this was your original "contribution" to the conversation)

condolences on your tireless devotion to denying javascript is
javascript.

khm

Re: [9fans] libframe Go port

[Skip Tavakkolian]

[-- Attachment #1: Type: text/plain, Size: 729 bytes --]

cool.

did you look at Alef (2nd Ed.) or Limbo version of Acme by any chance?  i'm
curious if either of those might have been easier to translate to Go.


On Sat, Oct 10, 2015 at 8:42 AM, Giles Hutton <hutton.giles@gmail.com>
wrote:

> Hi All,
>
> I'm currently in the process of porting acme to Go, and as part of that
> I'm porting libframe as well. It's currently in a fully transliterated
> state and needs a good refactor to make it more idiomatic Go.
>
> However, my question is whether this is something that people would be
> keen on using, and if so, what's the procedure for getting it added to the
> 9fans github repo once I've finished. Is a simple pull request enough?
>
> Thanks,
>
> Giles
>

[-- Attachment #2: Type: text/html, Size: 1164 bytes --]

Re: [9fans] libframe Go port

[Tharaneedharan Vilwanathan]

[-- Attachment #1: Type: text/plain, Size: 958 bytes --]

I believe Alef would be great compared to Limbo but not sure if Alef
version is a bit out-of-date.

On Sat, Oct 10, 2015 at 10:20 AM, Skip Tavakkolian <
skip.tavakkolian@gmail.com> wrote:

> cool.
>
> did you look at Alef (2nd Ed.) or Limbo version of Acme by any chance?
>  i'm curious if either of those might have been easier to translate to Go.
>
>
> On Sat, Oct 10, 2015 at 8:42 AM, Giles Hutton <hutton.giles@gmail.com>
> wrote:
>
>> Hi All,
>>
>> I'm currently in the process of porting acme to Go, and as part of that
>> I'm porting libframe as well. It's currently in a fully transliterated
>> state and needs a good refactor to make it more idiomatic Go.
>>
>> However, my question is whether this is something that people would be
>> keen on using, and if so, what's the procedure for getting it added to the
>> 9fans github repo once I've finished. Is a simple pull request enough?
>>
>> Thanks,
>>
>> Giles
>>
>
>

[-- Attachment #2: Type: text/html, Size: 1708 bytes --]

Re: [9fans] libframe Go port

[Staven]

On Sat, Oct 10, 2015 at 03:42:42PM +0000, Giles Hutton wrote:
> Hi All,
>
> I'm currently in the process of porting acme to Go

Why?

Re: [9fans] libframe Go port

[Tharaneedharan Vilwanathan]

[-- Attachment #1: Type: text/plain, Size: 240 bytes --]

Why not?

On Sat, Oct 10, 2015 at 1:55 PM, Staven <staven@staven.pl> wrote:

> On Sat, Oct 10, 2015 at 03:42:42PM +0000, Giles Hutton wrote:
> > Hi All,
> >
> > I'm currently in the process of porting acme to Go
>
> Why?
>
>
>

[-- Attachment #2: Type: text/html, Size: 578 bytes --]

Re: [9fans] libframe Go port

[Giles Hutton]

[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]

On Sat, Oct 10, 2015 at 9:57 PM Staven <staven@staven.pl> wrote:

> On Sat, Oct 10, 2015 at 03:42:42PM +0000, Giles Hutton wrote:
> > Hi All,
> >
> > I'm currently in the process of porting acme to Go
>
> Why?
>


I've been asking myself that same question a lot actually. A friend of mine
showed me acme
a couple of months ago, and it was different and interesting enough to keep
me using it for a little while. Coming from a vim background, my assessment
at that point was that acme does separate windows/panes orders of magnitude
better than vim, but acme's text editing was a bit too simplistic compared
to vim. So my initial intention was to port acme to Go, and add in vi-style
modal editing.

Since then I've learned to love the simplicity of it, and how expressive it
can be without the burden of hundreds of different key combinations. So
I've decided to port it without adding anything extra and perhaps
experiment with a vi-acme amalgamation project some time after that.

For now, at least, it's just a fun project.

[-- Attachment #2: Type: text/html, Size: 1403 bytes --]

Re: [9fans] libframe Go port

[Staven]

On Sat, Oct 10, 2015 at 09:27:57PM +0000, Giles Hutton wrote:
> better than vim, but acme's text editing was a bit too simplistic compared
> to vim. So my initial intention was to port acme to Go, and add in vi-style
> modal editing.

What text editing features from vim do you miss in Acme?

Re: [9fans] libframe Go port

[Giles Hutton]

[-- Attachment #1: Type: text/plain, Size: 720 bytes --]

Initially my main complaint was simply the heavy use of the mouse; it felt
jarring to have to move my hand off home row. However, I've now just
chalked that up to inexperience with acme.
Right now I actually can't think of anything I particularly miss about vim
text editing, which I guess is why I've dropped the idea.

On Sun, Oct 11, 2015 at 11:10 AM Staven <staven@staven.pl> wrote:

> On Sat, Oct 10, 2015 at 09:27:57PM +0000, Giles Hutton wrote:
> > better than vim, but acme's text editing was a bit too simplistic
> compared
> > to vim. So my initial intention was to port acme to Go, and add in
> vi-style
> > modal editing.
>
> What text editing features from vim do you miss in Acme?
>
>
>

[-- Attachment #2: Type: text/html, Size: 999 bytes --]

Re: [9fans] libframe Go port

[Bakul Shah]

On Sun, 11 Oct 2015 12:07:08 -0000 Giles Hutton <hutton.giles@gmail.com> wrote:
>
> Initially my main complaint was simply the heavy use of the mouse; it felt
> jarring to have to move my hand off home row. However, I've now just
> chalked that up to inexperience with acme.
> Right now I actually can't think of anything I particularly miss about vim
> text editing, which I guess is why I've dropped the idea.

If you produced any code or design notes, I'd be interested in
looking at them & may be using them as well. Thanks.