Redvant: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
 
(5 intermediate revisions by the same user not shown)
Line 13: Line 13:
and "vant" is just from haskell-servant.
and "vant" is just from haskell-servant.
</div>
</div>
<blockquote style="position:relative;left:300px;">
I mean the remit to be no more precise than that, informally a blob of code that DCP emits in app generation and runs in a DS context.
</blockquote>
<div style="font-weight: normal;background-color: #fbfcf8; color: black;">
<div style="font-weight: normal;background-color: #fbfcf8; color: black;">


= Substance =
= History =
<html>
<html>
<blockquote><span class=plainlinks>
<blockquote><span class=plainlinks>
In the original remit, use of Apache </html>[https://isis.apache.org <font color=lime>causeway (formerly ISIS)</font>]<html> or other fat DDD pkg was intended later in fulfillment of our overall DDD product line engineering (as 'redvantis'). Some enterprise users may prefer a java basing of ISIS or an ERP core and this is still an option for GC projects.
In the original remit (q.v.), use of Apache </html>[https://isis.apache.org <font color=lime>causeway (formerly ISIS)</font>]<html> or other fat DDD pkg was intended later in fulfillment of our overall DDD product line engineering (as 'redvantis'). Some enterprise users may prefer a java basing of ISIS or an ERP core and this is still an option for GC projects.
<p>However, subsequently, I decided a package I first ran into in the telematics work in '14/15 would serve as a basis for the Redvant line of  <b><u><a href=https://redvant.ai-integration.biz>product engineering</a></u></b>. <a href=https://clafer.org>Clafer</a> is essentially forked for this purpose here, its repos forked within 6 mo of the Sept. '23 update, which was the first activity on it in some time. It appears to be preserved and maintained but not actively developed which is fine as I intend the baseline here to veer strongly toward actual product line engineering of actually fielded apps and the redvant mission as well as DS DDD generally making it essentially Clafer for DS and my product lines.
<p>Next, Clafer, a package I first ran into in the telematics work in '14/15 was chosen as a basis for the, as then conceived. Redvant line of  <b><u><a href=https://redvant.ai-integration.biz>product engineering</a></u></b>. <a href=https://clafer.org>Clafer</a> is essentially forked for this purpose here, its repos forked within 6 mo of the Sept. '23 update, which was the first activity on it in some time. It is an archived project at its source, which simplifies my use here in applying to the product line engineering of the DSAP derivatives.
<p>Although I mean to keep local clafer tools close to the original on the common code intersection, there will be some rebranding to Redvant instead of Clafer to make clear the diff between just clafer the domain modeling lang and its use here.
<p>Although I mean to keep local clafer tools close to the original on the common code intersection, there will be some rebranding to Redvant instead of Clafer to make clear the diff between just clafer the domain modeling lang and its use here.
</blockquote></html>
</blockquote></html>

Latest revision as of 14:23, 8 January 2025


Précis

Redvant , or '<dcms' (dcms-bra), is a collective term for software including react and servant within a DCP context and packaged as a reusable resource demonstrated in various applications such as the tl:dr and by the KEE.

"red" could be

react, redis, light in the ~700 nm range, a proper name as in red5, the parfume, lil riding hood, Malcom X, Simply, etc..

and "vant" is just from haskell-servant.

I mean the remit to be no more precise than that, informally a blob of code that DCP emits in app generation and runs in a DS context.

History

In the original remit (q.v.), use of Apache causeway (formerly ISIS) or other fat DDD pkg was intended later in fulfillment of our overall DDD product line engineering (as 'redvantis'). Some enterprise users may prefer a java basing of ISIS or an ERP core and this is still an option for GC projects.

Next, Clafer, a package I first ran into in the telematics work in '14/15 was chosen as a basis for the, as then conceived. Redvant line of product engineering. Clafer is essentially forked for this purpose here, its repos forked within 6 mo of the Sept. '23 update, which was the first activity on it in some time. It is an archived project at its source, which simplifies my use here in applying to the product line engineering of the DSAP derivatives.

Although I mean to keep local clafer tools close to the original on the common code intersection, there will be some rebranding to Redvant instead of Clafer to make clear the diff between just clafer the domain modeling lang and its use here.

The hs aspect of DCMS

and DS app lang

Acknowledging clckwrks, et al. as suggestions for hs CMS, have taken a different route based on generalization and pass thru of the function of PHP and python CMSes such as django, Cliu/D7, and Plone. The design intent is for recovery of the function of contained CMSes as an abstracted and separately maintained bulk with their original and subsequent live code absorbed as is.

A Clafer/getit/happstack based server integrating servant with DCP domain content definition houses this unification. In general, where possible integration means operation of the CMS as is at the code level via its LDAP integration and running under MCP.

I mean Haskell to be the DS application lang and for DCP to semi-automatically generate apps for it. Central to this is my implementation of the Specious Present which I am available in #haskell-nlp.libera.chat as JuanDaugherty for chat.

Visibility

This is the sole exposition at this scope and will remain so. Technical detail will be in an eponymous § in the Books DCMS volume.