learning javascript

My goal here is to get working code for a javascript actuated web page.

To begin, I don't need it to do much. The point is to have a page that uses javascript to do something. Then I can add features gradually.

Here are the specs:

When linked to, the page pops up in a 4x6 inch window. Somewhere in that area ... lower left, maybe ... is a group of four miniature sliders that control %rgb and density of the background color. Oops, too complicated. It's a form, and users can type in the values, comma delimited, and press the enter button. Even better, if the values get changed, the color changes. No enter button. We can just type direction in the body.

Remember, the idea is to teach coding. The page comes with a set of explanations of the code, and, of course, the code itself. We can run ads, too.

It's also possible this interface controlling background color can be patented. It's pretty questionable whether that's possible, or, for that matter, desirable, but it's something to look into, anyway.

scalable vector graphics algorithm

click to enlarge

next gen browser principles

1) deeply interactive rendering engine
2) persistence
...
3) automated permissions
...
4) runs in existing browsers with dhtml

time lines project

A Principle:

We create things on line ... a blog post, etc., etc.

Over time, we accumulate small seas of these. The problem is making sense of those collections of things.

The plan:

Create methods that show whole seas of things. The individual things in such an image can be inspected more closely.

This is another instance of something that is being treated, in the industry, as important but peripheral and nascent, and which I think is actually paramount and worthy of immediate focused attention.

Example:

A blog records events over time. Design the blogging tool to create a graphic representation of whole spans of time - months and years of time, even - as represented by all the posts. The content of individual posts may not be visible at all, or it may be visible only in a symbolic form. The deployment of posts over time, however, will be a vital form of information entirely in its own right.

activity record

22090730Th1558 ... note to Benjamynn about August Mapping Sonoma Conference

simple web publishing concept

... in my meditation moment ...
... I gravitate towards the idea of small projects ...
... a small project ...
... (see "project types") ...
... "what shall I work on?" ...

... I want the technology to sell small essays on the web, at very low prices ...
... I wonder if there's an established product for that? ...
... if not, how would such a thing be created? ...

desired characteristics
... all I need to use the service is a paypal account ...
... a subscriber deposits some amount of funds, say, $1 ...
... that person can then read, say, 100 of my essays ...
... my share of deposited funds is transfered to my paypal account ...

how to build it
... 1) software team
... a) first task: software that reads my e-mails, identifies paypal payments ...
... 2) team to direct and supervise business affairs

project types

... sometimes I think about ...
... building big applications ...
... with broad implications ...
... for computing generally ...

... other times I think about ...
... small or simple applications ...
... designed to generate revenues quickly ...

meditating on purpose

... the meditation ...

... the idea ...
... is ...
... create products ...
... by ...
... describing them ...
... in posts ...
... in such a way that my programmers can build them ...

... a hypothesis ...
... what programmers actually build is program components ...
... compact, discrete code bundles ...
... what corresponds to that? ...
... compact, discrete assignments ...

... at the same time ...
... components operate within a larger context ...
... that's the other kind of post ...
... statements about the general nature of an application ...