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

It blocks some ads and specially page contents within pop-uped winddows for me too.

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

Tear bookmarks do not show up in the launch panel, I can live with it for a moment if it's going to be fixed in the next few builds - is it? Or can it only be fixed manually?
Thanks!

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

am i missing something-downloaded tear bookmarks-i have an icon on the side that when i press it says 'OPEN NEW WINDOW" however i still have the dashboard with spaces marked 1-9 under bookmarks-how do i get the bookmarks into those spaces--history and most used work but not bookmarks-i downloaded the tear bookmarks 2.6.1-

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

See previous page on how to launch tear-bookmarks in Personal Menu.

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

yukop4: When browsing a page you want to bookmark, simply click the greyed-out star to the left of the address bar. The star will turn yellow, signaling that you have bookmarked the page.

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

How do you erase history and clear cache?

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

now im worried. im willing to claim that webkit has become slower then microb on image heavy page!

it seems to hog the cpu for ages, making the interface unresponsive...

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

Not freezing on many images as such as it handles large numbers of small-mid ones but if the images are of large size/resolution and %ed down in 'img src', it does not do too well with N8x0's small memory. Closing apps or a few windows help, as does crashing :)

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

microb or webkit? if webkit, then one should see the same issues with microb on the same page, but im not.

microb seems to spend a whole lot of time post-processing layout, but even large images seems to pop on screen while webkit currently chugs on even small ones...

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

Tear bookmarks works okay in 770, however I had to force-depends the python libs.

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

tear is great, but it's much slower on some pages after the webkit update. i'm worried too.

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

tso, On webkit, microb basically slows down everything short of freezing till it's good and ready number crunching & caching, conforming to Nokia's many standard books' right-on procedures probably, which is why all things considered I prefer Tear as life's too short.

debudebu, I noticed that too & that's why I said in time as it gets heavy, a lite (old) version might be best. One solution: Keep things, bookmarks managers etc., as separate (apps/procedures) as possible and just read in a data file when asked.

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

Can you check if the 770 build is faring better on such pages? And provide an example one.

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

http://www.hardware.no/
norwegian tech news page.

and ill give the 770 build a spin...

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

Just opened it on my 770 and it loaded in about 20-30 secs. Of course flash is totally out there, while on 8x0 it may switch on in some iframes even if it says off, at least until I finish the options manager.

Btw, I'll be out of town for 3 days and no Eee :)

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

I checked, its there, but it still isnt working and ive typed the exact path in

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

Install as much as python repositeries, not python little addon/utility apps necessarily, as possible & select all here, below link, for a start, then check updates in app-manager and see pythonxxxxxxx installables:
http://gronmayer.com/it/

Better yet, see the recommended repos-lists on the Opening-Post of this thread.

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

already have all the gronmayer repos installed. Ill check and see what python stuff can be installed...any ideas, as the bookmark manager runs fine if i type cd bookmarks <enter> then python tear-bookmarks.py <enter> from the command line as i was originally instucted

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

If it runs from the correct working directory then the problem's not python nor the path but probably personal-menu's playiing up & needs reinstalling. Try personal-launcher first maybe.

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

tried personal launcher it and personal menu, when i tap the entry it makes the cpu spike as if something was launching but nothing happens

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

I haven't looked too closely but for libwebkit on extras, specifying bison-2.2 as a Build-Dep and adding this to the rules should work:

SBOX_REDIRECT_IGNORE := /usr/bin/bison
export SBOX_REDIRECT_IGNORE

PATH := /usr/bin:$(PATH)
export PATH

But, as previously said, the autobuilder uses sbox 1...

You may be able to get in touch with X-Fade/Jeremiah and see what they can do for you.

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

Personal Menu's erratic, mine didn't work or show up on desktop for a week. I tried this just now:
Make a test file in leafpad, type a word & save just as testfile (no extension). Copy it to the tear-bookmarks folder. Change leafpad's entry in P-M from simply leafpad to:
leafpad /home/user/bookmarks/testfile

Space after leafpad. If it works your P-M's probably fine and uninstall / reinstall tear & tear-bookmark (losing boookmarks). If not working then a sys/repos/python file's corrupted but leave the tear-bookmarks entry in P-M for a few weeks and give it a try as things update or P-M sobers up.

- To check environmental variables including paths, in X-term type: set
- Also if the leafpad test worked then maybe try making a batch file in tear-bookmarks folder and call that from P-M instead of calling the py file

I bookmaked this for old time's sake:
file:///usr/share/browser/home_page/index.html


Oh what fun. Self acclaimed King Monkey:
http://www.youtube.com/watch?v=DjeL3IUcqfo&fmt=18

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

Actually, you need to be in the directory tear-bookmarks.py is in to launch it, as it requires some other files in that directory and won't look there otherwise. Try this for your personal menu command:
That should work...

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

nope, didnt work. I uninstalled and reinstalled tear and the plugin. and using emelfm2 i went to /home/user/.tear and there is no bookmarks folder, even after i open tear and add a bookmark. when i originally downloaded the bookmark manager package like instructed was i supposed to put it in a different folder or something? Because still, all i have to type at the commandline to open the manager is cd bookmarks then pythin tear-bookmarks.py but there is no bookmark folder in the .tear directory.

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

There is no bookmark folder. All bookmarks are stored in tear.db.

Hmm, seems I'm not reading very thorough ;)

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

Ah, sorry... I thought you had extracted the bookmark manager to .tear/bookmarks. Try this:

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

so, what folder am i accessing then when i run the manager from the command line?

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

Well, since you said you just have to cd bookmarks, I'm assuming it's in /home/user/bookmarks (xterm starts out in /home/user when you open it).

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

Awesome True Journals, worked perfectly!! :)

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

ok...new problem...the command is good, but when i put it in personal menu it didnt open, said executuion failed, the in the settings for that entry i ticked the run in terminal box, then when tapped it opened 2 xterm windows then opened the manager

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

I believe the opening of xterm twice is a problem that Personal Menu always has.

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

oh well...guess i just wont be able able to get it to launch from personal menu then

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

You can, you just get an extra XTerm, which you can close. In fact, I'm glad you asked about it and that TrueJournals had a useful answer, since it's how I now get to Tear Bookmarks Manager :)

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

id rather not use personal menu if its going to pop any windows open besides the program i want

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

If you're running a shell script, maybe try putting 'exec' in front of your command inside the shell script. It should take over the shell scripts process and thus no more shell. And maybe you'll want to redirect stdout and stderr. Should work.

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

For Personal Menu, the following worked for me. I created 2 scripts called hw.sh and top.sh in /home/user.
hw.sh:
top.sh:
I set permisions to 755:

chmod /home/user/hw.sh 755
chmod /home/user/top.sh 755

In Personal Menu, I set 'Command to execute' in one to:

'/usr/bin/osso-xterm /home/user/hw.sh'

and:

'/usr/bin/osso-xterm /home/user/top.sh'

in the other.

I did not select 'Run in terminal' for either.

When I started them from Personal Menu I got one shell each.

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

Dirty page, many ads and cookies.

Times are the best of several retries

Tear:
Loading the page without privoxy (after browser startup): takes 20 seconds to start rendering, 55 seconds to be fully loaded.
Loading the page without privoxy (several reloads): takes 18 seconds to start rendering, 37 seconds to be fully loaded.
Loading the page through privoxy (after browser startup): takes 17 seconds to start rendering, 40 seconds to be fully loaded.
Loading the page through privoxy (several reloads): takes 15 seconds to start rendering, 20 seconds to be fully loaded.

Microb (with flashblock):
Loading the page without privoxy (after browser startup): takes 10 seconds to start rendering, 35 seconds to be fully loaded (and cpu down to 0).
Loading the page without privoxy (several reloads): takes 5 seconds to start rendering, 23 seconds to be fully loaded
Loading the page through privoxy (after browser startup): 15 seconds to start rendering, 25 seconds to be fully loaded.
Loading the page through privoxy (several reloads): takes 6 seconds to start rendering, 13 seconds to be fully loaded.

Main computer:
Firefox 3.1: 15 seconds to be fully loaded (and cpu down to 0).
Firefox 3.1 +adblock: 10 seconds
Firefox 3.1+adblock+noscript: 2 seconds
Konqueror 3.5: 20 seconds

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

interesting then that i got maybe 9 seconds from starting browser to page loaded in microb. still, could be something left over in cache, even tho i tried to clear it before doing the timing.

with webkit i was seeing 2 min+...

and i do not bother with flashblock, i just switch the plugin of. simpler that way...

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

I did all timings after making sure that everything was cached in disk, so network didn't mattered too much.
The very first time I tryed to load the page (so nothing was cached) it took about 1 min 90 seconds in tear (without privoxy), and about 45-60 seconds in microb with privoxy.

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

well i cant see how network should result in a 2 min+ diff in load time.

and the basic page was clearly loaded, but webkit (in both tear and osso-browser) was having a hard time getting those images up there, and in that time making things unresponsive to any kind of input what so ever.