will owb be avaible to use flash on the loong run. youtube and stuf like that. news stastions use it all the time..
For that someone would have to implement a NPAPI flash plugin for AmigaOS 4.x, I can't do everything myself. I didn't implement the plugin support in the AmigaOS 4.x port of OWB yet, but it's no big problem and if someone will implement plugins for AmigaOS 4.x I'll add it.
But for flash movie players like on youtube it would have to be much better than any existing 3rd party flash implementation on any platform, incl. gnash, therefore it's very unlikely that something like that will ever work on anything but Windows, MacOS and Linux/x86 where you can use the plugins from Adobe.
The glyph widths are floats but since rendering has to be done with integer pixel offsets there is no way to fix something like that (at least not without using sub-pixel rendering, and since the the support for it in the OS4 font engine had to be disabled for patent reasons I couldn't implement it myself for the same reason either).
In that case the glyph widths should be rounded to the nearest integer IMHO. I don't know exactly how it is on other systems, but I'm typing this in Firefox on WinXP and the distance between the characters is perfectly even. Also the font appears to be arranged so that the lines making up the characters are exactly 1 pixel wide and are pixel-aligned so that they don't blur.
joerg wrote: I didn't implement the plugin support in the AmigaOS 4.x port of OWB yet, but it's no big problem and if someone will implement plugins for AmigaOS 4.x I'll add it.
Please do this as soon as possible! For sure no-one will be writing plug-ins while there's no plug-in API!
If you add plugin support maybe we can use the IBrowse flash plugin, yes it is not complete and miss a lot of features, but better than nothing at this time
nbache wrote: BTW, is anybody seeing this apart from me? Sometimes (like right now), when I go to Amigaworld.net, the topic list on the main page has all the little icons showing as question mark icons (presumably because they couldn't be loaded?), and when I click on one of the topics, I get a message on a blank page saying:
Quote:
Bad Request
Your browser sent a request that this server could not understand. Size of a request header field exceeds server limit. Cookie: bbtopic_time[27589]=1228609028; bbtopic_time[27528]=1228608249; bbtopic_time[27588]=1228608166; bbtopic_time[27592]=1228608067; bbtopic_time[27322]=1228517567; bbtopic_time[27566]=1228433427; bbtopic_time[27579]=1228433228; [...] bbtopic_time[26766]=1220302685; bbtopic_time[26756]=1 Apache Server at amigaworld.net Port 80
Using IBrowse instead in such a case works normal.
It seems like a problem at the server, but why do OWB and IBrowse behave differently when that problem occurs?
PS: It is not a new problem with 2.18, I have seen it a few times previously.
Best regards,
Niels
It doesn't seem to be only once in a while any more, AW.net has this problem every time I go there the last few days.
Incidentally, is there a guide to checking out OWB and building an OS4 executable?
No. Checking out the sources is no problem, with OWB Doduo most of it even works with the old AmigaOS 4.x port of SVN (with OWB Blastoise it was impossible because the links were on the SVN and the AmigaOS 4.x port of SVN doesn't support links, in OWB Doduo the links are generated), but building it doesn't work.
Quote:
Does it build on OS4 or do you have to cross compile? (i have latest beta SDK).
I'm building the OWB executables on AmigaOS 4.1, but you can't only use AmigaOS 4.1 since OWB uses CMake, and even if there would be an AmigaOS port of CMake it couldn't work since there are perl scripts involved which can't work on AmigaOS (they need things like fork()). I use CMake on Linux for generating the makefiles, generated sources, headers, links, etc., transfer everything to AmigaOS 4.1 and adapt the makefiles, etc. for AmigaOS 4.1 (CMake uses absolute paths like /usr/bin/c++, the include paths have to be changed as well as some defines and compiler options, since I didn't add support for the AmigaOS4 parts to the CMake files some components have to be replaced by the AmigaOS4 ones, etc.).
If you add plugin support maybe we can use the IBrowse flash plugin, yes it is not complete and miss a lot of features, but better than nothing at this time
No problem, I could stop working on the OWB port for a few months and port the gnash plugin to AmigaOS 4.x instead. But what do you want with a plugin without a browser which can use it?
It doesn't seem to be only once in a while any more, AW.net has this problem every time I go there the last few days.
Anybody else at all seeing it?
I didn't have such a problem yet, but you should be able to fix it by deleting cookieCollection.txt, or at least removing the aw.net bbtopic_time#? ones from it. Unlike OWB Blastoise OWB Doduo doesn't have complete support for cookies yet. I enabled the libcurl cookie support as replacement to get persistent cookies in the AmigaOS 4.x port of OWB Doduo at all, but it doesn't work without problems that way.
Would it be possible for you to email me the sources in a form that i can type "make" on my a1 and get an exe out the other end?
No: 8.RAM Disk:> filesize CS:OWB_Doduo all 51,157 files, 2,142,997,470 bytes, 4,221,968 blocks (That's just OWB itself, without the required libraries.)
The largest parts are the object files, the sources are included twice (SVN), there are some executables of old versions, etc. If I remove them, as well as all soures and include a diff for a specific SVN revision of OWB instead, and pack everything with 7-Zip the size wouldn't be a problem, but there would still be other problems: - It will only work once, as soon as I update to a newer SVN revision the makefiles don't work any longer and you need new versions of the generated makefiles, sources, headers, links, etc. - It includes soft links but there is no AmigaOS archiver which works with links, even the ancient AmigaOS 4.x tar port doesn't work correctly with links. - Since CMake uses absolute paths for the generated files you have to use the same paths (volume name, or an assign) as I do.
joerg wrote: @nbache I didn't have such a problem yet, but you should be able to fix it by deleting cookieCollection.txt, or at least removing the aw.net bbtopic_time#? ones from it.
Thanks, yes, that fixed it.
Quote:
Unlike OWB Blastoise OWB Doduo doesn't have complete support for cookies yet. I enabled the libcurl cookie support as replacement to get persistent cookies in the AmigaOS 4.x port of OWB Doduo at all, but it doesn't work without problems that way.
Understood. Usually it seems to be working okay, though, but at least now I know where to find the "hammer" if needed in the future.
You don't necessarily need the sources of OWB to help out joerg with its development, there are many things that could be made by other developers (such as a download manager program, etc.) which could be developed separately and then be sent to joerg so he can integrate it into OWB. But whatever you decide to do for it, make sure you discuss with joerg in advance (e.g. to agree on some interface/API), so that it can be integrated with OWB without too much difficulty, etc.
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
