Under Construction

Click here to view anyways
  • Previous Page

  • Page 4 of 4

  • Table of Contents [Show]


    Forecast

    The "weather-data.php" file that is generated by the DarkSky script actually has a lot more data than what is displayed on the homepage, so I gave that data it's own page. Even then, darksky provides 50 hourly forecasts and I only use 7 (spaced in 3 hour increments), so as not to be overwhelming. The content is extremely standard and predictable, so I basically just copy and pasted the current weather code and made some small changes for the daily reports, like adding a neat-o phases-of-the-moon widget entirely with CSS.

    Resume

    The resume actually hails back to an earlier website that I made years ago called johnsdesk.ca. That site was cutesy, gaudy and a horribly skeuomorphic representation of what my desk might actually look like. To my chagrine Archive.org did save just enough of it to make it look even worse than it really was. When it was live, each of the images had an "active" alternative which replaced it and they all lead to pages that were similarly atrocious in their own ways. Remember, I said I was the runner-up to that web development job... It ways basically the "Microsoft Bob" of websites except uglier and even more useless. That said, I mostly kept the fundimental design of the resume page.

    I rewrote the functionality of that page and it is now set on a tame grey instead of woodgrain, but the "dosier" concept with the headshot and tabs is still the same. It did actually get me to a second interview, so it can't be too horrible, right? Functionally, the main content used to load with an iframe which made the "paper" scroll independently of the actual webpage; so that's better now. One thing I do want to add to this is a URL argument with a unique id for the coverletter. That way there is default content page for anyone who finds it in the menu, but I could email a link to a potential employer with a coverletter specifically for them. If I get itchy feet this might become a priority, until then it's just a thought.

    Currently a URL argument is used to determine which tab of the resume is active (with the absence of one meaning the coverletter). The contents for each tab are pretty much defined independently. Given that it will never exceed more than a few pages and the coverletter is always a special case, it doesn't make a huge amount of sense to bother abstracting away anything other than the stylesheet and tabbed paging.df

    Easter Eggs

    I pointed out earlier in the explanation of the domain name that you can click the domain name or logo in the header to explain the fact that the domain matches my name if searched as a regular expression. I also described in the article discussion that there are a couple of other arcitectural components that are not prominently exposed, but which can alter the user experience. These are some that are provided by URL arguments:

    • I described the "offset=X" argument in the the Table of Contents and Pagiation sections as the mechanism used to determine where to start rendering. You can select any section you want and it's mostly going to work, correct something out of bounds or print an error.
    • A similar feature that you wouldn't stumble accross accidentally is the "items=X" argument. This will display an alternate quantity of sections from that offset. Using '*' will show everything.
    • Articles also necessarily have a "topic=X" argument which tells the system which article directory to grab content from. Because only articles with a meta.php file will get loaded into the article lists, it is actually possible to find "unpublished" or "hidden" articles if you know their topic identifier. An example of this is the "About Me" article that is linked from the home page, but not otherwise listed.
    • There is also a "debug=1" option that is currently understood, but has little utility. It is required for some error messages that I use during development, but otherwise any possibel errors that I have written debugging for should pretty much be wiped out by the time it gets to production. There are also error that don't require the debug argument. For instance, try to define an offset or items argument that is not an integer and it will yell at you.
    • If you hit an error page, for example a 404 you get a random fullscreen image from the Horsetheif Canyon, AB gallery. It provides the error and lets you dismiss all of the window-dressing to see just the image (and a little X to get the window-dressing back).

    To Be Continued...

    The site is relatively stable, so development has slowed but it is still ongoing. Updates are pushed to the site quickly when written, but you can also view the develpment branch of the site by specifying the 'dev' subdomain. Some things I'm thinking about adding are:

    • More debugging code! Included the output in a block at the bottom or top rather than in-line
    • Duplicate "items=*" for list pages. Currently this only works for articles (but I don't have enough to hit the page limit yet anyways).
    • Code to interpret a "lang=" argument. I plan to translate some articles to French as I'm currently working to improve that skill. However my French is still too bad to confidently add that. I also gave a decent effort to learning Esperanto and might translate things to that if I get really bored. This would require a separate "meta.php" and "content.php" file but other than that it would not be terribly difficult to select which file to load, fallback to English if necessary and suggest alternate languages on pages that provide it.
    • The initial revision of this site was written almost entirely in JavaScript (Proof) including a lot of wizz-bang flash stuff. I decided to refine everything down to just the essential functions (currently, that is this single file and a couple of things in-line). One flashy thing I did kind of like in moderation was weather effects to the home page. Now that there is a dedicated forecast page, I might add those back there. Some of this was ripped off from another site which also goes against the rest of the site, so if I add it back, it will be simplified and hand-written. I'd have to refresh my JS a bit for the precipitation, but cloud and sun are trivial with CSS.
    • For "offset=" greater than the number of elements in the array, correct to the total number minus the item count (or 0).
    • Accept an offset equal to the section heading text. Determine the offset to that heading automatically. This would allow for easier linking to relevant content that will remain accurate if the index of that section changes.
    • Optimize formatting in Firefox Reader View (I don't care about whatever browser you use).
    • Set variables equal to the current article topic for easier internal linking. This would be easy, but it would also mean going through and updating all of my old URLs. I'll probably stop being lazy after the heading text link feature gets added.
    • Redirect non-existent "topic" to either applicable topic list with an error instead of to 404.

  • Return to projects list

  • Past Projects: Commandline 2048 Game