I’ll use this post to keep a running summary. The background can be found in the prior post: Alpha/beta site (todo list at the bottom of the post; will be moved to this post).
Essentially, these entries deal with changing the website using HTML/CSS, for now. There is one bit of javascript (more of this later, including a look at the different language options). Right now, I’m only working with the Sea Monkey editor and a simple text editor. Google has some edit apps now; I will try their HTML and CSS editors.
Aside: The world is moving fast; we all see technology running leaps and bounds. How do we make sense of all this? Does pulling the ostrich act cut it? Is exploiting the situations more than short term (oh yes, must be nice to roll in the dough, but there can be much discussion here about near zero and meta issues)? Ever think about truth engineering (essentially, knowing truth engines (all types) and using this knowledge)?
— Historic list (will reopen when more modernization work is done) —
04/21/2015 — Did Google’s Mobile-Friendly test.
09/03/2014 — Redid the header and color scheme.
08/26/2014 – Almost done with another JQuery lesson (did one earlier, was not motivated to follow through – all sorts of philosophical issue to discuss – albeit eight years after the horse was let out of the barn) on Codecademy. Taking it easy; what’s the hurry? The world is too rushed. So, what might we do with manipulations of the DOM that is interesting from the points of view that we are trying to develop here?
07/31/2014 – All done except for the Sources page. Also, have a FB page for announcements, plus.
07/18/2014 – Wikipedia page references (for one thing, using Vol. III, No. 2) being updated. About Us and 400ths being reworked. … Main page changed (Beacon issues migrated to new format). … Almost ready to get back to content.
07/16/2014 — Pushed up changes to many pages; created new page, devlog. At some point, will assess status of the pages (as in, count remaining ones to be done) and estimate some end date.
07/14/2014 — Clipping works with “position:absolute;” which will create tradeoffs, but it will work (that is, only use html/css). Will match this image (hopefully, position will look okay for most browsers). — Posted a little later, example banner in place for review. … WebGL looks very interesting and capable.
07/14/2014 — Filled in the table of Gardner’s Beacon issues. I like the column look by Volume. Earlier Volumes had more entries. … Started to look at using CSS shapes for the header/banner which is now an image. What comes up is clipping which works on images. So, started to look at Canvas and found this tutorial: 31 days of Canvas tutorials. Nice. The comments show that the “religious” wars of computing continue unabated. Perhaps, that drives the creativity. … Looking closer at the javascript approach, it’s tedium revisited (like 30 years ago?). Which then, brings us to newer efforts, such as WebGL. Per usual, the questions revolve around who can use and where (as in, we want to be able to support the widest range of browsers and users – as in, not following Apple’s exclusivity – where would Thomas sit in these arguments?). Official site for WebGl.
07/12/2014 — Added flyover menus on the navigator bar (About us –> Gardners and Gardners, etc.). Also, started the redo of Gardner’s Beacon (see Vol. IV, No. 2). For the collection, trying to use hover to provide a multi-select menu (issue, post, PDF). We’ll see how that goes. The titles are more visible. … Next up, there will be some redo of other pages and, then, a stop/review to see if some adjustments ought to be made before committing to total distribution. … Learned a lot. There has been a whole lot of activity by all sorts of folks. At first, I thought of it as much ado about not much (permutations, even if enumerated, do not say much). However, just using HTML/CSS provides a lot. … Which reminds me of the graphic redo (using shapes). That ought to be interesting.
07/10/2014 – After getting the CSS to settle down (lots to talk about here) and tying the test with the production, I went to look at fixing the image at the top. Also, started to look at menus. So, the fix was a simple one-line (z-index:10). Now, contents slide under the image. The footer fix did not require that (because it’s a div and not img?). On the menu, put in the text that will be in the menus. Thinking of having them on the side, invisible (float required?).