maemo.org - Talk - Tear 0.3 - Simple WebKit browser, now with Dashboard

Page 12 of 26

« First

< Prev

Next >

Last »

Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)

- Applications (https://talk.maemo.org/forumdisplay.php?f=41)

- - Tear 0.3 - Simple WebKit browser, now with Dashboard (https://talk.maemo.org/showthread.php?t=26475)

skatebiker

2009-03-15 21:49

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Does it support cookies ? When I save a cookie in javascript it does not show when the page is next loaded and this does work in MicroB.
Fuurthermore it works excellent.

Bundyo

2009-03-15 21:59

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

I'm not sure :) WebKitGtk didn't support cookies at the time, so pronvit came up with a hack to force CURL to handle them. I didn't had any problems with their support.

myp2p

2009-03-16 08:26

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

.

I find that tear fails
to display Chinese characters correctly for some Chinese pages. For
example, on www.baidu.com (gb2312), some Chinese characters show up as
squares. but work fine on www.solidot.org(utf-8)

ps:how to build libwebkit for 770? I want to build cross compiler with no-VFP support.

.

skatebiker

2009-03-16 08:53

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

I tested Tear more extensively and came to the following conclusions:

- Excellent rendering

- No cookies (at least they don't work)
- Dashboard is hard to read: when a site is on one of the nine fields, it is in gray on a lighter gray background (low contrast).
On the left of the dashboard there are three hardly readaboe texts which appear as 'History' and 'Bookmarks'
- Bookmarking is not possible . There is no clear user interface item to add a link to the 'bookmarks' tab on the dashboard.
- History items can only be opened from the dashboard when they are web links. Links to local pages (i.e. file://) do not open from the history tab of the dashboars.

So I feel tears when such an excellent rendering and fast javascript browser lacks such basic user interface thins.
I hope these issues will be fixed soon as forthermore it is good work !

meizirkki

2009-03-16 09:10

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

there is a star in the tear ui, click it, and you will have a bookmark.

Cookies are working for me (at least itT remembers my account, that is based on cookies, isn't it?)

Bundyo

2009-03-16 15:33

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

I plan to build 770 compatible WebKit version soon (if the dependencies can be solved :))

Jaffa

2009-03-16 16:04

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Quote:

Originally Posted by Bundyo (Post 271657)

At least Tear is currently impossible to get into extras/extras-devel. Unless Vala is currently supported with custom vapis and some changes to system includes.

I'll try and have a look at updating the mud recipe for Vala tonight. Worse case for the custom VAPIs could be a noddy little package which is in your Build-Depends which updates /usr/share/vala/vapi/.

Quote:

Another thing is even though I'm not sure Tear is stable enough for mass usage, people are willing to try it and are afraid of extras-devel,

There've been discussions (on -developers?) about having a third level in addition to extras-devel and extras(-stable). This should mitigate this concern.

Quote:

and it seems the already existing qole repo is good for easy installation.

Well, the pages following where people have difficulty installing it show otherwise ;-)

Quote:

The only lib in it that exists in extras-devel is libidn11 and its taken from there.

I'm sure Jeremiah will help get the other libs in as well.

Everyone should be just plain worried about software in use on their tablets which is not in Extras. As we've seen with pronvit's webkit-eal, developers can start on something interesting and wander off; without any source to rebuild from.

There are also advantages to developers, of course, diablo's Extras repo was seeded with the chinook sources - and it's looking like the same will happen with fremantle.

Quote:

Extras is out of the question yet.

Incomplete is not the same as dangerous, though.

myp2p

2009-03-16 16:06

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Quote:

Originally Posted by Bundyo (Post 272010)

I plan to build 770 compatible WebKit version soon (if the dependencies can be solved :))

great! tear will save all 770.

tso	2009-03-16 16:47

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Quote:

Originally Posted by Jaffa (Post 272025)

Everyone should be just plain worried about software in use on their tablets which is not in Extras. As we've seen with pronvit's webkit-eal, developers can start on something interesting and wander off; without any source to rebuild from.

he opened up a garage project before then, and basically warned everyone it could happen as he had a bad habit of doing so...

Jaffa

2009-03-16 16:51

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Quote:

Originally Posted by tso (Post 272055)

he opened up a garage project before then, and basically warned everyone it could happen as he had a bad habit of doing so...

Except a) the garage project didn't have the up-to-date source for the last released deb (the one including kinetic scrolling) and b) warning about it doesn't help solve it ;-)

tso	2009-03-16 16:59

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

kinetic scrolling was mostly a case of activation, iirc. that is, its in the webkit code, one just need to access it.

as for solving it, well it would be something of a setback. but its not like he did it all on his own. from what i understood it was based on some older, nokia initiated work...

qwerty12

2009-03-16 17:07

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Quote:

Originally Posted by tso (Post 272058)

kinetic scrolling was mostly a case of activation, iirc. that is, its in the webkit code, one just need to access it.

No, hns said he needed to reimplement kinetic scrolling in his version

skatebiker

2009-03-16 17:12

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Quote:

Originally Posted by meizirkki (Post 272004)

there is a star in the tear ui, click it, and you will have a bookmark.

Cookies are working for me (at least itT remembers my account, that is based on cookies, isn't it?)

I tried this the star turned yellow and then I opened the dashboard and its bookmark tab , but no bookmarks appeared.
Am I having the wrong version (0.3) ?

Bundyo

2009-03-16 17:14

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Quote:

Originally Posted by Jaffa (Post 272025)

Well, there's one little thing though - I'm not using automake, but WAF instead. And Tear needs Vala 0.5.7 to build. WebKit probably won't be a problem if the build system is NOT scratchbox 1.

Bundyo

2009-03-16 17:15

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Quote:

Originally Posted by myp2p (Post 272028)

great! tear will save all 770.

There's the possibility that the memory won't be enough :)

qwerty12

2009-03-16 17:17

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Quote:

Originally Posted by Bundyo (Post 272067)

WebKit probably won't be a problem if the build system is NOT scratchbox 1.

Well, you're in for a disappointment then :/

(Search "scratchbox" in https://garage.maemo.org/builder/dia...ild.log.OK.txt)

Bundyo

2009-03-16 17:22

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Quote:

Originally Posted by qwerty12 (Post 272069)

Well, you're in for a disappointment then :/

(Search "scratchbox" in https://garage.maemo.org/builder/dia...ild.log.OK.txt)

I kinda suspected it :)

Jaffa

2009-03-16 17:47

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Quote:

Originally Posted by Bundyo (Post 272067)

Well, there's one little thing though - I'm not using automake, but WAF instead.

Build-Depends: python, ...?

Quote:

And Tear needs Vala 0.5.7 to build.

This is what I'll be updating the package to.

Quote:

WebKit probably won't be a problem if the build system is NOT scratchbox 1.

What's broken with Scratchbox 1 and WebKit's build system?

Bundyo

2009-03-16 19:54

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Quote:

Originally Posted by Jaffa (Post 272080)

Build-Depends: python, ...?

The python for waf is not a problem but since I don't know how the autobuilder works - will it detect and resolve my dependencies or I need to do it somehow?

Quote:

Originally Posted by Jaffa (Post 272080)

What's broken with Scratchbox 1 and WebKit's build system?

Everything? :D No, seriously - latest libwebkit requires bison 2.2. The one in Scratchbox is 2.0 and it didn't look upgradeable - I had to install it with brute force (read by copying the directories where needed). I think there was something else too, but the main problem was that the after a successful build some CSS classes magically didn't apply. I tried many times, rebuilt libwebkit countless times to no avail. After I almost gave up, came pronvit with a working build. Then I knew something was wrong. Then after I lost 3 days to somehow install Scratchbox 2 on openSUSE (finally with chroot), the first build was working. Without any changes. My guess is that it requires GCC4, though that isn't mentioned anywhere. So that's it - it just doesn't work like it should when built in Scratchbox 1. Try if you want to.

qwerty12

2009-03-16 20:14

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Quote:

Originally Posted by Bundyo (Post 272115)

The python for waf is not a problem but since I don't know how the autobuilder works - will it detect and resolve my dependencies or I need to do it somehow?

Everything? :D No, seriously - latest libwebkit requires bison 2.2. The one in Scratchbox is 2.0 and it didn't look upgradeable - I had to install it with brute force (read by copying the directories where needed). I think there was something else too, but the main problem was that the after a successful build some CSS classes magically didn't apply. I tried many times, rebuilt libwebkit countless times to no avail. After I almost gave up, came pronvit with a working build. Then I knew something was wrong. Then after I lost 3 days to somehow install Scratchbox 2 on openSUSE (finally with chroot), the first build was working. Without any changes. My guess is that it requires GCC4, though that isn't mentioned anywhere. So that's it - it just doesn't work like it should when built in Scratchbox 1. Try if you want to.

Excuse me for not responding to the quotes properly. (Typing from a tablet).

You specify the dependencies needed to build by filling in the "Build-Depends:" field in debian/control.

To override scratchbox using an internal version of an tool, you do;

"export SBOX_REDIRECT_IGNORE=/usr/bin/tool && export PATH=/usr/bin:$PATH"

Jaffa

2009-03-16 20:36

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Following on from qwerty12's point, it shouldn't be impossible (or even that hard, once we figure it out) to get libwebkit, valac, your custom VAPIs etc. through the auto-builder.

Hell, the clean-slate approach it takes means the VAPIs can be just cp'ed to /usr/share/vala/vapi at the start of debian/control if we need to ;-)

Anyway, I'm in the process of updating vala now. Will let you know when it's in extras-devel.

Bundyo

2009-03-16 20:36

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Quote:

Originally Posted by qwerty12 (Post 272128)

ETo override scratchbox using an internal version of an tool, you do;

"export SBOX_REDIRECT_IGNORE=/usr/bin/tool && export PATH=/usr/bin:$PATH"

Okay, forgive me my autobuilder ignorance, but I can't read this. :) What will that give me?

Jaffa

2009-03-16 20:51

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Quote:

Originally Posted by Bundyo (Post 272139)

Okay, forgive me my autobuilder ignorance, but I can't read this. :) What will that give me?

It sets a variable, SBOX_REDIRECT_IGNORE for /usr/bin/tool, and then ensures that /usr/bin is at the head of your PATH.

Scratchbox uses host tools as much as possible (for speed), and also stuff within the devkit. However, the above allows you to override it.

So, for example, we could have a newer version of bison in Extras - your Build-Depends will specify the exact version - and override the version shipped as standard.

qwerty12

2009-03-16 20:58

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Quote:

Originally Posted by Bundyo (Post 272139)

Okay, forgive me my autobuilder ignorance, but I can't read this. :) What will that give me?

Lol, it's an general sbox1 trick :)

If you have a scratchbox 1 installed with python2.5 from extras, try this to see what I mean:

Code:

which python

Output:
/scratchbox/bin/...

Code:

python

Output:
Python 2.3...

From that output we see, that when you run "python", scratchbox intercepts it and runs its internal 2.3 version of python. We want the Maemo version of python 2.5 to be loaded so if I do:

Code:

export SBOX_REDIRECT_IGNORE=/usr/bin/python ; export PATH=/usr/bin:$PATH

and then do, this time:

Code:

which python

Output:
/usr/bin/python

Code:

python

Output:
Python 2.5

As we can see from that output (faked, but the outcome should be the same ;)), scratchbox now uses the version of a tool that you installed and does not use its internal version.

My idea is to implement the above in your debian/rules so scratchbox uses the newer version of bison instead of its internal version.

Now after typing that, I'm not even sure if scratchbox provides bison :o, but the trick is good to know all the same ;) :)

Bundyo

2009-03-16 20:58

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Can we have newer GCC too? It won't work with 3.x.

Jaffa

2009-03-16 21:13

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Quote:

Originally Posted by Bundyo (Post 272152)

Can we have newer GCC too? It won't work with 3.x.

I don't see why not. Trickier, of course, as we need the GCC to be able to cross-compile; which is bound to be more fiddly.

Bundyo

2009-03-16 21:22

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Okay then, when the time comes :) Thanks for the help.

Jaffa

2009-03-16 22:12

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Quote:

Originally Posted by Jaffa (Post 272138)

Anyway, I'm in the process of updating vala now. Will let you know when it's in extras-devel.

Vala is now in Extras-Devel, along with the simplest Vala Hildon program (a noddy "hello world" sample) demonstrating that packages written in Vala can also be built using the auto-builder.

More details here: http://www.internettablettalk.com/fo...172#post272172

Bundyo

2009-03-18 09:19

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Status report:
http://bugs.bundyo.org/viewissue.php?issue_no=19
http://bugs.bundyo.org/viewissue.php?issue_no=22
http://bugs.bundyo.org/viewissue.php?issue_no=23

terrencegf

2009-03-18 14:07

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

I'm not sure if I should post this here or try to use the bug reporter...

Tear doesn't work correctly with Privoxy. When I go to http://p.p/ (the easy way to view privoxy configuration), I get a dns resolve error. When I go to http://config.privoxy.org/ (the hard way to view privoxy configuration), I get "Privoxy is not being used".

Since privoxy is configured on the connection in maemo, I'm surprised that Tear managed to avoid using it.

Bundyo

2009-03-18 14:22

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

I'm not setting specific proxy in WebKitGtk (and I'm not sure I can), but add it to the tracker.

Matan

2009-03-18 14:26

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

The proxy settings in the connection manager is merely a setting that applications need to explicitly support - that is to read proxy settings using libconic and behave accordingly.

Bundyo

2009-03-18 14:59

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Yes, I can read them, no problem.

Bundyo

2009-03-18 22:56

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Another preview, since it is important for mime-type handling before I concentrate on Options Manager and the various reported tear/webkit fixes. Also some other features, check the first post.

Word of caution: some DB upgrade will undergo on first run, so may start a little slower. Please report if you encounter any issues with that.

daperl

2009-03-18 23:22

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Thanks for the update, but what does this mean?

Application manager icon control fields by qwerty12

Is it something I can see?

Bundyo

2009-03-18 23:24

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

This means an icon in app manager ;) Nothing more.

Bundyo

2009-03-18 23:31

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Hmm, why do I have Thanks button on my own posts? :)

Anyway, since noone of you complained from a broken db, I'm assuming that it is working and am going to sleep. :D

heelio

2009-03-18 23:33

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

I am getting an error when I try to delete messages in Gmail using Tear.

Matan

2009-03-18 23:44

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Can you make it a bit more "non-touch-screen friendly"?

Adding shortcuts to the menus is easy, but then I wanted to set Space to scroll one page down as in the default browser, but could not find how to do it. Did you write lines 87-377 of tear.vala? Can you give a few hints on how to read them?

Can you make Tab start from the first visible link, rather than first link of the page?

A longer term goal is a hot key that highlights the visible links and allows selecting any of them by a letter or two. Something like this firefox extension:

https://addons.mozilla.org/en-US/firefox/addon/1341

tso	2009-03-18 23:50

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

also noticed that the internal bookmark menu would truncate multiple bookmarks with the same name, so that only the youngest one can be accessed...

All times are GMT. The time now is 06:58.

Page 12 of 26

Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8