Re: [ANN] Guile Hall 0.3.0 released

[Catonano <catonano@gmail.com>]

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

Il giorno dom 24 mag 2020 alle ore 23:22 Alex Sassmannshausen <
alex.sassmannshausen@gmail.com> ha scritto:

> Hey Catonano,
>

Hi Alex !

Thank you for your review ☺

I liked the style of your text.  I've taken the liberty to expand on it
> some more — but I'm happy to go with your version if you / the
> maintainers prefer.
>

I'd go with my version, if you don't mind


>
> Also, I changed references from guile-hall to Hall.  Whilst the name of
> the folder etc is guile-hall, the project itself is called Hall, or
> Guile Hall to make it part of the Guile family :-)
>

Well, yes, I welcome this suggestion of yours !

The project name is "Hall", not "guile-hall"

Just a few words on why I'd prefer my version

There are 2 sentences in your version that i find debatable

The first one is:
"Hall helps you create, manage and package your Guile projects through a
simple commandline interface"

because there is nothing in Guile that is not meant for usage at the
command line, unfortunately

Also, the Autotools documentation suffers from the same problem of almost
ALL the GNU documentation: it's focused on properties and features and
completely (?) disregards user stories

Because of this reason, if I was a neecomer reading the Guile manual, I
wouldn't be able to associate the "create, manage and package your Guile
project" to the API offered by the Autotools machinery

Such association is not stated anywhere, as far as I can tell

So I'd be confused by such a formulation

The second sentence is:
"without worrying about whether your code will work on other
 people's computers"

I find that this sentence is more of the tutorial type

Finally, in your version the Autotools setup is mentioned as the last thing
introduced by "In addition..."

To me the Autotools setup is not an addition, it's the bread and butter of
Hall. it's the cetral feature !

And it needs to be stated first and foremost !

I wrote a new version (attached here) but it ends up being very similar to
my original one

I would go ith this one or my original one, for the reasons I mentioned

I hope this is not a problem 😯

[-- Attachment #2: 0001-added-a-reference-to-guile-hall-in-the-manual.patch --]
[-- Type: text/x-patch, Size: 1723 bytes --]

From e3e3cb177aa411a26d927e05e90dd00996721399 Mon Sep 17 00:00:00 2001
From: Adriano <catonano@gmail.com>
Date: Mon, 18 May 2020 17:44:15 +0200
Subject: [PATCH] added a reference to guile-hall in the manual

---
 doc/ref/scheme-using.texi | 25 ++++++++++++++++++++++++-
 1 file changed, 24 insertions(+), 1 deletion(-)

diff --git a/doc/ref/scheme-using.texi b/doc/ref/scheme-using.texi
index ac265fcca..d430f89e8 100644
--- a/doc/ref/scheme-using.texi
+++ b/doc/ref/scheme-using.texi
@@ -282,7 +282,7 @@ Run the optimizer on a piece of code and print the result.
 @deffn {REPL Command} disassemble exp
 Disassemble a compiled procedure.
 @end deffn
-
+  
 @deffn {REPL Command} disassemble-file file
 Disassemble a file.
 @end deffn
@@ -744,10 +744,33 @@ using a CPAN-like system.
 A complete list of guild scripts can be had by invoking @code{guild
 list}, or simply @code{guild}.
 
+@menu
+* Hall::
+@end menu
+
+
+@node guile-hall
+@subsection Bootstrapping projects and distributing them
+
+There's a tool that doesn't come bundled with Guile and yet can be very
+useful in your day to day experience with it.  This tool is
+@uref{https://gitlab.com/a-sassmannshausen/guile-hall, Hall}.
+
+When you start a new project, Hall creates a folder
+containing a scaffold of your new project.
+Such scaffold will include your basic Autotools setup, so
+you don't have to take care of that yourself
+
+The scaffold contains a directory for your tests,
+for your libraries, for your scripts and for
+your documentation. So you immediately know where to put the
+files you are hacking on.
+
 
 @node Installing Site Packages
 @section Installing Site Packages
 
+
 @cindex site
 @cindex site path
 @cindex load path
-- 
2.25.1