View Single Post
Posts: 1,203 | Thanked: 3,027 times | Joined on Dec 2010
#104
Ok, next batch done. Once the next file is built I think it will be 32/62.

I'm hitting the following error at the moment. First thought was to add gdk.h to includes. FAIL. Second try was to add gdkx.h or whatever the X11 specific header is called. FAIL. This file has been a right PITA.

hildon-color-chooser.c:1361:55: error: dereferencing pointer to incomplete type ‘GdkVisual {aka struct _GdkVisual}’
color->pixel = ((color->red >> (16 - system_visual->red_prec)) << system_visual->red_shift) |
Been trying to catch up on IRC comments as well. My thoughts on RAM usage is that my initial idea wasn't specific to the N900 but looking at freeing the software stack so that it could be used on other, more recent devices, like fmg's Allwinner tablet. Up until recently is was all built on top of a stripped down Mer stack with the intention of one day trying to make use of libhybris should we have a wayland based wm. Hildon UI on Fairphone2? Oneplus? GalaxyTab? Chromebook?

I know it's not very scientific/correct but its all I've got at the moment: The object files for the current 31 files under libhildon/hildon/ total 3.8MB. ALL the object files in the same directory of my Cordia fork total 3.5MB. In terms of CSS themes, yes they probably require more processing but if the low res jpg/png based theme can be replaced with CSS, the images don't need to be loaded. If it is ported to a higher resolution device we don't have to rely on the same texture files. At the moment though, this isn't implemented.
 

The Following 8 Users Say Thank You to Android_808 For This Useful Post: