From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Newsgroups: comp.lang.ada
Subject: Re: What is the best license to use for open source software?
Date: Tue, 27 Jan 2015 09:52:47 +0100
Organization: cbb software GmbH
Message-ID: <1bmcls0l0g4ka$.1u5nfke8o2aod.dlg@40tude.net>
References: <616ae348-41f6-446f-9c4b-0da8e398e75b@googlegroups.com>
 <a8b78b81-6eef-4287-8f73-54caa00d7e93@googlegroups.com>
 <1391828381444007928.494546nonlegitur-futureapps.invalid@reader80.eternal-september.org>
Reply-To: mailbox@dmitry-kazakov.de
NNTP-Posting-Host: p9a8jKAGz0rpkSSbWxF1gQ.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: 40tude_Dialog/2.0.15.1
X-Notice: Filtered by postfilter v. 0.8.2
Xref: news.eternal-september.org comp.lang.ada:24751
Date: 2015-01-27T09:52:47+01:00
List-Id: <comp.lang.ada>

On Tue, 27 Jan 2015 00:39:21 +0000 (UTC), G.B. wrote:

> I wish I had the time to write/vary a template compiler possibly different
> from AWS's
> that would allow integration of graphics design with Gnoga's way of
> creating web views,
> by identifying parts to the program via unique id attributes on elements.

There were other template projects initiated, but they didn't go further.

Maybe you could summarize requirements and features, at least. And put them
somewhere as a wiki? So that others would know what is expected.

E.g. one of my requirements when I designed HTTP server implementation was
having it working on a diskless embedded machine. Thus if a template
framework based on files were non-starter to me.

One basic issue more, should the template paradigm be:

A. Substitution-based (some escape sequences in the text);
B. Language-based;
C. Programmable (some API to manipulate the template, plus intermediate
embeddable code, plus GUI editor).

The rough correspondence to the word-processing world:

A were like groff, troff, HTTP, XML
B were like TeX / LaTeX
C were like MS-Word

I would prefer C, AWS solution looks like A.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de