Editing Liqbase library overview

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
-
{{out of date}}
+
=liqbase :: the core library=
-
 
+
-
==liqbase :: the core library==
+
'''Note, this document describes a library which is not currently available, however its precursor [[liqbase]] is available for download:'''
'''Note, this document describes a library which is not currently available, however its precursor [[liqbase]] is available for download:'''
Line 10: Line 8:
it will be expanded upon over the coming days.
it will be expanded upon over the coming days.
-
===Rationale===
+
==Rational==
liqbase was born of frustration.
liqbase was born of frustration.
Line 16: Line 14:
It started out as a collection of ideas and principles which show off the nokia internet tablet as a fast versatile handheld computer which very rapidly grew into a large monolithic application.
It started out as a collection of ideas and principles which show off the nokia internet tablet as a fast versatile handheld computer which very rapidly grew into a large monolithic application.
-
It was the first application I have written in C in many years has been used to learn about the device and the various libraries and interactions on the Nokia internet tablets.
+
It was the first application I have written in C in many years was and was used by myself to learn about the device and the various libraries and interactions on the Nokia internet tablets.
A proof of concept so to speak.
A proof of concept so to speak.
Line 25: Line 23:
It has been written in C for both speed and expandability.
It has been written in C for both speed and expandability.
-
At present it is very specifically focused upon the Nokia internet tablet computers though it is compilable and usable within x86 linux as well.
+
At present it is very specifically focused upon the Nokia internet tablet computers running linux.
-
===Why not GTK+ or Qt?===
+
==Why not GTK or QT?==
-
I looked carefully at GTK+ when I first got my tablet and would have been happy it if it had the required performance, it has (semi) sane construction methods and an expansive library of controls and utility functions.
+
I looked carefully at GTK when I first got my tablet and would have been happy it if it had the required performance, it has (semi) sane construction methods and an expansive library of controls and utility functions.
-
However on the tablet graphical performance was so poor that anything I attempted felt slow and applications crawled along. Qt had its own problems and still is not a viable option on the devices.
+
However on the tablet graphical performance was so poor that anything I attempted felt slow and applications crawled along.
 +
QT had its own problems and still is not a viable option on the devices.
I wanted to do things which I took for granted on my old PDA and have done for years in Visual Basic and found the existing toolkits lacking.
I wanted to do things which I took for granted on my old PDA and have done for years in Visual Basic and found the existing toolkits lacking.
-
 
+
==Dependencies==
-
===Dependencies===
+
liqbase makes use of the following libraries:  
liqbase makes use of the following libraries:  
Line 45: Line 43:
*xsp for the pressure sensitive mouse input
*xsp for the pressure sensitive mouse input
*ttflib ttf font handling
*ttflib ttf font handling
-
*libpng for reading and writing image data
+
*libpng
*libjpeg
*libjpeg
-
*sqlite3 for the database manipulation
 
-
graphics are rendered using the XV library using the YUV video format. This is a lower bandwidth video mode which has full resolution Luma, but half resolution Chroma.
+
graphics are rendered using the XV library using the YUV video format.
 +
This is a lower bandwidth video mode which has full resolution Luma, but half resolution Chroma.
-
===Base Classes===
+
 
 +
==core classes==
It is being constructed around a core set of interrelated classes
It is being constructed around a core set of interrelated classes
Line 61: Line 60:
*liqsketch a dynamic sketch built up from various strokes and points
*liqsketch a dynamic sketch built up from various strokes and points
*liqcliprect a physical rectangle within an image with direct drawing routines
*liqcliprect a physical rectangle within an image with direct drawing routines
 +
Beyond the core there is a second layer of classes dealing with structured layout and rendering
Beyond the core there is a second layer of classes dealing with structured layout and rendering
Line 67: Line 67:
*liqgraph a special resolution independent graphics interface which a cell uses
*liqgraph a special resolution independent graphics interface which a cell uses
-
With these classes I will be able to construct the applications started inside liqbase.
+
With these classes I will be able to construct the applications started inside liqbase
-
The classes outlined here existed in some form or other in the old liqbase and I have not yet documented the descendants of the cell class which sit together to form the UI itself.
 
   
   
-
===system class structure===
+
==class structure==
-
The system classes created in liqbase follow the same object pattern and contain the following default standard methods:
+
 
-
<source lang="c">
+
Most classes created in liqbase follow the same object pattern and contain the following default standard methods:
 +
<PRE>
class *class_new()
class *class_new()
{
{
Line 96: Line 96:
// call _release on all members of this class
// call _release on all members of this class
}
}
-
</source>
+
</PRE>
 +
The reference counting is held as a private member inside the instance itself.
-
User classes and instances built from cells do not require this interface.
 
-
 
-
The reference counting is held as a private member inside the instance itself.
 
There is no concept of inheritance at this level, however once you have instances of cell classes (described in detail below) they follow generic inheritance rules and can expand.
There is no concept of inheritance at this level, however once you have instances of cell classes (described in detail below) they follow generic inheritance rules and can expand.
-
===Example cell lifespan===
 
-
A usual cycle goes something like this
 
-
<source lang="c">
+
 +
==Example cell lifespan==
 +
 
 +
A usual cycle goes like this
 +
 
 +
<PRE>
 +
 
void hello_world()
void hello_world()
{
{
Line 127: Line 129:
     liqcell_release(myform);
     liqcell_release(myform);
}
}
-
</source>
+
</PRE>
-
 
+
-
===Cell inheritance===
+
-
 
+
-
The cell class provides a basic unit which everything is built up from. When used in a visual context, it represents a rectangular area on the screen. A cell can also be used as a simple  property holding information intended for its parent. Each cell can hold references to a font, an image and a sketch or even another cell. It can be inherited from other cells which expand its utility and purpose.
+
-
 
+
-
===Dynamic scaling===
+
-
 
+
-
liqbase is designed to operate in a truly resolution independent manner, after designing a widget according to specifications, it does not matter whether it is run on a lower or higher resolution display as the content will render correctly.
+
-
 
+
-
I have taken special care ensuring the font class operates as expected within a dynamic resolution independent environment. At design time, the operator configures a form to certain dimensions (at 225dpi) and configures font sizes and positions relative to this. The fonts make use of extensive dynamic caching to both improve loading speed and to ensure that the correct glyph is displayed at the correct size as required.  The slight drawback with this approach is that at different scales there is some very slight variation in the exact final font size due to integer only glyph widths.
+
-
 
+
-
At runtime, the entire screen is situated within the available boundary and rendered accordingly. A landscape layout will run correctly in portrait mode, however it will be displayed at a reduced size to maintain its aspect ratio.
+
-
 
+
-
===Event handlers===
+
-
 
+
-
You can assign event handlers to any cell in liqbase and have a routine called when the event is required.
+
-
New events can be dynamically created and utilized as required.
+
-
 
+
-
====Linking handler to cell====
+
-
 
+
-
<source lang="c">
+
-
*vcell_handleradd(self,    "paint",  world_paint);
+
-
</source>
+
-
 
+
-
====Handler Code====
+
-
 
+
-
<source lang="c">
+
-
static int world_paint(vcell *self, vcellpainteventargs *args)
+
-
{
+
-
//liqapp_log("painting...");
+
-
// tell the subsystem this event has been handled (returning 0 will cause the chain to continue)
+
-
return 1;
+
-
}
+
-
</source>
+
-
 
+
-
====Using a handler====
+
-
 
+
-
<source lang="c">
+
-
vcell_handlerrun(self,"paint",&paintargs);
+
-
</source>
+
-
 
+
-
[[Category:Software]]
+
-
[[Category:Documentation]]
+

Learn more about Contributing to the wiki.


Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!


Cancel | Editing help (opens in new window)

Templates used on this page:

Retrieved from "https://wiki.maemo.org/Liqbase_library_overview"