Jackson: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
Line 1: Line 1:
<h1>Function</h1>
<h1>Function</h1>
<blockquote>
<blockquote>
This is now a simple name, for which I will not implement anything. The concept of a common front end over other stuff is of course well worn, even in this specific context. Since first occurrence have done cordova apps and will soon do react native I think. <p> So this pure name is now used as a designation for a class of things dominated by this topic, common FE/UI, and the implementation is an adapted 3rd party thing, cordova between '14 and '18 and react next (tbd).</p>
This is now a simple name, for which I will not implement anything. The concept of a common front end over other stuff is of course well worn, even in this specific context. Since first occurrence have done cordova apps and will soon do react native I think. So this pure name is now used as a designation for a class of things dominated by this topic, common FE/UI, and the implementation is an adapted 3rd party thing, cordova between '14 and '18 and react next (tbd). Thus it is a appropriate for the designation of a class of apps which is what the AKJAKSN SKUs refer to.
</blockquote>
</blockquote>

Revision as of 16:23, 10 January 2018

Function

This is now a simple name, for which I will not implement anything. The concept of a common front end over other stuff is of course well worn, even in this specific context. Since first occurrence have done cordova apps and will soon do react native I think. So this pure name is now used as a designation for a class of things dominated by this topic, common FE/UI, and the implementation is an adapted 3rd party thing, cordova between '14 and '18 and react next (tbd). Thus it is a appropriate for the designation of a class of apps which is what the AKJAKSN SKUs refer to.