Brian_7 | # 71 | 2012-02-04, 23:30 | Report

At least with the last CSSU update, i am able to zoom in using ctrl+shift+s.

soleil | # 72 | 2012-02-05, 00:47 | Report

I got opera.sh working and all other tests was successful.
I has the grey bar issue on my N9 .
Opera mini can display vietnamese font. How can I change the font on Opera Mini ?
I'm trying to get other jar file working

santiago | # 73 | 2012-02-05, 10:57 | Report

i think we missed some features like

copy/paste option from the OS<->JVM
the JSR implementation.. this is too important for a valid JVM

but u made a great START with Phoneme i hope we can enjoy jsr support. thx for your WORK!

aRTee | # 74 | 2012-02-05, 21:44 | Report

Could anyone give the one from this page a try:
http://www.vbl.ch/getdoc/02801f6e-93...anleitung.aspx

I'm getting some weird errors, for files I don't even see inside the jar, perhaps I'm not looking in the right place/way..?
BTW I took the touchscreen (3rd) version.

DavyP | # 75 | 2012-02-05, 22:50 | Report

I installed Qt SDK 1.2 that got released a couple of days ago.
I changed QApplication to MApplication, and linked against the
meegotouchcore library, but the grey bar is still there in the
N9 emulator (i.e. I see no difference with the Maemo build running on N9).

Davy

DavyP | # 76 | 2012-02-05, 23:00 | Report

I am working on a build that replaces the current font subsystem
which uses a builtin monospace bitmap font (with limited
character set) to render text.

My latest 'unstable' snapshot now uses the default font on Maemo
and supports more text styles and sizes. The text rendering looks
much better, but rendering speed has become slower. I figured
as much on the emulator, and [DarkGUNMAN] confirmed the
performance hit on a real device too. However, should you care
trying the latest snapshot yourself, you can find them over here:

http://davy.preuveneers.be/phoneme/p...n900/unstable/

The most recent build is on top.

Davy

DavyP | # 77 | 2012-02-05, 23:12 | Report

I just gave one of the midlets at the above url a try, and I too get
errors about missing png images and text files that don't exist in
the jar file.

Davy

DavyP | # 78 | 2012-02-05, 23:54 | Report

The original phoneME implementation does not come with copy
paste support. Copying text in a midlet and pasting it to another
Maemo application is technically pretty hard (because you cannot
select text in a textfield or textbox). The other way around might
be possible by trapping the Ctrl+V key combination, looking which
text has been copied from elsewhere, and replaying this text as if
you would have entered the text manually.

I am well aware JSR support is limited. There are a bunch of
JSRs out there that would be nice to have. Unfortunately, there
aren't that many JSR implementations available as open source.
The only ones that Sun/Oracle have made available are those
that they 'own'. Have a look over here:

https://svn.java.net/svn/phoneme~svn/components/

Also, some of the JSRs you find there don't compile well or need
detailed knowledge about the underlying platform so you can port
these JSRs to a new device. This ain't easy, especially with just
the emulator at hand. I am aware of projects like microemu and
MIDPath. However, they have the luxury of being able to exploit
all the features of a full Java SE environment. Many of their
components would not work on a Java ME environment.

Right now, I just have JSR 172 and JSR 75 (with some minor
issues). Based on my experiences with porting for Windows
Mobile and Android, I think JSR 179 (Location API) and audio
playback with JSR 135 are doable given enough time and effort.
However, I am not sure if the Madde emulator can handle all
these features so that I would be able to test this. Things like 3D
support with JSR 184 are out of the question.

Davy

santiago | # 79 | 2012-02-06, 00:59 | Report

you're right... I have seen here in the talk tha someone has done something with the Openlapi and jsr 179.. To get working gps location antenna, by the way, the only possibility to get "partial" jsr support then can be using the jsr179? will be good having sound working i think the ctrl + v / ctrl + x / ctrl + c can be good for this powerfull jvm becouse some applets have a different input method and during the emulation you have no way to paste/insert caracters in the text field Thx for your detailed answer and for the support with phoneme!

edit: i attached a sshot about the font and window of phoneme, i'm using your last versione the one with font changes.. but i see it in this way i mean big font size respetc to the layout

Attached Images

 

---

Last edited by santiago; 2012-02-06 at 01:29.

DavyP | # 80 | 2012-02-06, 11:15 | Report

The text does not seem to be well-aligned in your screenshot. This is what I have:

http://davy.preuveneers.be/phoneme/p...roemu-demo.jpg

http://davy.preuveneers.be/phoneme/p...emo/opera2.jpg

About audio support: I cannot seem to produce any sound with the emulator, not even with the built-in 'play-sound' application or the Qt4 qmusicplayer example application. I am guessing QSound in Qt4 is not properly supported for audio playback :-(

/home/developer $ play-sound testmp3.mp3
socket(): Address family not supported by protocol
ca_context_open: Not available

About GPS: Yes, JSR 179 would provide the unifying API to get location information. Any location provider could be plugged into JSR 179, but GPS is quite likely the most important one.

I am aware of OpenLAPI. That is the implementation I used to support JSR 179 on my Android port. The only thing I need to figure out is how to get the GPS data natively on the N900 and how to activate and deactivate GPS programmatically, etc.

Davy