Redvant: Difference between revisions
No edit summary |
No edit summary |
||
(294 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
< | <html><style> .mw-headline {color: black !important;}</style></html> | ||
<div style="background-color: | <div style="font-weight: 600;background-color: #fbfcf8; color: black;"> | ||
<blockquote> | <blockquote><br> | ||
< | {{TOCleft}} | ||
= | = Purpose = | ||
The original purpose of the <b>Redvant</b> moniker was to name the separation of some product lines from their domain space aspects. Products developed under its rubric can be compiled for operation strictly on the basis of the FOSS or COTS software upon which they are based without any integration with DS though in some cases this can gut the app if presentation of a DS feature was its purpose. A non-DS application can then supply a new purpose. My <b>tl;dr</b> line and other product lines sold on stores may thus have core function repurposed to such new apps without committing to DS, DCP, etc.. | |||
However this separation is only in evidence at the time of its application in GC* projects and this separability is not discussed outside of such projects but it will be evident in the supporting implementation. | |||
= | *<span style="font-weight:normal;font-size:8px;">General Contracting (Rate Chart)<span> | ||
= Précis = | |||
<span class=plainlinks> | |||
'''Redvant''' , or ''''<dcms'''' (dcms-bra), is a collective term for software including react and [https://haskell-servant.readthedocs.io/en/stable/ <font color=lime>servant</font>] within a DCP context and packaged as a reusable resource demonstrated in various applications such as the tl:dr and by the KEE. | |||
<div style="position: relative;left: 50px;"> | |||
"red" could be | |||
<blockquote> | |||
react, redis, light in the ~700 nm range, a proper name as in red5, the parfume, lil riding hood, Malcom X, Simply, etc.. | |||
</blockquote> | |||
and "vant" is just from haskell-servant. | |||
</div> | |||
<div style="font-weight: normal;background-color: #fbfcf8; color: black;"> | |||
Redvant is a | = Substance = | ||
<html> | |||
<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. | |||
<p>However, subsequently, I decided a package I first ran into in the telematics work in '14/15 could be repurposed as a basis for <b><u><a href=https://redvant.ai-integration.biz>product line engineering</a></u></b> and Redvant. <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>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> | |||
== The hs aspect of DCMS == | |||
<blockquote> | |||
Acknowledging <html><a href=https://wiki.haskell.org/Web/Content_Management>clckwrks, et al.</a></html> 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.<p> The design intent is for recovery of the function of contained CMSes as a separately maintained bulk in PHP, python, etc.. | |||
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. | |||
</blockquote> | |||
= 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. | |||
<br> | <br><br> | ||
< | </blockquote><html><img width=150 align=right src=https://juan.ai-integration.biz/xasppage/xasppage.pl?XASPPAGE_STYLE=0&P=REDVANT></html> | ||
<blockquote> | |||
</ | |||
</div> | </div> |
Latest revision as of 00:48, 6 October 2024
Purpose
The original purpose of the Redvant moniker was to name the separation of some product lines from their domain space aspects. Products developed under its rubric can be compiled for operation strictly on the basis of the FOSS or COTS software upon which they are based without any integration with DS though in some cases this can gut the app if presentation of a DS feature was its purpose. A non-DS application can then supply a new purpose. My tl;dr line and other product lines sold on stores may thus have core function repurposed to such new apps without committing to DS, DCP, etc..
However this separation is only in evidence at the time of its application in GC* projects and this separability is not discussed outside of such projects but it will be evident in the supporting implementation.
- General Contracting (Rate Chart)
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.
Substance
In the original remit, 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.However, subsequently, I decided a package I first ran into in the telematics work in '14/15 could be repurposed as a basis for product line engineering and Redvant. 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 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.
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
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 a separately maintained bulk in PHP, python, etc.. 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.
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.