Re: WebKit engine for default browser
 

In order to conserve internal memory space (10 MB) , I tried the following:

mkdir /media/mmc2/usr_lib
cp /usr/lib/libwebkit-1.0.so.1.0.0 /media/mmc2/usr_lib
remove /usr/lib/libwebkit-1.0.so.1.0.0
ln -s /media/mmc2/usr_lib/libwebkit-1.0.so.1.0.0 libwebkit-1.0.so.1.0.0
the symlink exists (I tested)

But the browser did not start properly in webkit mode.
Why ? For the OS a symlink is the same as a 'real' file ?

Re: WebKit engine for default browser
 

I think the problem is linked to the fact that your mmc2 is FAT formatted : it doesn't support file attributes ...

Re: WebKit engine for default browser
 

Attributes shouldn't matter, a shared lib does not need to have the executable bit set (and if you look in /lib you'll see that they don't).

Re: WebKit engine for default browser
 

something dawned on me about that full screen osk. there is one other place where one of the same issues (specifically, that about not including previous input into its text area) shows up, and thats in the terminal.

if one have part of a command written, and tries to use the full screen osk, its text area will show up blank.

this is a behavior thats been around as far back as the 770, iirc. this makes me wonder about how the full screen osk interfaces with the rest of the setup, as the normal osk seems to have no such problems.

Re: WebKit engine for default browser
 

This is why c is a stupid language.

Re: WebKit engine for default browser
 

I figured out the reason for the wrong text in the full screen keyboard. It's because you have to bind a function to the GtkIMContext retrieve-surrounding signal and call set_surrounding() from there with the content of the textarea. I have this halfway working, except that webkit crashes when the content of the full screen keyboard is committed...

But something else: Do you even bring up the full screen osk for HTML forms in bundyo's libwebkit? I couldn't get the full screen osk at all with the d-pad center button until i figured out how to trigger that (calling gtk_im_context_filter_keypress() in the key release function).

Re: WebKit engine for default browser
 

Good news: I think I fixed both the stop button crashes in webkit-eal and most of the on-screen keyboard issues with libwebkit, including copy-paste and editing existing text with the full screen keyboard.

New webkit-eal package is here, see the changes file or garage svn for details.

New libwebkit package is here, that diff is against webkit revision 41128 with bundyo's patch applied. (This also disables most advanced HTML5 features which are enabled in bundyo's build).

Please let me know how this is working for you! Also, let me know what features you're missing for the next major release. I guess it'll be mostly more and better gconf backed options.

Re: WebKit engine for default browser
 

finger tap all the way ;)

and ill give the new version a spin! :D

Re: WebKit engine for default browser
 

just tested a bit, and the text is correctly imported on opening the osk with existing text in a box.

but it still closes the keyboard on a enter event, rather then producing a new line...

Re: WebKit engine for default browser
 

seems the new webkit plays havoc with the tear dashboard. specifically, the tabs on the left side shows the text as horizontal, not vertical.