The times of the network orchestrating multi- paradigm Architect are upon us. Once upon a time you could sit and fulfill your tasks one at a time, only contributing your small part to the big puzzle. Now consider a modern scenario where You have to pitch some kind of idea to a client, but given the intricacies of the world you can't even really be certain who your client is anymore. In addition you need to coordinate technical effort within a group to make the concept come together into that perfect idea that you had imagined. Now either you can sit patiently and wait for your idea to be accepted as the "grand design", or you can deploy your ideas onto the web and the public - And even let people interact with what you are building. You ordinarily have a base of operations. This location connects to servers somewhere, with your general databases for office web pages and virtual machines for employees and their workloads. Now also on these servers you should be considering connecting to your virtual desktop applications directly, giving them input from where you are at any one time, so that they can give you output for where you need to be in the upcoming moments. Although this is nothing new for Web developers and programmers, Architectural designers have not caught up. I am talking scripting and programming of the network services that will in turn automate and streamline these efforts. This has been a long time coming, but the need to produce results that are tangible immidiately is and always has been great. Now it is changing the routines of the Architectual designer as well. All the information needed to be able to proceed with an idea, process and project cannot rely on things like paper-based sources of forms, literature and presentation material that have to be moved from one physical location to another. Demands for more impressive visualization in the technological era will start to govern time tables and presentation forms. This is only just.

The next part of this consideration would be the network structure and deployment necessary to start fulfilling these obligations to yourself and the client. This more than puts a strain on the web- format and its scripting languages. Both user requests and server responses are historically text encodings, so web programming has ultimately been a text processing task. That is why it has been convenient to program using scripting languages. Working in this fashion you are quite limited to what kind of interactivity you can facilitate. While programming for web pages and the document- model the visuals and interactivity of a desktop Graphical User Interface are difficult to reproduce. Imagine a situation where a page contains various form elements related to different tasks in different widgets, and the event- propagation and updating of these widgets. Allthough your server application could be quite sophisticated, your typical HTML-, PHP-, CSS- and JavaScript- pages are not quite up to the task of interacting with it. Here I introduce the open source Web Application Framework WT(Web Toolkit), which is able to leverage this issue Using C++ lower level programming, WT libraries, Ajax and Websockets. No JavaScript to update using DOM manipulations or re- rendering of the web page. Widgets are at the heart of this framework, correlating to the windows used in desktop applications.

More to follow