Sasha FirsovAssembling the team for JS dev and standards in #DeclarativeCustomElement and #DeclarativeWebApplication
in the oncomming new company. As employee or a consulter.
The work is in native web components space.
Please DM me with email contact.
Today #DeclarativeCustomElement (DCE) started to asquire Embeddable Web Application features. The imperative POC of `embed-page` laid a basis: the forms, links, document location change would be scoped in DCE instead of page.
a 1st step towards #DeclarativeWebApplication (DWA)
GitHub - EPA-WG/embed-page: Proof of concept for Embeddable Progressive Application - a microapplication container, a WebComponent acting as seamless IFRAME or html include
Proof of concept for Embeddable Progressive Application - a microapplication container, a WebComponent acting as seamless IFRAME or html include - GitHub - EPA-WG/embed-page: Proof of concept for E...
Renoir Boulanger@ayo templating eh?
Maybe not what you're looking for. But worth sharing nonetheless.
Have a look at #DeclarativeCustomElement #DeclarativeWebApplication proposed by my friend @Suns It's in proposal at W3C Web Component Community #WebComponentsCG Group IIRC. Essentially using HTML to (declaratively) describe the template and use it.
Sasha Firsov (@[email protected])
Attached: 1 image #DeclarativeCustomElement now can be used without tags instantiating inline. And load images and templates from a library. https://unpkg.com/@epa-wg/[email protected]/demo/external-template.html
With all critics on ads and tracking in the browser and US government initiative on secure apps stack, I see no other way then create an #OSS browser as a platform. Capable of #DeclarativeWebApplication embedding, approved apps policies enforcement as on browser settings as on user level.
I doubt JS based apps could give such security layer as declarative stack would.
@passle , ssr is just a one tier. I am thinking on multiple tiers where Hydration is applicable.
And Custom Element is not a goal. Rather #DeclarativeWebApplication
@passle , I an thinking on #w3ctag proposal for steaming based processing for #DeclarativeWebApplication / #DeclarativeCustomElement the template html has to be read, parsed, dependent tree stream merged( including data) , template+data rendered in stream, diff to page DOM created, and finally merged. All steps should be using this unified API for bypassing own input to output.
Delivering results while the 1st tier yet to be completed.
@vanilla,
As of now the #webcomponent state is treated as 2nd class citizen by #w3c
. For now only state which is permitted on declarative syntax is either attributes or payload DOM. Which actually meant for visual and initial state, not the heavy-duty transactional model. If WC would be able to produce and consume the state without custom serialization, it would work on all tiers.
There is a proposal to make it a part of web stack.
Working on it as part of #DeclarativeWebApplication
@slightlyoff @phae nice. But there is not no-js web app capabilities in the browser yet. Join the #DeclarativeWebApplication no-js engine capable of running app as declarative HTML with multythreaded UI rendering, streaming, the best treats you name.
#DeclarativeCustomElement is a container for #DeclarativeWebApplication which also can be run standalone.
DWA purpose is to be embedded into 3rd party apps via DCE as a container. That is a main #web3 feature addressed by DWA/DCE. This proposal enables the DWA serving by DCE.
@tag
https://discourse.wicg.io/t/proposal-src-attribute-for-declarative-custom-element/6183
[Proposal] SRC attribute for Declarative Custom Element
Use cases: <custom-element tag="dce-internal" src="#template1"> - reference the template in page DOM <custom-element src="#template2"></custom-element> - inline instantiation, no tag <custom-element tag="dce-external" src="toc.html"> - external file <custom-element tag="dce-hash" src="../index.html#shared-template"> - by ID in external file <custom-element tag="dce-hash" src="embed-1.html" > - external file with embedding of another external DCE <custom-element tag="dce-hash" src="../ind...
#DeclarativeWebApplication stack would not be complete without URL and window APIs exposed declaratively. First AC for location #webcomponents which would expose the API as data slice.
