Stefan
Member
For interactivity, how about just a simple web page showing the current state and its successor states and you click on one to go there?
For interactivity, how about just a simple web page showing the current state and its successor states and you click on one to go there?
As for the image, I would enlarge the keys and the title. Especially the title - just like on a poster, it must be huge, so you can read it even from the end of your room. There is a lot of space on the top left quarter.
Well, yes, this could be a good start. In any case you need to encode at some level all relashionship data and this is missing (I have only an excel file and the image atm). Also, my "web application" designer skills would need to be improved (this could be a good chance).For interactivity, how about just a simple web page showing the current state and its successor states and you click on one to go there?
But I have to say that I found nice to have also the "whole picture" showing the size of all the data and, as someone said, it makes for a good wall poster .
One big problem for any "user" is the information retrieval, I can search for it, having the source svg, but I understand that if someone wants to know if something is there he has no easy task.
What about creating a new wiki page for each cube state/picture with the sub-group (as <F,R,U> for the [WIKI]2x2x2 Block state[/WIKI]), the transitions (the steps) to the next states (as [WIKI]XCross[/WIKI]) and the next steps (as [WIKI]F2L-3 state[/WIKI]) ?
Shouldn't it be easier han creating a new web page/ a web application ?
What about creating a new wiki page for each cube state/picture with the sub-group (as <F,R,U> for the [WIKI]2x2x2 Block state[/WIKI]), the transitions (the steps) to the next states (as [WIKI]XCross[/WIKI]) and the next steps (as [WIKI]F2L-3 state[/WIKI]) ?
Shouldn't it be easier han creating a new web page/ a web application ?
Seems rather laborious. Unless you write a program to create all these wiki pages, and then that's against the point of a wiki. And more work than just writing a non-wiki application.
What do you mean with "Cross+1" state? What should contain that state? A cross plus a c/e pair inserted in wrong spot or not inserted at all? Or a cross plus only one corner?Here are some ideas:
- Add "Cross+1" Step between "Scrambled" and a new "Cross+1" state (cross+1 c/e pair != Xcross)
I'm not sure of the name but I mean a c/e pair not inserted at all. During inspection, if you see you (can) have a c/e pair, you just try not to break it while making the cross. (To anybody: Is that right ?)What do you mean with "Cross+1" state? What should contain that state? A cross plus a c/e pair inserted in wrong spot or not inserted at all? Or a cross plus only one corner?
OK.I'm not sure of the name but I mean a c/e pair not inserted at all. During inspection, if you see you (can) have a c/e pair, you just try not to break it while making the cross. (To anybody: Is that right ?)
Here are some ideas:
- Scrambled State may have a "Scrambled" Label
- Rename "2x2x2" step to "2x2x2 Block" step
- Rename "2x2x3" step to "2x2x3 Block" step
- Remove "F2L-2" Label to "2x2x3 Block" cube state
- Beginners may treat EOLine as two steps: EO+Line. Add a step between "Edg Oriented" and "EOline". This step's name could be "Line" (and Set use only this subgroup: <R, U, L, D, F2, B2>)
- Add "Cross+1" Step between "Scrambled" and a new "Cross+1" state (cross+1 c/e pair != Xcross)
- State before "ZZLL" may have a "LL->EO+2EP" Label
- State before "PLL subset 9/21" may have a "LL->EO+2EP+CO" Label
- State before "2GLL (subs)" may have a "LL->EO+2EP+CP" Label
- Add "Beginner CP (Niklas)" Step between "LL->EO+2EP" and "LL->EO+2EP+CP"
- State after "F2L+1E" may have a "LL->1E(O+P)" Label
Well, maybe they are not so useful but at least they are "consistent". I don't think i want to lose all that info changing arrows color.+
- Colors of the lines (Yellow=Last slot, Blue=Corners...) aren't very useful : we just have to look at the cubes pictures around the step. Won't it be better to change (For instance : Yellow for a speedcubing substep, Blue for a blind substep, Green for Speed Blind, Red for Fewest Move Challenge, Brown for One Hand solving, Pink for Feet solving, ...) ?
The only difference is ... the size . This means that on big image you have double the resolution (XxY pixel and thus MBytes), allowing you to zoom in more and see the details (especially text). If you see different colors this is probably due to the viewer you are using (windows?) that at different zoom levels make some artifact or false colors. At full zoom level (1:1) you should have the same colors on both images.Wow! I admire your integrity to follow through with this idea of yours! One question; what's the difference between the medium and big graph? I can only see that some colors are more opaque
Wow! I admire your integrity to follow through with this idea of yours! One question; what's the difference between the medium and big graph? I can only see that some colors are more opaque
Okay. So is the text still readable on the medium one? I'm not at a computer for a while and can't check.The only difference is ... the size . This means that on big image you have double the resolution (XxY pixel and thus MBytes), allowing you to zoom in more and see the details (especially text). If you see different colors this is probably due to the viewer you are using (windows?) that at different zoom levels make some artifact or false colors. At full zoom level (1:1) you should have the same colors on both images.
LolThe resolution (image size). Try to zoom into both images, you'll see.
Edit: ninja'd.
It is, 99% of nodes. Only one which uses font with size=6 is barely readable on medium size img. I'll have to increase that.Okay. So is the text still readable on the medium one? I'm not at a computer for a while and can't check.
Oh okay. I'm planing on printing it out so I can examine it, I find it easier to process lots of info when I see it all, instead of having parts off the screenIt is, 99% of nodes. Only one which uses font with size=6 is barely readable on medium size img. I'll have to increase that.
If you need to print it I highly encourage you to get the bigger version. Even that is not so big for the purpose of printing, medium has 90dpi while big has 180dpi. I could actually generate also a bigger image from the source svg if you need, but size on disk would skyrocket.Oh okay. I'm planing on printing it out so I can examine it, I find it easier to process lots of info when I see it all, instead of having parts off the screen