Really Simple History (RSH) framework für AJAX

„The Really Simple History (RSH) framework makes it easy for AJAX applications to incorporate bookmarking and back and button support. By default, AJAX systems are not bookmarkable, nor can they recover from the user pressing the browser’s back and forward buttons. The RSH library makes it possible to handle both cases.
In addition, RSH provides a framework to cache transient session information that persists after a user leaves the web page. This cache is used by the RSH framework to help with history issues, but can also be used by your own applications to improve application performance. The cache is linked to a single instance of the web page, and will disappear when the user closes their browser or clear their browser’s cache.
RSH works on Internet Explorer 6+ and Gecko-based browsers, like Firefox. Safari is not supported.“ – AJAX Anwendung Bookmark-kompatibel machen

Really Simple History (RSH) framework für AJAX

AJAX MAssive Storage System (AMASS)

„The AJAX MAssive Storage System (AMASS) uses a hidden flash applet to allow JavaScript AJAX applications to store an arbitrary amount of sophisticated information on the client side. This information is permanent and persistent; if a user closes their browser or navigates away from the web site, the information is still present and can be retrieved later by the web page. Information stored by web pages is private and locked to a single domain, so other web sites can not access this information.
AMASS makes it possible to store an arbitrary amount of sophisticated data, way pass the 4K limit of cookies or the 64K limit of Internet Explorer’s proprietary client-side storage system. An AMASS-enabled web site can store up to 100K without user permission. After 100K, users are prompted on whether the web site can store the requested amount of information. Users can approve or deny the storage request. The AMASS system informs the client-side application on whether the storage request was allowed or denied. In my own testing I have been able to store up to ten megabytes with good performance; I’m sure even more information can be stored, I just have never tried beyond this amount.
AMASS works on Internet Explorer 6+ and Gecko-based browsers, like Firefox. Users must have the Flash plugin version 6+ installed to use AMASS; Flash 6+ is installed in 95% of machines, however.“ – Kleiner Trick wenn mal mehr Daten auf Client-Seite gespeichert werden müssen. Das sollte aber soweit es geht vermieden werden…

AJAX MAssive Storage System (AMASS)

AJAX MAssive Storage System (AMASS)

Phrame PHP Framework

„What is Phrame?
Phrame is a web development platform for PHP based on the design of Jakarta Struts. Phrame provides your basic Model-View-Controller architecture, and also takes a step further adding standard components such as HashMap?, ArrayList?, Stack, ListIterator?, Object and more… All of this functionality was designed to be as easy as possible to use by developers and designers.
Phrame encourages application architectures based on the „Model2″ approach, a variation of the classic Model-View-Controller (MVC) design paradigm. Phrame provides its own Controller component and integrates with other technologies to provide the Model and the View. For the Model, Phrame can interact with any standard data access technology, including Pear DB/DataObjects?, and ADODB. For the View, Phrame works well with PHP, Smarty Templates, XSLT, Flash MX, and other presentation systems.
Phrame provides an extensible development environment for your application, based on published standards and proven design patterns. Phrame was originally sponsored by the Software Development department of Texas Tech University and is released under the LGPL.
Read about Phrame’s History.“ – PHP Framework; macht einen sauberen Eindruck und gibts schon seit ein paar Jahren

https://www.phrame.org/wiki

Phrame PHP Framework

Fusebox Framework

„An Overview of Fusebox
Application developers face a daunting task: they must translate the often fuzzily-defined requirements for a new application into the rigid language of computers. While the Fusebox Lifecycle Process (FLiP) offers help in managing the project management aspects of creating a new application, what help is there available to developers approaching the technical challenges of creating and maintaining applications?

Application frameworks answer this question, offering pre-built (and pre-tested) code — a collection of services that can provide the architectural underpinnings for a particular type of application. Web-based applications are increasingly the choice for new application development in which the browser becomes the „universal client“. As web development matures, web-based application frameworks allow the developer to concentrate more on meeting the business needs of the application and less on the „plumbing“ needed to make that application work.

Fusebox is, by far, the most popular and mature web framework available for ColdFusion and PHP developers. The architecture of a Fusebox application is divided into various sections („circuits“ in Fusebox parlance), each of which has a particular focus. For example, the responsiblity for ensuring that only authorized users have access to all or part of the application might fall under a Security circuit.

The Fusebox application architect defines these circuits, as well as the individual actions („fuseactions“) that may be requested of it. When a fuseaction request is made of the application, the Fusebox machinery (the „Fusebox“) routes the request to the appropriate circuit, where the fuseaction is processed. This idea of encapsulation of responsibilities makes it easy for different functional circuits to be „plugged“ into an application, making it possible to reuse code.

Within the individual circuit responsible for carrying out the requested fuseaction, the Fusebox architect specifies the individual files („fuses“) needed to fulfill the fuseaction request. Thus, the Fusebox acts like a good manager, delegating tasks to appropriate departments where it is decomposed into individual tasks, each of which can be assigned to individuals to carry out.“ – Ein weiteres PHP-Framework, welches das MVC-Pattern umsetzt

Fusebox Framework

Fusebox Framework

Windows Vista Oktober CTP

Windows Vista ist in der Oktober CTP Ausgabe verfügbar. Einen Überblick über die Neuerungen beschreibt Robert McLaws in seinem Blog:

„What’s New:

    Internet Explorer – This is a build closer to Beta 2, with a bunch of new features:

  • Tabs – Now under the address bar… woo hoo!!!
  • Better Phishing Filter
  • ActiveX „Opt-In“ – Practically all ActiveX controls are off by default. Users have to specifically enable the ones they want to use. As a result, the XMLHTTP object that is so heavily used in AJAX websites is now native code for the browser, and not an ActiveX control.
  • Parental Controls – Windows Parental Controls tied into the browser.
  • Favorites Center – FINALLY a better Favorites management experience.
  • QuickTabs – Microsoft one-ups Firefox with an overview screen of all open tabs.
  • Tab Groups (or Tab Favorites) – You can save a series of open tabs as a single group, and open that group as a favorite.
  • Advanced Printing – Multi-page print preview with a default option to print only the selected text. You can also manipulate the margins live and see the results in a „print designer“.
  • Developer Toolbar – I’m presuming that this is the same as what was released for IE6.
  • Standards – Improvements to the way IE handles international domain names, and CSS 2.1 support.

Networking

  • Network Center – Replaces „My Network Places“ and „Network Neigfhborhood“.
  • Improved TCP/IP stack – You now have more control over network bindings, and there appears to be more fit and polish to the unified IPv4/IPv6 stack.
  • Diagnostics – Built-in memory, hard drive, and network diagnostics to help resolve common problems automatically.
  • Windows Mobility Center – New control panel to access common settings, such as screen brightness, volume, and power management. It’s reminiscent of a car dashboard.
  • Windows Media Player 11 – It may still be branded WMP10, but it’s definitely v11. The UI is nowhere near final, but it’s still sweet. Definitely worth playing around with.

What’s Hinted At:

  • Windows AntiSpyware – It’s in the Security Center, but it’s just a visual cue… there’s no code in there yet.

What’s Broke:

  • Windows Media Center – doesn’t seem to work on my Tecra M4 if I use the Nvidia GeForce 6600 driver (to finally get Glass) instead of the Nvidia GeForce Go 6200/6600 drivers for XP.
  • Tablet features – The TIP throws a Win32 exception when I shut down, and the neat pen-related visual cues (the „magic“ halo when you hold the pen down, etc). The TIP still renders horribly under Glass.

What’s Missing:

  • Sidebar – Don’t expect to see it in distributed builds until Beta 2. NOTE: The bootleg Sidebar that’s been going around the net doesn’t work on 5231

Ajax: CheckLoginName

„Dieser Text führt in die Programmierung von Ajax-Anwendungen ein. Per Ajax (Asynchronous JavaScript XML) lässt sich eine Website so benutzen wie die Programme auf dem eigenen Rechner. Rückmeldungen finden fortlaufend statt und nicht erst nach dem Drücken des Abschicken-Knopfes.
Als Beispiel wird ein Eingabeformular zur Registrierung eines Logins entwickelt, das schon während der Eingabe des gewünschten Loginnamens darüber informiert, ob der Loginname noch frei oder schon vergeben ist.“ – Sehr gutes Tutorial

Sven Drieling, "Ajax: CheckLoginName"

Ajax: CheckLoginName

Microsoft VirtualWiFi

Virtual WiFi erlaubt es unter Windows XP eine physikalische WLAN-Karte unter mehreren logischen Adaptern anzusprechen, um leichter auf unterschiedliche Konfigurationen zurückgreifen zu können. Ausserdem ist es z.B möglich gleichzeitig auf ein Infrastruktur-Netzwerk und ein Ad-Hoc Netzwerk zuzugreifen.

Microsoft VirtualWiFi

Microsoft VirtualWiFi

WASP – Web Application Structure for PHP 5

„What is WASP?
WASP is a powerful web application framework built on PHP 5. Like Ruby on Rails, WASP strives to allow web developers to make great applications with more fun and less code, but in the familiar playground of PHP.
Why use WASP?
WASP was written from the ground up in pure Object Oriented PHP5. WASP fully utilizes all of the enhancements made to PHP in version 5.
This means you use less code to create enterprise class applications.
This isn’t your hacker’s PHP. “ – PHP on Rails

WASP – Web Application Structure for PHP 5

WASP – Web Application Structure for PHP 5