Free microsoft framework software for linux

PIC USB Framework is a USB application framework dedicated to Linux (on the host side) and to the PIC 18F4550 family of microcontrollers (on the device side).
PUF includes: a bootloader that can flash the PIC application through the USB, a PIC demo and its corresponding application on the host side, and docker, the host-side flash programming utility.
The PUF also contains gputils and sdcc as cross-building tools, and odyssey 0.4vasco as a parallel port PIC programmer.
Enhancements:
- sdcc optimization flags are now switched on by default.
- A component library (including a console mechanism and a small real time scheduler) has been added to help building user applications.
- Tools have been upgraded to automake 1.9.6, autoconf 2.59d, sdcc snapshot 4482, odyssey 0.5, and gputils 0.13.4.
- The applications size has been optimized.

Wizard Site Framework project has been used in production sites for three years, serving countless thousands of page views.
It is modular , coming out of the factory with a basic structure, allowing the webmaster to spend more time on design and less on the plumbing.
Included is a user authentication system, scripts for registering, changing passwords, contact forms, confirmation emails, listing users, editing their profiles, privacy statements (etc.etc.), fully integrated into the site skeleton and under the rule of common CSS stylesheets.
Very cool is the menu and sitemap systems which are generated from the database automatically when a page is added or altered during authoring. The menu systems use the famed Suckerfish CSS-driven Javascript code harnessed to a MySQL database with PHP scripting.
You can, for example, have either horizontal or vertical menus, and they can be set at whatever depth you think is reasonable. You can hide pages from the menu or sitemap or restrict their view to only site members with the appropriate credentials.
Other features include such utilities as visitors statistics tied to the user management system so that you can see what specific pages on your site your registered members are viewing.
This is the third generation of the Wizard framework. While the structure of the site continues to be managed through an admin panel, and stored in a MySQL database, what is rather unique about the latest iteration is that the page content, indeed the entire page, is stored on the server as an HTML - PHP file.
While previous versions stored HTML content in the database, the Version 3.0 makes the page completely accessible to such online programs as Macromedia Contribute or other authoring tools.
Unlike previous versions, or content management systems (CMS) that store the HTML content in a database table, you have the ability to include whatever server-side or client-side code in site pages, removing a major disadvantage of most content management systems.
This makes Wizard Site Framework totally customizable and flexible. And because it is lightweight and very efficient it is easily scalable to large sites.
Enhancements:
- Many major and minor bugs were fixed.
- The front and back ends are now W3C compliant.
- A Poll and Blog script was added.
- Preliminary support for the PostgreSQL database was added.

Expresso Framework provides an architectural framework.
Expresso Framework is an open standards-based J2EE architectural framework that allows the developer to concentrate on application logic.
It is a library of extensible Java Server application framework components for creating database-driven Web applications based on open standards. Expresso integrates with Apache Jakarta Struts, which emphasizes presentation and application configuration, and bringing a powerful tag library to Expresso.
Expresso adds capabilities for security, robust object-relational mapping, background job handling and scheduling, self-tests, logging integration, automated table manipulation, database connection pooling, email connectivity, event notification, error handling, caching, internationalization, XML automation, testing, registration objects, configuration management, workflow, automatic database maintenance, and a JSP tag library.
Enhancements:
- Move password hash to UserInfo interface and its implementers: password hash no longer in User.java facade, but rather in UserInfo.java interface and its implementers. This allows more flexibility in handling external authentication.
Contributed By: Larry Hamel
- Velocity support for view rendering: Velocity can now be used to render the view. See EDG for details.
Contributed By: David Lloyd
- RunSQL Can Display Table Definitions: Enter the table name in the query section of RunSQL and it will now display the current definition of the underlying database table. Experimental
Contributed By: Michael Rimov
- RunSQL Executes Updates: RunSQL can now execute updates methods as well as select. This allows you to issue ALTER TABLE statements straight through the (secured) web interface. Experimental
Contributed By: Michael Rimov
- Initial Maven integration: Currently has been tested with the site:generate target and the corresponding compile, unittest, etc reports. Not yet used for building distributions. Experimental
Contributed By: Michael Rimov
- RequestRegistry automatically sets data context and security parameters: All calls to setDataContext() will no longer be necessary in client code. This info is propagated using ThreadLocal variables and the "Registry" pattern as described by Martin Fowler. Security parameters (i.e., requesting UID) are also propagated to RowSecuredDBObject, but for the sake of backwards compatibility, they are not propagated to SecuredDBObject. CheckLogin does this work. However, this functionality is also available in a servlet filter, RequestRegistryFilter. If you choose to use RequestRegistryFilter, you could do away with CheckLogin calls from the controller. We would use RequestRegistryFilter everywhere, but legacy installations have various URL paths, each of which requires filtering.
Contributed By: Michael Rimov
- Customizable per-instance UserInfo: Theres a new constructor in User that takes a UserInfo parameter. It allows special behavior for certain users.
Contributed By: Michael Rimov
- New Method: DataObject.setFieldsWithDefaults(): Populates all null fields in the object with default values as specified by the data objects metadata. The behavior mirrors that of DefaultAutoElement.
Contributed By: Michael Rimov.
- revise login bean CurrentLogin to be overridable: revise login bean CurrentLogin to be overridable, as a class handler in expresso-config.xml
Contributed By: Larry Hamel
- Added delimiter attribute to IfMemeberOfGroup tag: If a the delimiter is specified, the groupname will be split on the delimiter. The user will be search for any of the named groups (a logical OR is performed).
Contributed By: Mike Traum
- DataField.isChanged() works after update() and add(): Add method so that DBObject.update() and DBObject.add() can indicate when to cache the current field value as the original value for purposes of isChanged() comparison. Previously, isChanged() was working for DBObject.retrieve() only.
Contributed By: Larry Hamel
- AllowedHtmlPlusURLFilter: AllowedHtmlPlusURLFilter offers the recognition of a limited subset of HTML to be used within an input field. the subset has been chosen to offer some basic formatting without risking Cross site scripting (XSS) dangers.
Contributed By: Larry Hamel
- Struts Validator Integration: Expresso can now use Struts Validator for validating input forms. Rules are defined in validation.xml and validator-rules.xml. See Validating user input in EDG for more details
Contributed By: Raul Davidovich
- new class - com.jcorporate.expresso.core.controller.TilesController: Expresso aware implementation of the org.apache.struts.tiles.Controller interface. This allows for manipulation of theControllerResponse for a particular tile before it is displayed, independantly of the State currently being processed. Developers should extend this class and code the execute() method.
Contributed By: Malcolm Wise
- Various JoinedDataObject enhancements/fixes: You can now specify which fields to retrieve from each dataobject in the join. This list can also include expressions such as SUM(). Added custom WHERE clause facility. Aliases can be used in the custom WHERE clause and these will be translated when the WHERE clause is built. Fixed generation of ON clause when joining tables with a compound key. Provided setConnection() method to facilitate transactioning.
Contributed By: Malcolm Wise
- Stored Procedure support: Now DBObjectos have built in support for database stored procedures
Contributed By: Yves Henri Amaizo

WebMacro is a 100% Java open-source template language that enables programmers and designers to work together while promoting the ModelViewController pattern.
WebMacro is a viable (and proven!) alternative to JavaServerPages, PHP, and ASP. Its the fundamental page technology behind several major websites such as AltaVista.
WebMacro separates concerns about program code from concerns about the way a page looks:
- HTML should not clutter up program code
- program code should not clutter up HTML
- you should OwnYourOwnWork
- no-one should have to work through somebody else

Config::Framework is a Perl module with handy one-stop shopping for (most) of your configuration file needs.

SYNOPSIS

#create a new object, load two configuration files and decrypt the passwords. my $Object = new Config::Framework( Files => [ApplicationCfg.xml,UserCfg.xml], GetSecure => 1 ) || die $Config::Framework::errstr;

#change some data in one of the loaded configs $Object->{UserCfg}->{backgroundColor} = #00CCFF;

#write that change back to the file you loaded it from $Object->WriteConfig(configNamespace => "UserCfg") || die $Object->{errstr};

#Define a new configuration namespace %{ $Object->{newConfig} } = ( configNamespace => "newConfig", protectNamespace => 1, Version => 1, #arbitrary data keys follow backgroundColor => #006699, getRecords => 10, followLinks => 1, someThing => "in a bag" );

#Write your new configuration data out to an encrypted file #under the applications ApplicationFramework directory $Object->WriteConfig( configNamespace => "newConfig", Encrypt => 1, Crypt => "Rijndael", Key => "l33tp4sw3rd" File => "$Object->{FrameworkDir}/newConfig.xml" ) || die $Object->{errstr};

At long last I have decided to re-write the documentation for Config::Framework, in a manner which should be comprehensible by people other than myself. I would like to offer my sincerest appologies to anyone who tried to comprehend the sprawling stream-of-consiousness rant that was the previous documentation. Im sorry, I wasnt trying to make you insane. Now on with the show.

Ok so what is Config::Framework? Its a handy module for dealing with situations where you need your program to be able to load external data from a file that controls how your program operates. Im talking about configuration files here. So what do you do in a situation like that? Well you figure out a format to store your configuration parameters in, then write routines to read that format and put it some sort of meaningful data structure, and to write data from the data structure back out to the file.

Wouldnt it be nice if someone defined a standard config file format so that you wouldnt need to write your own parser? Well in the end, all a config file really is, is an arbitrary data structure expressed in in ascii. A standard way of serializing data structures in ascii you say? That sounds a bit like XML! Well the Data::DumpXML module will serialize perl data structures into XML and restore them for you, and you could certainly dump that to a file easily enough.
Ok getting to the point. The main thing that Config::Framework does for you is to define a standard data structure (or at least some standard guidelines for your data structure) and then front-ends Data::DumpXML so that you can arbitrarily dump and restore these data structures to files.

While were at it, Config::Framework aspires to be your one-stop-shop for config-type-stuff, by helping you stay organized in the way you handle external configuration data.

Salto Framework is a framework based on Ajax, Struts and J2EE technologies. Salto Framework provides graphical components such as datatables, treeviews and listboxes, and allows you to refresh only some parts on the screen. Thanks to the framework you dont have to write any javascript or to know anything about Ajax mechanism.

EmanonPHP Framework is a framework developed in PHP which uses a .NET-like convention for calling classes.

Generic Protocol Framework aims to allow users to rapidly prototype different emerging communications protocols. Implementations can be easily "dropped in" and tested independant of a finished product. Testing on both the end product, and the protocol itself can be easily accomplished. The tool aims to provide the developer and end user with a robust solution which can track the size of messages, how rapidly they will be generated, and how many of each type can be seen.
Why the GPF:
There are many similar tools available. The problem with many of these tools is that they are 1) closed source, 2) not easily adaptable to a specific implementation (they use custom languages), 3) expensive. The advantages of the GPF are its open source nature, the ease of which it can be adapted, and the cost: free!
Basic Flow:
Modification of the GPF is fairly simple. Tool-opts.h contains the basic options that will be applied to the packet while it is being built. To transmit a packet, the system calls the tx_message() function, and passes the message ID as well as the option block. This is then passed to the custom function: tx_message_custom() in tx.c. From the message id, the system selects an appropriate tx_* function (to be implemented by the user) and passes an unsigned char **, where the buffer will be written, and the option block. In turn, that function will make heavy use of the add_buf_tu*() functions, which will allow the user to add a tubyte8, tuint16, or tuint32 number to the buffer.
In daemonize mode, the basic options are set, and the system then listens for incomming packets. When a packet arrives, the system calls basic_parse() on the packet. This function then calls basic_parse_custom(), found in parse.c. In turn, this can call any appropriate parsing helpers, including the get_tu*() functions, which allow the user to retrieve a tubyte8, tuint16, or tuint32 from the buffer. CAVEAT: if the first two bytes of the buffer are zerod, it will be treated as an END message. However, recovery is available. In the basic_parse_custom() message, you can set the end_signal_caught variable of the option_block to 0. In this case, it will not stop the daemon from running.
Enhancements:
- Currently, TCP support is somewhat experimental.
- Testing for that portion will be ongoing.
- No clear examples are provided.
- The examples/ directory contains the precursors to a MIP example.