Enlightning talk on modern web application achitecture - including a deeper, challenging message. Really you should not miss it!
Showing posts with label Frontend. Show all posts
Showing posts with label Frontend. Show all posts
Friday, October 21, 2016
Thursday, August 10, 2006
I have just republished the article and samples about CSTL (Client Side Tag Libs), which brings TagLibs to JavaScript in an extensible object oriented model. The original articles are well 1 1/2 year old but since everyone seems to talk about AJAX these days, I just want to show, that I had my 50cent to distribute to that subject a long time ago. Besides the links were not working in quite a while.
full article download files
full article download files
Tuesday, August 08, 2006
24 ways owns a collection of 24 very nice articles about bleeding edge JavaScript and CSS hacks to make things look good and work well. Definately worth a look or two if you are in the web business.
Sunday, January 30, 2005
Client Side Tag Libraries (CSTL) are a JavaScript based infrastructure that enables web developers and designers to employ custom tags into a (X)HTML page. Custom tags are mainly used to have easy access to sophisticated UI components. Underneath CSTLs are based on JavaScript classes that provide object oriented features like inheritance, polymorphism etc. and on top of that are easily distributable and redistributable across even across domains.
A TagLib enhanced (X)HTML document needs to loads the so called TagLibProcessor, as an external JavaScript file. The processor then looks for TagLibs registered in the <head> section of the document. After loading the TagLibs, the DOM is traversed finding and processing all custom tags – which should be XML namespaced.
A custom tag brings with it a convenient manner to create UI components in a JavaScript class, by either direct and eased DOM modification or even easier (X)HTML generation. Also you can bind variables to custom tag attributes that may refer to JavaScript variables, objects and functions, which are resolved into their real values behind on demand. Also every tag can be independently refreshed, either on a timed basis or in reaction to events, always serving you the current variable situation. This is the base for great flicker free user experiences.
full article download files
A TagLib enhanced (X)HTML document needs to loads the so called TagLibProcessor, as an external JavaScript file. The processor then looks for TagLibs registered in the <head> section of the document. After loading the TagLibs, the DOM is traversed finding and processing all custom tags – which should be XML namespaced.
A custom tag brings with it a convenient manner to create UI components in a JavaScript class, by either direct and eased DOM modification or even easier (X)HTML generation. Also you can bind variables to custom tag attributes that may refer to JavaScript variables, objects and functions, which are resolved into their real values behind on demand. Also every tag can be independently refreshed, either on a timed basis or in reaction to events, always serving you the current variable situation. This is the base for great flicker free user experiences.
<html>
<head>
<script type="text/javascript" src="cstl.js"></script>
<cstl:taglib classPath="com.inspirationlabs.taglib.std.StdTagLib" ns="std"/>
<script type="text/javascript">
function date() {
return new Date();
}
</script>
</head>
<body>
<std:print var="${date}" refreshRate="1000">
N/A
</std:print>
</body>
</html>
full article download files
Saturday, November 27, 2004
Just to have another system of the open-source community opposing the closed source solution just presented I have to mention X-Desktop. X-Desktop aims to bring the a skinnable windowing metaphor to the web. And they do that pretty well. The project might not have evolved much since it has been orginially released (about 2 years ago). It's comprised of a few JavaScript files which provide an API to open, close and arrage skinned inline windows on any website.
You probably find some bugs that are worth fixing but basically it's a very stable software all in all. I have started using it, when it first came out and was still published under a non-commercial license. Those guys do not have it so much with licensing and I guess it's still not perfectly clear, how you can utilize the API in commecial projects.
You probably find some bugs that are worth fixing but basically it's a very stable software all in all. I have started using it, when it first came out and was still published under a non-commercial license. Those guys do not have it so much with licensing and I guess it's still not perfectly clear, how you can utilize the API in commecial projects.
Bindows.net is a client sided rich client application framework, that uses petty much CrossBrowser JavaScript to do really impressive things. It aims to enable developers to code OS-style applications using just XML and deliver them via the browser.
You can use XML to layout your application, and use JavaScript to implement dynamic behaviour for components in their own component model. Components can be embedded pretty easily into existing web site. It's a truely exiting technology, and since x-browser support is available for Internet Explorer and Mozilla I guess the reach of products built with Bindows is pretty great, too.
Although Macromedia Flash can probably deliver better user experiences, Bindows is probably better suited to provide OS-type/styled applications through the web browser.
I have not played around with Bindows too much, but the examples I see in the AppLauncher a very promising. On the downside this is no open-source technology as you need to aquire licenses if you want to use this stuff in production with a commercial project.
I originally came to notice Bindows though the creators original DHTML-website, WebFX, which provides a lot of cross-browser (and also browser specific) widgets components that are written in XHTML and JavaScript. Nice things such a menus, sortable tables, tabbed browsing etc. are available for free here. Not quite as integrated as Bindows. But this stuff got me addicted to, when I used to be a web design script kiddie ;-)
You can use XML to layout your application, and use JavaScript to implement dynamic behaviour for components in their own component model. Components can be embedded pretty easily into existing web site. It's a truely exiting technology, and since x-browser support is available for Internet Explorer and Mozilla I guess the reach of products built with Bindows is pretty great, too.
Although Macromedia Flash can probably deliver better user experiences, Bindows is probably better suited to provide OS-type/styled applications through the web browser.
I have not played around with Bindows too much, but the examples I see in the AppLauncher a very promising. On the downside this is no open-source technology as you need to aquire licenses if you want to use this stuff in production with a commercial project.
I originally came to notice Bindows though the creators original DHTML-website, WebFX, which provides a lot of cross-browser (and also browser specific) widgets components that are written in XHTML and JavaScript. Nice things such a menus, sortable tables, tabbed browsing etc. are available for free here. Not quite as integrated as Bindows. But this stuff got me addicted to, when I used to be a web design script kiddie ;-)
Subscribe to:
Posts (Atom)