caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Louis Gesbert <louis.gesbert@ocamlpro.com>
To: caml-list@inria.fr, Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
Subject: Re: [Caml-list] LablGtk3 beta1
Date: Thu, 06 Dec 2018 11:05:18 +0100	[thread overview]
Message-ID: <2293946.qdrdMMZSk8@agaric> (raw)
In-Reply-To: <966B3CBE-29BB-4336-BDBF-0012723E7099@math.nagoya-u.ac.jp>

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

Hi Jacques,

I'll try to package your branch in a `lablgtk3` opam package, and see if I can run some tests. Thanks for the port!

Louis Gesbert — OCamlPro

> - Jacques Garrigue, 06/12/2018 15:33 -
> Dear LablGtk users,
> 
> Due to the planned deprecation of gtksourceview2 in Debian,
> we have been working on a stripped down port of LablGtk2 to Gtk-3.
> 
> A first beta is available for download at the usual location:
> 	http://lablgtk.forge.ocamlcore.org
> 	https://forge.ocamlcore.org/frs/download.php/1769/lablgtk-3.0.beta1.tar.gz
> 
> There is no opam package yet, because I’m not sure how to do that:
> I seem to need to add a new conf-gtksourceview3 package too, and I’m not
> sure how to proceed. Help accepted.
> 
> Note that this is not the originally planned introspection based port, but
> a manual port of lablgtk2, dropping widgets that are no longer
> available. It is of course possible to add new widgets if people
> are willing to contribute.
> 
> The main goal is to allow application using lablgtksourceview,
> such as CoqIDE, to compile on top of Gtk-3. Since Gtk-2 itself
> stays available, lablgtk2 will continue to be supported for other
> applications.
> 
> The code is in the lablgtk3 branch:
> 	https://github.com/garrigue/lablgtk/tree/lablgtk3
> There is an ongoing discussion
> 	https://github.com/garrigue/lablgtk/issues/2
> 
> The current status is that a modified version of CoqIDE compiles
> and runs.
> 
> Please report issues on GitHub.
> 
> Jacques Garrigue
> 
> 

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-12-06 10:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06  6:33 Jacques Garrigue
2018-12-06 10:05 ` Louis Gesbert [this message]
2018-12-06 10:35 ` Gabriel Scherer
2018-12-07 10:04 ` Emilio Jesús Gallego Arias
2018-12-07 10:25   ` Gabriel Scherer
2018-12-07 18:34     ` Emilio Jesús Gallego Arias
2018-12-11  3:09       ` Francois Berenger
2018-12-11 11:34         ` Louis Gesbert
2018-12-14 11:41           ` Emilio Jesús Gallego Arias
2018-12-14 11:38         ` Emilio Jesús Gallego Arias
2018-12-16  8:12           ` Jacques Garrigue
2018-12-17 12:11             ` Emilio Jesús Gallego Arias
2018-12-18 14:33               ` David Allsopp
2018-12-19  1:20                 ` Emilio Jesús Gallego Arias
2018-12-19 10:15                   ` David Allsopp
2018-12-19 11:13                     ` Emilio Jesús Gallego Arias
2018-12-19 11:50                       ` David Allsopp
2018-12-19 16:41                         ` Emilio Jesús Gallego Arias
2018-12-20 11:33                           ` David Allsopp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2293946.qdrdMMZSk8@agaric \
    --to=louis.gesbert@ocamlpro.com \
    --cc=caml-list@inria.fr \
    --cc=garrigue@math.nagoya-u.ac.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).