<feed xmlns='http://www.w3.org/2005/Atom'>
<title>progmaweb/apps/web/tests, branch site/shared-preferences</title>
<subtitle>The site and account service of Progmasoft: a Next.js frontend and an ASP.NET Core API.</subtitle>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/'/>
<entry>
<title>Share the theme and the language across every Progmasoft host</title>
<updated>2026-11-17T11:33:32+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-17T11:33:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=6d78305900851f98e00cc1b688d1237b5e33f857'/>
<id>6d78305900851f98e00cc1b688d1237b5e33f857</id>
<content type='text'>
A theme chosen on progmasoft.com did not hold on account., viget.,
product. or console., and a language choice sometimes did not either:

- The theme lived in localStorage, which each host keeps for itself. It
  is now the cookie progmasoft_theme of .progmasoft.com, as the language
  is (lib/theme.ts): "light" or "dark", a year, SameSite=Lax, Secure over
  HTTPS, readable by the page's scripts. The bootstrap that sets the theme
  before the first paint reads the cookie; a choice an earlier version left
  in localStorage moves into the cookie once. The theme control writes the
  cookie and reads it again when a page is shown or comes back into view,
  so a tab left open follows a choice made on another host.
- The language cookie is shared (Domain=.progmasoft.com), but a cookie of
  the same name that one host kept from before shadowed it: the browser
  sends both, the host's first. The proxy now expires such a host cookie
  (lib/shared-cookies.ts) for the language and the theme alike, so the
  shared choice holds from the next request on.

Tests: unit tests for the cookie, the bootstrap (run in a vm with a fake
document) and the expiry of shadowing cookies (54 in all); layout tests
that choose a theme and a language on progmasoft.com and find them on the
other hosts, move an old localStorage theme, and clear a shadowing
cookie (144 layout tests pass); tsc, eslint and build pass.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
A theme chosen on progmasoft.com did not hold on account., viget.,
product. or console., and a language choice sometimes did not either:

- The theme lived in localStorage, which each host keeps for itself. It
  is now the cookie progmasoft_theme of .progmasoft.com, as the language
  is (lib/theme.ts): "light" or "dark", a year, SameSite=Lax, Secure over
  HTTPS, readable by the page's scripts. The bootstrap that sets the theme
  before the first paint reads the cookie; a choice an earlier version left
  in localStorage moves into the cookie once. The theme control writes the
  cookie and reads it again when a page is shown or comes back into view,
  so a tab left open follows a choice made on another host.
- The language cookie is shared (Domain=.progmasoft.com), but a cookie of
  the same name that one host kept from before shadowed it: the browser
  sends both, the host's first. The proxy now expires such a host cookie
  (lib/shared-cookies.ts) for the language and the theme alike, so the
  shared choice holds from the next request on.

Tests: unit tests for the cookie, the bootstrap (run in a vm with a fake
document) and the expiry of shadowing cookies (54 in all); layout tests
that choose a theme and a language on progmasoft.com and find them on the
other hosts, move an old localStorage theme, and clear a shadowing
cookie (144 layout tests pass); tsc, eslint and build pass.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Serve the Catch3 site at catch3.uk</title>
<updated>2026-11-16T13:27:16+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-16T13:27:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=62faa7158ce51495dcdd09e7858c23faee707cfd'/>
<id>62faa7158ce51495dcdd09e7858c23faee707cfd</id>
<content type='text'>
Catch3 has a domain of its own. Progmaweb answers catch3.uk with the
Catch3 page, its sitemap and its robots entry; catch3.progmasoft.com and
www.catch3.uk send a 308 to it from nginx, so one address serves the
site. catch3.uk has its own certificate (ops/README.md).

The page said Catch3 adds a C++20 library; it is a C++17 library, in
all four languages of the page.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Catch3 has a domain of its own. Progmaweb answers catch3.uk with the
Catch3 page, its sitemap and its robots entry; catch3.progmasoft.com and
www.catch3.uk send a 308 to it from nginx, so one address serves the
site. catch3.uk has its own certificate (ops/README.md).

The page said Catch3 adds a C++20 library; it is a C++17 library, in
all four languages of the page.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge main into legal/patent-grant-notice</title>
<updated>2026-11-15T16:34:39+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T16:34:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=c0d96223e2240cc61af194737e3e5dc9faa2f1d2'/>
<id>c0d96223e2240cc61af194737e3e5dc9faa2f1d2</id>
<content type='text'>
The README takes main's sentence, which no longer names the former site,
with PATENTS.md; REUSE.toml keeps the CC0-1.0 annotation of the JSON
Schemas and names AGPL-3.0-or-later alone. The Nginx file of
schemastore.progmasoft.com, new on main, gets the same SPDX expression.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The README takes main's sentence, which no longer names the former site,
with PATENTS.md; REUSE.toml keeps the CC0-1.0 annotation of the JSON
Schemas and names AGPL-3.0-or-later alone. The Nginx file of
schemastore.progmasoft.com, new on main, gets the same SPDX expression.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Remove what is left of the former language and its site (#70)</title>
<updated>2026-11-15T10:53:35+00:00</updated>
<author>
<name>Leitwolf</name>
</author>
<published>2026-11-15T10:53:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=1a73486c0f67ddf3bfe3fd01e2258648f81fbb48'/>
<id>1a73486c0f67ddf3bfe3fd01e2258648f81fbb48</id>
<content type='text'>
The dashboard, proxy, documents, issue templates and ops files no longer point at the former language, its site or its repositories. viget.progmasoft.com/api/v1/status answers from the Progmaweb API (5085); the archived website repository is no longer mirrored.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The dashboard, proxy, documents, issue templates and ops files no longer point at the former language, its site or its repositories. viget.progmasoft.com/api/v1/status answers from the Progmaweb API (5085); the archived website repository is no longer mirrored.</pre>
</div>
</content>
</entry>
<entry>
<title>Name the copyright license alone in SPDX expressions</title>
<updated>2026-11-15T10:14:38+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T10:14:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=3bda6d7bc28c5aa588418d12d9e3129f8526df50'/>
<id>3bda6d7bc28c5aa588418d12d9e3129f8526df50</id>
<content type='text'>
The Progmasoft Patent Grant is a separate permission added to the
copyright license, not an exception to it, so joining the two with WITH
said something the grant does not do. What makes the grant apply is the
PATENTS notice of the repository (Section 9 of the grant), not the SPDX
expression of each file.

Every project-owned file now carries SPDX-License-Identifier:
AGPL-3.0-or-later, and package.json says the same. PATENTS becomes
PATENTS.md: project-owned software in the repository is covered by the
Patent Grant, Version 1.1, whose canonical text is unchanged under
LICENSES/; third-party material keeps its own terms. NOTICE.txt and the
README point to PATENTS.md.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The Progmasoft Patent Grant is a separate permission added to the
copyright license, not an exception to it, so joining the two with WITH
said something the grant does not do. What makes the grant apply is the
PATENTS notice of the repository (Section 9 of the grant), not the SPDX
expression of each file.

Every project-owned file now carries SPDX-License-Identifier:
AGPL-3.0-or-later, and package.json says the same. PATENTS becomes
PATENTS.md: project-owned software in the repository is covered by the
Patent Grant, Version 1.1, whose canonical text is unchanged under
LICENSES/; third-party material keeps its own terms. NOTICE.txt and the
README point to PATENTS.md.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Make product.progmasoft.com a catalog like projects.apache.org</title>
<updated>2026-11-14T13:21:48+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-14T13:21:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=fd5d1dfc8223dd660815ee7cca118507985ccc39'/>
<id>fd5d1dfc8223dd660815ee7cca118507985ccc39</id>
<content type='text'>
The catalog listed two products as cards. It now works as an index of
every Progmasoft project, in all four languages:

- The front page counts the projects (released, in development,
  languages), searches them by text, category, language and status with
  a plain GET form, so no script runs, and lists them in one table: name
  and tagline, category, language, status, latest release; then the
  latest releases.
- /categories and /languages group the projects; /releases lists the
  latest release of each, newest first, then those without one.
- A project page has a facts box as Apache's has: status, category,
  language, license, latest release, start date, site, repository and
  issues. A project in development heads its list "What it is being
  built to do" instead of "What it does".
- Agenceland, Archer and Etincelle join Tazel and Catch3, each marked in
  development; the archived Tala projects stay out of the catalog.
- product.progmasoft.com has a sitemap of its own: the views and every
  project page.

The data is in lib/products.ts (facts, search, releases) and the text in
lib/catalog-messages.ts; tsconfig allows .ts imports between lib files
so that node:test can load them. Tests: the five projects and their
facts, search by text, category, language and status, the query-string
parsing, and release order (42 pass); lint and tsc clean; every route
rendered by next dev with the product host, in de-DE, ru-RU and he-IL
(right to left) too.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The catalog listed two products as cards. It now works as an index of
every Progmasoft project, in all four languages:

- The front page counts the projects (released, in development,
  languages), searches them by text, category, language and status with
  a plain GET form, so no script runs, and lists them in one table: name
  and tagline, category, language, status, latest release; then the
  latest releases.
- /categories and /languages group the projects; /releases lists the
  latest release of each, newest first, then those without one.
- A project page has a facts box as Apache's has: status, category,
  language, license, latest release, start date, site, repository and
  issues. A project in development heads its list "What it is being
  built to do" instead of "What it does".
- Agenceland, Archer and Etincelle join Tazel and Catch3, each marked in
  development; the archived Tala projects stay out of the catalog.
- product.progmasoft.com has a sitemap of its own: the views and every
  project page.

The data is in lib/products.ts (facts, search, releases) and the text in
lib/catalog-messages.ts; tsconfig allows .ts imports between lib files
so that node:test can load them. Tests: the five projects and their
facts, search by text, category, language and status, the query-string
parsing, and release order (42 pass); lint and tsc clean; every route
rendered by next dev with the product host, in de-DE, ru-RU and he-IL
(right to left) too.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge branch 'main' into feature/viget-c-languages</title>
<updated>2026-11-13T04:02:11+00:00</updated>
<author>
<name>Leitwolf</name>
</author>
<published>2026-11-13T04:02:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=7f8b15bf14d7784c856680e38cac9631f3a56018'/>
<id>7f8b15bf14d7784c856680e38cac9631f3a56018</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Lead the old Tala catalog addresses to the language list</title>
<updated>2026-11-12T23:01:41+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-12T23:01:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=61a2045ee9264e794e4ddf11d7b8b9fdf4109bd3'/>
<id>61a2045ee9264e794e4ddf11d7b8b9fdf4109bd3</id>
<content type='text'>
/langs/tala and everything below it, which tala.run and earlier links
still point to, now redirect permanently to the language list of the
ViGet home page, like /langs, instead of answering 404. The README, the
architecture guide and the bug-report template name the C, C++ and
Objective-C catalogs.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
/langs/tala and everything below it, which tala.run and earlier links
still point to, now redirect permanently to the language list of the
ViGet home page, like /langs, instead of answering 404. The README, the
architecture guide and the bug-report template name the C, C++ and
Objective-C catalogs.
</pre>
</div>
</content>
</entry>
<entry>
<title>Format the catalog and the site tests with Prettier</title>
<updated>2026-11-12T23:00:34+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-12T23:00:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=189b15ca0909033a40626bc8f600686e561b9cbb'/>
<id>189b15ca0909033a40626bc8f600686e561b9cbb</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Take the Tala products out of the catalog and describe the new Tazel</title>
<updated>2026-11-12T23:00:18+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-12T23:00:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=9a6cfb275189db7cb8d4a35917678d067b3e709a'/>
<id>9a6cfb275189db7cb8d4a35917678d067b3e709a</id>
<content type='text'>
Tala and its tools are no longer developed (2026-11-10), and tala.run,
talac.tala.run, talafmt.tala.run and talalint.tala.run lead to a notice
that answers 503. The catalog still offered Tala, talac, talafmt and
talalint with "Visit the site" buttons into that notice, and described
Tazel as the build system of Tala.

- Tala, talac, talafmt and talalint leave the catalog in all four
  languages, as Xide did; their product pages answer 404.
- The catalog names Tazel and Catch3.
- Tazel is described as it is now: it builds C, C++, Objective-C,
  Objective-C++ and Zig from MODULE.kts and BUILD.kts, finds Clang, GCC
  and zig cc, builds for other triples, is incremental per action, and
  runs commands of tazel_custom.txt. Nothing it does not do yet (ViGet
  packages, plugins) is promised.
- The site tests list the two products and route through them.

Answers the review of website#58, which found the product links leading
into the closed sites.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Tala and its tools are no longer developed (2026-11-10), and tala.run,
talac.tala.run, talafmt.tala.run and talalint.tala.run lead to a notice
that answers 503. The catalog still offered Tala, talac, talafmt and
talalint with "Visit the site" buttons into that notice, and described
Tazel as the build system of Tala.

- Tala, talac, talafmt and talalint leave the catalog in all four
  languages, as Xide did; their product pages answer 404.
- The catalog names Tazel and Catch3.
- Tazel is described as it is now: it builds C, C++, Objective-C,
  Objective-C++ and Zig from MODULE.kts and BUILD.kts, finds Clang, GCC
  and zig cc, builds for other triples, is incremental per action, and
  runs commands of tazel_custom.txt. Nothing it does not do yet (ViGet
  packages, plugins) is promised.
- The site tests list the two products and route through them.

Answers the review of website#58, which found the product links leading
into the closed sites.
</pre>
</div>
</content>
</entry>
</feed>
