Free architectural shingles software for linux

SchoolTool project is a common information systems platform for school administration.

SchoolTool is a project to develop a common global school administration infrastructure that is freely available under an Open Source licence.

The vision is to create a platform that is equally compelling for schools and colleges in First and Third World countries, that supports best practices in school administration, and that is readily customized to comply with local regulatory requirements.

It is based primarily on Zope 3, with an HTML interface and a Web service interface in the REST architectural style.

Install step-by-step Instructions

OK, using the aforementioned shell script makes things easier, but there are still a few steps you need to pay attention to.

You need a C development environment (build-essential on Ubuntu) and Python development libraries (python-dev on Ubuntu).

You need the Python Imaging Library (python-imaging on Ubuntu) and the Python libxml2 bindings (python-libxml2 on Ubuntu).

You need a very up to date version of Python setuptools, which will probably require downloading a new version of ez_setup.py and running that script as root.

Now you can download alpha2-install.sh to whatever directory you like to use for testing software and do chmod +x alpha2-install.sh to make it executable and then ./alpha2-install.sh.

Hopefully it will then set up the rest of your environment and give you some final instructions when it is done. You will probably get one error message when it runs the tests. Please ignore it.

Quanta Plus is a highly stable and feature rich web development environment. Quantas vision has always been to start with the best architectural foundations, design for efficient and natural use and enable maximal user extensibility.

We recognize that we dont have the resources to do everything we would like to so our target is to make it easy for you to help make this the best community based desktop application anywhere. Pretty much everything in Quanta is designed so you can extend it.

Even the way it handles XML DTDs is based on XML files you can edit. You can even import DTDs, write scripts to manage editor contents, visually create dialogs for your scripts and assign script actions to nearly any file operation in a project. You can even look at and communicate with a wide range of what happens inside Quanta using DCOP.

Quanta is based on KDE so this means it is network transparent from any dialog or project. It can use not only FTP but other KDE KIO slaves from file dialogs or in project settings. For instance if you want secure access try the fish KIO slave that uses SSH.

Just enter fish://[user]@domain in any dialog or select fish in your project settings. Here on this site you will find information on using Kommander to visually build dialogs you can extend Quanta with. These applications talk to each other using an IPC (Inter Process Communication) called DCOP (DEsktop Communication Protocol).

Of course I realize this can sound like alphabet soup techno-babble to some web developers, but heres what it means. When you are using Quanta and realize you would like to do something and you want to ask "Can I do this?" you can expect the answer will not only be yes, but it will probably be even cooler than you hoped for.

Not included on this site are other tools you can use with Quanta for revision control and reviewing and merging changes in files. Those applications are Cervisia and Kompare, and if they are not installed and you install them Quanta will use them.

We would like to think that there are rich rewards to be found here for those willing to explore new ways of doing things, or perhaps in some cases old ways that are just new to you.

PAPI aims to provide the tool designer and application engineer with a consistent interface and methodology for use of the performance counter hardware found in most major microprocessors.
PAPI enables software engineers to see, in near real time, the relation between software performance and processor events.
The Performance API (PAPI) project specifies a standard application programming interface (API) for accessing hardware performance counters available on most modern microprocessors.
These counters exist as a small set of registers that count Events, occurrences of specific signals related to the processors function. Monitoring these events facilitates correlation between the structure of source/object code and the efficiency of the mapping of that code to the underlying architecture.
This correlation has a variety of uses in performance analysis including hand tuning, compiler optimization, debugging, benchmarking, monitoring and performance modeling. In addition, it is hoped that this information will prove useful in the development of new compilation technology as well as in steering architectural development towards alleviating commonly occurring bottlenecks in high performance computing.
PAPI provides two interfaces to the underlying counter hardware; a simple, high level interface for the acquisition of simple measurements and a fully programmable, low level interface directed towards users with more sophisticated needs.
The low level PAPI interface deals with hardware events in groups called EventSets. EventSets reflect how the counters are most frequently used, such as taking simultaneous measurements of different hardware events and relating them to one another.
For example, relating cycles to memory references or flops to level 1 cache misses can indicate poor locality and memory management. In addition, EventSets allow a highly efficient implementation which translates to more detailed and accurate measurements.
EventSets are fully programmable and have features such as guaranteed thread safety, writing of counter values, multiplexing and notification on threshold crossing, as well as processor specific features. The high level interface simply provides the ability to start, stop and read specific events, one at a time.
PAPI provides portability across different platforms. It uses the same routines with similar argument lists to control and access the counters for every architecture. As part of PAPI, we have predefined a set of events that we feel represents the lowest common denominator of every good counter implementation.
Our intent is that the same source code will count similar and possibly comparable events when run on different platforms. If the programmer chooses to use this set of standardized events, then the source code need not be changed and only a fresh compilation and link is necessary. However, should the developer wish to access machine specific events, the low level API provides access to all available events and counting modes.
If an event or feature does not exist on the current platform, PAPI returns an appropriate error code. This significantly reduces the porting effort of code using PAPI because the semantics of each call to PAPI remains the same, just the argument lists need updating. In addition to the standard set, each PAPI implementation supports all native events through the ability to directly accept platform specific counter numbers. Definitions for most, if not all of these, are included as conditional macros in the header file. In this way, PAPI avoids having inefficient code to translate all events for all platforms into a uniform representation and back again.
This translation is only done for the relatively few events defined in the standardized set. Some processors like those in the POWER series have counter groups. They enable access to specific groups of counters, instead of individual events. This presents a serious portability problem, thus PAPI abstracts hardware counters from their groups with a packed naming scheme. Each counter control value or event is made up of the counter group number and the number of the specific counter in that group.
PAPI can be divided into two layers of software. The upper layer consists of the API and machine independent support functions. The lower layer defines and exports a machine independent interface to machine dependent functions and data structures. These functions access the substrate, which may consist of the operating system, a kernel extension or assembly functions to directly access the processors registers.
PAPI tries to use the most efficient and flexible of the three, depending on what is available. Naturally, the functionality of the upper layers heavily depends on that provided by the substrate. In cases where the substrates do not provide highly desirable features, PAPI attempts to emulate them as described below.
PAPI makes sure the underlying operating system or library guards against overflow of counter values.
Each counter can potentially be incremented multiple times in a single clock cycle. This combined with increasing clock speeds and the small precision of some of the physical counters means that overflow is likely to occur.
One of the more advanced features of PAPI is to provide a portable implementation of asynchronous notification when counters exceed a user specified value.
This functionality provides the basis for PAPIs SVR4 compatible profiling calls, that generate an accurate histogram of performance interrupts based on hardware metrics, not on time. Such functionality provides the basis for all line level performance analysis software, from the antiquated days of AT&Ts prof to SGIs SpeedShop. Thus for any architecture with even the most rudimentary access to hardware performance counters, PAPI provides the foundation for a truly portable, source level, performance analysis tool based on real processor statistics.
Enhancements:
- The API was extended to decouple abstraction layers from hardware support and to provide initial support for different types of performance counters.

CYCAS is a 2D+3D CAD package for drafting and design in high quality and for creating 3D presentations and technical illustrations easily.

Some of its features include an easy-to-handle user interface, special architectural elements and functions, a WYSIWYG display, printing, plotting, import and export filters, photorealistic rendering with POV-Ray, documentation and tutorials, example drawings, and an extendable 2D/3D symbols library.

Easy to handle. Dialog boxes to design drawing elements easily with a database function to improve work flow. A layer technique which is flexible to employ.

It simulates working with transparency sheets. HTML online help, illustrated with many graphics. Graphical user interface based on GTK (The Gimp Toolkit).

Lines, circles, texts, patterns and color fillings, calculation of areas and volumina, semi-automatic and manual measurement, support of architectural presentation, extendable Symbol library.

Architectural elements such as walls, openings, windows, doors, 3D basics, extendable Symbol library.

Intuitive working in the ground plan, elevation and isometric views. Computing graphics such as hidden line graphics or wire graphics from various perspective or isometric views.

Direct export to POV-Ray [TM of the POV-Ray Team] module to generate high-quality rendered images easily. Extendable Material database to support output of 3D data to renderer.

Sauerbraten is an experimental engine based on Cube, can be seen as "Next-Gen Cube", or "Cube 2". Much like cube, the aim of this engine is not to produce the most eyecandy possible, but rather allow map/geometry editing to be done dynamically in-game, and make map editing a lot of fun.

Sauerbraten has an even simpler world model than cube (fewer exceptions, just one kind of building block), is quicker to edit geometry with, yet allows for significantly greater class of shapes. One way to see the transition from Cube to Sauerbraten is to say Cube was a 2-directional heightfield (floor and ceiling), and Sauerbraten is a 6-directional heighfield (heighfields can be modeled in all 6 directions).

The world consists of an octree of deformable cubes. It being an octree has just one important effect: it allows the mapper to work at any scale, from large landscape areas to small architectural details. The octree is largely invisible to the mapper though, he can arbitrarily break up larger cubes or merge them, and the engine takes care of the rest.

The deformable cubes are geometric shapes made out of maximally 8 vertices. In its maximum size, it is a regular cube that fills the entire octree node it sits in, as minimum size all 8 vertices coincide which is to say the cube is "empty". Anywhere in between theres a variety of slanted cubes and wedge shapes that are possible to any degree and orientation, and together with neighbouring cubes can form any shape easily.

The editor is similar to the one in Cube but much easier / direct to use, as there arent all the different kinds of cubes to worry about. Here, you can simply "push and pull" geometry with your mousewheel in 6 directions, depending on the orientation of the surface you are looking at. Modifier keys allow you to influence single vertices on a cube, connected vertices touching multiple cubes, edges, faces and entire cubes. Selections can be made to operate on more primitives at once. Many complex shapes are quick and easy to make. It is definitely the most fun way to model architecture to date.

The internal representation of a deformable cube is very different from a vertex based representation, and is based on "edge spans" which allows the engine to represent any kind of shape uniformly in just 12 bytes. This means it can hold great amounts of geometry in memory and maps on disk are small. To render this kind of geometry, the engine goes through a process of converting the internal representation to vertices using plane intersections based on the edge ranges, culls coinciding faces, merges vertices etc. to arrive at something which renders efficiently by hardware and caches this in chunks based on the octree. This allows Sauerbraten a significantly higher polygon throughput than Cube while maintaining its ability to have dynamic geometry.

The current implementation inherents all the non-world geometry related code from Cube, and as such works without modification: entities, AI, gameplay, network, console/script. For the new code, rendering and editing are close to done, physics and lighting are working quite well, level loading/saving is complete, SP & MP work, but plenty of more advanced stuff like occlusion culling & LOD is missing.

UPDATE: Sauerbraten has now started as a Cube community Open Source Engine (& Game) project. It interesting for developers & mappers, but maybe not players yet (though SP & MP do work). If you are interested in checking it out, or even in contributing, I suggest you visit the forums (see below).

NEWS: may 24 2005 release with lightmaps and working MP/SP gameplay! download from sourceforge below.

Swing XML Authoring Tool is a Swing-based authoring tool for the quick and easy development of GUI Java applications.
It implements out-of-box a true MVC framework and uses XML to define the view (SwiXml is used as the XUL engine), BeanShell as a scripting language for the controller, and JXPath as the binding mechanism between the view and model.
Swing XML Authoring Tool provides a complete environment in which it is possible to almost write an entire Java Swing application without writing Java compiled code. The use of XPath makes it very simple to traverse the object tree of the applications business model.
It takes a lot of work to develop a Swing application, laying out and configuring GUI components, and then integrating them with the application functionality. SwiXAT addresses both of these issues by providing a framework based on a complete implementation of the MVC architectural pattern.
The benefits obtained by a such framework are the followings:
- Architectural Correctness: By adopting a true MVC (Model View Controller) based framework, it is very easy to correctly implement any UI application. Its not difficult to write a Java/Swing application, but whats very difficult is to build a good, well designed Swing application, where the adoption of the MVC paradigm permits to reduce the maintenance costs, thanks to the clean separation between the view and the application logic.
- Development Speed: The adoption of a framework reduces the development cost by providing out-of-box, well integrated and easy to use common features, like wizards, plugins, support for MDI interfaces, etc. Moreover, the use of XML to define the user interface, as well as the adoption of an interpreted scripting language, permits to implement the Code&Test development style, where the compilation time is reduced to zero.
- Code Reuse: The net separation between the view and the control logic permits to write reusable modules that can be combined in several manners. The developer is naturally induced to modularize the application and write reusable code, minimizing the effort of building new applications or adding new functionality to existing ones.
SwiXAT is all the above, and we hope youll appreciate our effort.

LOSSA project is a home automation system.
LOSSA is a home automation system that aims at distributed network of devices with simple interconnect system, personal computer intercommunication, simple wiring, and very low cost.
The project is still in architectural development state and the files avalivle as download (including this readme) are there to collect as much feedback as possible from those people who have experience in similar projects.
Dew to the contained price, easy requisition, wide veriaty of opensource developement tools and very little external components requirements I think that Microchips pic16f84 will be a mandatory choice in any case.
Enhancements:
- Added application showing internal pic eeprom usage and TIL311 interfacing
- Added simple pic application showing interrupts (tools/beginner_pic_app)
- Defined EEPROM Memory Assignments for config amd power fail retention
- Review of: transmission type, collision detection, physical medium
- Added a tools directory with PicMicro developing and programming tools
- Reorganization of the documentation
- Review of the transmission protocol
- Made Makefile (just for packaging for now)