From: Christophe Raffalli <christophe.raffalli@univ-savoie.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] cameleon2
Date: Tue, 27 Mar 2007 11:46:06 +0200 [thread overview]
Message-ID: <4608E7DE.5060107@univ-savoie.fr> (raw)
In-Reply-To: <20070327093444.3e324784@tintin.inria.fr>
>
> 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.
>
The third screen shot on this page:
http://gtksourceview.sourceforge.net/screens.html
> 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).
Yes very much, thanks. Remark: my previous mail did criticize the doc of gtksourceview not
the one on cameleon or lablgtksourceview, but after rereading it I see it was not so clear,
so sorry for that.
>
> 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.
>
--
Christophe Raffalli
Université de Savoie
Batiment Le Chablais, bureau 21
73376 Le Bourget-du-Lac Cedex
tél: (33) 4 79 75 81 03
fax: (33) 4 79 75 87 42
mail: Christophe.Raffalli@univ-savoie.fr
www: http://www.lama.univ-savoie.fr/~RAFFALLI
next prev parent reply other threads:[~2007-03-27 9:44 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
2007-03-27 9:46 ` Christophe Raffalli [this message]
[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=4608E7DE.5060107@univ-savoie.fr \
--to=christophe.raffalli@univ-savoie.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).