tuespetre / html-mvc Goto Github PK

multipart/json response parsing

• Parsing the entire message
• Splitting the body at boundaries
• Parsing headers, quoted & unquoted
• Value-less MIME type parameters

element interactions

• <a>
• <area>
• <form> and friends

In order to prevent developers from having to pepper their models with countless AnyItems / NoItems attributes and their code with statements to populate them, there should be a replacement solution for bindeach that, in the spirit of the existing code, gives the 'hidden' attribute special treatment:

• bindsome, which would add the hidden attribute if the expressed value was either not a collection or was empty, and
• bindnone, which would add the hidden attribute if the expressed value was a non-empty collection

Of course, both would cause the hidden attribute to be removed in their opposite scenarios.

In addition, there should be an isomorphic bindcount expression which functions like bindtext but uses the number of items in the expressed collection, as there will be differences in how various languages express that and once again, developers shouldn't need to waste their time populating simple integer fields any time they want to display a number.

• bindcount
• bindsome
• bindnone

Currently it's using the title attribute from HTMLAnchorElement and HTMLAreaElement instances. Need to think about how this should be done with all elements including forms and their submission elements.

• Persistent models in localStorage, versioned by application-name and application-version
• Transient models in history state

Probably just going to hack together some regex/string splitting kind of thing in its place. At least it falls back to normal form submission ;)

• application-name
• application-version

Also figure out how changes in version could be effected during model negotiation

• Using the meta tags at document load time
• Updating the meta values from background requests
• Applying the meta values to history entries to force reload on popstate where the entry was from a previous version

In order to allow developers to pre-cache views, a specific type of HTML import should be supported.

Developers would want the referenced resources to be highly cacheable, and should use the server-side framework to generate the links and their hrefs.

Conventional overview

• Structuring view trees
• Content negotiation at the server
• Declarative members for declarative bindings
• Application versioning

Advanced

• Dynamic view tree switching for permissions and reducing view 'weight'
• Using bindskip for performance
• When using HTML MVC might not be the appropriate choice

Using with other libraries

• Using with jQuery
• Using with Angular
• Using with React

Adding 'modern' features as progressive enhancements

• Filter as you type
• Showing/hiding form elements
• Tab panels
• Complex layouts, dashboards

General handling for both GET and POST requests:

• 2xx

  Scan the response for updated metadata and models and perform the document update/add the new history entry; issue a full GET request for text/html if missing required model information

• 3xx:

  Let the browser handle the redirect and re-apply these specifications to the resulting response

• All others:

  • If the response is of type text/html, replace the current document (probably using document.write()) and add the new history entry
  • If the response is of type multipart/json, scan the response for updated metadata and models and perform the document update/add the new history entry; issue a full GET request for text/html if missing required model information
  • Else, issue a full GET request for text/html

Specific questions to be answered

• pushState or replaceState: is there ever a place for replaceState, especially for POST forms? Should it be an attribute-based option?

This would prevent crawling the tree twice.