2-771 [Frook 2, chapter 7.7, brick 1] - Old stuff

I'd like this for mobile (one single line at the top left of the screen)

2777 > ^ v < * # in .c F ? 0 1 2 X S M L X
It was the beginning of....

where:
"2777" doesn't have a dash or period
'#' = brick map (call it map not grid)
"in" = index (of mobile skipFron)
".c" = switch to .com (of skipFron)
'F' = link to "frangles.mobi" / ...
"X S M L X" = 1 2 3 4 5 (sizes)
"0 1 2" address the color scheme

Try getting familiar with a mobile emulator(s) when altering mobile code... Things shouldn't be big and bold with titles and sizes and centering etcetcetc. (It's hard to realize that on a standard 1024x768 monitor) These things can take up whole pages, and increase loading times. The phrase:

Chap 7 <b>The whole title</b> READ

can be read 10 times faster than:

skipFron - Chapter 7 - READ - <a style blah = bold>The whole title of this Chapter Even if It's very long because some idiot freer Didn't Consider the Global Consequences of to Mobile Users of His Idiot Fourthwalse Title <not bold> - <underline> READ <stop underline> skipFron - <br><br><br>end stuff - blah - foo <a href=blah foo><style=i_can't_code_html_for_shit><more stupidly long stuff that contrives my point><close stuff>
 >> Just look at the HTML source (not the PHP) of the mobile version and you'll see that my code is clean, small and beautiful :P; even in the .com version (apart the tab thing, of course, which indeed in the mobi is done different)
\~Chip\

That's 6 seconds versus a MINUTE on a slower or bad connection. (One easy way to check it is just to adjust the size of the browser you're testing to as small as it can possibly take, and edit/test the com in another window)

EXPLATAIONS++

[This is a bit strict on compression, but right now there's not a whole lot of difference between the com and mobi site. I.e. I can surf the com site pretty well on my cell phone. The two versions might as well be set apart enough where they're more usable for different purposes and barely cross over. More compression is always great for very very small devices, and an iPadish device can have the option of small or com. obviously the eventual goal is to have the .com version so that every page would crash on a small device.]

[Numbers can mean absolutely anything, esp in a project based around unorthodox numbers. X S M L X is much more intuitive than 1 2 3 4 5. X S M L X is something that one could figure out looking at a page their very first time. importantly, is already been used on Frangles mobile.]

[actually putting "skipFron" right now is a bit confusing, as people familiar with frangles will be confused what skipFron means... likewise it shouldn't say "frangles" either. if there's no title, the page is versatile, so it can be whatever the user thinks in their head is most appropriate. this of course bad for marketing, since drilling a term into a visitor's head helps popuate things. then again... it's also a bit spammy to have the name of a project at the top of evvvery sinnnngle page, and is rude to long-term fans who have no need to be informed of the name of the project. it's kind of like an advertisement... this is for now anyway, eventually we have to either harmozize the frangles mobile site adn skipfron mobile site, or have it easy and intuitive to switch between them.]

[The symbol you have to skip to the next nova is very confusing. If something's going to switch novas, the foremost thing to do would be to skip exactly 49 (base 10) bricks, so you could progress the story formed by taking 1 brick from every nova and reading forward. As it is, there's so little written that interconnects novas that it's really pointless to have anything moving whole novas, especially not "go to the start of the next nova", which would be less important than "go to the start of the next chapter", which would have to exist for your nova-skip symbol to make sense. "Inter-nova" stuff can be put off for a good long while.]
 Meh. That's not nova, it's chapter. But I suppose the same is valid for the chapter too. So now removed.
\~Chip\





So right now there are inaccessible bricks on the mobile site... bricks that can't even be reached. please fix this by having > skip empty bricks, and/or allowing the user to look at a grid/map of each nova or frook.
Revision> Could you just have > skip empty bricks for now, don't worry about maps/grids, or any of the stuff below. The most important thing is having them be accessible by at least one method, and it seems an easy fix.

Arrows should go to the next available brick, i.e. skip some if necessary. (Skipping 7 should skip in multiples of 7, not skip ahead 4 bricks if there's a brick between the brick we're on and one 7 away. So 345 should go to 365 if 355 is not available, even if every other brick between 345 and 365 exists.)...

Eventually.. there should be some signal to the reader that a link will have to skip bricks. A different color or symbol for an arrow, etc. They should never be stuck like being lost in a forest or maze. this could be a generalized CSS variable like "special link color" that would be used whenever a link needs to signify something special. (I eventually want to remove all the underlines everywhere but doing that requires very careful attention to color schemes and interactions between them and that's not something to worry about just yet.)
\\