Sunday, August 12, 2018

EPA-Translation as Community-Driven Localisation for Web Apps



Just redefined description for epa-translation:

the community driven translations of web application will extend the application audience beyond the initially targeted countries and lingual dialects.


Why I have started a new project? Ideas are cheap, "every day a dozen" appear and are back logged forever. But this time it became another project to worry about. Worthy of the effort, ApiFusion.com and EPA-WG are actively in progress. 

First, a bit of history. When a new more or less valuable idea appears, it is usually written out and sometimes shared with friends who could have potential interest. Usually that is where its life ends. But this time, Hogne Titlestad from FriendUp invited me to discuss it in their IM group. Apparently the work on translation is in progress there. 

To make it visual for discussion, I thought 3 hours would be sufficient for proof of concept. That is when the project started. And as usual the appetite came during the meal, making me feed-frenzy towards the unusual challenges.

The challenge factor is crucial for hobby style projects. Otherwise, why bother, right?  However, it is not just the challenge swung me to work on proj. The EPA-WG needs a few clear microapplication samples, better in web 3.0 context( cross- service vendors UI and integration ). So far epa-translation seems to be complex enough in functionality and simple enough to understand. 

There is final reason to get it done: epa-translation fits into concept of community-driven content and knowledge/culture evolution which drives modern civilization to progress, where only collective intelligence could counter-balance AI. ( I do recognize other options such as AI and human fusion, but that is a bit in the future. Rather, community initiatives are acting now.)

epa-translation is a part of EPA-WG (Embeddable Progressive Application Working Group) initiative. #OpenSource hosted on GitHub.


PS. This project's challenges came from various sides:
* how to make the translation process seamless?
* how to embed microapplication into host app context?
* How to split several flows ( view, edit, sync to cloud) into independent microapplications?
* What radically new pattern microapplication gives and does it give significant advantages?
Some in HTML5 
* How to identify the text chunks in page, select and substitute?
* What local storage to use - localStorage vs IndexedDB? There is large matrix of pros and cons on each side.

Cloud layer
* Should it be server-less based?
* Should the platform be open?
* Could distributed DB be used? BlockChain vs CDN.

I am pretty sure the list of challenges will grow.

Wednesday, January 24, 2018

Sunday, October 29, 2017

WebComponents via AMD - pragmatic view

What I need for apps is ability to use AMD dependencies for my and external web components:
  • use the external libs from their CDN on prod, and local on developer machine
  • own AMD-based JS loading web components via AMD (webpack, dojo, requirejs) dependencies
  • own HTML syntax web components which list dependencies in JS section via AMD
Why AMD API? It is running without any compilers/transpilers in browser and compatible with webpack in case of need the bundling.

Why AMD instead of ES6 imports?

While ES6 imports are giving ability to load module from relative path, that is not enough as libraries could be served from different locations including different domains. AMD provides runtime URL resolving based on configuration making a combination of local component development with CDN dependencies a breathe.

How to load WebComponents via AMD?

require([   "link-import!iron-demo-helpers/demo-pages-shared-styles.html|onload"
        ,   "link-import!iron-demo-helpers/demo-snippet.html"
        ,   "link-import!../test-element.html"
        ], (a,b,c)=> console.log(`${a}, ${b}, ${c} webComponents loaded`) );

Of course the AMD configuration should be set to define URL mappings and common script loaded

  var dojoConfig ={ async: true
                  , packages:
                      [ { name: "webcomponentsjs", location: webcomponent_root }
                      , { name: "polymer", location: polymer_root }
                      ]
                  , aliases:  [ [ "link-import"  , isLocal ? "/components/link-import/link-import.js" : "../../link-import.js" ]
                              , [ /(vaadin-)(.*)/, (m,x,y)=>`${vaadin_root}/${x}${y}`   ]
                              , [ /(iron-)(.*)/  , (m,x,y)=>`${iron_root}/${x}${y}`     ]
                              ]
                  , deps: [ "webcomponentsjs/webcomponents-lite" ] // common for all pages
                  };

Here the Polymer and Vaadin Elements are used as good example of WebComponent frameworks.

Your custom WebComponent could use Polymer 2.x syntax and defined as HTML. Just the script section will have a class declaration wrappd into define() and dependencies are listed as JS strings instead of link imports:

        const NAME = 'test-element'
        define( NAME
            ,   [   "link-import!polymer/polymer-element.html"
                ,   "link-import!iron-ajax/iron-ajax.html"
                ,   "link-import!vaadin-material-theme/vaadin-text-field.html" //,   "link-import!vaadin-valo-theme/vaadin-combo-box.html"
                ,   "link-import!vaadin-combo-box/vaadin-combo-box.html"
                ]
            , ()=>
            {
                class TestElement extends Polymer.Element
                {
                    static get is() { return 'test-element'; }

                    static get properties()
                    {
                        return  {   prop1: {
                                        type: String,
                                        value: 'test-element'
                                    }
                                };
                    }
                }

                window.customElements.define( TestElement.is, TestElement );
            });
        require([NAME]);

Where to find the working sample of loading and making WebComponent via AMD?

cdn.xml4jquery.com/ajax/libs/AmdHarness/link-import/test/demo/index.html

What library I need to use AMD loader in my WebComponent?

link-import on github or NPM

Want to go wild?

Help me with creation of module loader for JS and WebComponents as jQuery plugin. The async API for jQuery is already available via xml4jQuery, WebComponents integration is missing:
$('.my-el')
    .html('loading...')
    .linkImport('vaadin-combo-box/vaadin-combo-box.html') // path resolved by config
    .html('');
$('my-el')
    .html('loading...')
    .asWebComponent('vaadin-combo-box') // path resolved by config, WC loaded, and injected
    .prop('items',['red','green','blue]) // property assigned once WC is ready

//  will be auto-populated  even if the code run way later:
$.defineWebComponent( 'my-component' )
    .$on('load')
    .$then( ()=>$.get('colors.json') )
    .addWebComponent('vaadin-combo-box')
    .$then( (combo, colors)=> combo.items = colors );
Happy coding!

Saturday, September 16, 2017

Moraga fiscal emergency solution

The sfchronicle post inspired me to look on infrastructure cost solutions across the globe and national scope. Seems the cities and larger entities already developed several ways of making sustainable and balanced budgeting models. 

The base principle came from this brief review: the cost should be placed on shoulders the entities which actually utilizing the infrastructure. From the owners of properties to utility companies. 

For utilities the shared infrastructure rental from municipal entity, for landscape owners - the amount of water and traffic they create, ...

There is a way to have the rental super-attractive by making it significantly cheaper than servicing by themselves. The way to achieve that: use the shared infrastructure for different services. The drain system with embedded fiberoptics(cable TV, internet, phone), power, sewage and water. The highly modularized, oriented on hot-swap non-destructive replacement  grid will cost a fraction of single service. And having many services will cut the cost on level of magnitude.

Monday, July 24, 2017

SVG use notes

Notes for myself.
Dimensions Embedded SVG within HTML page have several ways to define those:

  1. CSS via style="width:18px;height:18px" or class name like class="icon"
  2. attributes via width="18px" height="18px"
  3. viewport and viewBox attributes
While all of above could define the image sizes, there is a need for discipline in orchestrating all. The best way is to rely on CSS for sizing within HTML. Hence to use only #1. 
The reason is that in HTML CSS has higher priority than width/height attributes and if SVG tag has any default style, it would override those width/height inline attributes.

For cross-browser compatibility you still need the viewBox="0 0 1000 1000" attribute to define dimensions in SVG coordinates, usually it matches the image size. Only exception is a tile - when multiple images collected in SVG and you want to display only one a time. That is an advanced technique handy for collections like color icons. 
More on W3C site.

Sunday, June 4, 2017

XmlView moved to CDN

XmlView bookmarklet and XSLT makes the table presentation of JSON and XML in browser.

Now the XmlView would work for any web site which does escalate the security setting to use only own domain resources. So far it is almost any web site on interned.

What is new:
  1. Bookmarklet uses https on CDN which permits to see the transformantion without altering CORS browser settings
  2. Flickr and LinkedIn web services given for reference of JSON RESTful APIs
This release 1.0.0 is now located on https://cdn.xml4jquery.com/ajax/libs/XmlView/1.0.0/
Happy coding

Friday, May 26, 2017

xml4jQuery 1.1.0 released

Proud of it. Finally passed a full set of tests on all features I had in mind:

  • event handling 
  • call chain results propagated into callbacks 
  • Promise support for single run and $then() for recurrent call chain invocation 
  • error handling matching the Promise behavior 

$(".toFill")    .html("Click here")
                .$on('click')
                .html('Loading...')
                .sleep(1000)
                .xmlTransform( 'test/test.xml', 'test/test.xsl')
                .toggleClass('clickable')
                .prepend('Still clickable <hr/>');
 Also not so visible:

  • moved tests to ES6, they shortened at least twice 
  • made release build script to match CDN and NPM deployments, before it was a manual process 
  • started to use ApiFusion.com for project documentation 
For next release:

  • IE tests compatibility via AMD loader shim to load ES6 in IE on fly
  • $then() to accept other async chain 
Somewhere in future
  • refactor sources to ES6, target compiler to ES6, 
  • auto-transpiler shim for IE reference implementation

  xml4jQuery.com