I wrote the compile script and I informed myself a bit more than Tiger i think.

I Would go for no documentation at all inside CMakeList, there is usage information inside compile.sh
I would out the documentation in the standard COMPILING.md, as a reference I will explain it here: (and please also read the email I sent to support@cuberite.org)
The app downloads and installs zip files that are prepared by the build server. It's basically the binaries zipped because zip files can be read natively in Java. For more information, see the code of compile.sh under the section "all". Additionally, the app allows the import of a zipfile, that is either prepared locally or manually downloaded. The app stores a sha hash of the last used zipfile, downloads the build servers' sha sum and compares them regularly (once a week or so, configurable). This is called check for updates and will either ask the user to install the new one, disable updates or skip this update (mark this sha sum as skipping). Same applies not only to the used binary but also to the server directory. In case of the server directory, every file in the new server directory will replace the corresponding file in the old one, including but not only crafting.txt. As far as I know this doesn't contain settings.ini and webadmin.ini because they are generated on run time. The sha sums are also used to check the integrity of the download.
Now how to get the correct binaries. Android runs on many different phones, you can think of it similar to 32/64 bit. Although 64 bit is now standard on computers, this isn't established on phones. The ABI (<- that's how it's called; application binary interface) is set on compile time, the android ndk (native development kit, this is needed during compilation for android) brings several tool chains for cross compiling with it. Normally, you would prefer armeabi, which is supported by most phones, namely those with 32 bit arm processors (de facto 99% of all phones that were released until a few years ago). armeabi-v7a is the ABI with some additions made to it, many devices support this, this is actually the preferred abi on most devices (those that came with Android 4 I think). Note that one phone can support multiple ABIs the way a 64 bit processor can also support 32 bit programs. The app always looks for the preferred abi. CMake knows another ABI, armeabi-v6a, but Google doesn't document it so I skipped it. Newer phones running with arm processors are probably 64 bit ones, these need the ABI arm64-v8a. Apart from that there is mips and mips64 (for 32/64 bit on the mips platform) for some special phones and x86 and x86_64 for some special phones but also desktop PCs (yes, they can run Android). These are the 7 ABIs we currently support, through that and together with the minimum api level of 16 we support around 97% of all phones (the last 3% would dramatically increase the work that needs to be done as well as the mess with binaries). Api level 16 (android 4.1 I think) was chosen because it is actually recommended by Google, because it is a compromise between features and compatibility (and keeping the amount of work small). Api level 16 is also the minimum for so-called position independent executables (PIE) that is a security feature which is enforced since Android 5 (api level 21). Note that the minimum api level for 64 bit ABIs is 21 because android supports 64 bit since android 5 (the compile script has a check for the correct level, but this can cause strange issues when compiling by hand). Cross compiling is configured with a rather long cmake command, where system version is the minimum api level, build type is obvious, arch_ABI is explained above (the app shows the preferred abi on startup), tolua generator can be omitted I think and android_ndk is the ABSOLUTE path to the android ndk root. I am not entirely sure what the  -G option does, fact is that testing showed that MinGW Makefiles are required on Windows whereas Unix Makefiles are required on Linuxes. After that one can invoke make as normally, also with -j96 for 96 threads (makes compiling a lot faster if you have a nice machine :P). The binary goes into cuberite/android/Server/Cuberite regardless of the selected ABI.
Now that was the lengthy compilation instruction, now the short one if you are using Linux. First of all, download the NDK and make sure you have cmake >=3.7 installed (this is default on Ubuntu 16.10, and arch of course, every other OS would probably need to install it manually. For this reason the compile script explicitly asks for the cmake binary, so you don't have to install it globally. It you have the right cmake in the path, just use CMAKE="cmake" when invoking. Next, you decide which Abi to build for (or all, but this may take a very long time, an hour on my 2 core vps. Not the fastest, but also not the slowest one) and invoke the compile script as following. CMAKE="<path to cmake executable>" NDK="<path to ndk root>" <path-to-compile.sh> <abi|all|clean>. Yes, you can execute the compile script from wherever you want. Clean does not need the cmake and ndk variables, it deletes the android-build directory and is actually needed before compiling for a different ABI. All compiles and zips cuberite for all ABIs, leaving you with 8 zip files, once the server directory and one for each ABI. Specifying an Abi will not zip anything.

Just as last reference: zip files are expected to be without a preceeding directory, just the contents of the server directory or the binary. You can achieve this on Linux using `zip cuberite.zip Cuberite` next to the built binary or for the server directory `zip -r server.zip *` inside the server directory.

Wall of text, I know. Please post any further questions in the android pull request. (and look into support@cuberite.org @cuberite/core-team)

Another note: some features of the app are not yet implemented :P this is just the road map


Your description is correct, but the code change wasn't.
I fixed and commited the fix.

Thanks for the information.


Thanks for correcting the article on the Doom Wiki.


Good point. `update.delete()` would be better but it's difficult for me to add `thread_id` or `parent_id` for a LiveUpdate instance.


@whoburg as discussed at Friday meeting, but I can't get orbital values of deltaV despite using good values for Isp and mass fractions. Not sure what's going on, will have a look at it again in a few days.


Arghh thanks!


Jj


> update commit


Hello. When do people expect this to be in a release?


@walkerzheng
I believe we need a method in `Spy` to decrease the amount of lives the spy has.

Then we can remove the comment on this line and make the call to decrease spy lives by 1.


Estaba en test? Debería ir en exception, voy a probar moviéndolo

2016-11-20 17:10 GMT-03:00 keze87 <notifications@github.com>:

> El ant no la encuentra en test.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/keze87/TP2/commit/0f33f9aa048c151f03926d472dfe65d04324f364#commitcomment-19896239>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ASdG416pPACw_eSnxZs7nmb3-Hjot7y6ks5rAKkqgaJpZM4K3oCb>
> .
>


Thanks Rocky!  :)


Лучше помений значение FONT_SIZE_LARGE в gui_config.h для Mac или напиши
#ifdef Q_OS_MAC
m_plotterAxesLabelFont     = FontManager::instance().regular(GuiConfig::FONT_SIZE_BIG);
#else
m_plotterAxesLabelFont     = FontManager::instance().regular(GuiConfig::FONT_SIZE_LARGE);
#endif
Иначе в винде и линуксе подписи осей очень мелкие.


> Then we have a LiveThread and LiveEvent

It sounds really confusing for me because I know reddit live terminoogy, but others may have different impressons.


@michaz maybe useful for debugging as well :) ... to calculate the correct day offset we would need to publish the timetabling starting day e.g. via the /info endpoint... in a later change


hello world!!!


Updated: https://github.com/praw-dev/praw/blob/praw4/.github/CONTRIBUTING.md#style-recommendations


+1 for these selection criteria. They are defenitely more elegant than before!


Should this be 425? According to minecraftwiki (So it may be outdated) Coal is 1600 ticks and a stick is 100 ticks. This makes 1700 for 4 torches, or 425 per torch


Strange now that I'm messing around with both it seems my editor can now read it just fine from package.json.


👍 don't forget to port this to `5.x` too.


I don't like that. For example, `live_thread.add(text)` is not easy to read (where to add? sidebar?)


Thanks! :+1:
But this means that my MySQL server let in more errors that it probably should...


Yeah I suppose the thread's id will need to be injected into the appropriate object. Maybe Reddit can add the thread's ID to the update if it doesn't already exist.


That string doesn't make sense, agree.


Regexes do not work - why, I have no idea.


> Since there are a fair number of moderator related actions on a LiveThread, I think we might want to do the mod helper route similar to what other objects have (Subreddit, WikiPage).

I completely agree with that. I've took simple/easy route to implement.

> ContributorRelationship

I'll check that.


nice going


Seems like either works just fine as you said with `npm run lint` too, I'm not sure this was always the case (in one way or another) which lead me to the duplication, but I could be wrong as I don't recall dwelling on it too much. I'm just not sure which is preferred (.eslintrc or package.json eslintConfig)?


Sorry I missed that.


@Ipmanchess could you please pull again? I have fixed a possible race condition so it would be great if you can discard previous code and pull it again. Thanks.


Yes, I was hoping to release all projects following the main ical4j release. So hopefully I'll release in the next week or so.


Sorry, I made a mistake in my comment from the issue. This should be separated by spaces instead of commas.


How come you didn't finish?


Shouldn't this say `deprecated`?. In case it was not intentional, it's not a big deal; but as people say, this is technical documentation after all.


As much as possible, it's a good idea to avoid 301 redirects in development mode (I understand this is a generic .htaccess for both production and development modes), because a 301 redirect sticks into the browser cache, and it is difficult to remove (it's necessary to remove the browsing history). Using 302 would be much better (and our optimization guide can suggest to set it to 301 for better performances).


Yeah this is frustrating. Having a noun 'update' is very confusing with the presence of the very common verb 'update'. This method should be called `update` in order to maintain consistency in PRAW.

LiveUpdate need not be renamed but I feel like that will cause some confusion as one might think the `update` method adds a new update rather than updates the thread's settings. Suggestions?


Replace this file by [ThrowsConstraint](https://github.com/nunit/docs/wiki/ThrowsConstraint)


I think essence is necessary for one of the developments of @AngelFQC (CKeditor's multimedia lib?) or @jloguercio (social network's auto-linking?). Not sure we can safely remove it...


Well, just thought you might want to know.


Yes, `update.strike()` or similar is better, but e147a37#commitcomment-19896680


What is this choice based upon?


Is

> this.B_OWSE.Text = "**Title Screen**";

supposed to be something else? I'm assuming OWSE means Overworld Special/Static Encounters?


changed


Check that balance is unchanged too


oh its tipsy :-)


It does not need to be equal, rather it being slightly worse makes more sense as you are reducing your fuel to a small size (kinda like how compacting into blocks makes it better). Besides, you need 200 ticks to smelt a single item anyways, the extra 25 is pretty useless.


I need documentation on this file to understand why we need it. What does it do and where is it used?


Agreed. I'll take a look into other PRAW interfaces to get more consistency.


Thanks for the update!


Do we want to add it if it is "not being used"?


@keyboardsurfer where are you actually changing the colour?

When I tried to use the Recolor transition I did something similar to what alexjlockwood is doing here (https://github.com/alexjlockwood/custom-lollipop-transitions) but if in this case how would you animate the status bar color from black to white?


Makes sense. I'd prefer `add_update` than `post_update` simply because I don't want to introduce another verb and `add` is already used.


Yes, this was necessary. No, I'm not distracting myself with pointless changes.


After some thought, I don't like event since that could be confused with the thread itself. Thus I think keeping it as `LiveUpdate` is okay, and any confusion between `LiveUpdate` and the `update` method should be pretty apparent when someone is working with their code/documentation.


smh @Marty-D


What fix?


So I believe there are a few things at play here.

1) you should set the version of turbolinks to the latest version of 2(2.5. something)  vs the newest version of 5, as Turbolinks 5 is really for use with Rails 5 apps.
2) I believe you may also need the turbo-links jquery gem

I am not able to get this to work either, played with it for the last hour and a half with no luck.  I will do some more reading and see if I can figure it out, later this week.

the rest of this PR looks good.


We could rename `reddit.live` to `reddit.live_thread` or `reddit.livethread` to make it clear that the namespace is for working with live threads. I'm not sure if it's necessary, but might be a little more intuitive.


lol, you were ahead of me by two minutes in the `git blame` game


What's the source for this list?


But this would cut e.g. "en_GB" to "en_", which is not a valid code?


Yea I already caught this one.  It'll be pushed later on.


Good to know! :)


Thanks a bunch Andrew. I am in the middle of some Chapter 13 things at the moment, but when I am at a good stopping point I will try the things you mentioned. I have recently discovered that some of the more obscure issues may be related to my installation of rails 4.2.x whereas the book is definitely 4.0. In looking at the downloadable source code I have seen some differences between what they have listed between even their 4.0 & 4.1 source code. It's possible that in editing up some of the files that were generated with 4.2 to match what the books says for 4.0 I may have broken some things.


Yassine, thank you, a very critical contribution. Updated the latest zip on the website as there are no affected users (luckily).


Much Kajtków such comments


@kochigami Can you test and merge this?


no, still will cut 2 characters if length > 3


You might try using normal variables instead of an array.


Created a Sweep project


The def _method(self):
is and internal only method (methods are just functions inside a class :P). You can access it from outside of the class but aren't supposed to.

The difference between def method(self): and def method() is that "method(self)" is called using self.method() and "method()" is called using Classname.method(). The idea is that "Classname.method()/def method" is a generic function that is used without creating and Object. While "self.method()" acts on data that is part of an "active" Object.


Try to avoid data dependencies like lines 590 and 589.

Ideally you could do 4 merge, then 1 perm (unrelated to the last merge), more merges, the store related to the previous perm and so on.


Why this bizarre underscoring?


@xen0n well... It didn't like it. It seems that whenever I used that commit of @fire855 the device wouldn't boot.
Would this be down to all my other patches seem to be ferhungs and not fires?
Every time over tried to use just fire855s patches, including device and vendor. Obviously with minimal changes (libs and things), I can't get the device to boot either. Only been successful with ferhungs.. Am I doing something wrong? Is there any chance of me uploading my device/vendor files, and patches, and someone quickly looking at them, see if I'm missing anything? Thanks for all your help so far guys! Its really appreciated!


This is something that optimizer would be able to do (and there is a `FIXME` for that). We discussed it with @swiftix and he said it's not unreasonable.