git Your Project on GitHub (calculator)

If it’s not one thing, it’s another.  This is life; this is coding.

So, my calculator didn’t trim rightmost zeros.  It does now.

It wasn’t accepting a decimal point on zero.  It does now.

It also was allowing miscreants to press the ± button on operators and causing all manner of havoc.  You can still break it by doing things that aren’t natural, but most natural things are covered.

And the repeated application of = still works.  I’m about ready to turn it in. So, that meant converting it to 3 files and putting it on my local drive and then gitifying it. This was an interesting process. I found out that my buttons were too big (fixed) and too close together (fixed) and a few other nitpicky stuff.

Here are the steps to gitifying  a project from the command line (I iterate, I am totally lost with GUIs):

  1. Do the project. This should be a no-brainer, but you look rather silly with empty stuff on the repo.
  2. Make sure you have a git. Installing a git is beyond the scope of this document.  FreeCodeCamp uses GitHub. This is for Win/Mac users.  I have a dual boot capacity so I run the GitHub software on my Win partitions.  I won’t tell you what options to use because I operate command-line style.  I reiterate, I am totally lost with GUIs.
  3. Put your project in your special place. My special place has a long name and a short name.  The short name is a symbolic link (I run Linux and a symbolic link is a fancy name for a shortcut) of gitstuff in my home directory.  I make a directory for the new project in gitstuff and I can always find it. So, in this case, it’s ~/gitstuff/calculator/ I have three files there at this point
    • index.html
    • style.css
    • script.js
  4. Make a file.  Directions on markdown can be found on the Markdown Cheatsheet.  I shouldn’t need to tell you how to do this (after all, you made those other three files).
  5. Make a file.  This is trickier. You can get one from  Mark it down.  Make it your own.  You will now have five files in your directory.
  6. Initialize your git. Type git init at the command prompt in your project directory.
  7. Go to GitHub and start your project. If you’re not logged in, log in and click the [Start a project] button.  Fill out the fields. When you are finished, click the green [Create Repository] button. The page asks for the following:
    • Repository Name: this should be short.  Mine is calculator
    • Description: this should be a little longer but not much, explaining what it is
    • Public/Private: unless you pay, it’s public.
    • Initialize with a README: do NOT check this, as you made your own in step 4.
  8. Go back to your project folder and do a remote add.  You need the URL from GitHub.  It’s in the box at the top of the screen.  Type the command git remote add origin followed by that URL from the box.
  9. Add your project files to your local git. Type git add . at the command prompt in your project directory.  Don’t omit that period.
  10. Commit your work.  Type the command git commit -m “initial commit” at the command prompt. The stuff in quotes is your commit message.  Since this is the first one, that’s what you say.
  11. Push it to GitHub.  The command for this is git push -u origin master and it will ask for your account name and then your password. The account name will display, the password will not.

After all that, your project is now on GitHub.  If your project is a Website type thing (like the calculator) people won’t be able to view it as a page unless you do another step.  Go to the Settings tab and scroll down to GitHub Pages. Under Source choose Master Branch and click Save.  

This sounds like work, but it is worth it.

pomodoro: the clock stops here

Preparing to turn in my calculator means I can turn my attention to the next project.  Build a Pomodoro Clock. This will require me to learn new things, like time-based anything and how to cause my HTML to emit sound.

But like any other HTML/web project, the first part is figuring out what it will look like. Here is a screenshot of my Pomodoro Clock.Incurably retro.  I got the idea from someone who mentioned they had a seven-segment font they were using for the calculator project and I thought how totally awesome that was for a clock.  Now this font, being truly seven segments has no plus sign or colon.  So the buttons (and the text) are in the Roboto font. which is how the real world deals with seven-segment stuff. Which is to say, they don’t use it except for the actual digital display.  What you can’t notice from the screenshot is everything is in rem not px.  This meant I had some artifacts and issues trying to make the actual clock part of the display work.  I resolved them with Flexbox. You’ll find out more Thursday.

The person who helped me with the flexbox also gave me a link to a stackoverflow discussion about javascript timers.  It’s interesting and relates well to stuff I saw on CSS Tricks.  The key to using anyone else’s code is that you have to understand it and not only how it works but why it works.  If I can’t, I’ll look other places.  The synthesis of the two sites is working for me in understanding that a function that counts time based on milliseconds will drift from the actual time and that you may want to adjust for it by checking against the real time now and then. The main issue seems to be how often do you need to do this to stay on target vs having extra overhead.  I’ll know more Thursday when we meet again.

calculator: the chain gang

Let me be blunt.  The calculator is not a difficult project once you’re aware of the eval() function that takes a string and treats it as an arithmetic expression and evaluates it. If I knew the name of the person who mentioned it, I’d share.  The trouble is, it was a toss-off comment in a reply to someone else and I happened to be paying attention.  For the record, attention is good.

I hang out in the gitter FreeCodeCamp room quite often and this sort of thing is there, going on all the time.  Someone posts a problem, whether it’s with a challenge (“how do I nest my image element in an anchor tag?”), an algorithm (“can someone check my Roman number code?”) or a project (“my Twitch viewer shows the same channel eight times instead of showing the eight channels from my array”) and others offer help. Usually, the problem is spotted and resolved (often the person posting sees the issue as soon as they shared it). Someone else’s calculator issue was solved by eval() and I was watching.  This was back when I was doing random quotes or something.

The difficult part of the calculator for me was how do I make something that looks like a calculator in HTML and CSS. The answer is by looking at someone else’s calculator.  Google Images to the rescue.  I found the OSX calculator icon. It has buttons on it for Clear and ± and memory management stuff in the top row that I don’t need. So if I delete the top row, I have a basic idea of what a calculator should have. If you look at it side-by-side with my calculator, you can see how it was inspired by this one. My phone calculator looks like someone was too lazy to bother making it look like it wasn’t an app on a phone. So using that as a guide would have given me something really ugly and not like the project was looking for.
OSX calculator icon phone calcmy calc

The colors for my calculator are courtesy of Computer Hopes HTML Color Codes & Names page.  I found the red for that button as a trinary color for the blue of the other buttons. You can find trinary colors by typing or pasting the hex code for a color in the box at the top. I got the display box color by sampling the color from the OSX calculator and averaging it. It took a bit of trial-and-error to get good button colors with my faceplate color.

But that’s only part of it, there are also fonts. For the display, I wanted a font with something in the zero.  A slash or dot or something. But not for the buttons. Zero on a button should look empty and the C should look reasonable.  So I hit up Google Fonts.  I specifically typed in the digits and the key signs (so I could see what the keys would look like) and told it to make that be the sample for all of the fonts.  Then I said I only wanted monospace fonts. And alphabetical because I was looking for specific things, not popularity. The fonts I chose were Abel for the the keys and Allerta for the display. I liked the look of the C in Abel and the fact the 4 was closed.

So, on to making it function.  I’m sure there’s a better way—there always is—but what I did was made a click event for each button and then handled it. For the digits, it was easy—check if the the entry was zero—if it was, replace it with the number, otherwise, add the digit to the string for the current number.  Decimal point was tough—you can only have one per number.  And signs meant I had to peel off the current number and make a new one.  And then the equals meant, run eval().  Okay, that all worked so I took it to gitter.

And someone said it didn’t “chain”.  Now, I could type 2+5*4  and press the equal sign and get 22 so I knew it worked.  But that wasn’t what they meant.  They meant, if I pressed equals again, it should repeat the last operation so I should get 88 (22 * 4) the next time, and so on.  While I was fixing it, we got into a side conversation about how I don’t generally use a calculator so I was unaware of that expected behavior.  Then, right when I had typed “try it now” they typed, “don’t worry about it, mine doesn’t do that, either,” and I had to laugh because, well, mine does it.

Here’s how.  I’m already keeping the current number separate from the rest of the current expression.  I have to so I can use the ± on it.  So what I need to do is grab the last operator from the string (it will be the last character) and combine them and put that in the chain:

$("#eqButton").on("click", function(){
if(curNum != ""){
// if the expression isn't empty, evaluate it
curResult = eval(curExp + curNum);
if(curResult === 3/0){
curResult = "0 Divide Error";
chain = curExp.substr(curExp.length-1) + curNum;
curExp += curNum;
oldExp = curExp;
// they pressed = again
curResult = eval(oldExp += chain);
curNum = "";
curExp = "";

It’s still on CodePen but will be moved to GitHub before I turn it in.  The links on the right will always be current.

weather: wrap-up

If you look at your calendar, you’ll notice I’m writing this on not-a-Monday and not-a-Thursday. This is a bonus blog, made possible by my finishing my calculator which is the first advanced JavaScript project. Because I finished it so quickly, you won’t get to read much about it.

Weather.  I slept and woke up and it still worked.  I did some tweakage, found a Google font I liked (Cabin) and rewrote the “created by” part to clearly identify my weather app as a FreeCodeCamp project. Then, I had to put it back on GitHub.  When I typed git init it said it was re-initializing. Since I din’t know if I wanted that, I did an rm -r .git and then tried again. As far as GitHub was concerned, it was a new repository so I had to do the new repo things, but as far as my end was concerned, I had a and a and everything so I was ready to add, commit and push.  So I did all of that.  and it’s all there, now.  Except I forgot to edit the so it referred to things that were untrue, like DarkSky. When I looked at the repo, I immediately saw the problem. And fixed it, followed by an add, commit, and push.

You can look on the side and see my weather app in the links.  Or you can go here. To see the repo, go here instead.  And  notice the calculator.  It’s a CodePen but that will change before I turn it in.  Probably I’ll write about it Monday.

weather: conditions are changing

So I asked around and determined that the weather source for the FCC pass through is OpenWeatherMap.  And the first thing I found out when starting work today is that I got an error message when trying to connect to it.  As always, “it used to work” only gets you so far in life, and I hit up the gitter rooms looking for help.  @Masd925 was there for me. It seems I wasn’t making the call right. Here’s the relevant line of code:

[js]url:”” +myLon+ “&lat=” + myLat,[/js]

I had not been “plussing” my variables and that had been okay but between my last post and today, that became broken.

On to condition codes.  When we left, I was searching for condition codes so I could use my icons instead of the sorry icons shown here with their associated weather conditions.  These icons are 50px by 50px PNG images. Like this one for a thunderstorm.


Jussayin’.  These are not real icons.  But hey, there are weather actual condition codes, like for clear skies or thunderstorms or whatever. I’m in luck, right?

This turned out to be a can of worms.  First off, DarkSky had had condition codes that included day or night so it would say, for example, “clear-day” as the condition description and I could then assign a sunny icon to display or “clear-night” and I could assign a moon icon.  Well, OpenWeather has a numeric code, in the weather[0].id field of the data object that corresponds to everything from “clear sky” to “hurricane” but it is not so kind as to tell you if it is day or night.  It does however, give you the sunrise, sunset and current time (in seconds since January of 1970 but who cares?) and you can thus figure out if it’s dark or not.  It’s only one more step, right?

Okay, achievement unlocked! I can determine which icon to display and I can use more of my wonderful weather-icons icons (which are actual icons, not PNGs) and thus respond to font-size: settings in CSS and otherwises comport themselves with aplomb. And I mean more because with OpenWeather’s coding system, there are so many more weather conditions that can be displayed.  Some have only one or two 3-digit code and others are ranges. I try to grab the special cases first for ease of coding, but not all of them, as the 800-level codes are odd.

You saw the aside on wind-bearing.  This is how I do stuff.   Here, without further apology is the mondo if structure for the condition codes.

// first some special cases
if (icon == 962) { wIcon = "wi-hurricane";} else
if (icon == 902 || icon == 781) { wIcon = "wi-tornado";} else
if (icon == 906 && !isNight) { wIcon = "wi-day-hail";} else
if (icon == 906 && isNight) { wIcon = "wi-night-alt-hail";} else
if (icon == 711) { wIcon == "wi-smoke";} else
if (icon == 731 || icon == 751) { wIcon == "wi-sandstorm";} else
if ((icon == 611 || icon == 612) && !isNight) { wIcon = "wi-day-sleet";} else
if ((icon == 611 || icon == 612) && isNight) { wIcon = "wi-night-alt-sleet";} else
// now the general cases
if (icon >= 200 && icon <= 299 && !isNight) { wIcon = "wi-day-thunderstorm";} else
if (icon >= 200 && icon <= 299 && isNight) { wIcon = "wi-wi-night-alt-thunderstorm";} else
if (icon >= 300 && icon <= 399 && !isNight) { wIcon = "wi-day-rain-mix";} else
if (icon >= 300 && icon <= 399 && isNight) { wIcon = "wi-night-alt-rain-mix";} else
if (icon >= 500 && icon <= 599 && !isNight) { wIcon = "wi-day-rain";} else
if (icon >= 500 && icon <= 599 && isNight) { wIcon = "wi-night-alt-rain";} else
if (icon >= 600 && icon <= 699 && !isNight) { wIcon = "wi-day-snow";} else
if (icon >= 600 && icon <= 699 && isNight) { wIcon = "wi-night-alt-snow";} else
if (icon >= 700 && icon <= 799 && !isNight) { wIcon = "wi-day-fog";} else
if (icon >= 700 && icon <= 799 && isNight) { wIcon = "wi-night-fog";} else
if (icon == 800 && !isNight) { wIcon = "wi-day-sunny";} else
if (icon == 800 && isNight) { wIcon = "wi-night-clear";} else
if (icon == 801 && !isNight) { wIcon = "wi-day-cloudy";} else
if (icon == 801 && isNight) { wIcon = "wi-night-alt-cloudy";} else
if (icon >= 802 && icon <= 899) { wIcon = "wi-cloudy";} else
{ wIcon = "wi-na";}; // if all else fails, display a giant N/A
iconStr = '<i class="wi ' + wIcon + '" style="color:' + iColor+ ';"></i>';

That iColor is my custom color I wrote about last time.  That gives me a color for the temperature and the icon based on the Celsius temperature. It has a mondo if too.

Next time, I submit it and push it to GitHub (in the other order, though). You always want to try to sleep at least once before turning in code to make sure you caught stuff. And yeah, that’s not always doable.

weather: switching to the FCC

I had a wonderful weather app. Here’s a screenshot:
You see it was powered by DarkSky and it has a temperature and an icon for the weather-type and they’re a color. That color changes based on the Celsius temperature (as per the FCC user story:

User Story: I can see a different icon or background image (e.g. snowy mountain, hot desert) depending on the weather.

I found the colors on a site called Color Brewer 2.0 and they had several kinds of color sets to choose from and different sizes of color sets.  I found one that had ten colors, which I figure is plenty.

One teensy-tiny problem, though.  My API key was showing.  This is a unilateral no-no.  People can steal your key and then make a zillion calls to the API in your name and rack up a bill you have no way to pay.

There are two approaches to take here.  One is to set up a proxy so that my API would be kept secret. The trouble with that approach is that not everyone has the means to implement it and I don’t like being an elitist.

The other approach is to use the new(!) FCC pass-through.  This is new since I did weather before, so I didn’t have it available.  I do now.  Trouble is, all the fields have different names, and, they want a GET request, not $.getJSON (I believe that’s what the words mean.  It’s okay, I did that for my wiki-viewer, so I know how it works.

They document the fields, but how that actually works in practice is why the ghods invented console.log().  I absolutely spent a bunch of time verifying that stuff was what I thought it was.  And it turns out humidity is already a percentage and not a decimal number (unlike DarkSky, where I needed to multiply by 100 to get a percentage).  Stuff like that.  The temperature is Celsius. I’m still uncertain of the units for wind speed because, at the current time, conditions are calm and with no wind, there is nothing to verify against another source.

The icons are tricky.  There are icons provided by the API but I have the beautiful set-up I’ve described.  I don’t want to lose that so I need to know what the ranges of weather conditions are so I can populate one of my mondo if structures with the right icons.  This is a good stopping point for today and hopefully, by Thursday, I’ll have an answer.

an aside on weather: Wind direction

Most weather APIs don’t convert the wind bearing into a cardinal direction. That’s okay if you’re a pilot or something where you’re used to figuring the bearing, but for the rest of us, what does wind bearing 142 mean?

I found a handy website (there are probably many) that had a little graphic to show how the two mapped to one another here.  I used that info to make a killer if-structure to find the cardinal direction.  Here it is:

wDir = "";
if (wBearing >= 348.75 || wBearing < 11.25) { wDir = "N";} else
if (wBearing >= 11.25 && wBearing < 33.75) { wDir = "NNE";} else
if (wBearing >= 33.75 && wBearing < 56.25) { wDir = "NE";} else
if (wBearing >= 56.25 && wBearing < 78.75) { wDir = "ENE";} else
if (wBearing >= 78.75 && wBearing < 101.25) { wDir = "E";} else
if (wBearing >= 101.25 && wBearing < 123.75) { wDir = "ESE";} else
if (wBearing >= 123.75 && wBearing < 146.25) { wDir = "SE";} else
if (wBearing >= 146.25 && wBearing < 168.75) { wDir = "SSE";} else
if (wBearing >= 186.75 && wBearing < 191.25) { wDir = "S";} else
if (wBearing >= 191.25 && wBearing < 213.75) { wDir = "SSW";} else
if (wBearing >= 213.75 && wBearing < 236.25) { wDir ="SW";} else
if (wBearing >= 236.25 && wBearing < 258.75) { wDir = "WSW";} else
if (wBearing >= 258.75 && wBearing < 281.25) { wDir = "W" ;} else
if (wBearing >= 281.25 && wBearing < 303.75) { wDir = "WNW";} else
if (wBearing >= 303.75 && wBearing < 326.25) { wDir = "NW";} else
{ wDir = "NNW";};

It’s very readable and that’s important for something like this.  Sure, it takes a bit of time to set up, but it makes the direction so much more user-friendly.

“Hello, world,” is traditional …

… and why buck tradition?

Actually, this is the most difficult post I’m going to write because I have to initiate and there’s a lot to get going.

Kicking around my new digs here.  I’ve had blogs before but never anything where I shared my code.  I’ve shared poetry, fiction, recipes, menus and stuff, but never my code.  Yes, I’m repeating myself.  This is scarier than it looks because it’s one thing to show your code to the guy in the next cube and say, “Can you help me with this?” and quite another to go to the whole world wide web and let folks see how you do what you do.

As I say on my about page, I’m not especially clever, though I have my moments. Nor am I holding down the other end of the bell curve.  I’m somewhere in the middle, like most of you folks reading.

This first post is sort of a where we’re headed.  The first thing is weather.  I’m doing the FreeCodeCamp curriculum and one of the projects is a weather app. Okay, I did a Very Nice one, but it had an issue–the API key was dangling in the public view.  This is a no-no.  So I need to fix it.  The next post will be about evaluating my options and seeing how I want to deal with it.  And after that comes the actual dealing.  And anyone who wants to follow along, may.