J-Stuff 1
Clothing
The XULRunner packages contain only the chrome code for XUL Widgets, with the following structure: * chrome/xulwidgets.jar (jarred chrome only) * chrome/content/xulwidgets/ (flat chrome only) * chrome/locale/en-US/xulwidgets/ (flat chrome only) * chrome/skin/xulwidgets/ (flat chrome only) * chrome/xulwidgets.manifest.inc To use them, merge the chrome directory with your XULRunner application, and then append the contents of xulwidgets.manifest.inc to chrome.manifest.
xulwidgets: installation
Introduction This tutorial will take you through the steps required to build a very basic extension - one which adds a status bar panel to the Firefox browser containing the text "Hello, World!". Note: The extension created by this tutorial won't work in Firefox that don't have a static status bar (that is, Firefox 4 and up). You can find a more up-to-date tutorial in the XUL School tutorial The Essentials of an Extension . Since Firefox 4 (and other Mozilla 2 based applications) there are two types of extensions: Traditional, classic, or XUL extensions are more powerful, but more complicated to build and require a restart to install.
Building an Extension - MDC
XPToolkit: Cross-Platform UI Toolkit
The Mozilla Toolkit is a set of programming interfaces (APIs) built on top of Gecko which provide advanced services to XUL applications. These services include: Profile Management Chrome Registration Browsing History Extension and Theme Management Application Update Service Safe Mode Official References Structure of an Installable Bundle : describes the common structure of installable bundles, including extensions, themes, and XULRunner applications Extension Packaging : specific information about how to package extensions Theme Packaging : specific information about how to package themes Multiple-item Extension Packaging : specific information about multiple-item extension XPIs XUL Application Packaging : specific information about how to package XULRunner applications Chrome Registration More Information
Amazon.com Amazon Web Services Store: Alexa Web Information Serv
This page contains the following categories of information. Click to jump down: AWIS provides the following operations, or "actions": URL Information The URL Information action gives developers direct access to information pertaining to web pages and sites on the web that Alexa Internet has gathered through its extensive web crawl and web usage analysis.
PROXY lists
What is Proxy Server? A proxy server is a machine that sits between the proxy users and the servers that they need access to. When a proxy user requests a certain remote resource using a URL, the proxy server receives this request and fetches the resource to fulfill the client’s request. This process enables the proxy server to store the requested content in a cache. Any new request that asks for information already in the cache no longer needs to be serviced by fetching it from the remote server. Instead, the new request is serviced from the cached data.The ubiquitous Linux, Apache, MySQL, and PHP/Perl/Python (LAMP) combination powers many interactive Web sites and projects. It's not at all unusual for demand to exceed the capacity of a single LAMP-powered server over time. You can take load off by moving your database to a second server, but when demand exceeds a two-server solution, it's time to think cluster. A LAMP cluster is not the Beowulf kind of cluster that uses specialized message-passing software to tackle a computation-intensive task.
How to configure a low-cost load-balanced LAMP cluster
Introduction The first article in this series, " Reusable assets, recipes, and patterns " introduced a recipe as a way to provide prescriptive guidance to create SOA implementations using patterns and a layered architecture. This recipe was called the SOA service implementation and optimize recipe. In this second article we examine this recipe in detail and explore the other reusable assets that it refers to. It should be noted that this recipe is by no means complete; rather, we use it to give a flavor of what is possible.
Building SOA applications with reusable assets, Part 2: SOA reci
Elements of Service-Oriented Analysis and Design
Introduction The basic concepts of Service-Oriented Architectures (SOAs) and Web services are becoming part of our everyday language and recognized as a suitable architectural style for crafting modern enterprise applications. In this context, the underlying issues of: what makes good services are becoming increasingly critical for ensuring the successful implementation of SOAs. Existing modeling disciplines such as Object-Oriented Analysis and Design (OOAD) , Enterprise Architecture (EA) frameworks , and Business Process Modeling (BPM) provide us with high-quality practices that can go a long way in assisting with the identification and definition of appropriate abstractions within an architecture. However, experience shows that these practices fall short when being applied independent of each other.
The introduction of new object-oriented programming (OOP) features in PHP V5 has significantly raised the level of functionality in this programming language. Not only can you have private, protected, and public member variables and functions -- just as you would in the Java™, C++, or C# programming languages -- but you can also create objects that bend at runtime, creating new methods and member variables on the fly. You can't do that with the Java, C++, or C# languages. This kind of functionality makes super-rapid application development systems, such as Ruby on Rails, possible. Before I get into all that, however, here's a word of caution: This article is about the use of very advanced OOP features in PHP V5 -- the kind of features you won't necessarily need in every application. Also, the kind of features that will be difficult to understand if you don't have a solid grounding in OOP and at least a beginner's knowledge of PHP object syntax.
Going dynamic with PHP
WURFL
An error has been encountered in accessing this page. 1. Server: wurfl.sourceforge.net 2. URL path: /php/index.php 3. Error notes: NONE 4.