Skip navigation

Hosting by: digital.forest

ADHOC 2005 Call For Papers

Following up on an exciting and successful MacWorld San Francisco, The Advanced Developers Hands On Conference (ADHOC) is announcing the Call For Papers for ADHOC 2005/MacHack 20. ADHOC focuses on, but is not limited to, Macintosh and Unix development issues. Abstracts for papers must be received by March 15, 2005 by the conference papers committee for consideration.

Have you done interesting work you would like to tell others about? Many new things are happening in the world of computing, from low cost supercomputing to new OS releases. New programming languages and tools are always showing up and need good discussion. New or expanded techniques used in code development can be shared and expanded on for the good of the software community.

Possible topics for this year's ADHOC include:

Why should you write a paper?

Paper authors do not pay the conference registration fee (US$575). You must give a presentation of your paper during the conference, which enables everyone to realize just how cool your topic really is. Copies of the papers are included on the conference CD.

Papers usually range from 2000 to 4000 words or 8-15 pages in length. Once your abstract is accepted, we will provide you with a document template for formatting your paper. Since the ADHOC audience is technically oriented, pure marketing topics or content are unlikely to be well received. Paper acceptance is at the sole discretion of the papers committee, not all submissions of acceptable topics will be accepted for publication and presentation at the conference.

Contact the papers committee at papers2005@adhocconference.com and check the ADHOC Conference website for papers from previous years at http://www.ADHOCConference.com/papers/.

[/Papers] Link to this story
Last updated 2006-03-29

Confirmed Papers

Paper: Cross-Platform Approaches from a Macintosh Perspective

Jonathan Hoyle

Friday, July 29, 2005 at 4:00 PM

One of the many difficulties that Macintosh software developers must face is how to justify to their management the expense of development on the Mac when less than 1/10 of the users are it. Cross-platform development seems to be the only economically feasible, yet so many of these approaches give you "least common denominator" solutions. This paper will detail the many approaches to cross-platform development from the Macintosh perspective, looking at the pros and cons of various frameworks and modern RAD applications. Hilights and pitfalls will be addressed for environments such as RealBasic and Java, but most emphasis will be placed from a C++ perspective. Frameworks such as CPLAT, wxWindows and Qt will be looked at, as well external libraries which take platform specific frameworks like PowerPlant and make them cross-platform. Examples of professional applications who have used these various strategies and their success (or lack thereof). Design principles which expedite a cross-platform strategy (like an MVC architecture) will also be examined. In the end, a few recommendations can be made for best practices and viable approaches, plus some downloadable starting sample projects will be made available.

Paper: Cross-Platform Development with Qt

Scott Collins

Friday, July 29, 2005 at 2:00 PM

Qt is a mature, cross platform GUI toolkit enabling developers to write one application, but compile and run it on many platforms including Mac OS X, Linux/Unix/X11, Windows, embedded, or even on cell phones. Qt works with your favorite tools and features graphical UI design a la Interface Builder. Qt is available under the GPL but is also available under a non-GPL-encumbered commercial license if you don't want distribute your own source code. This paper will present an introduction to Qt, a comparison with other GUI toolkits, and the creation of a non-trivial application from start to finish.

Paper: Hacking the Mac OS X Kernel for Unsupported Machines

Ryan Rempel

Friday, July 29, 2005 at 5:00 PM

To get Mac OS X running on machines that Apple no longer supports, some changes to the behavior of the kernel and certain IOKit kernel extensions were required. Since most of the relevant code is open source, it would have been possible to substitute custom components for the ones that Apple supplies. However, this would have required recompilation and redistribution for every minor version change in Mac OS X. Fortunately, the IOKit system provides a sophisticated run-time environment that often allows your own kernel extensions to inherit Apple's code, and fix only the things that need to be fixed. The techniques involved can be useful for anyone doing driver development, even on supported systems.

Paper: Program Analysis and Verification on Mac OS X

Gordon Worley

Friday, July 29, 2005 at 11:00 AM

Computational techniques to analyze and verify computer programs give developers powerful tools that can help them write quickly and efficiently correct programs that accomplish their intended goals. In this paper we explain the computer science foundations of program analysis and verification, review some of the important literature, and look at the program analysis and verification tools available on Mac OS X.

Paper: simg5

Mark Szymczyk

Friday, July 29, 2005 at 3:00 PM

Profilers like Shark tell you what parts of your code are running slowly. To learn why your code is running slowly, Apple includes tracing tools with the CHUD Tools. simg5 tells you why your code is running slowly on G5 processors. The paper shows you how to create the trace files simg5 needs, how to run simg5, and how to use Scroll Pipe Viewer to view the path each assembly language instruction takes.

Paper: Types++: Typesafe Metadata, and Other Thoughts Beyond int

Ryan Wilcox

Friday, July 29, 2005 at 2:00 PM

C/C++ (and other strongly, statically typed languages) use type data as a compile-time check: you can't put that there, or the ever popular "some data might be truncated" warnings. Still there is possibility for error: can you know for certain, just by looking at a function prototype, that the Str255 parameter is a PString, or a shortcut by a lazy programmer? Or can you ever be certain that your divisor (int) is not zero, without checks all over? What character encoding does that std::string contain? In essence: metadata, not just type, is an important factor of many variables. Metadata focus can be achieved by using metadata class templates, which supply both compile-time checks, runtime checks, and also serve as form of documentation for future maintainers. This paper will further discuss metadata, metadata templates (implementation, usage, examples, and drawbacks), and other thoughts for modern "type" safety.

Paper: XGP: Turning a UNIX Prolog compiler into a Mac OS X development environment

Lindsey Spratt

Thursday, July 28, 2005 at 4:00 PM

[/Papers] Link to this story
Last updated 2006-03-29