I am making a basic program using xLibC that tells how to solve 6 different types of rubik's cubes.
Who wants to help w/ the code?

well, I am not familiar with xLib, but can help out with the generic BASIC code (menus, flow, formatting, all of the non-graphic stuff)

I want to help you too, but can you give us some more information? What will it exactly do, what do you have already so far, what are you going to add etc.? Do you need help with xLIBC or the program structure? What do you expect of us?

The program starts by displaying the six types of cubes that i am including in it, and you highlight the one that you want and select with 2nd of enter, and it goes to a screen that displays the cube situation that you want to fix, and then it tells you how to fix it. I want it to be able to scroll between the different teps for each cube by pressing left and right. You can go back to the menu with clear or delete, and you can quit with the same two keys. Do you want me to send you what i have done so far? ( I started it last night)

If you already have the solving code, I think displaying the correct Rubik's cube arrangement and being able to scroll through the steps should be quite trivial. Your code probably goes through a series of loops, therefore, every time it comes up with a new step, add in a getkey loop (or real(2.0.0 if you want to maximize your use of xlibc) where the user can input the arrow keys. If you've coded it using matrices or lists (hopefully with numbers 1 through 9), simply refreshing the screen grabbing the new modified values in the the list/matrix, linking each value to an actual color code from the palette, and finally, displaying the 9 squares with the new color codes seems like a fairly reasonable solution. If you've done it using only variables, the process would be similar, but probably a little slower and larger in terms of bytes since you would have to update each variable in different snippets or code.

I know how to solve all sizes of rubik's cube and several other types, so the solving shouldn't be a problem. I am pretty much doing what you said otherwise. Do you want to see the code?

That sounds like a good idea, so we can probably help you.

I mostly have the shell of the program finished (w/o any information in it) so i can put the code in the thread, so you can see/ critique it.

Code:

Now that you seem to have the basic structure of the program finished, how do you plan to give the information? I personally would explain the notation first off, then tell about the algorithms and basic steps and what they do (for example, explaining how to actually solve the white cross, and maybe some F2L algorithms could be included?) As for method, at least for the 3x3, I'd go with the total-beginner method that Rubik's teaches in their instruction booklets (or even F2L if you think they're gonna feel brave ).

...Hold up, I'm confuzzled! Is this a program that teaches you the LBL algs or do you input certain scenarios and it generates a solving alg for you?

@JWinslow: Seconded, except for your last F2L statement. Leave that to the speedsolving wiki. Most people would need the LBL, not CFOP. Although a calc program with the CFOP algs would be nice...

'Twas a joke. However, a solver with the capability of doing this would be cool on a calc.

I'm actually interested in what direction this program will go...solver, or tutorial. Or BOTH.

Tutorial, I am not skilled enough at programming to do a solver, especially not one compatible with 6 different types of cube. Also, it would be confusing trying to input the scrambled cube, and tedious.
The program just tells you what steps to do for each movement you are trying to accomplish.

*BUMP*
Any progress of late, Pieman?

I am going to pick this up again, now that my hybrid basic skills have been sharpened by CC18 ;P
(thanks for that jonbush) ;P

Hey Pieman, do you have a GitHub? If not, you should make one; it makes everything a whole lot easier when sharing and editing code. If you have/get one, post the link in this topic, so I can possibly go and make some edits. If you don't want to make it, not a problem.

I have one... I dont have anything for this on it yet though

https://github.com/Pieman7373/QBSOLVE/tree/master

Okay, I've submitted a pull request that fixes a few things. You can see the full details in the pull request.


AFAIK, Pieman is using the CSE for this, which doesn't have the eval() function. You could have this instead:

Code:

Haha, I realised this was in hybrid-basic and therefore not compatible with the CE yet, and therefore he must have been using the CSE, and thus, the eval() command was not available to him. This is why I promptly removed the post, but I guess you had time to quote me on that
As for the code, you have to note that the page number sometimes goes up to double digits, and if we want to keep things in decimal, your method won't work. That is not to say that it won't work entirely, but it won't work for the one case where the page number goes up to 10. Therefore, we will have to go with the perpetual thorn or the longer, less popular method which is only really an option if we're dealing with integers, which we are. I've thus decided to list out the two sensible ways it could be done (and work for page 10 too).
The nice way

Code:

The ugly (but smaller) way that overwrites a lot more variables

Code:

I am going to start this program over from (almost) scratch [because my code is old and abysmal], so i will post code and or screenshots once i make progress