#gradle

here's how i did;

elementary - 25/25 (100%)

for the first part i graded a bit differently than the rest bc i didn't know there would be more suspect and things to keep track. hindsight is 20/20. regardless, i did this section as pass or fail. all were correct or i failed.

occult medium - 23.5/25 (94%)

for this section grading was a bit for complicated. each murdle was 2 parts for a point. if all answers were correct it was a full point. if 2 correct it was half. 1 or 0 and it was no point.

hard boiled - 25/25 (100%)

for this section and impossible, each point for a murdle is four parts. +.25 for each correct answer.

if i got the person wrong, but 2-3 of the details correct under the right suspect then i would grade according to that (allowing for .5 or .75 max, otherwise it just defaulted to the answer i got.)

impossible - 20/25 (80%)

see hard boiled for grading explanation.

--

total grade for the book was 93.5%

Just when I was bored and starting to feel discouraged and depressed, Gradle Inc. released a major update to its open-source build tool.

I'm not sure yet whether this is a good thing or a bad thing.

I use the tool in dozens of projects, most of which I keep up-to-date, so even the patch releases of Gradle are major events for me.

I recently tested one of the release candidates, and a lot of things didn't work, so I suspect the transition to Gradle v9 will require considerable effort on my part.

Soo I am getting back into Android, its been a long, long, long time. While trying to get re-acquainted with F-Droid app submitting procedures some dude told me to start using Gradle. The old process of building Android apps is deprecated.

I started to get acquainted with Gradle. So I learn, its a programing language itself. And get this. It considers a project as a construct.

The point. Here I am claiming things like executables and even documentation should be thought of as constructs. All this time, I am thinking I am alone in this. Well, not really. Gradle did something similar.

The difference is that they came up with this via a necessity point of view. I come from a theoretical point of view.

🤔 I didn't consider the build process, I guess I should.

The main take away: When you think of things as constructs, you can then make use of them in programming languages AND you might be able to represent them graphically. The reason I needed to think of executables as constructs was to be able to represent them in GUI form. I needed to think of documentation as constructs to be able to tightly integrate it to source code. I should also look into the build process and integrate that into SavageGardens. Gradle sees projects as constructs to be able to use programming languages to manage the build process.

have you ever opened up a new project and wondered what is the mysterious build.gradle file and gradle folder? what do they actually do, and why are they important in projects?

heres’s a quick guide!

"back in my day"

before gradle, setting up a Java project meant handling each step manually

compiling - you had to compile each file with javac