View previous topic :: View next topic |
Author |
Message |
Ranger
Joined: 12 Dec 2006 Posts: 6030
|
Posted: Tue Mar 20, 2007 3:27 pm Post subject: |
|
|
I just checked CMS dev snapshot and can confirm atlas loading errors on k750i.
@Kruch,
Do you have a current list of TB parameters usable for CMS ?
@Radim,
Could you attach here smoother font set ?
|
|
Back to top |
|
 |
guest
Joined: 08 Oct 2006 Posts: 5035
|
Posted: Tue Mar 20, 2007 4:18 pm Post subject: |
|
|
Ranger> I think it doesn't make any sense to post here modified font because Kruch will change the structure of font bitmap so my font image will no longer be applicable.
-rst-
|
|
Back to top |
|
 |
Ranger
Joined: 12 Dec 2006 Posts: 6030
|
Posted: Tue Mar 20, 2007 4:36 pm Post subject: |
|
|
guest wrote: |
Ranger> I think it doesn't make any sense to post here modified font because Kruch will change the structure of font bitmap so my font image will no longer be applicable.
-rst- |
... in current form. But can be useful to build prototype.
From my point of view, everyone designing every CMS resource doesn't have sense.
|
|
Back to top |
|
 |
kruch Site Admin
Joined: 02 Jul 2006 Posts: 5676
|
Posted: Wed Mar 21, 2007 12:52 am Post subject: |
|
|
It just "feels" the bitmap should be complete 7-bit ascii charset, so be it. The font bitmat layout (rows vs columns) will not matter; I've added two mandatory attributes to <font> - character height and width:
Code: |
<font name="96px" file="96px.png" ch="96" cw="59"/>
|
I've collected there parameters so far (do not have shortcuts for all yet):
- numeric
* coords [according to settings]
* time [hh:mm]
* alt - altitude [m]
* alt-d vertical speed [m/s]
* spd - speed [km/h]
* spd-d - dec/acceleration [m/s]
* azimuth
* azimuth to wpt
* total time [hh:mm]
* distance travelled [km]
* distance to wpt [?]
* average/min/max speed [km/h]
- "graphical"
* provider status
I'll fix the atlas problem on K750i and make an updated snapshot available asap.
Description: |
|
Filesize: |
10.13 KB |
Viewed: |
15119 Time(s) |

|
|
|
Back to top |
|
 |
krzysiekz
Joined: 07 Oct 2006 Posts: 168
|
Posted: Wed Mar 21, 2007 9:45 am Post subject: |
|
|
I've got error when switching maps in atlas. When new part of map of the same layer should be loaded tb shows error "Illegal Agrument java/lang/IllegalArgumentException Current Displayable is an Alert". When changing to another layer in atlas there is no errors.
Nokia 6230i v3.70, tb from cms.zip
forgot: About options in cms - could coordinates be divided to lat&long? So they will be displayed in two rows.
|
|
Back to top |
|
 |
Ranger
Joined: 12 Dec 2006 Posts: 6030
|
Posted: Wed Mar 21, 2007 11:37 am Post subject: |
|
|
What you think about time to wpt parameter (counted from distance to wpt and average or settable speed) ?
Any medium font, ie 36 pts available ?
|
|
Back to top |
|
 |
kruch Site Admin
Joined: 02 Jul 2006 Posts: 5676
|
|
Back to top |
|
 |
kruch Site Admin
Joined: 02 Jul 2006 Posts: 5676
|
Posted: Thu Mar 22, 2007 10:11 am Post subject: |
|
|
I get OutOfMemory error when I try to draw even a single character with bitmap font on K750i; on N6230i it works just fine... how about you? I kind of think there's a bug in K750i regarding 2-color bitmap (with transparent bg) handling...
|
|
Back to top |
|
 |
Ranger
Joined: 12 Dec 2006 Posts: 6030
|
Posted: Thu Mar 22, 2007 3:27 pm Post subject: |
|
|
Couldn"t confirm, I don"t know which font you exactly have in test.
But I can say, that version with not smooth, one row font works on k750i (with adopted to 176x220 layout only).
Do you have version handling multiple row fonts ?
|
|
Back to top |
|
 |
kruch Site Admin
Joined: 02 Jul 2006 Posts: 5676
|
Posted: Fri Mar 23, 2007 4:25 pm Post subject: |
|
|
Multiple-row font does not help. I just cannot get 96px font to work in K750, no matter if chars are organized 1x128 or 8x16. It loads but I get out-of-memory when trying to draw a char region. 36px font is ok.
The fact is that 96px font bitmap represents 700000+ bytes in 8bpp mode, and I think SE phones internaly use 16bpp. It appears that when an image (or its region) is to be drawn, device uncompresses it, and K750 just does not have enough memory for that.
So for the CMS "font", we'll probably have to split one "big" bitmap into several pngs, eg:
font.lc96.numbers.png (0-9)
font.lc96.specials.png (:;. etc)
font.lc96.lowercase.png (a-z)
font.lc96.uppercase.png (A-Z)
or, when taking 8x16 chars ASCII bitmap as a base:
font.lc96.3-4.png (rows 3,4)
font.lc96.5-6.png ..
font.lc96.7-8.png ..
What do you think?
|
|
Back to top |
|
 |
Lakva
Joined: 09 Jan 2007 Posts: 212 Location: N 50,2380 E 12,8760
|
Posted: Fri Mar 23, 2007 4:42 pm Post subject: |
|
|
I think 96px is almost too big...
On many phones this is about 1/3 - 1/2 of display resolution. The phone displays are small, so:
1) if I have a big resolution display - 640x480, i.e. - then single pixel is so small, that I can't see it. And that's why it does not matter, if 96px text is made of 48px font.
2) If display has some ussual resolution - 320x240 i.e. - then I never need charactes bigger than 48px.
I suppose, that 96px font is unnecessarily big and you don't have to solve this.
_________________ The best thing a man can do for themselves is to help to the others.
-I know it sounds strange... but you may try it  |
|
Back to top |
|
 |
Ranger
Joined: 12 Dec 2006 Posts: 6030
|
Posted: Fri Mar 23, 2007 5:10 pm Post subject: |
|
|
I agree with Lakva, for k750i 96px font is a little bit too large, screen width compared to 208px is 15% smaller. So 72px font is enough for k750i, if you can have its smooth version.
But I see another problem, large speed digits drawed from left jumps too much on screen, probably is better to have fixed digit positions. If you could add a leadind space(s) when speed number have not 3 digits (or use leading zero(s), it can be nice.
|
|
Back to top |
|
 |
kruch Site Admin
Joined: 02 Jul 2006 Posts: 5676
|
Posted: Fri Mar 23, 2007 5:37 pm Post subject: |
|
|
Well for example my N6230i handles 96px font ok, and it looks really cool having speed show with so big letters.
240x320 is becoming de facto "standard", and 48px is IMHO not be big enough - its only 15% of screen height...
Look at krzysiekz's 208x208 display, or another proposal - on higher resolutions displays (like 240x320), you will not able to get such proportions with max 48px or so
Description: |
|
Filesize: |
30.81 KB |
Viewed: |
14584 Time(s) |

|
Description: |
|
Filesize: |
5.71 KB |
Viewed: |
14584 Time(s) |

|
|
|
Back to top |
|
 |
Ranger
Joined: 12 Dec 2006 Posts: 6030
|
Posted: Fri Mar 23, 2007 5:47 pm Post subject: |
|
|
Kruch,
For me is absolutely clear, that CMS layouts and fonts should be properly selected for different screen sizes. So my earlier post about sizes is valid for k750i only. Krzysiek design is really nice, I like to have it in my phone
Last edited by Ranger on Fri Mar 23, 2007 5:49 pm; edited 1 time in total |
|
Back to top |
|
 |
kruch Site Admin
Joined: 02 Jul 2006 Posts: 5676
|
Posted: Fri Mar 23, 2007 5:48 pm Post subject: |
|
|
OK OK OK...
Only numbers are important, labels/units/other text could either be drawn with fonts provided by the device, or just small custom bitmap matching numbers size (like that big "km/h" in proposal above).
So - "font" could be just a bitmap with 0-9, and probably '+','-' and '.' chars...
|
|
Back to top |
|
 |
|