Re: Re-using bootstrap in the half-strap
Hello, Christopher Allan Webber writes: > A thought this morning... one challenge with Guile's 2.1 branch is it > takes a log time to bootstrap. There are good reasons for this, and > Andy Wingo has documented them: > > > http://wingolog.org/archives/2016/01/11/the-half-strap-self-hosting-and-guile > > However, I can't help but wonder if we could reuse the initial > bootstrapped compiler. What if we had an external package that > contained *just* the scheme interpreter used to bootstrap the rest of > the system? We might not need to separate the codebase, but have this > be a separate make output. > > If you could package *just* the bootstrapped compiler, if a user doesn't > feel like waiting through the whole bootstrap process, they could use > the existing bootstrap package, like: > > ./configure --with-bootstrap=/path/to/guile-bootstrap > > and maybe we could have a guile-bootstrap package in guix, etc. If you > want to do the whole bootstrap yourself in the Guile package, you could > do so, but it wouldn't be a requirement, assuming you had that separate > package... > > Thoughts? Useful? Badly informed? > - Chris I feel the same way. I don't know about the technical details, but such convenience would be more than welcome. Thanks, -- Mathieu Lirzin
Re: [PATCH 0/4]
Catonano writes: > This is a bunch of emacs packages I made on the same branch, so git > shouldn't claim any inconsistency with these. > > I hope this attempt is gonna be successful > > they are > > 1) emacs.queue > 2) emacs-pkg-info > 3) emacs-spinner > 4) emacs-seq Please make an effort to send these patches to the appropriate mailing list. Thanks. -- Mathieu Lirzin
Re: [PATCH] emacs-epl
Hi, Catonano writes: > From 0d303576f88d00f2d3b58e7c452bcf575876b124 Mon Sep 17 00:00:00 2001 > From: humanitiesNerd > Date: Thu, 26 May 2016 01:31:30 +0200 > Subject: gnu: Add new variable (emacs-epl). > > * gnu/packages/emacs.scm (emacs-epl): New variable. Please send this to guix-devel instead, thanks. -- Mathieu Lirzin
Re: rename from q to queue
Hello, ra...@openmailbox.org writes: > The following library uses a pun writing 'q' instead of 'queue': > <http://www.gnu.org/software/guile/manual/html_node/Queues.html> > > I propose renaming the module from (ice-9 q) to (ice-9 queue) and > spelling queue throughout in the usual scheme style of using full > words. > > Attached is a patch that does this. If there is a positive consensus > on the rename I am happy to apply the change to all the documentation > and tests too. As stated on IRC I think it is an improvement to have a meaningful name for this module. However as pointed in other replies, It is not possible to implement it this way because (ice-9 q) is a public API. One way to not break backward compatibility, would be to move (ice-9 q) code in (ice-9 queue) and make (ice-9 q) use it and re-export every variable with its old name. Finally we will need a way to give the information that (ice-9 q) module is deprectated to the users. I am not sure what is the best way to achieve this. Maybe with: (eval-when (expand load eval) (display "..." (current-warning-port))) What do others think? -- Mathieu Lirzin
Re: Elisp branch ready for merge (??)
Christopher Allan Webber writes: > Mathieu Lirzin writes: > [...] >> Small nitpick. Could you remove the extra spaces at the start of >> indented lines? :) >> >> I know this practice is/was a common practice in Guile but even if it >> looks prettier with indentation, this is not the proper change log >> format described by GCS and recognized by 'change-log-mode' in Emacs. > > I could... but I'm hesitant to do so if it's not the standard ways to do > things in Guile's repository. I'll leave that question to whoever is > interested in merging it. If they'd like me to change it, I'll do it, > and since they have commit access, I consider them the authority. Sure, it will be an opportunity to discuss this major issue! ;) -- Mathieu Lirzin
Re: Elisp branch ready for merge (??)
Christopher Allan Webber writes: > Well, I didn't think I'd have time to do this (and in a sense I didn't) > but: > https://gitlab.com/dustyweb/guile/tree/merge-bipt-elisp-wip > > I've rebased the whole branch against git master and added ChangeLog > style entries. "make check" is passing. It seems to me that it's ready > for merge. I did the best I could on the ChangeLog additions, both with > my limited ChangeLog experience and from my limited Guile internals > experience. So, corrections welcome, but otherwise... Nice! Small nitpick. Could you remove the extra spaces at the start of indented lines? :) I know this practice is/was a common practice in Guile but even if it looks prettier with indentation, this is not the proper change log format described by GCS and recognized by 'change-log-mode' in Emacs. -- Mathieu Lirzin
Re: What's needed to get elisp updates into Guile master?
Christopher Allan Webber writes: > Mathieu Lirzin writes: >> >> You should bring that on emacs-devel where most people seem to think >> that a 'git commit -m "..."' with the actual diff is self explanatory. >> :) > > I'm afraid to. The emacs list has had strong responses moving between > tremendous enthusiasm for the guile-emacs work to outright hostility. I > think there are only a couple of hostile people, but they are vocal. > I'd prefer to have the next stage of things merged before I reach out > again. > > But maybe I'm being irrational. I could probably still ask for help. I was implicitly referring to a current discussion on emacs-devel: https://lists.gnu.org/archive/html/emacs-devel/2016-03/msg00180.html Sorry for not giving the context of my sarcasm at first. Anyway, thanks for giving guile-emacs some love! :) -- Mathieu Lirzin
Re: What's needed to get elisp updates into Guile master?
Christopher Allan Webber writes: > Christopher Allan Webber writes: > >> So even better news: I've successfully rebased BT Templeton's wip elisp >> branch on top of guile master... you can get it here: >> >> https://gitlab.com/dustyweb/guile/tree/merge-bipt-elisp-wip >> >> Maybe I should update the Guix package to make use of that? > > So I'd like to get this merged in before it bitrots too heavily. > It would be a shame to not get it in, after how far it's come! Agreed. > Now that it's rebased and running on master, there are two issues I see > that would need to be addressed: > > - The most recent commit disables three tests (specific to elisp). >They should probably be re-enabled, or at worst at least commented >out with a warning rather than being switched to expect-fail as they >are right now. > >I'd prefer re-enabling them with fixes; for now, commenting out with >clear explaination still seems better than bitrot though. (The other >tests all do pass.) I don't understand why you would want to do that. 'expect-fail' is the correct semantic for a test that should pass but is known to currently fail, like in TDD. Do I miss something? > - The commits are not in ChangeLog style format and are fairly terse in >their message. I imagine it's a requirement to fix that. This seems >like the bigger challenge; if anyone but the original author were to >do it, there would have to be some careful reading to figure out what >the purpose of each commit and change meant. That seems like some >work. I'm not sure I have the time for it... are there any >volunteers? You should bring that on emacs-devel where most people seem to think that a 'git commit -m "..."' with the actual diff is self explanatory. :) Indeed, it seems a tedious job to add those change logs since it requires to understand the purpose of the commit. The volunteer should be familiar with Elisp in general and the limitations of current/previous Guile implementation. > Is there general agreement that if we can get these two things done, > that it would be worth merging this? I think it would be great. -- Mathieu Lirzin
Re: [PATCH] Added Artanis info to new main page
l...@gnu.org (Ludovic Courtès) writes: > Mathieu Lirzin skribis: > >> l...@gnu.org (Ludovic Courtès) writes: >> >>> Luis Felipe López Acevedo skribis: >>> >>>> On 2015-11-08 15:35, Dirk-Jan C. Binnema wrote: >>> >>> [...] >>> >>>>> With the rest of the website looking so very welcoming, I could imagine >>>>> that the gdb screenshot might look a bit scary to newcomers; perhaps >>>>> (part of) the foo-pretty-printer[1] would be a bit easier to digest? >>>>> >>>>> https://sourceware.org/gdb/onlinedocs/gdb/Writing-a-Guile-Pretty_002dPrinter.html >>>>> >>>>> Cheers, >>>>> Dirk. >>>> >>>> Mathieu, could you take the screenshot? Maybe with your suggestions >>>> and Dirk-jan's? I don't use GDB (I'm not there yet :P). >>> >>> Mathieu? What’s up? :-) >> >> I was waiting to get the screenshot done, but I have overestimated my >> motivation to look into GDB Guile pretty printing. I think that for now >> we can use: >> >> https://multimedialib.files.wordpress.com/2015/11/gdb-guile1.png > > LGTM! Could you add it to the web page? > Done in 7a2a06a1dd8dc4e6120ed5e3a6969a6dc8361a35. Thanks, -- Mathieu Lirzin
Re: [PATCH] Added Artanis info to new main page
l...@gnu.org (Ludovic Courtès) writes: > Mathieu Lirzin skribis: > >> l...@gnu.org (Ludovic Courtès) writes: >> >>> Mathieu? What’s up? :-) >> >> I was waiting to get the screenshot done, but I have overestimated my >> motivation to look into GDB Guile pretty printing. I think that for now >> we can use: >> >> https://multimedialib.files.wordpress.com/2015/11/gdb-guile1.png > > LGTM! Could you add it to the web page? I will do that in a batch with my other patches. -- Mathieu Lirzin
Re: [PATCH] libraries: Abstract packages and categories.
Mathieu Lirzin writes: > I will take a look on this old CVS thing and ask if it don't get it. ^^ ^^ at I I am french and tired. :) -- Mathieu Lirzin
Re: [PATCH] libraries: Abstract packages and categories.
l...@gnu.org (Ludovic Courtès) writes: > Mathieu Lirzin skribis: > >> +;;; XXX: In order to allow a proper alignement of keywords in Emacs we need >> to >> +;;; enable the prefix keyword type ':NAME'. >> +(read-set! keywords 'prefix) > > If you want to take that route, you need to make sure the reader change > is effective when the file is read, rather than at run time: > > (eval-when (expand load eval) > (read-set! keywords 'prefix)) > > I would suggest fixing Emacs though, or ignoring the limitation for now. > > WDYT? This makes sense, I have removed this hack. > Other than this minor issue, I find it very nice! > > I’ve added you to the Savannah group so you can push changes to the web > site. Please restrict yourself to guile-web.git and post changes here > beforehand (and feel free to ping those lazy maintainers when it takes > too long!). Thanks. :) > When you push a change to the web site’s source, can you please update > the CVS web repo at the same time? See > <https://savannah.gnu.org/cvs/?group=guile> for instructions. If in > doubt, don’t hesitate to ask. I will take a look on this old CVS thing and ask if it don't get it. -- Mathieu Lirzin
Re: [PATCH] Added Artanis info to new main page
l...@gnu.org (Ludovic Courtès) writes: > Luis Felipe López Acevedo skribis: > >> On 2015-11-08 15:35, Dirk-Jan C. Binnema wrote: > > [...] > >>> With the rest of the website looking so very welcoming, I could imagine >>> that the gdb screenshot might look a bit scary to newcomers; perhaps >>> (part of) the foo-pretty-printer[1] would be a bit easier to digest? >>> >>> https://sourceware.org/gdb/onlinedocs/gdb/Writing-a-Guile-Pretty_002dPrinter.html >>> >>> Cheers, >>> Dirk. >> >> Mathieu, could you take the screenshot? Maybe with your suggestions >> and Dirk-jan's? I don't use GDB (I'm not there yet :P). > > Mathieu? What’s up? :-) I was waiting to get the screenshot done, but I have overestimated my motivation to look into GDB Guile pretty printing. I think that for now we can use: https://multimedialib.files.wordpress.com/2015/11/gdb-guile1.png Sorry every one for my late answer. -- Mathieu Lirzin
Re: Ideas for a Guile tutorial to go with the new site
Hi Christopher, Christopher Allan Webber writes: > - Intro > - Getting up and running >(picture of one of those robots with a wind-up-toy-key on its back?) >+ How to start guile from the command line, add readline support >+ Editor setup, simple > > Details how to write some scheme with any editor, maybe makes a > free software editor recommendation of something simple that's not > too hard to get going with Scheme. Would GEdit work? As much as I appreciate my Emacs environment, I think GEdit + basic REPL in a terminal is the right choice for presenting Guile. I think it would be better not explaining how to setup Geiser+Emacs in this tutorial and just mentioning it by giving a link to separate resource (which don't exist yet...) for those who are already familiar with Emacs. > I'm sure there are other things! But I think a tutorial in this style > might be fun, and would fit the site well. And the desire for a good > tutorial has been expressed many times. This is definitely a great initiative! Thanks, -- Mathieu Lirzin
Re: [PATCH] Added Artanis info to new main page
Luis Felipe López Acevedo writes: > On 2015-11-06 04:19, l...@gnu.org wrote: >> A bit hard to read, so I don’t know. Original screenshots at: >> >> http://www.fdn.fr/~lcourtes/tmp/gdb-guile2-cropped.png >> http://www.fdn.fr/~lcourtes/tmp/gdb-guile1.png >> http://www.fdn.fr/~lcourtes/tmp/gdb-guile2.png >> http://www.fdn.fr/~lcourtes/tmp/gdb-guile3.png >> >> Thoughts? > > I'm fine with adding both Weechat and GDB. For the latter, as Mathieu > says, I think a close-up would work. For example: > > https://multimedialib.files.wordpress.com/2015/11/gdb-guile1.png I'm fine with Adding both Weechat and GDB too. For the GDB pic, I don't have a strong opinion on the amout of zoom. It might improve readability to use a “slight“ hinting for the font. A less black emacs theme might fit the Guile website better (like Wombat or Adwaita). OTOH I'm not the designer here, so I'm confident you will DTRT. ;) Ludo: Can you describe how to reproduce the example from your screenshot? -- Mathieu Lirzin
[PATCH] libraries: Abstract packages and categories.
Hi,
Since the “libraries” page in the website will probably change regularly
it is useful to have some abstractions to facilitate the maintenance.
A second step would be to provide a way to sync the software entries
with Guix package definitions.
--
Mathieu Lirzin
>From 7ad1e1bd620d48099013b276be2e89ea48a3ec1c Mon Sep 17 00:00:00 2001
From: Mathieu Lirzin
Date: Sun, 8 Nov 2015 00:06:53 +0100
Subject: [PATCH] libraries: Abstract packages and categories.
This provides a distinction between the data and the SHTML
representation.
* website/apps/base/libraries-page.scm (texi->shtml, package)
(package->shtml, category, category->shtml, %packages-core)
(%packages-gui, %packages-file-formats, %packages-tools)
(%packages-apps): New procedures.
(, ): New record types.
(guile-lib, guile-lint, guile-reader, guile-syntaxe-parse)
(guile-clutter, guile-gnome, guile-gtk, guile-ncurses, guile-sdl)
(libruin, artanis, gnutls, guile-avahi, guile-rpc, scss, autogen, guix)
(libchop, beast, geda, lilypond, skribilo, snd, texmacs, xchat-guile)
(%categories): New variables.
---
website/apps/base/libraries-page.scm | 651 ++-
1 file changed, 408 insertions(+), 243 deletions(-)
diff --git a/website/apps/base/libraries-page.scm b/website/apps/base/libraries-page.scm
index 320b17b..2e15c76 100644
--- a/website/apps/base/libraries-page.scm
+++ b/website/apps/base/libraries-page.scm
@@ -1,5 +1,6 @@
;;; Guile website --- GNU's extension language website
;;; Copyright © 2015 Luis Felipe López Acevedo
+;;; Copyright © 2015 Mathieu Lirzin
;;;
;;; This file is part of Guile website.
;;;
@@ -17,10 +18,396 @@
;;; along with Guile website. If not, see <http://www.gnu.org/licenses/>.
(define-module (website apps base libraries-page)
+ #:use-module (srfi srfi-1)
+ #:use-module (srfi srfi-9)
+ #:use-module (srfi srfi-26)
+ #:use-module (texinfo)
+ #:use-module (texinfo html)
#:use-module (website apps base components)
#:use-module (website utils)
#:export (libraries-page))
+(define (texi->shtml str)
+ "Return a SHTML representation of texinfo fragment STR."
+ ;; 'texi-fragment->stexi' uses a string port so make sure it's a
+ ;; Unicode-capable one (see <http://bugs.gnu.org/11197>.)
+ (with-fluids ((%default-port-encoding "UTF-8"))
+(stexi->shtml (texi-fragment->stexi str
+
+;;; A package entry.
+(define-record-type
+ (make-package name description url tags license)
+ package?
+ (namepackage-name) ;string
+ (description package-description) ;string
+ (url package-url) ;string
+ (tagspackage-tags) ;list of strings
+ (license package-license)) ;string
+
+(define* (package #:key name description url tags license)
+ "Convenient procedure to provide keyword when defining a package entry."
+ (make-package name description url tags license))
+
+(define (package->shtml pkg)
+ "Return an SHTML representation of package PKG."
+ `(section
+(@ (class "lib"))
+(h3 (a (@ (href ,(package-url pkg)))
+ ,(package-name pkg)))
+(p ,@(map (lambda (tag)
+ `(span (@ (class "guile-version-tag")) ,tag))
+ (package-tags pkg)))
+,(texi->shtml (package-description pkg))
+(p (b "License: ") ,(package-license pkg
+
+;;; XXX: In order to allow a proper alignement of keywords in Emacs we need to
+;;; enable the prefix keyword type ':NAME'.
+(read-set! keywords 'prefix)
+
+
+;;;
+;;; Core.
+;;;
+
+(define guile-lib
+ (package :name "Guile-lib"
+ :description "Guile-Lib is intended as an accumulation place for
+pure-scheme Guile modules, allowing for people to cooperate integrating their
+generic Guile modules into a coherent library. Think \"a down-scaled,
+limited-scope CPAN for Guile\"."
+ :url "http://www.nongnu.org/guile-lib/";
+ :tags '("Guile 2.0" "Guile 1.8")
+ :license "LGPL 2.1 or later"))
+
+(define guile-lint
+ (package :name "Guile-lint"
+ :description "Syntactic and semantic checks on Guile 1.8 programs
+and modules. Picks up things like unbound variables in hard-to-reach
+places (note that Guile 2.0 brings part of Guile-Lint's functionality through
+its @uref{manual/html_node/Compilation.html, compiler warnings.})"
+ :url "http://user42.tuxfamily.org/guile-lint/index.html";
+ :tags '("Guile 1.8")
+ :license "GPL 2 or later"))
+
+(define guile-reader
+ (package :name "Guile-Reader"
+ :description "Guile-Reader is a toolkit to build readers for Guile,
+making it easy to extend the syntax. It makes it possible to have several
+coexisting readers, recognizing different syntaxes."
+ :url "http://www.nongnu.org/guile-reader/";
+ :tags '("Guile 2.
Re: [PATCH] Added Artanis info to new main page
Nala Ginrut writes: > On Wed, 2015-11-04 at 22:27 +0100, Mathieu Lirzin wrote: >> Also you have removed “Ragnarok”. if it is related to this change can >> you explain it in the commit log otherwise please do a separate patch. >> > > Now that Luis has updated to add Artanis to libraries, I think I don't > have to send the patch twice. ;-) > Anyway, I could explain it here. Ragnarok as a generic server is > obsolete now, it'll be replaced by Artanis as a monolithic framework > with a strong server core (this will happen in v0.2+). Thanks for your explanation. In fact Luis has only append Artanis without removing Ragnarok, so here is the updated patch to remove the Ragnarok entry. >From 8df2c33eff51eb74cae4f4324eece56a8be283fc Mon Sep 17 00:00:00 2001 From: Mathieu Lirzin Date: Fri, 6 Nov 2015 21:04:55 +0100 Subject: [PATCH] libraries: Remove Ragnarok. * website/apps/base/libraries-page.scm (libraries-page): Remove Ragnarok which has been declared obsolete by its author. Suggested-by: Nala Ginrut --- website/apps/base/libraries-page.scm | 8 1 file changed, 8 deletions(-) diff --git a/website/apps/base/libraries-page.scm b/website/apps/base/libraries-page.scm index b2a4775..320b17b 100644 --- a/website/apps/base/libraries-page.scm +++ b/website/apps/base/libraries-page.scm @@ -208,14 +208,6 @@ "parsing user-supplied style information and for querying the " "resulting cascade using SXML/SDOM documents or plain text.") (p (b "License: ") "GPL")) - (section - (@ (class "lib")) - (h3 (a (@ (href "http://gitorious.org/glow/ragnarok/";)) - "Ragnarok")) - (p (span (@ (class "guile-version-tag")) "Guile 2.0")) - (p "A server for HTTP and other Internet protocols, with support " - "for templates, CGI, and more.") - (p (b "License: ") "LGPL 3 or later")) (h2 (@ (id "tools")) "Tools") (p "These projects are tools for or implemented with Guile. Mostly, " "these are the types of things that automate documentation or " -- 2.6.2 Since you are the author of Ragnarok, I would suggest to add in the README file a statement that Ragnarok is obsolete/unmaintained. Thanks, -- Mathieu Lirzin
Replace Sly on the website main page? (was: [PATCH] Added Artanis info to new main page)
Luis Felipe López Acevedo writes: > On 2015-11-05 04:58, l...@gnu.org wrote: [...] >> GDB! What would the associated picture be? >> > > GDB, The GNU Project Debugger? It has a mascot: > > https://www.gnu.org/software/gdb/mascot/ > > Someone on #guile also suggested WeeChat <http://weechat.org/>, which > can be scripted using Guile: > > http://weechat.org/files/doc/devel/weechat_scripting.en.html Maybe It is better to use Weechat to emphasize the idea that Guile is not focus only on GNU packages. -- Mathieu Lirzin
Re: [PATCH] Added Artanis info to new main page
l...@gnu.org (Ludovic Courtès) writes: > "Thompson, David" skribis: >> What should we put in its place? > > GDB! What would the associated picture be? I'm fine with adding GDB. What about adding its current mascot? Another solution would be to make a zoomed screenshot of emacs GUD with one breakpoint in the fringe. WDYT? Thanks for your suggestion. -- Mathieu Lirzin
Re: [PATCH] gnu: guile: Add guile-irregex.
Christopher Allan Webber writes: > Irregex, packaged for Guile! Horray! > > On a side note, it would really be nice to have a > r6rs-build-system... starting to result in a lot of similar spaghetti in > a few of these packages. > > I don't know how that works though, so consider that a research project > for another day. > > >>From 38edbac8ab42e1518424fd2da4d53ece2c96094c Mon Sep 17 00:00:00 2001 > From: Christopher Allan Webber > Date: Thu, 5 Nov 2015 12:20:03 -0600 > Subject: [PATCH] gnu: guile: Add guile-irregex. > > * gnu/packages/guile.scm (guile-irregex): New variable. Hi, I guess you have sent this to the wrong ML. Can you send it to guix-devel? Thanks, -- Mathieu Lirzin
Re: [PATCH] Added Artanis info to new main page
Hi, Nala Ginrut writes: > Hi folks! > Our new main site really rock, right? > > I believe that we may add more to "Applications using Guile". > Here's mine, the entry of GNU Artanis. I think it would be a great idea to include Artanis in Guile's website. >>From e6b323352382898b570e81c9f43b970c3facb1a3 Mon Sep 17 00:00:00 2001 > From: Nala Ginrut > Date: Thu, 5 Nov 2015 02:42:49 +0800 > Subject: [PATCH] Added GNU Artanis info > > * website/apps/base/index-page.scm > * website/apps/base/libraries-page.scm It would be nice to use ChangeLog style for the website. What about something like: --8<---cut here---start->8--- libraries: Add GNU Artanis. * website/apps/base/libraries-page.scm (libraries-page): Add GNU Artanis. * website/apps/base/index-page.scm (index-page): Likewise. --8<---cut here---end--->8--- Also you have removed “Ragnarok”. if it is related to this change can you explain it in the commit log otherwise please do a separate patch. On a more general topic, IIUC Artanis is not an “application” but a library so maybe it is not a good idea to include it in (index-page) since it uses the term “applications using Guile“ (The same problem will apply to Sly I guess). WDYT? Thanks, -- Mathieu Lirzin
Re: Alternative logo proposal
Thorsten Wilms writes: > Hi! > > I wasn't subscribed before, but got aware of Luis's mockups via > IRC. While I think there's a lot just done right on the website > mockup, I see issues with the logo proposal. > > The G in parens concept is fine, but the weighting could be > better. Even then, a G that is all round on the outside is hard to > make harmonious ... and to keep at a far distances from Google's new > G. Then in the lockup, where one paren has to step in the background, > the concept falls apart, to my eyes. > > So here's my (first?) proposal, still inspired by Luis's work: > http://i.imgur.com/oKyEvkr.png Thanks for proposing an alternative. I rather prefer Luis' logo which I find perfectly harmonious. -- Mathieu Lirzin
Re: New logo and website design proposal
Luis Felipe López Acevedo writes: > Hello list, > > As part of the Guile project I imagine, I'd like to propose these > visual modifications for the logo and the website. > > Logo > https://multimedialib.files.wordpress.com/2015/09/guile-logo-proposal-2015-06-16.png > > Website mockup (some rough sketches here) > https://multimedialib.files.wordpress.com/2015/09/website-mockup-2015-09-15.png > > My intention with this proposal is, hopefully, to modernize the image > of the project a bit and make it more attractive to potential users. > > > Your comments are very welcomed, Amazing! If you need help on the SXML part I'm willing to help. -- Mathieu Lirzin
