Active Topics
-
How many of you still use N900 as main phone? (592)
to Community by bradvesp - 1 day, 7 hrs ago -
Which is the best N95? What software modifications could be made to it? (3)
to General by Kalatti - 1 day, 17 hrs ago -
Installing CSSU Stable in year 2024 (2)
to Maemo 5 / Fremantle by teroyk - 2 days ago -
Porting apps to Leste (34)
to Maemo 7 / Leste by Arno_11 - 2 days, 10 hrs ago -
[ANNOUNCE] CSSU-thumb thread - stable Thumb2 on N900 (2,266)
to Maemo 5 / Fremantle by pali - 4 days, 2 hrs ago -
Firefox with Leste (7)
to Maemo 7 / Leste by teroyk - 4 days, 6 hrs ago - more...
 |
antezz |
2010-05-21
, 19:52
|
|
Posts: 172 |
Thanked: 160 times |
Joined on Jan 2010
@ Sweden
|
#31
|
It's empty in /usr/local/bin
|
|
2010-05-21
, 20:04
|
|
Posts: 124 |
Thanked: 213 times |
Joined on Dec 2009
|
#32
|
I apologize antezz (and everyone else).
I was using a nonstandard location (/usr/local/bin) to install my symlinks. I should be using /usr/bin
I have made the minor change required and uploaded a new .deb
Please uninstall mmjre, go back to the first post, and reinstall with this [hopefully!] final version.
I was using a nonstandard location (/usr/local/bin) to install my symlinks. I should be using /usr/bin
I have made the minor change required and uploaded a new .deb
Please uninstall mmjre, go back to the first post, and reinstall with this [hopefully!] final version.
| The Following 3 Users Say Thank You to Dak For This Useful Post: | ||
 |
|
2010-05-21
, 21:23
|
|
Posts: 4,274 |
Thanked: 5,358 times |
Joined on Sep 2007
@ Looking at y'all and sighing
|
#33
|
Originally Posted by Dak
Sure.
There's also some mime registration stuff in there that doesn't seem to work yet...it doesn't hurt anything else thoughThe idea was that you could just click on a jarfile in your file browser (or create a desktop shortcut to it) and it would automatically launch jarexec for you. I'm sure it's something simple I've overlooked...maybe somebody can cast some fresh eyes over it and tell me my mistake
Firstly, you include a XML for the JAR mimetype. This is what you usually do, yes, but not when it's already defined by another file: /usr/share/mime/packages/freedesktop.xml
Your desktop file is installed in the wrong place; it should be installed in /usr/share/applications/hildon/
And its contents replaced with:
Code:
[Desktop Entry] Encoding=UTF-8 Version=1.0 Type=Application Name=Jarfile NoDisplay=true Exec=/usr/local/bin/javalauncher X-Osso-Service=javalauncher X-Osso-Type=application/x-executable MimeType=application/x-jar;
Code:
D-BUS Service] Name=javalauncher Exec=/usr/local/bin/javalauncher
How it works in Maemo is that a "mime_open" method will be called on the application specified in the .service field (the X-Osso-Service field in the desktop file tells Maemo which service file to look for) with an array of file names passed to a handler handling this method in the app; the libosso library has functions that will register your program and allow to add a handler for these messages.
I've attached a "quick-'n'-dirty" launcher written in Vala as its syntax is closer to Java than C's and it doesn't have the overhead of Python. It needs compiling and installation as /usr/local/bin/javalauncher
Last edited by qwerty12; 2010-05-21 at 21:28.
 |
|
2010-05-21
, 22:59
|
|
Posts: 147 |
Thanked: 53 times |
Joined on Dec 2009
@ West London, UK
|
#34
|
Originally Posted by torshind
Wonko's hildon SWT port does work out-of-the-box. It did for me, anyway, when trying out my existing SWT applications. Point me in the direction of anything you'd like testing.
There's libswt-hildon but I don't know if it's complete.
I have a blog entry about it.
|
|
2010-05-22
, 04:16
|
|
Posts: 124 |
Thanked: 213 times |
Joined on Dec 2009
|
#35
|
OK...thanks to qwerty I reckon I'm getting somewhere
[See attached .tar.gz]
I converted the Vala into a little C prog (main.c)
I included the service and desktop files
Now, when I click on a jarfile in FileManager it no longer asks me what I wish to use to open it with....it just does nothing.
So I ran the javalauncher prog on the cmd line, and I could see that it successfully called osso_initialize and osso_mime_set_cb, but I have no way of knowing if the prog is being successfully called by FileManager/mime_open.
What is the best way to debug this mechanism?
[See attached .tar.gz]
I converted the Vala into a little C prog (main.c)
I included the service and desktop files
Now, when I click on a jarfile in FileManager it no longer asks me what I wish to use to open it with....it just does nothing.
So I ran the javalauncher prog on the cmd line, and I could see that it successfully called osso_initialize and osso_mime_set_cb, but I have no way of knowing if the prog is being successfully called by FileManager/mime_open.
What is the best way to debug this mechanism?
|
|
2010-05-22
, 05:51
|
|
Posts: 4,274 |
Thanked: 5,358 times |
Joined on Sep 2007
@ Looking at y'all and sighing
|
#36
|
Originally Posted by Dak
*Cries* - Vala converts to C before building
OK...thanks to qwerty I reckon I'm getting somewhere
[See attached .tar.gz]
I converted the Vala into a little C prog (main.c)
(Although, blame any stupidities of mine such as checking the suffix on my cold...)
Originally Posted by Dak
In your service file, you call the service "org.maemo.javalauncher", which is fine but you've still left it as "javalauncher" in the desktop file. When a name is not given a prefix, it automatically assumes "com.nokia.javalauncher". So you've got a desktop file looking for com.nokia.javalauncher but a service file only defining org.maemo.javalauncher.
I converted the Vala into a little C prog (main.c)
I included the service and desktop files
Now, when I click on a jarfile in FileManager it no longer asks me what I wish to use to open it with....it just does nothing.
So I ran the javalauncher prog on the cmd line, and I could see that it successfully called osso_initialize and osso_mime_set_cb, but I have no way of knowing if the prog is being successfully called by FileManager/mime_open.
What is the best way to debug this mechanism?
This is also true for osso_initialize(), so the call to that must also be amended.
I verified your program actually starts by doing a - wait for it - "while true; do ps | grep java | grep -v grep; done"
from the terminal. However,
PHP Code:
dbus_connection_flush((DBusConnection*)osso_get_dbus_connection(ctx));
dbus_connection_read_write((DBusConnection*)osso_get_dbus_connection(ctx), 0);
So I went back to what works for me: A GMainLoop. libosso will automatically call dbus_connection_setup_with_g_main () on both its connections for you, and mime_cb was actually getting called this time. And, according to ltrace, it's sure not waking up as much
Now, the name given will be a URI. javac doesn't understand so I used the g_filename_from_uri function from GLib. Whilst it's tempting to just remove the "file://" prefix, the browser, when "opening a file", will give you a real URI that must be escaped
When doing this, it all worked
PHP Code:
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
#include <libosso.h>
//#include "osso-internal.h"
static char* jarexec_cmd = "/usr/local/bin/jarexec";
static void mime_cb(GMainLoop *loop, int argc, gchar** argv)
{
int cmdlen = strlen(jarexec_cmd) + 1;
int arglen = 0;
char* cmd = NULL;
int i = 0;
for (i=0; i<argc; i++)
{
if (argv[i] != NULL)
{
gchar *cmd_filename = NULL;
arglen = strlen(argv[i]);
cmd = malloc(cmdlen + arglen + 1);
memset(cmd, 0x00, cmdlen + arglen + 1);
printf(cmd, "%s %s\n", jarexec_cmd, argv[i]);
fflush(stdout);
cmd_filename = g_filename_from_uri (argv[i], NULL, NULL);
sprintf(cmd, "%s %s", jarexec_cmd, cmd_filename);
g_free(cmd_filename);
//osso_system_note_infoprint () -- would be nice, IMHO
system(cmd);
free (cmd);
}
}
g_main_loop_quit (loop);
}
int main(int argc, char** argv)
{
osso_context_t* ctx = osso_initialize("org.maemo.javalauncher","0.1", 0, NULL);
GMainLoop *loop = g_main_loop_new (NULL, FALSE);
if (ctx != NULL && loop != NULL)
{
printf("javalauncher osso_initialize succeeded\n");
printf("\n");
fflush(stdout);
if (osso_mime_set_cb(ctx, mime_cb, loop) == OSSO_OK)
{
printf("javalauncher osso_mime_set_cb succeeded\n");
fflush(stdout);
/* while (jar_running)
{
dbus_connection_flush((DBusConnection*)osso_get_dbus_connection(ctx));
dbus_connection_read_write((DBusConnection*)osso_get_dbus_connection(ctx), 0);
sleep(1);
} */
g_main_loop_run (loop);
}
else
{
printf("javalauncher osso_mime_set_cb failed\n");
fflush(stdout);
}
}
else
{
printf("javalauncher osso_initialize failed\n");
fflush(stdout);
}
return (EXIT_SUCCESS);
}
| The Following 3 Users Say Thank You to qwerty12 For This Useful Post: | ||
 |
|
2010-05-22
, 06:23
|
|
Posts: 518 |
Thanked: 334 times |
Joined on Mar 2010
@ italy
|
#37
|
i'm trying to launch one app... it says have a look for evalation period... is it eval?! just to change... microemu is better... iced tea too
|
|
2010-05-22
, 06:24
|
|
Posts: 518 |
Thanked: 334 times |
Joined on Mar 2010
@ italy
|
#38
|
90 days eval,,, you gotta write that its eval!? dont be clown... write in the trhead that its evaluation!!
|
|
2010-05-22
, 06:28
|
|
Posts: 4,274 |
Thanked: 5,358 times |
Joined on Sep 2007
@ Looking at y'all and sighing
|
#39
|
Originally Posted by santiago
90 days eval,,, you gotta write that its eval!? dont be clown... write in the trhead that its evaluation!!
Originally Posted by Dak
Must beat the limit
[...]and a convenience script called "jarexec" (which also refreshes the license every time you run it, so your JRE will never expire)
| The Following 6 Users Say Thank You to qwerty12 For This Useful Post: | ||
|
|
2010-05-22
, 06:41
|
|
Posts: 518 |
Thanked: 334 times |
Joined on Mar 2010
@ italy
|
#40
|
everydays not sometimes... its really orrible that write... check for evaluatio time.... can u remove it?!