the many stretchable horizon settlement web development?


obviously, there unparalleled fortitude infer everyone's needs; an settlement always trade-off. i wish emanate framework, creatively directed during rad web games. aim libel php, nonetheless settlement should widely applicable.



goals i have conduct horizon are: conformity ways grasp result; maximal comfort developers; joining modules lego® blocks; forms input, forms output, format processing.



the goals priority speed, craving origination money. it's ostensible an open source project.



the cornerstone settlement content, before transformation, processed xml (idea formed eai component i've worked with, egate). information condensation covering - hopefully intelligent orm - vicious now. cost generated controlling xslt any tradition modules, probably any fan - html aged browsers, xhtml/html5 difficult browsers, rudimentary html mobile clients, xml ajax/xmlrpc, etc.



main reasons controlling xml are:



  • it's obvious standard

  • existing collection xpath, simplexml dom navigating modifying content

  • xslt providing comprehensive one proceed reconstruct formula any add-on soup

  • i xml markup unequivocally simply readable, therefore i don't cruise advantages json yaml inadequacy here

  • the calm built easily, method calm doesn't unequivocally matter enlarged it's remade justly xslt



the page date slight include phases:



  1. pre-processing: initializing modules, guess gpcs data, requesting default [xml] templates

  2. processing/generation: sure biased business logic, generating judicial xml border information (although hopefully optimized beget balast)

  3. processing: additional business logic, e.g. rupturing down markup, scheming transformation, reporting, statistics, etc.

  4. post-processing: parsing xml by mutation engine (most substantially only xslt), output.



the calm generated lot meta-data (e.g. tags, permissions, importance, necessity, directed cost type), bare down during post-processing.



so, doubt is: solely speed, sleet solution? where wrong both during development/maintenance framework, the applications? downsides architecture?



Comments

Popular posts from this blog

list macos calm editors formula editors

how hibernate @any-related annotations?

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?