The EMF FTL classifications

This page, StarForce Alpha Centauri, has an interesting examination on different types of FTL capabilities. I've been thinking about FTL theory a lot since reading this article on FTW (faster than the wind).

We: Current Layout

I made up some page numbers, but I'll wait on adding them until I'm sure we're going to use them.

Here's the current layout:

Update: Here's the final layout:

Don't just post responses willy nilly

"What is your royal wedding guest name? Start with either Lord or Lady. Your first name is one of your grandparents' names. Your surname is the name of your first pet, double-barreled with the name of the street on which you grew up."

Please do not answer these type of facebook chain messages. If you understand, many sites have alternative password "recovery" entry points using the answers to questions posed by these quips. All it takes is someone who is a friend of a friend with slightly open Facebook security settings, and now a poser or stranger has access to your alt questions, meaning they have your authentication credentials, and access to your websites.

We: Current Progress

After completing a few pages, I decided to stick to one background color for the scheme.

I think there are likely to be only a few more image pages, and the rest of the pages will feature Large Quotes, as I originally proposed for the project.

We: Distopian Worlds

Here is another dps (double-page) spread for the We book.

We: Entropy Plot

Spent most of the afternoon and this evening building a plot of the story entropy for several characters (ciphers) and the One State, using flot.

Added axis labels (04/26/2011):

And added this complementary page (04/26/2011):

We: Building inspirations

Guangdong Museum, Guangzhou, China

Biodome, Montreal

We: Audio Inspirations

0 - DVD Title look

9 - intro

1 - when he's at peace in the beginning / O-90

2 - the music produced by their music machine / maybe more 8-bit?

2.5 - more popcornesque music

3 - when he's growing more confused

4 - relating to I-330s attitude/rebelliousness

5 - D-503s obsession with I-330

6 - Traveling in an aero

7 - after the wall falls (intro reverb)

7.5 - outside the green wall

8 - the glass jar (mind wiping I-330)

9 - empty streets after the Operation

10 - closure

We: Book Drawing Sketches

Here are some more thoughts on the "We book" It's going to be a book expository, the kind that puts the source book into a variety of contexts. A historical, politico, scientific assessment, performed visually at the expense of narrative. As book, the layout of a single page is someone tied to the layout on the next page. They can complement or deviate, but too much of either concept might look forced. It will have some drawings, but somehow try to keep them looking futuristic without looking like a Captain Sky album cover.

Colors


Personae


Math


Integral site


Timeline


Glass jar


City


Authors/Related authors

We: Book Specifications

According to the ourhubbub link for scrapbookers, these are the required image sizes:

Cover: 3580px x 3025px

Pages: 3325px x 2651px

Pentacular measure selection from Kuler:

More colors:

Saffron

We Mind Map:

Brave New World around the corner

I just got a banner ad in Yahoo mail for a situation where "Child forgot his homework"? "All you have is tears?" "Here's a drug for you..." Do people really think this is the right path? Every medication has consequences. Here's why people need to read science fiction... to at least hypothesize what the effect of their actions might be.

We: Fonts

Looked at some futuristic fonts for the We book. I settled on these:

Circuit

Pole Position

Republika

Rough Draft

Space Age

Also, it would be interesting to look at treating the fonts with a "lightsaber glow", similar to: this video intro.

We: A Visual Interpretation

For my graphic design course at MCAD, we need to create a printed media composition. We have only two more weeks to create the final project so I figure I'd better start working on it. I'm not that creative under pressure, I need time to weed out the bad ideas and tweak the good ones.

I wasn't definite on a direction so I gave the instructor, Jenny Tondora, several ideas to play with. She responded that she liked the idea of the book/perhaps droid version of an artistic word book on the concept of Zamiatin's We, a ground-breaking distopian novel written in the 1920s.

I've long thought this would be a good novel to make into a Motion Picture, but the pitch I need is to develop a storyboard to go along with a screenplay for it. With this assignment, I don't have time to develop the whole storyboard, but perhaps instead come up with the pitch, the narrative preface to what the work is about.

First step: finding my copy of We I received two years ago at Christmas from Quincy (One book in a house full of books is sometimes time-consuming and stressful).

Second step: installing photoshop/tablet software on the laptop.

Third step: thinking about the kinds of layout I'd like to do.

Creative/artistic elements

1. Words/quotes - quotes from the book, settings, persona, literary comparison to similar works

2. Silhouettes - images silhouettes of people white on black, strong contrast, using photoshop to

3. Ideation - do I have time to compose some brain maps such as using Freemind?

4. Font gathering/focusing/selection

5. Futuristic objects/buildings/cities

Futuristic Inspirations:

Furniture: Zaha Hadid

Cities: Ralph McQuarrie

Vehicles: Masarati - Trimontane, Masarati Birdcage

MCAD Design Week 3: Exhibition Poster Designs

1. Horizontal

2. Horizontal and Vertical

3. Diagonally

MCAD Design Week 2: Elements and Principles of Design

Using a shape and only black and white, illustrate the five concepts: similarity, continuity, closure, proximity, and foreground/background.

1. Similarity

2. Continuation

3. Closure

4. Proximity

5. Figure/ground

MCAD Design Week 1: Examples of Good and Bad Design

1. Road Signs

a. Good. In these standard road signs, the meaning is clear. Something is happening which affects the road. The road is represented by the solid black line. In the first merge example, there are two before and one after. Clearly action must be taken to merge.

b. Bad. In this version of a merge sign the road is now indicated by its boundaries, and the insinuation is that the flow inside is constricted. But using the same metaphor as the good signs will lead your eyes to believe the model where some of the roads get just a little closer together, but no worry, they don't actually meet. The no passing zone sign is redundant in all situations since the same message is already indicated with solid or dashed yellow paint lines on the road.

2. Web Sites - respecting the visible area

a. Bad. These are two websites don't respect vertical or horizontal screen real estate. In the first, x10.com's bizarre home page delivers a whole web site of information in a single bottomless HTML stream rather than navigating to other pages for different topics. Www.anthem.com is another bad site but it takes the horizontal approach to unlimited screen real-estate. It's a common mistake by designers/developers blessed with dual large monitors to think their customers want or can afford to lose 100s of pixels of screen width for each website category color band. The most critical link in the website for a customer, the login, is far away to the right, probably offscreen on an Aspire One.

b. Good. I like BBC's sites for their clean look and feel. Radio1 has a slit-screen photograph feel that gives a techy edgy feel, a symbol which carries over as an animation to their player/streaming component. The colors are a little flamboyant but they harmonize. Catering to the customer, the dj/show search link is ready available at the upper left.

3. Web sites - consistency, fonts

a. Good. I saw this font on a student organization's mural on the Washington Bridge: Innovative Engineers. To me, that font is pure tech. It's inspirational like a Science/Tech/Eng/Math STEM counterpart to those groovy 60s music poster fonts.

b. Bad. CIA Factbook:The CIA releases a handy wealth of information about countries in the world. This is a great site for consise information - determining population, currency, politics, religion, etc. I like the site information, and the style within the "c-clamp" area.

There is not a consistent style for the site. There are over 5 fonts used on this page alone. To the left and right, an attempt is made to make the sidebars 3-dimensional. But this falls short as the shadow changes from the left to the right side.

Is usability part of graphic design? If so this is also an issue I (currently) have:

In the last couple years, they decided to change the layout of the page so that when you first come in, all the information is hidden. I call this the IMDB approach. IT COULD be easy to scroll, search using your browser for information on the page, but because it starts out as hidden (unexpanded) you can't see it. If you have a slow enough/wireless connection you can even see it for a second before they use script to hide it.

Programs as vectors

This was brought up because someone mentioned the expression problem in a talk today about an introduction to closure.

Swung over to remembering this concept I expressed at Lawson Software, that of a complete, working program as a vector of components. Each component has a different version, expressed as a number line in the version repository. We could manufacture different libraries in the framework where every program is layered on top of the libraries it requires.

FOSD cubes are a software engineering expression for a multi-product line. My belief is that this is similar to a multi-objective programming model. In order to provide the best "next release" of a program for a client, they could express their interest based on their objective function - they want the latest, best version that meets the "works best = known tests pass" for a particular line such as the HR system. You would then use multi-object programming techniques to find the preferred solution.

URL archiver/proxy (ElephantUrl)

Here's my deal, twice today some links that I had for documentation went away, one because of a partner and one because of Oracle's biomass oozing over other companies.

So this is my idea, have a web service that acts as a proxy go-between and archive recovery tool for your important links. It combines some of the idea of the bit.ty and tinyurl sites, but what those lack is a way to see what the linker really intended.

You, the linker, found some important information. Maybe it's an API for some code you're working on, or maybe it's someone's blog post that solves that problem you were having today. Either way, you end up linking to it on your blog, or in your Javadocs with an @see flag. The problem is, easy come easy go. There's nothing you can do about the host. They might belly up, or be absorbed into the Oracle ooze and have their links redirected into a oblivion.

The proxy stores the current contents at the destination site. Clicking on the proxy link, brings up a dialog which has some options, but goes away after a while. Meanwhile, it continues to the originally specified link. Now, if the link has been modified, lost or redirected, you, the user, can choose instead to bring up the archived link. (It may or may not have been webdevilled so the images, css, js etc would still work). Otherwise you can click on the dialog and confirm you got there ok.

Hand out the elephant url, because, an elephant never forgets.

Nagios

R2-D2 integration with Nagios.