Redvant: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
 
(13 intermediate revisions by the same user not shown)
Line 10: Line 10:
= Précis =
= Précis =
<span class=plainlinks>
<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.  
'''Redvant''' , or ''''<dcms'''' (dcms-bra), is a collective term for software including react and [https://servant.dev<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;"><br>
<div style="position: relative;left: 50px;"><br>
<span style="position:relative;left:-30px;top:-5px;">"red" could be</span>
<span style="position:relative;left:-30px;top:-5px;">"red" could be</span>
Line 16: Line 16:
  react, redis, light in the ~700 nm range, a proper name as in red5, the parfume, lil riding hood, Malcom X, Simply, etc..
  react, redis, light in the ~700 nm range, a proper name as in red5, the parfume, lil riding hood, Malcom X, Simply, etc..
</blockquote> <br>
</blockquote> <br>
and "vant" is just from haskell-servant.
and "vant" could be similarly zweideutige. Thing with a node red face and haskell servant backside is another.
</div>
</div>
<blockquote style="position:relative;left:150px;">
<blockquote style="position:relative;left:150px;">
Line 23: Line 23:
</blockquote>
</blockquote>
== Transparency ==
== 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 &sect; fanout in the DCMS volume in Books.
Redvant will remain opaque except as is clear from exposed working artifacts until several iterations of production use when some technical detail will be exposed in a &sect; fanout in the DCMS volume in Books IV,VI,VII and VIII. The link under the article title is the storyboard domain. In practice, the storied Redvant tool chain will in general require some expertise and is unlikely to be workable by the average domain owner or popular group member, or even a single IT professional. This is compensated for by the fact that domains are defined by their DCE (Domain Controlled English) definitions in natural language form which are workable by domain owners or PG members.
 
<div style="font-weight: 600;background-color: #fbfcf8; color: black;">
<div style="font-weight: 600;background-color: #fbfcf8; color: black;">


Line 29: Line 30:
<span style="position:relative;top:-5px;left:10px;font-size:10px;">and DS app lang</span>
<span style="position:relative;top:-5px;left:10px;font-size:10px;">and DS app lang</span>
<blockquote style="position:relative;top:-10px;">
<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.
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]]. I have created #haskell-nlp.libera.chat for discussion about it.
<br><br>
<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. At the detail level this is mediated by domain for codegen of models, beam for abstraction of the rdbmses, and compdata.
Various services are integrated by DCP in the process of domain content definition and maintenance. De novo domains and the unification of CMSes mentioned in the next &para;. In general, where possible integration means operation of the received CMS as is at the code level via its LDAP integration and running under MCP. At the detail level this is mediated by domain for codegen of models, beam for abstraction of the rdbmses, and compdata.
<br><br>
<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>
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 WP, mediawiki, Cliu/D7, and django-cms. 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.
 
</blockquote>
 
</blockquote>
</blockquote>
</div>
</div>
== History ==
== History ==
<html><blockquote><span class=plainlinks><p>
<html><blockquote><span class=plainlinks><p>