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

i think extra for maemo is almost empty, search the forum for "where the f*** can i find xxx" and make yourself an opinion, if you can without thinking of being Maemo Community Council chair, wathever it means.
i bought an n810 because i thought it was open source and then i find out that i can't have a kernel upgrade because of closed parts of hardware drivers, and then i'm obliged to stick with maemo, not being a programmer.
so nokia is telling me that i can have a full opensource device with rx51. i'm not gonna take it, and i don't like that you pontificate about a 3rd repository against a man who's stealing time to his family to try to add a decent web-browser to an operating system without being paid. i'm a user, not you, and i decide if something is user hostile. 3rd parts repository would be user-hostile if i could hope to find useful apps in extras as i find in a brand-new installed diablo. i think that debian-maemo transition is taking more time to me than the windows-linux transition, wich was some year ago.
sorry bundyo, i'll not post so bad anymore

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

Been keeping tabs on this thread and just installed Tear (using Qole's Repo) a few min ago; I'm impressed. Very...

Some sites seem to have an overflow issue with content. Will have to wait and see if this is just a bug in the engine or the sites. So I won't log that yet.

Will chime in on the issue in terms of logging into sites that require user/pass as many of these get prefilled on my N800 and I cannot seem to unfill them to login.

Tear seems to not be a resource hog whatsoever. THANK YOU!!!

That loading bar under the address bar is nice and all, but it looks like a graphical artifact. Personally, I like it when the loading status is in the address bar, it looks cleaner that way.

The placement of the + and reload buttons should be inversed. Or move refresh to a combined function with the green Go. There's no real need to have Go and Refresh IMO. They do the same thing. When one is on a site it should show refresh, when one is typing or has just placed the cursor into the address field then it should be a Go Button (and be a Stop button while a page is loading while I'm thinking about it. Aka, context changing button).

The dropdown in the address filed is nice in that it contains the title field of the sites visited. Wonder what kind of font and style things can be done there to break up the samness of things between the title and addresses (make address a smaller font, bold and italiacs to the title, etc.). I'd also say that having the ability to star/mark as fav from that screen would also be beneficial.

Dashboard is a great idea, but there's too much chrome. Make the 9 boxes larger by about 3-5px w/h and default the address bar to be a google (user configurable???) search. Doing that for the search means that you can move the MRU/BkMks/History tabs to the top, where they would be better seen and more readily used.

Feature Request: Not sure if its possible without one coding this directly, but a function to have Tear (or any other browser) replace the microB as the default browser would be great. Either something in the control panel (guessing that's an applet) or a setting in Tear (and any other browser).

Having only come in at this point, I have to say that I'm really impressed at the progress of this. I'll have to keep at things though since I'm using the IT as a work folder these days.

If GoogleGears/HTML5 local storage is added to tear, and some tolerance settings for the inertial scrolling were added, this would really rock as a nice competitor to Fennec/Firefox.

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

being worked on, tear just got dbus support, and that means that dbus-switchboard could be used to control what browser thats being used.

stay tuned ;)

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

Alright, so let's start by setting aside the personal attacks. They're neither useful nor productive. Thanks. :)

First, Extras is not empty. Many new packages are added to Extras every week and there are many more existing packages receiving frequent updates. Just take a look at the autobuilder mailing list.

Second, the bit about people not being able to find anything is exactly why I want to see as many packages as possible put into Extras, so users don't have to hunt around for software and random 3rd party repositories disappearing from this reality doesn't cause the software users rely on to disappear as well.

I'm not sure how this relates to Extras and maemo.org, but what closed drivers? Open source WiFi drivers are available and you're certainly not stuck on an old kernel (more importantly, if you're not able to switch to something other than Maemo—Mer and Deblet are pretty easy, really—why do you want a new kernel?).


Alright, fair enough, it's your prerogative as a consumer to decide where you want to spend your money, but, again, I'm not sure how this relates to Extras.

None of the people in this discussion are getting paid to do what they do. We're all volunteers who are trying to make things better for users like you (even if those users don't seem to understand the how or the why of it).

Actually, I, too, am a user. I own a use several tablets day-to-day, which is one of the selfish reasons why I'd like to see the Maemo infrastructure improved.

Of course you wont find many applications on a brand-new Diablo install, as Extras doesn't ship enabled! I'd ask you to do a quick test for me: flash Diablo, open the Application Manager, refresh the application catalog, and tell me how many applications there are available. Then follow these instructions to enable Extras, refresh the application catalog and tell me how many applications there are? A lot more, yes? Well, those all came from Extras.

Alternatively, you can browse around the repository a bit directly then get back to me. . . .

Anyway, this thread has been derailed enough, please contact me directly or open a new thread if you have more questions.

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

i didn't have any question

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

I want to do the same, but I'm not aware of any GTK+ control that can do that directly. And as everything in Tear that is not that important and requires more coding, this too is left for later :)

Go and refresh don't do the same thing. Refresh reloads the current page, while Go goes to whatever you wrote. Anyway your context idea is good.

I'm not yet so proficient in GTK+ to do this (though I was considering it. I prefer when the title is highlighted and the domain below.

The address bar already searches in Google. However if there are some symbols in it, it is detected as URL. That's why there is another one. Plus on a 225 dpi screen you wont see 3-5 px size increase :) Also I plan to add more buttons on the right side and make them all user configurable - like assigning a bookmark folder to one. Plus if I make the tabs on top, how will I show off that I made them with inline SVG with vertically rotated text? :)

Currently the svn version can be opened from the command line and the second time it is not starting a new program, but a new window. Plus you can open a url with a standard dbus method_call.

There should be local storage support in this WebKit version, though I didn't test if it is working properly.

Just as a reminder - could you people also post these bug reports on the project bug tracker, I just enabled guest reports. Here.

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

That's an interesting note about the search. I would not have guessed that search is enabled from the address bar in that view. Can the text there be changed from "about:blank" to "Search or Type Web Address?"

Inline SVG is indeed cool; yet my mind always looks at form following function and experience. Very cool that you have that tech there, me begins to get ideas amore.

I'm a former web developer and graphic artist, I can see pixels just about everywhere on just about every device. Its honestly the most annoying thing I encounter in terms of being in front of a computer all the time. Though since I did mention it, are the sizes of those boxes percentage based or hard coded?

EDIT: Previously mentioned bug now posted.

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

Hello qole! How are you? I'd to help out with packaging tear. :^)

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

I'll help out if I can, you guys can reach me at jeremiah@maemo.org and on #maemo.

I also want to say that those of us who work on maemo and on maemo.org are serious about helping with packaging and getting your software into the repos on maemo. We are improving quality assurance for packages with some new tools. We are going to expand the repos so that there is a more volatile repo you can use to upload to if you just want some place to put a package that might not be ready for extras or even extras-devel. We expect more packages in the repos for fremantle and are serious about being prepared for the influx.

In short, we want to make the maemo repos the go-to place for community packages when a user wants to find a new web browser or game. To do that, I hope to demonstrate that maemo is working hard to help developers as much as we can.

I hope to be in touch with you about tear and packing it for extras.

Thanks and warm regards,

Jeremiah

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

i like the dashboard tabs as they are, on the side. i use the tablet with one hand a lot and i can't reach all the way across the top of the screen with my left thumb while holding the tablet in my left hand. i would like the bookmarks tab on top, though.