![]() |
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Quote:
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Quote:
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Quote:
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Minor UI suggestion: make text inside each button in dashboard vertical centered.
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Quote:
http://www.internettablettalk.com/fo...&postcount=580 |
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
step by step guide for tear 0.3 on 2008He/770, http://www.internettablettalk.com/fo...645#post274645. Thanks again Bundyo and all other contributors, to make my dusty 770 alive, again.
bun |
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Okay, meanwhile you should correct that guide, because there are two new builds out:
http://bundyo.org/maemo/webkit/libwe...37-2_armel.deb http://bundyo.org/maemo/webkit/libwe...a770_armel.deb with the fixed capitalization from hns' and the n8x0 one has vfp enabled (e.g. faster). Btw, bun, are you sure the Tear package from garage is working on 770? P.S. Just checked, it works, that saves me two build at least for Tear. |
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Quote:
bun |
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Um, for Tear it seems no :) For libwebkit - yes. :)
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
there is a noticable speedup, worth it imo.
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
The new version of the n8x0 libwebkit is in my repo. If you want the 770 version, you must get it from one of the other mirrors. If you have my repo enabled and you install the 770 version, the Application Manager will tell you that there is an upgrade to libwebkit for you. Ignore it.
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Got bongo's bookmark app working with 'python /home/user/.tear/bookmarks/tear-bookmarks.py' in personal menu. Exported old bookmarks as a file and bookmarked it's location in Tear too. Use microb to manage bookmarks but set DBus-switchboard to launch html/htm files with Tear. Some files, attachments ..., don't save right and popups are not blocked and sometimes mistaken for files to be saved and a basic search field is needed. But the speed & GUI functionality, drag scroll zooms speed & opening new windows not full-screen plus overall feel etc., is so great I use it %90 of the time so a big thank you for your efforts and those who help you.
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Fist of all, thank bundyo for the great work u done...ok im trying to install tear- bookmark, its asking me for python2.5 hidondesktop. I tried apt-get it said Couldn't find package python2.5hidondesktop, so can someone put here please ?
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Its in Diablo extras-devel if I remember correctly.
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
It's in regular extras, too. Direct link to deb: http://repository.maemo.org/extras/p....2-2_armel.deb You might have to install http://repository.maemo.org/extras/p....2-2_armel.deb first, though. Also note that the application manager might not want to isntall these, you might have to dpkg -i them.
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Still no word on why the bookmarks dont show up in the same order in the lower right menu as they do in the plugin?
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Quote:
WOW too much headache to install just tear bookmark,,i'm newbie i followed everything u posted above it said incomparable app package. i need easy installing. u gonna kill me to say that, but that's why i love window os one click and u have the apppliccation. |
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Hmmm windows..one click and you have the app...By chance have you installed vista yet? LOL
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Actually, I always thought installing something in Extras was fairly much "one-click".
What is this "Incompatible Application Package" error that people keep getting? Does it mean that it is for a different version of the OS (eg Chinook instead of Diablo)? EDIT: By the way, Bundyo, Tear is really really coming along nicely now. It is really feeling polished. It works well in alternate environments, too. I think you've outstripped the other Webkit implementations (Midori, Arora, etc) now. My number one enhancement request is cookies. |
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Ive installed and uninstalled and reinstalled tear and the bookmarks a couple of times and have never had an error running the latest diablo.
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Quote:
remember, if one try to install a package via a downloaded deb, app manager will not attempt to look up dependencies... what we are looking at is a multi-faceted problem. 1. throwing everything into extras-devel results in less eyes for testing as people stay away because they risk updating something that works with something that do not, and thats important to them. as there is no way to say, in app manager, that this is a app that one do not want to upgrade from extras-devel, while another is, one get to issue 2. 2. because of issue 1, and people being lazy bastards that dont want to take the time to apply for access to extras-devel (or wathever), we have non-repo debs floating around of alpha/beta grade software that people want to try out. but because the managment have in their eternal wisdom decided that its best to have everything on extras(-devel), especially with source code, they have made the manual install of debs via app manager near worthless, by having it not check and take care of dependencies. 3. app manager giving errors that have nothing to do with the underlying cause of the error, resulting in confused newbies making confusing posts on forums... sure, the intention of the policy may be good, but right now someone needs to slap app manager silly and give people a bit more info, and a lot more fine grained control. and no, having to dive into apt-get config files do not help, if so one could just scrap app manager fully and point everyone to apt-get and dpkg... |
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Ive never understood, since I got my first tablet (have had all 3) why app manager doesnt check for dependencies on manual installed .debs.
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
its to make more people use repos (and by extension, extras), especially in combo with uploading the source so that even if the original dev ups and leaves (like we had with webkit-eal) the source is still there for others to pick up and continue with.
sure, its a noble intent. but as they say, the road to hell is paved with good intentions. and in this case, it seems to turn into some kind of support hell all to often... |
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
The tablets have been my only experience with linux, and Im no dumbass when it comes to computers, but Im convinced that alot of peop,e in the linux community feel the need to make things harder than they need to be.
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
The main advantage of Tear above bootup speed is it's great scroll and overall performance due to it's superb responsiveness. If in time as it gets heavier and slow in interaction then it loses it's edge and raison d'être. In that case a second 'lite' version might be apt but hopefully we won't come to that.
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
In my opinion its already damn near perfect, for myself, the only issues I have are login issues on a couple sites I frequent. Other than that, all I would as for is an ad blocker...but given the speed it operates at even on ad heavy sites this isnt necessary, just a want...cause I couldnt give a flying **** at a rolling doughnut about damned acai berries! LOL
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
thing is, the deb system and repos work, when there is a large pool of people handling the creation of debs and there is a similar pool of ready source code to made debs from.
on the tablets, this is not equally true, and so people come up with ad hoc solutions and beta software that they want to get people to test before putting it into the general software pool. basically its a problem of fine grained control. if you open your tablet to extra-devel, you get the whole deal, warts and all. you simply cant say that your only interested in the devel version of tear or some other interesting but not "must work" important. or you can, but that means having to dig into some config files that have no friendly ui... |
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Quote:
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
OK... let me try to clear up some of the confusion here...
First off, the "Incompatible application package" usually stems from one problem: the section field of the package. Packages that the user normally wants to install, and packages that the application manager shows you are in some user/* section. Libraries, and packages that you really don't need to install by themselves, things just depend on them, are not in a user/* section, so the application manager throws the very uninformative "Incompatible applicaiton package" error. [edit]Looks like Bundyo also explained this in the post above... I just took too long to type this :p Second, installing applications on the tablets IS a "one-click process" if that application is in a repository. You've probably noticed this when installing other application: just click, wait, and you've got an application. That's more than I can say for ANY windows program. (Usually, run the installer, click Next, check that you agree, click next, verify install location, click next, choose where you want shortcuts, click next, wait for install, click next, choose to see readme or run the application, and click finish.) I would hardly call this "one-click". The problem on debian arises when you try to install a package you downloaded as a deb. In this case, the dependencies will NOT automatically be filled (for package safety reasons, I believe... not sure if this is configurable anywhere...) Generally, though, applications are in repositories, and dpkg will throw an error if there are missing dependencies that you just need to apt-get install. Finally, all these problems can be avoided with the tearbookmarks package with the help of some advice I've been trying to avoid giving: enable extras-devel. If you do this, the package will show up in your applications list. However, beware! Do NOT upgrade anything it says is upgradeable, or install anything else. After you install the bookmark plugin, DELETE extras-devel. It's really only meant for developers, and unstable/not-ready-to-be-released packages, and some crazy stuff can happen if you keep it enabled. Having said all this, I'm only holding off putting the bookmark plugin in extras for two reasons: one, it's incomplete; two, I'd like to merge it with the bookmark manager; three, I'm waiting for tear to be in extras. In order to be complete, the bookmark manager has to support folders. I'm working on this code, but having a bit of trouble with it... stay tuned! I still need to work with Bongo a bit on implementing some of his code, and getting a package with his bookmark manager and my plugin together. And, of course, this package is useless without tear, so there's no point in having it in extras if tear isn't there. It would only confuse people. Qole: Could you maybe stick the tasknav plugin in your repository? That should clear up some of these issues, without having to put it in extras. If I'm wrong or oversimplifying anything here, please feel free to correct me! Learning is an ongoing process :) |
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Have any details been released about what browser will be with fremantle? If its something other than just microb, they will be hard pressed to beat tear!
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Also, Qole, was wondering if you were going to take that 770 version of tear out of your repo so it isnt showing in updates since I already have the N8x0 version of preview 6 installed.
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Its not the 770 version anymore, but newer, with fixed capitalization and compiled with optimizations. :)
P.S. If you're talking about Tear - no differences between the two versions. |
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Quote:
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Awesome, I didnt see anybody post that there was a newer version than preview 6.
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Quote:
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Like i have said...as it stands now, once the few issues I have with tear have been fixed I wont be using microb at all! I think this is one of the best developed projects for the tablets!
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Quote:
bun |
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
I cant get The One's command to launch the bookmark manager to work in personal menu.
|
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Quote:
Make sure there are no bracketing quotes 'xyz' as in my previous post, space after python and check your folder path to see if tear-bookmarks.py is there: /home/user/.tear/bookmarks/tear-bookmarks.py Or if path's OK, just copy/paste the below into the top 2 fields: In box "Name of the menu entry": Tear-bookmarks In "command to execute": python /home/user/bookmarks/tear-bookmarks.py |
Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
Quote:
Is this the result of my using a hosts file, some inherent ad-blocking in tear, or what? http://i248.photobucket.com/albums/g...g?t=1238118503 |
| All times are GMT. The time now is 06:58. |
vBulletin® Version 3.8.8