day / night mode by hour

[bluebrother]

Since the build system I use can't run rockboxdev.sh as it has a 10 minute timeout per command.

That doesn't make rockboxdev.sh "buggy". "buggy" is something completely different. If the system you're trying to run the script on terminates it after a given amount of time it's a limitation of the system you're running it on. It is in no way a problem of rockboxdev.sh. Building the toolchain takes a while. A process requiring some time isn't "buggy" but, depending on what the process does, totally normal and expected behaviour.

Please stop stating such wrong facts.

[torne]

Yes; the problem is that the CI system expects build dependencies to either be available in binary form to be installed, or to be able to download and build them in a few seconds. It's a hosted system run by a third party who doesn't want their resources to be wasted compiling gcc from scratch over and over again.

If you want to use this system then it's your problem to work out how to create suitable packages for it to use; there is nothing wrong with rockboxdev.sh - it's not intended for this, is all.

[rbhawaii]

would any developers be willing to code this?

it runs a cgf file at a predefined hour thats all

instead of giving him so much beef for trying cant one of you just write it?

or tell him exactly where to look so that he can get it done himself much-faster.

do you guys feel all the advice you have given him so far is helping him get this done? i dont
im sorry

[wodz]

Look, he decided to use external service we do not support - it is his choice but at the same time he screams that our tool (rockboxdev.sh) designed to cope with our way of building is broken. If he wants to use our tool with external service it is his duty to glue it all together.

[[Saint]]

do you guys feel all the advice you have given him so far is helping him get this done?

Yes. I do.

But, as you've seen, giving advice has absolutely no bearing on whether or not that advice is followed or not. If a decision is made to ignore that advice, what would you have us do? We cannot force anyone to do our will.

The solution isn't to do it for him.


[Saint]

[torne]

instead of giving him so much beef for trying cant one of you just write it?

The way this project (like many open source projects) works is that people write things they want/care about/are interested in. If someone else wanted to do it they'd've done it already, so it looks like the answer is no, nobody else wants to.

or tell him exactly where to look so that he can get it done himself much-faster.

Telling someone exactly where to look in this case is analogous to explaining the library filing system to someone who can't read the language the books are written in.

[Reece]

      The beauty of RockBox is the customization. You don't have to be restricted by what Rockbox currently offers... You can modify it to your liking, and if its lacking something you want, then you can add it! . And if that modification is good enough, it can even be added to the official build.
But for those of you who don't know anything about coding, (kinda like me) that can be a draw back. But there is always time to learn, and there is no better time then now.
I think the best place to start is theming. Its a great way to get to know your way around the ".rockbox" files. I have learned ALLOT from looking at other peoples themes. The best way to learn is to fallow the leader.

[[Saint]]

For what it's worth, I'm not entirely sure that learning our proprietary skin engine language would be beneficial in any way to learning C or ASM.
It certainly couldn't hurt, but I don't think it would help. There are no similarities in these languages.


[Saint]

[AlexP]

I'll go further, it'll be of no use at all

[whiskers75]

You're right, I don't know C, and shouldn't be doing this. Therefore, I won't.

[[Saint]]

I don't know C, and shouldn't be doing this. Therefore, I won't.

That seems rather defeatist. One would think the answer would be to learn C.

I hope you haven't come to the conclusion that anyone is trying to drive you away from the project or discourage you from contributing.

To put it as simply as I can, one can either give a man a fish, or teach a man to fish. If you are going to teach a man to fish, one should first make sure that they are using a fishing rod, instead of a shovel.


[Saint]

[whiskers75]

I don't know C, and shouldn't be doing this. Therefore, I won't.

That seems rather defeatist. One would think the answer would be to learn C.

I hope you haven't come to the conclusion that anyone is trying to drive you away from the project or discourage you from contributing.

To put it as simply as I can, one can either give a man a fish, or teach a man to fish. If you are going to teach a man to fish, one should first make sure that they are using a fishing rod, instead of a shovel.


[Saint]

What I'm saying is, I shouldn't be doing C while I'm in the middle of JS stuff.

[whiskers75]

This is being worked on.

After reading up on C, I know more about how to do it.
(FYI, the CI system is now working using rockboxdev.sh)

Create a function:

Code: [Select]

void update_dn() {
}

Save it in daynight.h
Require it in main.c:

Code: [Select]

#include "daynight.h"

Call the function (every second/minute/hour):

Code: [Select]

update_dn()

Profit!

[bluebrother]

Save it in daynight.h

You shouldn't put functions in header files. There are a few cases where this is necessary but this isn't one of them.

Profit!

That function is empty, i.e. does nothing. How is that going to profit?

[whiskers75]

I left out the bits inside the function.
OK, fine, I'll put it in daynight.c.
Update: Here: Day/night prototype 1, commit 26a4a3b55e. Include daynight.c and run daynight() when you want to update day/night status. Build Status