Domain Authority 50 for your website - Guaranteed Service

We`ll get your website to have Domain Authority 50 or we`ll refund you every
cent

for only 150 usd, you`ll have DA50 for your website, guaranteed

Order it today:
http://www.str8-creative.co/product/moz-da-seo-plan/

thanks
Alex Peters

1603, Quest For Quintana Roo!

In this episode we look at the game Quest for Quintana Roo, which I mispronounced for most of the show. Thanks to Eugenio for correcting me. I loved the game and I hope you will too. Next up is a big game, Joust by Atari via Williams. If you have any thoughts on this game, please get them to me by end of day 5th October and I'll put it in the show. Remember, just tell me your thoughts on the game, I'll take care of the game play. you can send those thoughts to 2600gamebygame@gmail.com. Thanks so much for listening!

Quest for Quintana Roo on Random Terrain
Atari Age thread on Quintana Roo Carbon Dating
Sunrise memo on Atarimania Page 1  Page 2
Ed Salvo interview by Scott Stilphen
Atari Compendium Quest For Quintana Roo Easter egg and bug page
No Swear Gamer 461 - Quest for Quintana Roo
No Swear Gamer - Quest for Quintana Roo gameplay

Some Good, Old Fashioned, Rocket Fisting

I haven't felt much like painting this year so I needed something different to kickstart myself back into it. I started Defender X for Monsterpocalypse a couple of weeks back and finished him up this weekend. I tried painting him last year but wasn't a fan of how the purple was coming out. After a bit of ink and contrast paint mixing I got something that I was happy with, here's the result.

G-Tanks and a Repair Truck are next.

1500 google maps citations cheap

Rank the google maps top 5 for your money keywords, guaranteed

http://www.str8-creative.io/product/1500-gmaps-citations/

regards,
Str8 Creative

Closer To Home

 That's better!  

The inner call to free my 54's from the grid and to restore the infantry to their original 8 figure units, some of which date back to the 1990's and MacDuff to the Frontier, has finally won the hearts and minds battle, and now appears to have finally led to a real contender for a set of rules that will allow me to play interesting, full scenarios on my pint size table with enough units and figures to satisfy me.  

End of Turn 3 of the current game.

The last three attempts all had something to offer but each suffered from some critical failures, not engaging enough, too abstract, too obviously derived from current copyrighted games (Did anyone notice the battlecry dice in some of the photos in the last post?), too tedious/repetitive/indecisive/etc, or just didn't use my old 8 figure infantry unit standard that I would like to revive. 

Three turns in is a little early to call success but so far it IS promising. More in a day or so.

Brian The Lion Starring In: 'Rumble In The Jungle' (Amiga) - Guest Post

This week on Super Adventures, mecha-neko has returned to tell you a tale about a lion, called Brian.

Developer:

Reflections

|

Release Date:

1994

|

Systems:

Amiga 500, 1200, CD32

---

Ray and I have played more than a few mascots and almost-mascots for the Amiga, but it's time to show you the last, and best. Introducing Brian the Lion.
Read on »

Domain Authority 50 for your website - Guaranteed Service

We`ll get your website to have Domain Authority 50 or we`ll refund you every
cent

for only 150 usd, you`ll have DA50 for your website, guaranteed

Order it today:
http://www.str8-creative.co/product/moz-da-seo-plan/

thanks
Alex Peters

Website Updates

Over the last few years I've been trying to increase the accessibility of my site. I have 25 years of web pages that I maintain so it was a lot of work to do all at once. I split it up into multiple phases:

1. Phase one: I converted 85% of my pages to use a "responsive layout", which takes into account the reader's browser size. I converted pages that had a 600px width and were relatively easy to convert to a variable px based layout. My focus was to write responsive CSS rules that smoothly varied the layout and font size based on browser width. I wrote my notes on how to do this.
2. Phase two: I tackled the 15% of pages that were more difficult to convert, because of their use of non-standard layout, or interactive diagrams, or iframes, or anything else that made it difficult. I wrote a blog post about this. I still used a px based layout.
3. Phase three: I'm ready to switch from a px based layout to a rem based layout.

This is how I often make progress past "analysis paralysis": I break the problem down into smaller, simpler ones and then work on them one at a time.

Browsers default to 16px fonts typically. Most people don't change the default. But some do. Around 3%. My site had overridden the reader's preferred font size and then set the layout based on my font size.

I have the page layout link the font size and the paragraph width.

• For narrow browsers, below 550px, the paragraphs are the width of the browser, with a narrow margin. The font is 10px.
• For medium width browsers, the paragraphs gain some space, but the margins also gain some space. The font grows along with the paragraph.
• For wide browsers, above 1000px, the paragraphs are capped at 660px, and the rest goes to the margin. The font is capped at 20px.

I wanted to keep this variable font size but make it scale with the reader's preferred font size. Note that I'm not displaying at the browser font size, but instead scaling my variable font size (10px to 20px) based on the ratio of the browser font size to the default. If the reader has set the font size to be 20% larger than the default, then my font sizes will be 20% larger, so 10px becomes 12px and 20px becomes 24px. I made the layout match the font size change by changing the "breakpoint" sizes and the paragraph sizes to use rem units instead.

Since the browser defaults to 16px = 1rem, the simplest thing to do is to divide all px sizes by 16 to make them rem units. For example, the paragraph size of 660px becomes 660÷16 = 41.25rem. However, that doesn't handle all the corner cases.

Sizes inside diagrams, including font sizes and line widths, were already scaled to the diagram's size. And I made the diagram's size responsive to the browser size in phase two. So that means sizes inside diagrams should stay as px units.

Secondly, on some versions of Safari, @media queries work better with em sizes than with rem sizes. So I used em for those.

Third, I had picked sizes like 600px because it was a nice round number. Converting it to 34.375rem makes me wonder: does it really need to be 600px, or could it have been 35rem. This is similar to a problem with Metric vs English units. Why does Coca Cola have 12oz cans (355mL) but 2L bottles (67.6oz)? It's a "nice" number in one unit but not the other. I had previously used px so I picked sizes that were nice in that unit, but now that I'm using rem I may change the sizes slightly to be nice in that unit instead.

I first made this change on my main stylesheet that I share for all my pages, then went through hundreds of pages and made individual adjustments to them. Since my diagrams are generated in Javascript, I also had to adjust the code for some pages to work.

I tested this change by changing my browser's default font size and then browsing my pages. I think it works pretty well. If you see any layout issues, let me know!