OWB 2.19

New release, here the changelog:

2.19 (10.12.2008)

* Added support for FONTKERNING tooltype to enable font kerning, since it makes text input fields unusable it's still disabled by default.
* Now rounds all font sizes down to integers, makes the results less precise but avoids getting different spaces between the same chars depending on the context.
* Added FONTHINTER tooltype to overwrite the font specific hinter settings configured with TypeManager (0 = don't overwrite, 1 = best available, 2 = best available (light), 3 = always autohinter, 4 = always autohinter (light), 5 = no hinter, default = 3) and changed the defaults of FONTXDPI and FONTYDPI to 96. Now the results with the AmigaOS font engine look very similar to the ones of libfreetype, and if you still don't like it you should have enough options for changing it.


You can find it on OS4Depot, upload section

@samo79

The fonts look great in v2.19.

All I'm missing now is file downloading and tabs, though the latter might be a little impossible. :(

http://wookiechat.amigarevolution.com/pics/owb.png

Am I being thick or does changing the height and width tooltypes for OWB make no difference to the size of the window it opens in?

Great work on the browser though, I am really liking it. Thank you!

@jahc

Quote:I doubt that I can complete the download support this year, since nobody else did it it took me a lot of time working on the static libraries (cairo, xml2, xslt, ...), which were requried to be able to use OWB on AmigaOS 4.0 again and for some AmigaOS 4.1 users who always had problems with the shared objects, and now the font changes as well, instead of beeing able to work on the up- and download implementation

Using tabs instead of multiple windows would be quite easy, but supporting both isn't.

@joerg

Quote:
Do you mean that it would be possible to have e.g. a tooltype to select whether you want all pages as tabs or all pages in separate windows?

Or can there only be one of the two solutions in the code?


Best regards,

Niels

P.S. Personally, If I had to make a binding choice, I would prefer tabs. I can always start another instance of OWB if I really need a separate window.

@nbache

Quote:That would be no problem. The easiest way for tabs in OWB would be like in Chrome, i.e.instead oflike in FireFox, IBrowse, etc.
That way the code for multiple windows and tabs would be nearly identical, like each window currently each tab would still have it's own gadgets and only the states of the shared menu has to be saved and restored when switching between the tabs.

@joerg

Quote:

I vote for TABS

BTW, thanks for you work! Now the fonts are very nice!

@Lecta

IMHO better wait until Joerg can include both solutions

Here no times problems !

@Joerg

For me it is ok to have tabs because i think it is more comfortable

@joerg

Prefer tabs myself but it's hardly a priority.

i take tabs over windows any day.

WOW these updates are coming fast. Downloaded OWB 2.18 on Sunday and was using it as my main web browser since then.

I have been using OWB 2.19 for about half an hour. Very nice.

---
redfox

@redfox

Think about reinstalling a program so frequently under windows... it would crash system after that ;).

@joerg

Quote:
Cool! Pretty please implement tabs when your to do list becomes shorter. :)

What do you think memory usage would be like? The same as multiple windows?

@joerg

You do need to make a GUI prefs for OWB.
The setups are getting bigger and bigger..

@samwel

Or someone could make a Reaction-based Prefs GUI for joerg, so he can integrate it into OWB. The problem is that right now the options are changing so frequently that it'd be a lot of work to keep updating a Prefs GUI all the time, whereas with tooltypes it's not much effort.

@spotUP

Quote:

You thought about rehab?

Rude!

Oh, Tabs!!! Yay!

@jahc

Quote:Less than with multiple windows, but it will only be a very small difference.

@samo79