titannanode/applicationframe

simple and lightweight library for building ECMAScript applications

applicationframe's Issues

[DataBinding] Only update text values if they are dirty

It doesn't make sense to update values on the DOM which didn't change.

[IndexedDB] allow DB to be closed

There might be situations in which we'd like to close a DB, this should be possible.

refactoring the scope system

I don't like the decisions I made while designing the scope system.
This big prepare function will be depraved and replaced by a smaller and better one.
In addition there will be three types of scope functions public, private and system only.

[DataBinding] Rewrite DOM Node management without Mixins

It should be possible to get the Polymer compatibility to work without the usage Proxies.
The support for proxies is to rare as that we can actually use it in production.

[DataBinding] RenderEngine

Introduce render engine to be able to directly access the browsers render process.

The render engine allows to insert tasks into the rendering process. They can be added either to the next frame, or after the next frame has been rendered. It's also possible to add hooks which are executed every time a frame is rendered.

[IndexedDB] store upgrade causes exception

When upgrading an existing store to a new version it causes an Object store named 'x' already exists at index 'y' exception. This is caused by

ApplicationFrame/IndexedDB/index.js

Line 109 in a46eead

store = transaction.objectStore(storeDefinition.name);

where the wrong name property is used.

ServiceWorker event dispatch is broken

ServiceWorker events are not correctly dispatched through to the clients and the service worker also doesn't correctly receive event messages posted to it.

Implement 0.2

Implement all new features, classes, etc. for 0.2

wiki documentation

the main functions must be documented in the wiki before the first release.

[DataBinding] fix repeat + auto-binding + replace

The new auto binding doesn't work with repeat and replace since the repeat binding immediately invokes the sub cycle for the auto binding, but does not insert the new element before it is done.
So the auto binding needs to be async to be executed after the current update cycle is done. Also replace doesn't play so well with the repeat binding and it will mess up the injection logic if some template elements are replaced with their content. A insert attribute should be added here.

• make auto-binding async
• add insert attribute
• print out a warning that repeat + auto-bind + replace doesn't work

[NetworkRequest] redo GET request data handling

We should re-implement the submission of get requests to use the URLSearchParams constructor.

[CE] Provide CustomElement prototype

The CustomElement prototype should make it easier to work with custom elements. It's supposed to generate attribute-to-property bindings, auto cast attribute values and provide easy to use callback functions for common custom elements tasks such as, general attribute change, specific attribute change and element creation.

[DataBinding] empy expression returns context

currently an empty expression returns the context it is evaluated against. This should be fixed to return undefined;

[Memory] refactor allocation

We can refactor the implementation to always take one argument, so we can avoid the redundant string for object allocations.

Fix JsDoc Documentation

web/ServiceWorker.init() should return promise

The web/ServiceWorker.init() method should return a registration promise, so errors can be appropriately handled by the user.

[IndexedDB] upgrade DB at runtime

There might be situations in which someone might what to upgrade the database at runtime. This is currently not possible without destroying the existing DB object and creating a new one. An in place reopen / upgrade method would be useful here.

implement delay function

The idea of this function is to receive a callback and an amount of milliseconds. The Function then returns a new function. Once the new function gets called a time out is set and the callback will be executed after the delay. The wrapper function returns a promise which will resolve to the callbacks return value.

Proposed trait:

delay(fn: Function, time: Number) => (...args) => Promise

[Cache] SW cache does not recover from deleted cache storage

If a cache storage has been deleted by the browser, the SW cache should be able to recover from that situation and recreate the cache.

switch all modules to the new modules system

Switch all modules to the new modules system.

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

services implementation

First steps done by ee94c3d will be followed by some future commits after #1.

Cleanup before 1.0

The existing code base requires some clean up before it can be released.

An in-range update of eslint is breaking the build 🚨

The devDependency eslint was updated from 5.12.0 to 5.12.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ✅ coverage/coveralls: First build on greenkeeper/eslint-5.12.1 at 62.058% (Details).
• ❌ Travis CI - Branch: The build errored.

---

Release Notes for v5.12.1

• eb5c401 Chore: use meta.messages in some rules (2/4) (refs #9870) (#10773) (薛定谔的猫)
• aa56247 Fix: avoid loading core rules dynamically from FS in Linter (#11278) (Peter Metz)
• 04450bb Docs: clarify process for adding committers (#11272) (Kai Cataldo)
• 3ffcf26 Docs: add @g-plane as committer (#11277) (Kai Cataldo)
• c403445 Fix: warn constant on RHS of || in no-constant-condition (fixes #11181) (#11253) (Merlin Mason)
• 9194f45 Fix: Manage severity of 1 with TAP reporter (fixes #11110) (#11221) (Gabriel Cousin)
• 000f495 Docs: fix example for sort-imports ignoreDeclarationSort (#11242) (Remco Haszing)
• 7c0bf2c Docs: Add npx usage to Getting Started guide (#11249) (eyal0803)
• da9174e Docs: fixes typo peerDepencies (#11252) (Christian Kühl)
• 9c31625 Docs: Improve custom formatter docs (#11258) (Nicholas C. Zakas)

Commits

The new version differs by 12 commits.

• faf3c4e 5.12.1
• 1010c98 Build: changelog update for 5.12.1
• eb5c401 Chore: use meta.messages in some rules (2/4) (refs #9870) (#10773)
• aa56247 Fix: avoid loading core rules dynamically from FS in Linter (#11278)
• 04450bb Docs: clarify process for adding committers (#11272)
• 3ffcf26 Docs: add @g-plane as committer (#11277)
• c403445 Fix: warn constant on RHS of || in no-constant-condition (fixes #11181) (#11253)
• 9194f45 Fix: Manage severity of 1 with TAP reporter (fixes #11110) (#11221)
• 000f495 Docs: fix example for sort-imports ignoreDeclarationSort (#11242)
• 7c0bf2c Docs: Add npx usage to Getting Started guide (#11249)
• da9174e Docs: fixes typo peerDepencies (#11252)
• 9c31625 Docs: Improve custom formatter docs (#11258)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[DataBinding] Sort repeat bindings into DocumentFragment

It's easier to just reinsert all the repeated nodes, and it's also more performant.
We append all nodes to a DocumentFragment and once the list is up-to-date we add it to the DOM.

[DataBinding] StyleBinding

A style binging ,binds layout and style properties to a model scope. This gives easy access to information like, with, height, position and other styling properties.

remove obsolete files

We need to remove obsolete files, these include af.js, modules/packageManager.js, modules/net.js, modules/l10n.js, modules/ServiceLoader.js, modules/dom.js, modules/physical-touch.js, modules/core-extensions.js, modules/prototypes, viewController.js

remove inline documentation

especially the infos for the engine options. They will be moved to the wiki soon.

mozilla add-on content-script integration

after #2 I will commit some changes to improve af in the add-on environment to get it to work with content-scripts.

Requests are not properly matched against static cache

The cacheName is being incorrectly extracted and therefore requests are not being matched against the static cache. The first argument of the then() callback is an array of values.

ApplicationFrame/ServiceWorker/Cache.js

Lines 87 to 95 in e691477

	.then(cacheName => {
	const queries = [];
	queries.push(caches.match(request, {
	ignoreSearch: true,
	cacheName: cacheName.value
	}));
	if (indexRequest) {

ServiceWorker cache is constantly being refreshed

The cache is currently being refreshed each time the SW is initialized. This happens regardless of when the cache was checked the last time and whether the buildId changed, because neither cacheUpdate or staticFileBuildId are ever updated.

[NetworkRequest] support node.js runtime

NetworkRequestshould support the node.js runtime. Therefore, we need to implement a compatibility layer which supports both node HTTP requests as well as XHR. The current interface of NetworkRequest shouldn't be changed.

Fix audit issues

We should make sure to utilize the npm audit and fix all issues.

Implement Serviceworker Framework

Service Worker support is elementary for Application Frame. A proper framework has to be implemented.

The Framework should consist of two parts. A) the service worker has to be embedded into Application Frame, therefore core/ServiceWorker prototype should control the worker registration. The Prototype ServiceWorker then allows to setup the worker it self in a separate module.

[DataBinding] add binding for child scopes in parent scopes

We need to recycle all the child scopes if we do an single scope recycle. To achieve this we should place a binding in the parent scope that triggers the recycle for a child scopes.

[Branding] Project Logo

We currently do not have any kind of logo for the project. Coming up with a logo to represent the library would be a great step forward.

[DataBinding] DOM less testing

Create fake copies of the main methods so applications and systems can be tested without actually interfacing with the DOM.

• analyze the data binding interface and add all the required methods
• write fake implementations
• new interface method to enable test mode
• write test

[Node] provide require hook to intercept dependencies

To improve the usability of the node VM, we should add a requireHook() that lets people intercept require calls and possibly alter them.

[NetworkRequest] support request cancellation

It should be possible to cancel an already sent request.

[Rendering] support generators as render tasks

By using generators as render tasks, it would be really simple to interrupt these tasks.
The task could simply yield after consuming rendering time and could be continued when ever there is new render time.

[DataBinding] $ are stripped from expressions while parsing

the parsing RegEx accidentally strips $ from variable names. That should be fixed soon.

[NetworkRequest] make requests cancellable

We need a cancel() method on NetworkRequest. This method should interrupt already sent requests. If the request hasn't been sent yet, nothing should happen.

[IndexedDB] it's not possible to delete entries

It's currently not possible to delete any store entries.

[Rendering] Complete test coverage

Test coverage for the rendering module should be completed. We need tests for all remaining API methods.

[Tests] move test files from .travis to tests

All tests should be moved from the .travis/ directory to a new tests/ directory. References to the .travis/ directory have to be moved as well.

replacing self with g_

I really don't like this but in the Mozilla Add-on content-script environment self and window is not the same. Because it is impossible to overwrite self in this context, I have decided to rename the global object from self to g_.

[Rendering] implement time to live and segmentation

Create an interface that is injected into every task. This interface should allow tasks to check how much time they have left. If tasks run out of time and need to interrupt their work, they should be able to notify the render engine by returning false. The engine then will call them again in the next frame. It's in the responsibility of the task to continue where it left off.

[Threads] implement a toolset to work with threads

We need to create a tool set that makes it easy to work with threads / web workers.
This should Include:

• IOThread prototype
• main Thread capabilities in the Application prototype
• thread bootstrapping in the IOThread
• spawning and managing of additional threads as required
• providing an API to separate work into different threads.

[IndexedDB] Increase test converage

Come up with more tests for the IndexedDB driver to get the test coverage to 100%.

Redoc

Update and complete code documentation.