Redvant: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
 
(283 intermediate revisions by the same user not shown)
Line 1: Line 1:
<div class="plainlinks" style="background-color: maroon; color: white;">
<div class="nomobile">
<div style="background-color: indigo;"> <blockquote>
<h6 style="position:relative;top:-15px;">redvant.ai-integration.biz</h6>
<html><style> .mw-headline {color: gold !important;}</style></html>
<div style="position:relative;top:-15px;font-weight: 600;background-color: #fbfcf8; color: black;">
<blockquote>
__NOTOC__
<br>
<html><img style="position:relative;left:-20px;float:left;" width=175 src=https://eg.meansofproduction.biz/eg/images/c/c7/KASTALIEN.svg></html> &nbsp; &nbsp;
<br>
<br>
<div style="width='95%'; background-color: grey; color: white;">
<blockquote>
= Pr&eacute;cis =
= Pr&eacute;cis =
 
<span class=plainlinks>
'''Redvant''' , or ''''dcms<'''' (dcms-bra), designates middle and front end software with red things and
'''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.  
[https://haskell-servant.readthedocs.io/en/stable/ <span style="color: pink;">servant</span>]
<div style="position: relative;left: 50px;"><br>
middleware to access domain space backend services and a focus on incubation of the sameboat and tl:dr[AK] applications.  
<span style="position:relative;left:-30px;top:-5px;">"red" could be</span>
<blockquote>
<blockquote>
"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..
<blockquote>
</blockquote> <br>
  react, redux, redis, or just plain red, a simple name as in red5, the parfume, riding hood, etc..
</blockquote>  
and "vant" is just from haskell-servant.
and "vant" is just from haskell-servant.
</blockquote>  
</div>
 
<blockquote style="position:relative;left:150px;">
Product line development often starts with free form dev flows in anticipation and incubation of a full DDD process.
Redvant is defined to be a production line that begins with Figma mocks applied to Clafer models and emiting Android and iOS binaries via turnkey MCP cells worked by DevOps users.<br>
I mean the remit to be no more precise than that, informally just workflows DCP manages in app generation and runs in a DS context.
</blockquote>
== History ==
<html><blockquote><span class=plainlinks> Of this line of <b><u><a href=https://redvant.ai-integration.biz>product engineering</a></u></b><p>
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.
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 line. <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.
</blockquote></html>


{{TOCright}}
== Transparency ==
Redvant will remain opaque except as is clear from exposed working artefacts until several iterations of production use when technical detail will be exposed in a fanout in DCMS series in the Books metaphor.
<div style="font-weight: 600;background-color: #fbfcf8; color: black;">


= Story =
== The hs aspect of DCMS ==
<span style="position:relative;top:-5px;left:10px;font-size:10px;">and DS app lang</span>
<blockquote style="position:relative;top:-10px;">
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. 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.
<br><br>
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.
<br><br>
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.</blockquote>


Red&lt;thing&gt; is a name for a dev workflow defined by an implementation path from front end thru DCMS middleware, to arbitrary backend function and DCP agents;


Redvant is rapid prototyping and React oriented but its work product is not disposable. Rather it remains the simple, easily mutable, and generally feature poor base of a product line entry.
</blockquote><html><img width=150 align=right src=https://juan.ai-integration.biz/xasppage/xasppage.pl?XASPPAGE_STYLE=0&P=REDVANT></html>
 
Redvis is DDD oriented and uses the Apache ISIS and hence Java EE ecosys as front end and middle layers of a product line.
 
In an actual entry, a specific version could be Redvant Expo, Redvant Native, Redvis alone or Redvis behind Redvant Native, where the first Redvant screens precede the Redvis ones.
 
== Sonstiges ==
=== Commonalities ===
<blockquote>
The [https://sameboat.live/sb-app <span style="color: pink;">sb-sff</span>] common Redvis reusable base with ...
#common DS SSO
#Jitsi adapted to DS, default in sb-sff, optional otherwise
</blockquote>
=== Deliverables ===
<blockquote>
*tl;dr product line engineering [https://desktop.thoughtcrime.biz <span style="color: lime;">cases</span>] for [https://play.google.com/store/apps/details?id=org.commoditysoftware.greentravel <span style="color: pink;">GT2</span>], [https://tl-drak.meansofproduction.biz/products/tl-drtask <span style="color: pink;">TASKPM</span>], and [https://yas3fs.ai-integration.biz <span style="color: pink;">YAS3FS].
*stable production level  [https://doorbell.meansofproduction.biz <span style="color: pink;">Ft</span>] and [https://ac.ai-integration.biz <span style="color: pink;">AC</span>] SPAs
<br><br><br><br>
</blockquote>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</div>

Latest revision as of 10:54, 13 February 2025

redvant.ai-integration.biz


   

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.

Redvant is defined to be a production line that begins with Figma mocks applied to Clafer models and emiting Android and iOS binaries via turnkey MCP cells worked by DevOps users.
I mean the remit to be no more precise than that, informally just workflows DCP manages in app generation and runs in a DS context.

History

Of this line of product engineering

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. 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 line. 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.

Transparency

Redvant will remain opaque except as is clear from exposed working artefacts until several iterations of production use when technical detail will be exposed in a fanout in DCMS series in the Books metaphor.

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.