|
Who's Online
|
7 user(s) are online (6 user(s) are browsing Forums)
Members: 1
Guests: 6
Swoop, more... |
|
|
Browsing this Thread:
1 Anonymous Users
|
|
|
spotUP [image]
|
Re: Help Joerg |
|
Quite a regular
|
Posts:
761
|
|
Posted on: 2010/7/20 21:57:12
|
|
@samo79
nope i didn't download that port..
i'd need the developer archive of glib2 though.
edit: so let's try to compile glib...
configure: error: *** pkg-config too old; version 0.16 or better required.
doooh...
edit: so let's try to compile pkg-config then.
what was i originally doing again? :P
edit: no luck there... glib needs to be crosscompiled for now i think.. afxgroup, could you upload your glib2 port?
Edited by spotUP on 2010/7/20 22:13:55
|
|
|
 Transfer
|
|
|
|
|
Fab [image]
|
Re: Help Joerg |
|
Just popping in
|
Posts:
63
|
|
Posted on: 2010/7/21 0:16:02
|
|
@Hans
I wrote an input protocol that hooks to ffmpeg with a registered url-protocol, that takes care of buffering incoming data through the regular OWB network layer. It supports "fast seeking" by resuming (something that GStreamer backend didn't until a few weeks ago). Media data is then demuxed in another thread, which itself passes packets it to video and audio decoder threads. And since cairo rendering for such video needs isn't blazingly fast, i provided a fast overlay output mode that is enabled when fullscreen mode is enabled (it's actually a fullwindow mode, but whatever).
Of course, the whole thing is more simple than a full-blown GStreamer layer, but it does as much in this HTML5 context, and was much more interesting for me. Chrome also has a similar approach, using ffmpeg directly and implementing their own stream layer.
But having GStreamer for other things would still be interesting, of course.
Edited by Fab on 2010/7/21 0:41:18
Edited by Fab on 2010/7/21 0:42:08
|
|
|
| Transfer
|
|
|
|
|
afxgroup [image]
|
Re: Help Joerg |
|
Site Builder
|
Posts:
608
|
|
Posted on: 2010/7/21 5:25:48
|
|
@kas1e
i have an old version of glib2 taken from amycignyx and patched to remove all cignyx: calls. It is useful for my works but is old and if you try to use it with new projects it needs a lot of other missing functions.
You can ask Edgar (Mr X) for a newer version.
|
|
_________________
i'm really tired... 
|
| Transfer
|
|
|
|
|
afxgroup [image]
|
Re: Help Joerg |
|
Site Builder
|
Posts:
608
|
|
Posted on: 2010/7/21 5:59:03
|
|
@kas1e
you should remove the unused stuff but i don't think it would be a great effort
|
|
_________________
i'm really tired...
|
| Transfer
|
|
|
|
|
joerg [image]
|
Re: Help Joerg |
|
Quite a regular
|
Posts:
887
|
|
Posted on: 2010/7/21 6:16:08
|
|
@KimmoK
Quote:Yes 
Quote:A bounty for the fusion of AOS4+AROS+MOS OWB.
It would/could bring OWB developers together to merge their doings to one combined browser.
Once the same code compiles for all flavours, the bounty would be given (split) to all three origins.
- Different goals: The AmigaOS 4.x version is a port of OWB (with minimal features added to make it usable at all, for example a GUI, support for multiple windows/tabs and the much faster AmigaOS font implementation) while the author of the MorphOS OWB seems to try to implement a desktop browser around OWB (which makes no sense).
- Neither the AROS OWB nor the MorphOS OWB use an AmigaOS GUI but Zune or MUI4 instead, i.e. you can't use anything in GUI related parts from the other 2 in the AmigaOS 4.x OWB and most of the platform specific parts depend on the GUI. Or you'd have to downgrade the GUI of the AmigaOS 4.x OWB to MUI, but it's impossible to collect a bounty large enough for me to consider touching extreme crap like MUI ever again.
- To compile the same code for all OSes you have to replace every single OS function call by wrapper functions which have to be implemented for the 3 incompatible OSes. Even for my old AmigaOS 3.9 port of OWB I didn't do that, creating a new port from scratch instead which didn't share a single line of common code with my AmigaOS 4.x port was less work.
- Unless you want to limit the AROS version to AROS/PPC you have to do the same for all endian depending memory accesses, for example in the AmigaOS font implementation, since AFAIK the AROS compilers for little-endian CPUs don't support generating code which automatically fixes them like the Amithlon GCC did.
- No idea why, but the AROS OWB uses SDL. On AmigaOS 4.x using SDL graphics in OWB is a little bit (less than 5%) faster than using it's Cairo graphics implementation, but even if SDL would be twice as fast as Cairo on AROS they'd have to change it. The SDL graphics implementation of OWB is way too incomplete to be usable.
Cooperation would only make sense in OS and GUI independant parts of OWB, for example adding PowerPC support in SquirrelFish Extreme. The only difference between AmigaOS, AROS and MorphOS there would be allocating the executable memory.
|
|
|
| Transfer
|
|
|
|
|
afxgroup [image]
|
Re: Help Joerg |
|
Site Builder
|
Posts:
608
|
|
Posted on: 2010/7/21 7:22:59
|
|
@joerg
Quote:
- Different goals: The AmigaOS 4.x version is a port of OWB (with minimal features added to make it usable at all, for example a GUI, support for multiple windows/tabs and the much faster AmigaOS font implementation) while the author of the MorphOS OWB seems to try to implement a desktop browser around OWB (which makes no sense).
Why not? in this case you could use OWB with SDL/fontconfig implementation, remove all useless (tab are useless if it isn't a desktop browser) gui stuff and launch it from shell as the original version.
Sorry but these are your opinions and your goal, but maybe someone would have another goal for OWB on OS4
|
|
_________________
i'm really tired...
|
| Transfer
|
|
|
|
|
afxgroup [image]
|
Re: Help Joerg |
|
Site Builder
|
Posts:
608
|
|
Posted on: 2010/7/21 9:21:39
|
|
@Daniel
Quote:
Could GUI parts be taken from AWeb, which is open source and has a Reaction GUI?
Maybe you don't understand that he doesn't want to add useless GUI to OWB
|
|
_________________
i'm really tired...
|
| Transfer
|
|
|
|
You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You cannot vote in polls.
You cannot attach files to posts.
You cannot post without approval.
Home |
