OpenBOR for Android [APK]

I actually heard that some people used Tortoise SVN to access the source code. I already installed it and needed the SVN link, you guys know the link for it?
 
That's what I use, but I'm on the road. Soon as I get to a PC I'll send it.

DC

*edit* Ninja'd
 
Btw DC, have you saw this?
https://github.com/rofl0r/openbor

OpenBOR (anallyst edition)
--------------------------

ABOUT THIS GIT REPO
===================
this git-repository has both the anallyst version of
OpenBOR (branch master) and the "official" version
from Chronocrash (former Lavalit) from SVN in branch svn.

The anallyst edition was forked off from SVN revision
3233 and was kept in sync with lavalit until rev 3318.

Differences:
the anallyst version is heavily optimized, debloated and
debugged and runs much faster than the lavalit version.
it has also a lot of platform-specific junk stripped off.
unlike the official version, this version is able to play
extracted mods directly from a directory.
this makes it much easier to debug and improve them.

the lavalit version has more bugs and some new features
which are not in mainstream usage.
some of the new features that were encountered in real-world
mods were backported to the anallyst version.
the anallyst edition should be able to play 99% of available
mods, after unpacking and repacking them with borpak from this
repo (see below).


the history of this git repo lasts back until SVN REV 3020,
at which point the repo was split into 2 parts.
the official svn repo is broken and it is not possible to
retrieve earlier commits.
the history was slightly edited with automatic tools to
remove all embedded binaries
(except of the required resources like .png's).
the original had a lot of cruft in the tools directory
(entire tarballs of toolchains, svn-setup.exe, etc.)
adding these to this git repo would make it about 100x bigger
and thus slower to use, so they were omitted.
also automatically generated changes to version.h, meta.xml
and Info.plist were removed from the commits (version numbers
generated by make), as those just make it harder to see the
relevant information.
Click to expand...
 
Damon Caskey said:
That's what I use, but I'm on the road. Soon as I get to a PC I'll send it.
Click to expand...
Sorry bout that. I got the SVN working. I'll try and recompile my changes to it and add it. Is it possible to add changes to SVN by using my SF privilege?
 
O Ilusionista said:
Btw DC, have you saw this?
https://github.com/rofl0r/openbor
Click to expand...

Yes, I have and even spoke of it once. That's Anallyst. He's a fantastic coder, but has one of the worst attitudes of anyone you will ever meet. Not just here, I've seen his interactions in other places too. You should have seen that readme before. It used to consist of little more than chest puffing and playground level insults leveled toward anyone and everyone involved with OpenBOR.

He also has no concept of user experience or the nuances of developing an application that depends on user generated content. Half the changes he made caused fundamental functionally breaks that had to be reverted.

Anyway, while what I'm doing is similar to his (as you can see untouched for a year) project, there are some huge fundamental differences. For one, I'm not into making silly micro optimizations that sacrifice the interface. The other big one is that while I too don't like ports, I'm not removing them. Much as I HATE them, ports are huge part of what keeps OpenBOR going. Lastly, LUA scripting is fine and all, but C style has been the the defacto coding standard since UNIX and for a good reason. Removing it just to prove a point is beyond idiocy in my opinion.

DC
 
Ah, I see. But there isn't any optmization from him that we could bring to the official version?

Hum, I am looking in that "alternate" source, and I found some things that can be useful.

https://github.com/rofl0r/openbor/commit/9c39ccb14479d7114da8921e80304caf623b51d9
"rewrote checkunused.pl. the old version was incredibly slow and didnt…work very well"

Code: 
-my @music = qw(data/music/complete data/music/menu data/music/remix);
+my @music_bor = qw(data/music/complete.bor data/music/menu.bor data/music/remix.bor data/music/gameover.bor);
+my @music_ogg = qw(data/music/complete.ogg data/music/menu.ogg data/music/remix.ogg data/music/gameover.ogg);
+my @music_oga = qw(data/music/complete.oga data/music/menu.oga data/music/remix.oga data/music/gameover.oga);

So he made the engine to look for "complete", "menu" and "remix" in .ogg format? That is cool, because the actual version doesn't does it. Even if you set menu song as .ogg it won't work - if you go to select screen then back to menu, the engine will look for only the .bor version. If its not avaliable, nothing is played.

Or things like "replacefilelinks.pl add tools to detect and delete unnecessary files in paks"
 
Damon Caskey said:
You should have seen this readme before he mellowed it out a bit in in the last commit.
Click to expand...

Saw it and I agree with you. I mean, OpenBOR is 'really badly designed'? Tell that to Senile who first made it. BTW, it was rofl0r who mellowed it down, not Anallyst. Sorry bout that, rofl0r IS Anallyst.

Damon Caskey said:
Lastly, LUA scripting is fine and all, but C style has been the the defacto coding standard since UNIX and for a good reason.
Click to expand...

Couldn't agree with you more.
 
Yeah, I saw that readme.
Things like "it has also a lot of platform-specific junk stripped off" bothers me a tad, because he removed platform support, as my crap english tells me?

just to make things clear: I am not dishing anyone. And I still believe more in someone who holds the torch since long time than someone new who appears out of nowhere.
 
O Ilusionista said:
...
Click to expand...

Oh I agree, some of what he does is great, but all of it are things I'm working on anyway. The menu and static defaults are all going bye-bye, but all in due time. He has the luxury of dumping ports and not supporting a user base. I don't.

As for the "the old version was incredibly slow and didnt…work very well", those are opinions. Take them with a grain of salt. In many cases he's right - but again, because of his tendency to put down everything other coders do, you have to review the actual work to verify good idea vs. potentiall breakage for no real benefit.

DC
 
Good to know.
After reading things like "(as can be expected of any good C source taken by gamers and scriptkiddies and collectively extended with half-baked features)" I understand the whole scene. Its not a behaviour I accept, its just...well nevermind.

Sorry for the derail :)
 
O Ilusionista said:
Yeah, I saw that readme.
just to make things clear: I am not dishing anyone. And I still believe more in someone who holds the torch since long time than someone new who appears out of nowhere.
Click to expand...
Not going to comment on that, I admit it for the nth time. Then again, that's the reason I still go here, people who have feedback than just being stoic and undermining, than people like Anallyst's (as reflected in his readme).

O Ilusionista said:
...
Click to expand...

That's perl scripting not C. The stupidest thing that I did was I didn't see this one coming until the answer in SE came, either way whatever anallyst did, it's just his thing, don't care, we still got DC making things for the engine and as long as Chronocrash will be better, it's just a scar that will remind us of the things happened in the past.

@DC, what do you mean the menu, the pack menu? I think revising it instead of destroying it is way better or what you mean that it's better if the engine will just be an engine and make a separate launcher instead?

EITHER WAY, I'm now going to make the port now, which will take a while...
 
That took a while. See first post.

Same fixes, accelerometer disabled, fixes for phones and all that jazz. Plus it's updated to the latest version 4086.

@DC - Permission to put my fixes onto OpenBOR's main code?
 
Not going to comment on that, I admit it for the nth time.
Click to expand...
Just to make clear, you were not my target. ;)

it's better if the engine will just be an engine and make a separate launcher instead?
Click to expand...
If the engine could accept command line codes, then we could use frontends to make some cool stuff.
 
That's what I figured as well, a better frontend than letting the engine itself be the frontend ...

Dang, I think I got DC's point and possibilities on why he wants to remove the menu here.  :o

Now, all I have to do is wait a while, I want to talk something different, I've been modifying the UI for the pack menu most of the time (and the main reason of this thread here), I've been thinking of designing a new UI skin to replace the dark one that I have. I've been seeing using the orange theme of the XBOX launcher for OpenBOR as a color scheme, matches the icon and logo too.
 
CRxTRDude said:
@DC - Permission to put my fixes onto OpenBOR's main code?
Click to expand...

Yes. And you should already have write access through SVN. Just makes sure you fully document everything. I want carefully commented code, a synopsis in the submission on what was done, and same here on the forum.

DC
 
Thanks DC! As we speak, I've actually modified the original Readthis.txt that utunnels originally used. I'm going modify the code afterwards to add comments and then how do I post my submission in the forums?
 
Finally added my first subversion commit! Release 4087:

Modified and revised the Android build with fixes and additions, see Readthis.txt for more details. Revised the menu.c with a new log screen and menu for Android. Modified video.c to reflect Android port revision.
Click to expand...

I also changed LICENSE, adding the OpenBOR team as part of the license, but generally the commit is all about the aforementioned than the latter.

Now finally, I can rest.
 
You must log in or register to reply here.
Back
Top Bottom