I am no graphics artists; however, I had an idea in my head as to what I wanted for my site icon and image on the landing page of my site. So I got Stephanie to take a picture of me in the shirt I wanted to wear striking a couple different poses.
The idea was to have something which ties them together which is the ‘thinking’ pose I’ve struck. I use me looking off to the one side for my favicon and to the other for the image on the landing page of my site with the idea of the things around me representing bits and pieces of what I enjoy doing (hobbies and otherwise).
This is another step forward in getting the landing page of my site completed to finish off the overall look.
It was fun to tinker with, but made me realize that graphics are not quite my forte! Lol.
I’m back! This project has been put on the back burner for a while, but now that it is fall and winter is soon to follow I can’t think of a better time to ramp up development again, especially since a new requirement for my tracker application has arisen! In chatting with my girlfriend, who is an avid quilter, would like a place to track the quilts she has completed. Currently this is done by taking a picture of the quilt and storing just the image on her laptop. She would like to keep track of other information as well, which lead to the addition of a Quilt table (first eight rows) and a Quilt Image Path table (remaining rows) including the following columns:
Primary Key of Quilt Table, Auto Increment (Also FK of QuiltImagePath table)
Foreign Key from User table
Will use inches as unit
Will use inches as unit
The name of the pattern used in creating the quilt
Who the quilt was made for
When quilt was finished
Total cost of quilt, includes materials, etc.
Path, with file name, to the quilt relative to project
Primary Key of Quilt Image Path table, Auto Increment
I thought this would be a nice addition, as it also adds in another technical element I haven’t had to deal with in any of the other items I am tracking. This is the addition of being able to upload, store, reference, and display an image related to the content. Also have to implement the functionality to delete a record along with corresponding images. I believe, without attempting an implementation yet, I am going to accomplish this by:
Storing the images in a folder on disk (this folder will be contained within my VS project so I know how to properly reference the folder)
Rename the file on upload after record is created to include primary key in file name for if need to cross reference for any reason, also ensures unique names are being stored
Storing the relative path (from project perspective) with file name in the database (FilePath column)
Implement deleting of a record to also include deleting of the file, on missing files skip and continue with deletion of record
My goal for the winter is to have an initial implementation for all the features I currently have slated for my tracker application.
After giving some thought into what I would like to have as a logo for my website I have come up with a design I am happy with. Since I understand the limits of my artistic skills in drawing, whether it be on a physical medium or digitally, I aimed to keep the design simple and yet capture me. I believe I accomplished this goal with the aid of All-free-download.com for the sport equipment graphics.
The central focus of my logo is my name, using the same Avero font as the theme, with my first initial in my domain expanded to my full name and keeping my middle initials. To capture my athletic side I represented the ‘i’ in my name graphically. I chose to make the base of the ‘i’ a golf tee and the dot a golf ball, as one of my favorite pastimes in the summer is golfing. I slanted the tee and position the golf ball off to the left to signify movement like teeing off.
With my initials the periods presented another opportunity to represent a little more me. The first dot is a tennis ball, another one of my favorite summer pastimes. I still needed to capture the technical side of me, as that is a significant part of who I am. With my second middle initial being the letter C and software development being a key interest I represented the dot as the hash character (#); a nod to programming and the C#.NET language, which is the first language I worked with in industry for any real significant period of time. Yes, checking out my resume you will see my first programming job was a summer at Tbaytel using VB.NET; however, that lead to a 16 month co-op at HydroOne, followed by a full time job upon graduation where the language is C#.
Once I had an initial design mocked up in Paint.NET I tested it with the Quark Theme and realized I did not like the look, in part due to the oversized graphic compared to the 300×80 pixel recommendation. I tried placing Devin W.C. on the top line and Ryan underneath (left aligned, then right aligned), but getting the golfing idea in made the graphic to high and so I moved ‘Devin Ryan’ on the bottom and W.C. on the top, right aligned, which I liked better. The graphic was still to large and I wanted to make sure my first and last name was the focal point, which lead to me reducing the font size of my middle initials and using bold for my first and last name.
Overall I am pleased with what I have come up with and will be sticking with it unless I come up with some grand idea :). So now that I have my main logo done that leaves my favicon, which I know what I want that to be, just need to get a decent picture to create it.
What is an application without some sort of storage mechanism behind the scenes? Above represents my database design which I am going to go into more details about.
At the heart of the database is the User table which stores user information and associates a reading list, measurement, or golf round with a corresponding user such that users can only see their data when logged in. This also makes it easy to track additional information by adding the corresponding tables which will then get associated with a user if I choose to expand the application at a later time. The other tables which stores, what I will call public data, is visible to all users to avoid duplication of data. This includes golf course information (Golf Course, Address, Region and Course Par Information tables) and book information (Author, Book, and what authors are associated with which book). The measurement and course par info tables each have a ‘special’ column. The measurement table contains a column called Type which takes a number from 1-4. Since this never changes the application can handle the numbers, rather than creating an additional static look-up table in the database. The number representation is as follows:
The course par information table contains a column called IsCNine to accommodate courses that have more than 18 holes with a format of: (Course Color)*( )(Front|Back). Where there can be 0 or more colors Examples of this would be:
This format allow for courses which provide 27 holes of golf as they typically have a white, blue, and red course, each with 9 wholes. I’d imagine both would also have a front and back nine. I have never played at a 27 whole golf course but I try to develop for future (or potential) possibilities.
I’ll explain the user profile dynamic content and dashboards text boxes in the diagram in my next post about the dynamic content and dashboards I plan to provide in my application.