Forums - All Posts - The Amigans website

Forum Index

Board index » All Posts (joerg)

Bottom

« 1 ... 58 59 60 (61) 62 63 64 ... 85 »

joerg

Re: OWB 2.7

Posted on: 2008/9/3 1:53 #1201

Just can't stay away

@ShInKurO

Quote:

bug in c&p function: if you paste text in ASCII extended with for example ????? from another program you will have this:

It's not really a bug in OWB but a limit of the AmigaOS clipboard, text copied to/from the clipboard by OWB is/has to be UTF-8 encoded, using a 8 bit charset you couldn't for example copy&paste Chinese texts. Since there is no charset stored in the AmigaOS clipboard I can check if it's something else and convert it to UTF-8 before passing it to OWB. I could add a check if it's valid UTF-8 and if not assume it's in the current system default charset, but that wouldn't fix the general problem.

In any case where texts are used without their charsets there are only 2 options which make sense: Limit it to US-ASCII which is the same in all 8 bit charsets supported by AmigaOS4 as well as in UTF-8, i.e. remove everything or replace by '?'s which isn't an US-ASCII char, or use UTF-8.

AFAIK all AmigaOS programs have similar problems, for example if you copy something from a program using the Greek 8 bit charset (ISO-8859-7) and paste it to program using the Cyrillic one (ISO-8859-5) you get wrong chars as well. To fix such problems either the charset has to be added, which may be possible in the clipboard, or use UTF-8, which is the only solution in other cases like file names where a charset can't be added.

Topic | Forum

joerg

Re: OWB 2.7

Posted on: 2008/9/1 20:50 #1202

Just can't stay away

Quote:

- Added WINDOWLEFT, WINDOWTOP, WINDOWWIDTH and WINDOWHEIGHT tooltypes
for configuring the position and size of the window.

WINDOWWIDTH and WINDOWHEIGHT are broken in 2.7, will be fixed in the next update.

Topic | Forum

joerg

Re: OWB 2.6

Posted on: 2008/8/31 19:21 #1203

Just can't stay away

@orgin

Quote:

You could set up a new page using http://snack.orgin.se

Should have everything you need except the bug tracker, but you could use either the forums or content management for that until you find one.

Exactly the same as with any other bugtracker or CMS is missing: Time to install and configure it and maintain it

Would be nice if a project like OpenAmiga.org could provide a bugtracker for OWB, although OWB doesn't really fit it's at least open source, and some people think a browser has to be included in an OS.

Topic | Forum

joerg

Re: OWB 2.7

Posted on: 2008/8/31 18:51 #1204

Just can't stay away

@COBRA

Quote:

1. It takes relatively long for OWB to start (I measured it to be about 8 seconds or so from double-clicking of the OWB icon to the Window opening). If the startup time cannot be shortened, maybe opening the window sooner, or adding some startup progress bar or similar would be good as the user would at least be aware that something is actually happening.

I got a splash screen image from Mason for that some months ago already, but the problem is that OWB does open the window nearly immediately, something else could only be displayed by OWB less than 1/10 second before the window is opened. It simply takes that long to load and relocate the about 20 MB OWB executable (incl. shared objects) and before everything is loaded no code of it is executed.

If you have OWB or SOBJS: on a FFS partition using a SFS partition instead should be faster, if both are on a SFS partition already defragmenting the partition can help.

The only way to display something while OWB is loading would be a small executable for example displaying a splash screen and using something like "wbrun OWB", but that's something others could implement as well since it doesn't need any changes in OWB.

Topic | Forum

joerg

Re: OWB 2.7

Posted on: 2008/8/31 18:20 #1205

Just can't stay away

@pjs

Quote:

As near as I can tell, the new OWB seems to hang about 1/6th
of the way through the progress bar if you provide it with any
CLI paramaters... at that point, all I can do is close the
window... there is nothing on the serial port that indicates
a crash, per se.

OWB doesn't display HTTP, name server, time out, etc. errors. If your provider has a proxy you can use it in OWB by setting the http_proxy or ALL_PROXY (if you want to use it for ftp, etc. as well) environment variable (setenv SAVE http_proxy "http://proxy.foo.bar:3128") and get such errors displayed by the proxy.

Quote:

Besides window size parameters that used to work on 2.6, even
just providing a URL causes this to happen, like:

OWB www.google.com

Of course, this pretty well kills my script for transferring
pages from IBrowse, when needed... :-/

Any ideas?

Window size parameters were only supported by OWB Blastoise (1.x), and it added "http://" if no protocol was specified for the URL. The only argument supported by OWB Doduo is a complete URL, you have to use "OWB http://www.google.com/".

Topic | Forum

joerg

Re: OWB 2.6

Posted on: 2008/8/30 3:18 #1206

Just can't stay away

@nbache

Quote:

I think I may have spent too little time RTFM'ing .

There isn't much FM to read, actually nothing at all but just the readme, and some comments from me here

Since "just" the AmigaOS4 OWB port itself is a lot of work and I can't do additional things as well it would be nice if others could help. Helping with the code would be very much appreciated as well of course, but there are missing parts much more people could help with, for example:
- Writing a manual for the AmigaOS4 port of OWB. Installing it with all required shared objects, the optional webcore fonts, unicode font and AISS (most of that is here already), what the supported tooltypes do, the keyboard shortcuts OWB supports, ...
- Creating a better homepage for the AmigaOS4 port of OWB. No matter what you do, it can't be worse than my current one

- A bugtracker for AmigaOS4 specific bugs and feature requests. I probably have everything required on my homepage (PHP, SQL, etc.) but if someone else could host and maintain it it would be even better.

Edited by joerg on 2008/8/30 4:19:52

Topic | Forum

joerg

OWB 2.7

Posted on: 2008/8/30 2:37 #1207

Just can't stay away

OWB 2.7 (30.8.2008)
- Fixed copying text.
- Optimized scrolling.
- Added text zoom and and redraw to the menu.
- Added reload gadget.
- Fixed wrong underlining offsets.
- Implemented PlatformScreen for AmigaOS4.
- Fixed wrong window height.
- Added WINDOWLEFT, WINDOWTOP, WINDOWWIDTH and WINDOWHEIGHT tooltypes
for configuring the position and size of the window. WINDOWWIDTH and
WINDOWHEIGHT are only used if WIDTH/HEIGHT aren't used.
- Fixed checkbox markers.
- Updated to SVN revision 460.

Topic | Forum

joerg

Re: OWB 2.6

Posted on: 2008/8/28 19:00 #1208

Just can't stay away

@xeron

Quote:

BTW, why does it default to 80,72? Modern monitors should have a native mode that matches their physical dimensions, meaning pixels should be more-or-less square.

If you set them to the correct values (72, 72) you'll probably see why ...

Check the OWB 1.x thread starting from http://www.amigans.net/modules/newbb/ ... t_id=20620#forumpost20620 for more information.

Topic | Forum

joerg

Re: OWB 2.6

Posted on: 2008/8/28 8:47 #1209

Just can't stay away

@xeron

Quote:

Also, when i log in to amigans.net, no matter how many times i click "Remember me", a tick never appears in the box!

Fixed.

Topic | Forum

joerg

Re: OWB 2.6

Posted on: 2008/8/28 0:14 #1210

Just can't stay away

@nbache

Quote:

Hmm, just found another little odd thing:

I put WIDTH=1152 and HEIGHT=870 in my tooltypes, running on a 1280?1024 WB. But the window opens with the dimensions of 1179?1016. And since my WB title bar is 26 pixels high (and OWB quite reasonably opens the window below the title bar, i.e. from 0,26), this actually means the bottom 18 pixels are outside the screen.

I wonder if there are some calculations that need revising?

While fixing the wrong screen size reported by OWB yesterday I found a bug in the window size calculation as well and fixed it

The toolbar height was wrongly added to the height of the webview.

Quote:

BTW, if at some point it would be an easy matter for you to implement, it could be quite nice to also have control over the TOP and LEFT positioning in the tooltypes.

That's very easy, will be included in the next version.
OTOH it will be strange to set the TOP/LEFT position of the whole window, but with WIDTH/HEIGHT the size of the webview. I probably should add WINDOWWIDTH/WINDOWHEIGHT tooltypes as well to be able to configure the window size instead of configuring the webview size.

Topic | Forum

joerg

Re: OWB 2.6

Posted on: 2008/8/27 23:59 #1211

Just can't stay away

@blmara

Quote:

Thanks for this great program. Will OWB be AmiUpdate'able some day?

It's intentionally disabled currently since that would update all 1.x versions, when OWB 2.x has at least the most important additional AmigaOS4 features the OWB Blastoise (1.x) port had which are still missing in the OWB Doduo Port (bookmarks, downloads, ARexx port, etc.) I'll add it again.

Another option would be to use a different name in the AmiUpdate support for 2.x to make it possible to keep both versions installed, maybe I'll do that in the next update, but that would only update the 2nd to next one with AmiUpdate and I hope to have everything implemented in OWB Doduo by then.

Topic | Forum

joerg

Re: OWB 2.6

Posted on: 2008/8/27 18:28 #1212

Just can't stay away

@xeron

Quote:

The only thing is, the font spacing for proportional fonts is all messed up here. I can take a screengrab if you need it?

Only after changing it to 72 DPI? If yes that's the reason why 80 is used as default for XDPI.
I didn't manage to get it working correctly yet (exactely as in the libfreetype OWB font implementation, or for example like in the OS4 TypeManager). The libfreetype OWB font implementation is several times slower, using the AmigaOS4 font implementation instead is one of the largest speedups in the AmigaOS4 port of OWB.

Quote:

Also, when i log in to amigans.net, no matter how many times i click "Remember me", a tick never appears in the box!

It's not displayed but it should work. It's not a bug in the OS4 port and happens on Linux as well. If I'd try to fix all bugs in OWB/WebKit myself I'd have to stop working on the OS4 parts for several months ...

Topic | Forum

joerg

Re: NetSurf2.0(dev) Bugs Thread

Posted on: 2008/8/26 22:21 #1213

Just can't stay away

@Chris

Quote:

btw, is a static version of your libopenssl port available anywhere?

No idea, it doesn't seem to be on Edgar's homepage. The only library OWB uses I ported myself was libSDL_gxf.so. Like most other shared objects OWB uses libssl is IIRC the version from Edgar Schwan, some others like the ICU ones were ported by Andrea Palmat?. I just rebuilt them as shared objects, most without changes, some with very small changes like using DEVS: instead of S: for the ca-bundle in libcurl. IIRC I dind't change anything in the libssl sources, but I'm not 100% sure. I can send you the sources, or rebuild them as static link libraries, if you want to make sure you are using the same code as in the shared object used by OWB.

Topic | Forum

joerg

Re: OWB 2.6

Posted on: 2008/8/26 21:50 #1214

Just can't stay away

@TMTisFree

Quote:

For example, if I request an iconify button, an ARexx port (AWeb commands), and an editable context menu (right click scriptable ?-la AWeb), how much do you evaluate the work?

Since it's not using a window.class window but an intuition one adding iconify is not just setting a flag and handing the the (un)iconfiy events but has to be done manually, but it's no problem and implementing it should take less than an hour.
For the rest, everything not just AmigaOS related in general, I have no idea how much work it would be since I only understand a very tiny part of the about 150 MB OWB sources and how OWB/WebKit works, what it can do and what not, etc. The configurable context menu and the ARexx port would be just AmigaOS related code, but they have to use OWB/WebKit parts to do something useful, and for example I have no idea if OWB can do everything the AWeb ARexx commands support already or if I wouldn't only have to implement the AmigaOS parts but new features in OWB/WebKit as well.

Topic | Forum

joerg

Re: OWB 2.6

Posted on: 2008/8/26 21:27 #1215

Just can't stay away

@DBAlex

Quote:

Will the 68K version ever get an update??

Updating the old OWB Blastoise version wouldn't make much sense IMHO. Like in the AmigaOS4 ports the AmigaOS related code of OWB Blastoise can't be used for an OWB Doduo port, I've reimplemented all AmigaOS parts in the OS4 port of Doduo and would have to do the same for an AmigaOS 3.9 port. Like in the OWB Blastoise ports it would be a completely new and independent port as well, the AmigaOS 3.9 and AmigaOS4 parts of the OWB Blastoise ports didn't have a single line of common code.

Additionally an AmigaOS 3.9 port is much more work than an AmigaOS4 port, the last version of the AmigaOS 3.x/m68k GCC is 3.4.0 which is too old and workarounds have to be added in the OWB code to be able to compile it at all, it's the same for the libraries used by OWB (SDL, curl, openssl, xml2, xslt, ..., even the ixemul C library) and workarounds for the bugs and missing features in these ancient versions have to be added, using outline fonts on AmigaOS 3.x without the new OS4 functions is more work, for the GUI even more workarounds for new OS4 features which didn't exist in AmigaOS 3.9 yet, and for old bugs which are fixed in OS4, have to be added, etc.

At least as long as the AmigaOS4 port of OWB Doduo isn't completed I wont start a 2nd port, one is more than enough work. When I did the AmigaOS 3.9/m68k port of OWB Blastoise there was not much I could have done in the AmigaOS4 port since I had to wait until OWB Doduo was ready for the beta release and I got access to the sources.

Quote:

It *is* slow though so maybe not worth it...

It shouldn't be too slow on a current x86 PC using UAE with JIT enabled, it's just useless since you can use much better browsers on the UAE host OS instead.
Of course it's too slow on a real Amiga, a 68060 CPU is way too slow for any modern browser.

Topic | Forum

joerg

Re: OWB 2.6

Posted on: 2008/8/26 20:51 #1216

Just can't stay away

@TMTisFree

Quote:

How I have to donate to have an iconify button & menu?

A Paypal donation button is on my homepage, there should be a "notes" field in the PayPal form where you can add comments. Feature requests sent that way will of course get a higher priory and implemented before the ones on forums or sent my email

Topic | Forum

joerg

Re: OWB 2.6

Posted on: 2008/8/26 20:37 #1217

Just can't stay away

@nbache

Quote:

BTW, while PageUp/Down work fine and are very useful, is there any chance of getting Home and End (and/or AUISG equivalents like Ctrl+Up/Down) to work as well?

It's a bit problematic since OWB uses all these keys already. And it does use HOME/END even outside of input fields, it's just very strange what it does ... For example on amigans.net it scrolls horizontally with HOME/END, on amigaworld.net it scrolls vertically to the top/bottom instead, and in both cases only after clicking on an empty part of the page.

Maybe I can add a check if an input field is active when a key is pressed and if not use something else which makes more sense

Currently you can use the mouse wheel(s) instead, with <shift> pressed it scrolls pages and with <ctrl> to the top/bottom. With <alt> pressed additionally the 2 mouse wheels are swapped, most mice have only one wheel but that way you can scroll horizontally as well.

Topic | Forum

joerg

Re: NetSurf2.0(dev) Bugs Thread

Posted on: 2008/8/26 20:14 #1218

Just can't stay away

@Chris

Quote:

however, what i really need is a function that tells me which charset is the best match for my UTF-8 string.

No, you don't, at least not for the final version.

You have to convert everything to 32 bit, or at least 16 bit, Unicode instead, which is no problem, and use the bullet API to get the glyphs and draw them manually which isn't easy. The new OS4 diskfont.liibrary functions make it a little bit easier, but the general problem is still the same as it was in AmigaOS 2.x: To display Unicode text you have to render the individual glyphs yourself, there is no function in AmigaOS which can render Unicode strings using an outline font to a rastport.

Converting everything to 8 bit charsets, (re)opening the font with the correct 8 bit charset and using IGraphics->Text() may work for a lot of languages, but at the latest with languages like Chinese or Japanese using charsets with much more than 256 glyphs it can't work. Since the GTK NetSurf can display for example http://www.yahoo.co.jp/ the AmigaOS4 port should as well.

Topic | Forum

joerg

Re: OWB 2.6

Posted on: 2008/8/26 19:38 #1219

Just can't stay away

@nbache

Quote:

Ah, okay. So I assume it is known by the SandLabs folks, then?

I've fixed it and it's reviewed and committed in the OWB SVN now.

Topic | Forum

joerg

Re: NetSurf2.0(dev) Bugs Thread

Posted on: 2008/8/26 1:11 #1220

Just can't stay away

@ShInKurO

Quote:

for UTF you could use the uni.library and unisupp, you find them on Aminet :)

I didn't find uni.library, but according to the readme UniSupport.lha is just as redundant on OS4 as the codesets.library he is using already is. For UTF and other charsets conversations the iconv functions of the OS4 C library can be used, and if you don't need UTF you can use diskfont.library for converting between unicode and 8 bit charsets as well (IDiskfont->ObtainCharsetInfo() DFCS_MAPTABLE).

Topic | Forum

Top

« 1 ... 58 59 60 (61) 62 63 64 ... 85 »