caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Maxence Guesdon <maxence.guesdon@inria.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] cameleon2
Date: Tue, 27 Mar 2007 09:34:44 +0200	[thread overview]
Message-ID: <20070327093444.3e324784@tintin.inria.fr> (raw)
In-Reply-To: <20070326113406.61b3effe@tintin.inria.fr>

On Mon, 26 Mar 2007 11:34:06 +0200
Maxence Guesdon <maxence.guesdon@inria.fr> wrote:

> On Mon, 26 Mar 2007 11:14:06 +0200
> Christophe Raffalli <christophe.raffalli@univ-savoie.fr> wrote:
> 
> > 
> > > 
> > > Yes indeed. There's a FAQ about this:
> > > http://home.gna.org/cameleon/faq.en.html#noocamlsyntaxhighlight
> > > 
> > > I'll add some code to make chamo use an additional directory for
> > > languages specs files (used by gtksourceview) when the ocaml mode is
> > > not available.
> > > 
> > 
> > Why not having the make install of either cameleon either
> > lablgtksourceview copy ocaml.lang in the general directory (if it is not
> > already there) ? Moreover, the distrib of lablgtksourceview has
> > ocaml.lang in it.
> 
> On debian/unstable, ocaml.lang is now included in the gtksourceview-common
> package. I'm not sure that walking on another package's feet is the right
> way to do. But may be testing if the file exists and copy it if it does
> not could be ok, indeed.
> 
> > Just another question: Where to find a readable description on
> > the customization of Highlighting. I have seen a screen shot mixing
> > two distincts fonts in gedit ... but was unable to discover how you do
> > that. I found hat the .lang file defines the regexp needed for
> > highlighting, but I did not find where to choose the color and fonts ...
> > all this seems bably documented
> 
> It's the application's responsability to associate fonts and colors to
> syntax elements. By now, Chamo can only make the user choose one font for
> all text of a gtksourceview.
> What should be done to have different fonts for different syntax elements
> is to improve the gtksv_utils module included in cameleon2, which allows
> to use gtksourceviews in various (ocaml) applications and share the same
> fonts and colors associations to syntax elements.
> 
> For example, topcameleon (a graphical toplevel included in cameleon2) and
> chamo share the same colors and fonts for the ocaml syntax mode.
> 
> By now, the associations between style and syntax elements for each mode
> are stored in your /.mlgtksourceview directory, one xml file per language.
> 
> I add to the todo list the ability to have  a different font associated to
> each syntax element.

In fact, there is no font attribute in source tag styles of gtksourceviews.
I could not find any gedit screenshot showing two distinct fonts in the same
gtksourceview.

Here is a little explanation about how the gtksourceview works (as I
understand it).

Gtk offers buffers and views on buffers. There can be more than one view on
one buffer. In each buffer, one can define "tags", and associate parts of
the text in a buffer to these tags. These tags can have different style
which allows to render the (parts of) text in different colors, font
weight, ... depending on the associated tags. This is for Gtk.

What gtksourceview brings is a convenient way to define syntax elements and
new buffers and views, inheriting from the original ones of gtk. The new
buffers (source_buffers) can be given a language, which is a description of
syntax elements. The buffers then automatically define tags
corresponding to the syntax elements of the language and associates these
tags to the parts of the text in the buffer, according to the definition
of the syntax elements (keywords, beginning and ending of blocks, ...). The
application only has to define the styles of each of these tags to provide
syntax highlighting.

The styles associated to "syntax tags" can be used to define background and
foreground colors, bold, italic, strikethrough, and underline attributes.

So each application has to define (and eventually store) the attributes
associated to each "syntax tags" for each language.

I hope this explanation was useful (and quite clear).

By the way, the lablgtksourceview library offers bindings to the
gtksourceview library (and so the features above):
http://helm.cs.unibo.it/software/lablgtksourceview/

This library is used in Chamo to provide syntax highlighting.

-- 
Maxence Guesdon
http://yquem.inria.fr/~guesdon/
http://devel.inria.fr/rocq/


  reply	other threads:[~2007-03-27  7:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-24 14:08 cameleon2 Christophe Raffalli
2007-03-24 18:33 ` [Caml-list] cameleon2 Christophe Raffalli
2007-03-24 23:52   ` Christophe Raffalli
2007-03-25  8:53     ` Christophe Raffalli
2007-03-26  6:53       ` Maxence Guesdon
2007-03-26  9:14         ` Christophe Raffalli
2007-03-26  9:34           ` Maxence Guesdon
2007-03-27  7:34             ` Maxence Guesdon [this message]
2007-03-27  9:46               ` Christophe Raffalli
     [not found]               ` <4608E388.2030509@univ-savoie.fr>
2007-03-27 21:03                 ` Maxence Guesdon
2007-03-27 23:14                   ` Christophe Raffalli

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=20070327093444.3e324784@tintin.inria.fr \
    --to=maxence.guesdon@inria.fr \
    --cc=caml-list@inria.fr \
    /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).