[Tickit-dev] C library project
Bruce Mitchener
bruce.mitchener at gmail.com
Mon Dec 22 22:41:51 GMT 2014
Hello!
As you know, but other readers would not, I'm using libtickit from the C
level and have written bindings to use it from Open Dylan (
http://opendylan.org/). The bindings can be found at
https://github.com/dylan-foundry/tickit-dylan/.
As such, I've found that having the Tickit::Window code in C would indeed
be useful and so I've started on this:
https://github.com/waywardmonkeys/libtickit/tree/tickit-window
The files src/window.c and include/tickit-window.h include my work in
progress. I'm building my own widget layer in Dylan, but having the
C-based tickit-window is going well.
(All of this is so that I can put a terminal-based UI on the Deuce editor.
Deuce is a descendant of ZWEI from the Lisp Machine days which was i turn a
descendant of early emacs. My code for this is present at
https://github.com/dylan-foundry/deuce-terminal.)
- Bruce
On Sun, Dec 21, 2014 at 9:58 PM, Paul "LeoNerd" Evans <
leonerd at leonerd.org.uk> wrote:
>
> I've started to create more of a first-class presence of the C library
> part of Tickit now. Primarily the source code is now mirrored up to
> Launchpad:
>
> https://launchpad.net/libtickit
>
> I've created a few blueprints ("feature request" discussion areas,
> basically):
>
> https://blueprints.launchpad.net/libtickit
>
> The first one to look at is the "window" one, the feature of moving the
> Window code into the C library:
>
> https://blueprints.launchpad.net/libtickit/+spec/window
>
> Having done that we should be in a position to declare a version 0.1
> release; hence the milestone:
>
> https://launchpad.net/libtickit/+milestone/v0.1
>
> Further plans from that start to depart from the Perl module some more,
> into some features of the RenderBuffer that make it easier for Neovim
> to use, and other use-cases I hadn't originally considered in the Perl
> use-case.
>
> Also, purely as a matter of internal implementation neatening, I'd like
> to move libtermkey into libtickit itself:
>
> https://blueprints.launchpad.net/libtickit/+spec/termkey-merge
>
> Having done that, there'll start being more exciting things we can do
> with the term driver once it has a tighter integration with the input
> later. (Terminal) clipboard management and RGB8 colours come to mind.
>
> --
> Paul "LeoNerd" Evans
>
> leonerd at leonerd.org.uk
> http://www.leonerd.org.uk/ | https://metacpan.org/author/PEVANS
>
> _______________________________________________
> Tickit-dev mailing list
> Tickit-dev at leonerd.org.uk
> http://mail.leonerd.org.uk/mailman/listinfo/tickit-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.leonerd.org.uk/pipermail/tickit-dev/attachments/20141223/0e41e28e/attachment.html>
More information about the Tickit-dev
mailing list