Talk:XmlAspect.org/XmlView

From ApiFusion
Jump to: navigation, search

Bookmarklet

flow implementation

SCRIPT inject

In chrome XML by default is rendered as "http://www.w3.org/1999/xhtml" which need to be passed when creating SCRIPT tag by createElementNS.

PROS:

  • Easier development in dedicated script file.
  • Short bookmarklet.
  •  ?no need to reload document
  • same document origin

TODO: other browsers

bookmarklet transformation

Use the document object as transformation source. Cut off the initial HTML and replace with transformation results.

PROS:

  • Easier development in dedicated script file.
  • Short bookmarklet.

CONS:

  • long bookmarklet.
  • difficult development

forward to renderer.html with URL to original XML

PROS:

  • easiest development, full control over rendering.

CONS:

  • XML could be unavailable from HTML. Work around: set html "origin"

IFrame/Frame with renderer.html

CONS: if XML via URL is not available, its content need to be passed over messaging.


XML presentation change

get XMLDocument options

XHR on document.URL

access original xml document

Browser renders XML as XHTML document. The original document shall be referenced somewhere. But it is not among document properties. PROS:

  • no double XML load

CONS:

  • no implementation

Use proxy on same location as XSLT

PROS:

  • no cross-site origin issues

CONS:

  • requires dynamic content on server side, incompatible with CDN
  • double XML load

use renderer.html/php

bookmarklet forwards to renderer.php which has ORIGIN set to original XML document. PROS: ? no cross domain issues CONS: if PHP , incompatible with CDN

v1.0

Version 1.0 seems to be ready. Bare bone functionality and styling in place. Time for whistles and bells, including business model. Need your input on ideas.

BD

   "donate" - for sure. But only on home page. Time for non-profit?
   Shall ads be placed or wait until became popular?
   shall XmlView be a part of XmlAspect or independent entity?
   XmlAspect.org/XmlView vs XmlView.XmlAspect.org. I guess own domain will be easier to maintain but cost few $ extra.

Whistles and bells

  • support for random XML format with level complexity recognition( i.e. table vs tree view on sub-branch )
  • another views in addition to table
    • chart pie,
    • chart bar
    • nicer tree, perhaps with extra usability
  • style editor - on each view type
  • YouTube instructions
  • social links( G+,FB,twitter ) - which ones?
  • Support
    • forum
    • FAQ
    • wish list+vote+$ pledge
  • Parameters for rendering
    • URL parameters, need tricks on in-browser XSLT
    • service to keep URL-parameters mapping, need access control. Perhaps commercial, version 2.0
  • table parameters:
    • sorting
    • field visibility
    • field filtering
       all of above could be done over XML as a layer before feeding to UI transformation
    • XPath selector for 1 level table rendering. low priority, difficult
  • table parameters change from rendered UI