The New World of Single Page Interface Sites is now LGPL v3

Discussions

News: The New World of Single Page Interface Sites is now LGPL v3

  1. ItsNat v1.2 is the first release LGPL v3 licensed allowing closed source web sites and applications built on top of ItsNat.

    ItsNat focus is Single Page Interface (SPI) web sites, that is, web sites ever running in a single page with no page reload or page navigation, in the same time with no sacricife of any required feature of web sites such as SEO, bookmarking, back/forward buttons, JavaScript disabled (accessibility), freedom of layout design etc.

    The Single Page Interface Manifesto summarizes this "new" trend of web sites.

    ItsNat is not the only tool to deliver SPI sites like Google Search, Twitter, FaceBook or LifeHacker,  but it is probably the only server-centric tool for this kind of web sites, in ItsNat most of coding is done in server using Java W3C DOM APIs managing pure X/HTML templates (page and page fragment) instead of a client-centric approach based on clumsy JavaScript, ItsNat approach is the same as in client but Java based with all the goods of server-centric programming like no communication bridges, view logic and data together, out of the box security and so on.

    Almost any typical conventional web site based on hundreds of pages can be converted to a single page, changing only page parts on demand usually as the result of user actions. This example shows how a conventional page based e-commerce web site can be converted to SPI (in this case 2 pages with more effort could be one), the same in Google App Engine. In spite of server-centric nature of ItsNat, memory consumption can be extremely low (interesting for GAE).

    Single Page Interface delivers an amazing user experience but it has a price, you must be a master of JavaScript and be ready to tons of JavaScript code and custom made AJAX calls, on the other hand you can follow the server-centric approach of ItsNat avoiding the client/server impedance because client synchronization is automatic. Anyway client code can be easily integrated into an ItsNat site/application (tutorial).

    Feel free to build with ItsNat the new generation of SPI web sites.

     

  2. any advantage of this over ZK or vaadin?

     

    both may be used to make an n-page web-site where n is any integer between 1 and infinity depending upon your preference. neither mandates that you use the gawdaweful language Javascript.

  3. any advantage of this over ZK or vaadin?

    both may be used to make an n-page web-site where n is any integer between 1 and infinity depending upon your preference. neither mandates that you use the gawdaweful language Javascript.

    ZK and Vaadin are fantastic for web applications, I'm not sure for web sites.

     

  4. some tips[ Go to top ]

    On the ItsNat website, your demos are running on port 8080. Most (if nor all) corporate firewalls only allow http/s traffic on 80/443. Stick a reverse proxy in front of your tomcat/jetty/whatever and direct all traffic over port 80 so that everyone can see the demos.

    Secondly the websites that are developed with ItsNat are still loadin in my browser. it does not reflect well on ItsNat.

    - Saqib

    http://code.nomad-labs.com/

  5. some tips[ Go to top ]

    On the ItsNat website, your demos are running on port 8080. Most (if nor all) corporate firewalls only allow http/s traffic on 80/443. Stick a reverse proxy in front of your tomcat/jetty/whatever and direct all traffic over port 80 so that everyone can see the demos.

    Secondly the websites that are developed with ItsNat are still loadin in my browser. it does not reflect well on ItsNat.

    - Saqib

    http://code.nomad-labs.com/

    Yes, you are right, anyway if you download and deploy the war file of demos you will get the same demos in local in minutes (usually dropping the war files in your app server).