JLinX – Blog

Consolas Font Pack

• AT Attention Command
• AT*=? Test if command is supported
• AT Attention Command
• ATI Identification information
• AT+CGMI Request manufacturer identification
• ATA Answer Incoming Call Command
• ATH Hook Control
• AT+CLCC List Current Calls
• ATS0 Automatic Answer Control
• AT+BLDN Bluetooth Last Dialled Number (Letzte Nummer anrufen)
• AT+CBC Battery Charge
• AT+CSQ Signal Quality
• AT+CKPD Keypad Control !!!
• AT+CIND Indicator Control
• AT*ECAM Ericsson Call Monitoring
• AT+CLAN Language
• AT+CSIL Silence Command
• AT*ESKL Key-Lock Mode
• AT+CRSL Ringer sound level
• AT+CLVL Loudspeaker Volume Level
• AT+CMUT Mute Control
• AT*EMEM Ericsson Memory Management
• AT*SEFUNC SE Functionality status
• AT*SESP Speakermode On/Off

The Macwold 2008 is opened and Steve Jobs finally announced “the world’s thinnest notebook” – the MacBook Air that we’ve all been waiting for. (-;

Nothing Great was ever achieved by being realistic.

• Developer Connection
• Leopard Dev Center

• Tutorial: Intro to Core Animation
• A Three-Pack of Core Animation Tutorials
• Core Animation Sample Code by Lucas Newman
• ADC – Core Animation Menu Sample Application
• ADC – GeekGameBoard (Sample Code)

• MacResearch
• The Mac Developer Network

Se the following references to use VTK together with Cocoa:

• Installing VTK: Installing VTK on Mac OS X 10.4.x for the purposes of Cocoa
• Example: SimpleCocoaVTK by Sean McBride and Mike Jackson

Tutorials on MacResearch:

• Installing VTK on Mac OS X
• Beginning 3D Visualization
• Continuing 3D Visualization
• Finalizing 3D Visualization

In context of exploring the Model View Controller (MVP) pattern I came across following collection of links.

It also contained a link on Four Layer Architecture:

Problem:

When designing an object system for a client-server environment, what is the most appropriate way to structure the overall application architecture? How do you structure your system when you have both significant presentation and domain components?

…

The View layer. This is the layer where the physical window and widget objects live. It may also contain Controller classes as in classical MVC. Any new user interface widgets developed for this application are put in this layer. In most cases today this layer is completely generated by a window-builder tool.

The ApplicationModel layer. This layer mediates between the various user interface components on a GUI screen and translates the messages that they understand into messages understood by the objects in the domain model. It is responsible for the flow of the application and controls navigation from window to window. This layer is often partially generated by a window-builder and partially coded by the developer.

The DomainModel layer. This is the layer where most objects found in an OO analysis and design will reside. Examples of the types of objects found in this layer may be Orders, Employees, Sensors, or whatever is appropriate to the problem domain.

The Infrastructure layer. This is where the objects that represent connections to entities outside the application (specifically those outside the object world) reside. Examples of objects in this layer would include SQLTables, 3270Terminals, SerialPorts, SQLBrokers and the like.

MSDN Germany released a recorded TechTalk on Visual Studio 2008 and the .NET Framework 3.5:

Visual Studio 2008 und .NET Framework 3.5 – Was ist neu?