Free demonstrates software for mac

DateTips presents solutions to a few real-life problems that have been posed in AppleScript discussion groups in recent years, concerning the prediction or calculation of dates.

The solutions themselves may not be useful to anyone else, but they demonstrate the sort of thing that can be done with AppleScript dates. Theres also a handler that returns short dates in the users preferred order rather than the scripters.

VideoOut Plugin demonstrates how QuickTime Video Output Components can be used to play video out to hardware. A common use would be playing a dv stream (.dv file) out QuickTimes FireWire Video Output Component and recording it on your handy dandy DV camera.

The plugin contains the VideoOutComponent and VideoOut classes. VideoOutComponent uses the component descriptions of the MacOS. If a valid component instance is created, you use this class to obtain the default settings from the VideoOutComponent, to present it to the user and let the user alter the settings. The client is able to design a settings dialog, or even avoid the presentation of such a dialog.

distributed.net believes in the capability and potential of distributed computing. Our mission consists of three interdependent goals: development, deployment, and advocacy, to be pursued in the advancement of distributed computing. We will develop open, easily portable, highly adaptable, best-of-breed software, as well as networks and other necessary infrastructure to support that software.

We will do this by conducting and actively supporting distributed computing research of all kinds. We will deploy our software to form an immense, globally distributed computer that solves large-scale problems and provides an accessible pool of computational power to projects that need it.

This deployment will also demonstrate the real-world utility of both distributed computing in general and our software in particular.

Finally, we will advocate distributed computing, by encouraging global participation and contributions of processing power, bandwidth, and expertise; by providing a forum for discussion; and by raising awareness on the Internet and in the mainstream.

Display3DS is a Free Software application demonstrating how programmers using Visual C++ and MFC can easily decode 3D Studio MAX (.3DS) mesh files and display the result using the OpenGL 3D Graphics API.

Complete source code is offered freely and without warranties or restrictions to help others seeking a minimal MFC compliant codebase onto which your own features and functionality can be added.

Display3DS is made up of only three components:
• Display3DS - a small, legible mainline which handles the Windows graphics user interface environment including window creation and management, keyboard interface, timer event handling, etc.
• Okudagram - a small class to handle all aspects of the OpenGL 3D graphics API including Rendering Context creation, Perspective and Orthographic view projection management, Display Lists, etc.
• Mesh3DS - is my object-oriented translation of David Farrells old View3DS code which performs basic 3DS mesh file decoding to internal data structures as needed by the Okudagram class. This class is not small, but using Mesh3DS is painfully easy.

This API provides an abstraction layer to allow accessibility applications a way to manipulate the UI of other applications, be they Carbon or Cocoa. The API is provided for use by both Carbon and Cocoa applications, although this sample demonstrates their use from a Cocoa application.

In UIElementInspector, the Accessibility API is used to get information about whatever AXUIElements (widgets) are under the mouse at any given time. Information may be obtained from the AXUIElement, and actions that it has may be performed.

As the mouse moves, the inspector window displays information obtained through the new API. When you then lock the inspector window on an element, you can dig deeper into the information provided by the API for that object, as well as trigger any actions that it might provide, in the interaction window.

UIElementInspector sample does not demonstrate how to make a custom UI element accessible so that the Accessibility API can access it. Custom Cocoa widgets will often just inherit the right behavior from their superclass.

Carbon applications will typically need to provide a little more code to serve up the right information to applications that are interested. Instead, this sample shows how to use the Accessibility API itself - to get information on other applications and UI elements on the screen, which you would need to do as an accessibility application.