Login
Username:

Password:

Remember me



Lost Password?

Register now!
Sections
Who's Online
67 user(s) are online (56 user(s) are browsing Forums)

Members: 1
Guests: 66

Rigo, more...
Support us!
Recent OS4 Files
OS4Depot.net
Report message:*
 

Re: Reaction OWB better than MUIOWB?

Subject: Re: Reaction OWB better than MUIOWB?
by kas1e on 2013/7/1 7:21:46

@K-L
Quote:

Because Roman wants money.


In other words Roman bad and wants money on work done by another. That what you mean right ? I.e. Roman sucker who do not want to loose all his time to make a port of browser from another os, while he not programmer, while he have no interest to be a programmer, but do it because another ones can only ask, chill and say that only os4 true-teh-omg os ? And be in hope that someone else will do what can do anyone if only have a bit of energy and just ability to talk with another ppls ?

Taking aside that all this sucking "because kas1e wants money" mean "kas1e want money to send it to developers and not for yourself". I repeat it many times everywhere, but still some of you want to see me like a faggot who want money and nothing else. Like i am here because of money. MONEY ! Amiga and money, don't you found it funny ? I am sure in FR you guys not so poor and have at least 1-2-3k per mo, and so you still call time consuming and time wasting projects for which someone want money (to split it between all developers to motivate them, i note it again, yes, so you will see why) a "money" ? Are you for real ? You guys happy to spend thousands on expensive HW and then think that SW will appears magical without any single income ? A bit of too much, nope ?

@Elwood
Quote:

Maybe (and I really mean maybe) someone else should look at it.


Maybe there is no sane and time-free persons left anymore who just put pieces in one puzzle and just finish stuff ?Maybe there is no developers at all who want to worry with porting browser because they have bunch of agendas of different kind ? Maybe Elwood want to do that ?:) Or who else you mean ? Everyone who have skills keep busy for everything, but there is not many of them anymore, sadly.

I will be only happy if someone will just do one normal browser for os4, be it port or whatever. And i didn't mean that sluggish firefox with "its not just a browser , its technology". I see enough of developing speed on those projects. Its all even worse in end as i think before. It takes not 1-2 years, but 5-7 for simply things which done on another oses for months.

Sad truth is there is almost no more developers left. With all that agendas about "we not want port os4 to mac because of blablalb", we suck some boing balls in end, and such task as porting of browser do person who know nothing about coding (i.e. me) till his peg2 not die.

@ChrisH
Quote:

Timberwolf is a SPARE TIME *PERSONAL* PROJECT of the Friedens, where-as Warp3D & LibreOffice are OFFICIAL PAID JOBS.


Does not matter at all how to call it all. Official, smacificial, personal, not personal. Its all very slow in all the cases. Its unreal slow developing of everything. Simply task take years (=> fail).

Quote:

There MUST be other reasons, even if it is (as it appears from the outside) that Kas1e has just lost interest in OWB (even with the prospect of money).


I never have any interest in it, but in some time i was in hope that muiowb can be ported with all the stuff. But all that mambo-jambo with html5 player and other deps, make me think that os4 version will be always worse, and in end of all, its just maybe indeed better to buy cheap mac with morphos and use it ?

@Fab
Quote:

Just for the record, Odyssey is already in a versioning system, and that's MorphOS CVS. I just don't want to maintain two different branches of it.


Is that morphos cvs public ? I assume of course not. That mean, does not matter what it have, no one except you have access to, no one can apply any patches and just simply recompile for aos4/aros. Of course it suck to maintain different branches, but i see no other solutions if you have interest to have it on all amiga likes. It can be so much easy when i just can ask you on some SF forum "hey fab, is it ok to apply such code?" you say "ok", and i do commit. And that ifdef keeps in code for all the time, and no one will need to reimplement a wheels again and again with every new version. Its just time consuming and non-interesting. With such commits everything will be in end very easy for everyone later. You can add as commiters only those who port it, with words "ok, guys, any commit only with asking me before". And no problems.

Quote:

And really, the amigaos4 diffs are really minimal, small enough that they can be kept in small patches that apply to any given snaphot i could provide.


How can you say that :) Don't you remember how much of small problems happens which not happens on mos, and which arise with every new version ? All that crap about tabs (code of which you for sure change from time to time, so now will need to understand new code, to be able to reuse our replacement), about all those player related parts with loosing ifdefs, which ok for mos, but make a black problems on os4, about those functions which make a garbage on os4 when they not strduped (and you for sure add bunch of new of them in different places, but not one can see where, because there is no public svn), about those "static/non static" problems which happens on some parts , and only on os4, about rewriting all those "createtasks" and crap, which i do not remember where in all the code they are, about new adding code related to pointers (there was some for sure), about those random crashes which happens only on os4, and to fix which i loose month or so, about every new single added line which make old "patches" just do not works and which will make new problems 100%. And you for sure create some new and tons (really tons) small other moments, in which again need to dig in together with all old problems.

If only there was idefs already in code, its all will be very easy to fix _new_ moments. But now, when i will get new src, its all will be the same old dances for a weeks, to making again the same and the same (half of which i just do not remember, and how can i remember code done not by me ?).

Don't forget also how much of 3d party libs you use, and sources of which i also need, because you know that i am not programmer and all those curls, fontconfigs, libcairo/libpixman and all the other libs which have specific morphos changes also need it , to make a proper port. Without them, i again stuck with my buggy ports of those deps, which i need again report in new versions, and i do not know them as well and i will need to loose a lot of time on them too, as before.

And i don't say that you use now shared libraries code of which are not open too. What to do with them ? Disable functionality ? The same as html5 player (which in general, was the #1 motivation for me to make a port, and later i just realize that you can't give that code for anyone. Its all like just give half of candy. Without html5 player muiowb not that interesting).

Quote:

So it really doesn't compare to the amigaos4 diffs. These ones mostly apply to the morphos part and this one i don't change in a major way so often, so it won't conflict a lot. It's really the easy part...


Still you change it, still it will conflicts, still if will need programmer's work, while i am not programmer and you know it. If it will be on public svn, then i can ask anyone for help, then discuss commits with you, and everything will be easy and done. For now, its all pretty hard to maintain for anything except mos. Patches will not works, because code changes, new bugs will happens, and with every new snapshot i will need to do the same again and again, which can be done one time, then followed on SVN, and changes can be indeed easy, small and trivial.

And i forget to mention that for every new version you something changes in compilation as well, like 'make' options, which i also need somehow to understand without knowing what they do and for what.

Without public SVN its all will be like this all the time. I just really was in hope that when i done one time with it, all ifdefs will be in code, and there will be no problems for later recompiled, but in end it force to be pretty boring work of doing the same again and again. Its all of course much easy in compare with first port, but still.
Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project