Sunday, April 12, 2015

Installing Tor on Unbuntu

I am, by no means, an expert on either. But here's a little hint:

On Unbuntu, downloading Tor is not a 1-click deal. Here is a link to the commands you need to run on Terminal to get Tor working. It's not hard; just a few extra steps. I think the only big deal about this is realizing that Ubuntu is a little different.


Tuesday, February 3, 2015

Reflection of a string using Javascript and CSS

What I wanted to do was reflect a string in the same way CSS can be used to reflect an image. I didn't readily find a way to do this, although it is fairly easy. My code is here.

First, I have 2 divs wrapped in a container div. This is simply for convenience of moving the inner divs around since they need to stay "stuck" together for the effect of reflection.

Second, I used transform in CSS to rotate the original image to make it upside down but only applied this to the second div where the reflection occurs. At the end of the Javascript function, I make this upside down image the value of the second div which is otherwise empty.

Third, the Javascript code first stores the original value ("Heather") in a variable. This string is then broken up into a char array using charAt and stored in another variable. I then use reverse() to reverse the order of the chars.

Finally, my last task is to get rid of the commas separating the chars, so I use join("") and store the new string in a third variable. (Hint: Don't forget to use a separator or join won't get rid of the commas.)

Wednesday, January 28, 2015

CSS: Background and repeat

I was playing around with displaying an image via img src in HTML and background in CSS. I did this:
      #image_id{
width: 45px;
height: 45px;
background:     url(/*insert location of image here*/);
}

The result was the image displayed two times and appeared to be trying to display a third time, except that it was partially blocked by another image. I didn't have this problem using img src in HTML. Why?

Because background causes the image to repeat. The solution is to add:
        background-repeat: no-repeat;

There is also the option of having the image repeat on the x-axis or y-axis only.

I make no representation as to the validity or desirability of using background instead of img src. I do, however, hope to save someone a little time when they start going batty trying to figure out where in their code they made the image appear twice when they use background. Happy cascading!



Thursday, January 8, 2015

Simple marquee/ticker in Javascript/HTML

First, here is my code. Second, you can find code to make a marquee here or here.

Third, what I wanted to do was count the number of days since the Chibok girls in Nigeria had been kidnapped by Boko Haram. The main thing for me to figure out was how to count so that the number of days would be updated each day. I discovered Date.parse() and decided to subtract the date of the kidnapping from the current date using Date.parse(). That total is then divided by 86400000 because Date.parse() will give you the number of milliseconds since 1/1/70, so you have to convert that to days. I then used Math.round.

Finally, I just inserted the marquee code.

Now go make a ticker!

Sunday, January 4, 2015

Planning your first app/program

First of all, I'm talking about something more than "Hello Word". Second, I started this process in the fall and "completed" it at the end of December with not quite the result I expected. I learned a little more about Javascript and a lot about planning.

1) Don't get caught up in the details - survey the big picture first:
    I wanted to create a real estate app. I spent a significant amount of time researching how to access the local MLS database. What I finally discovered was that I couldn't get access to the database unless I had major financial backing.  But before I spent any time researching the database, I should've considered what OS my target (an individual in this case) used. It was a Mac. I do not own a Mac. I do not intend to own a Mac. You may naturally conclude at this point that I do not know Swift and don't plan on learning it anytime soon. Hmmm. What to do.

2) You're about to spend $$ - do you really need to?
     I found a solution to my Mac predicament. It would be a small investment but if I could make a cool, functional, pretty app, it would be worth it. Again, I spent a lot of time learning about the solution in question. Then the reality of car tags, HOA dues and bar dues hit me. I wondered if there was another way that wouldn't cost as much. Free would be good.

3) Don't overcomplicate:
    Yes, there was an option. It's called Javascript. It'd didn't accomplish half of what my original app idea would do. However, it would accomplish one essential function that was the most important part of all. I got that part right - if you can't make your app do everything, focus on what is absolutely essential, the real reason for your app existing in the first place.
     What I did not get right is, once more, spending hours upon hours, figuring out how to do a particular task with Javascript. I don't mind that I did this. I learned about uploading a csv file with Javascript and I spent some quality time with regexp. In the real world, however, customers won't wait while you spend a few months exploring options in depth without exploring the real potential of those options.
      After spending quite a lot of time overcomplicating, I realized my end user already had half of what I needed - a pivot table that I could import with html. In the end, I made a simple web page that would display multiple pivot tables and accomplished what I intended in the beginning. It was not as great as my original idea, but it was free and that increased its value significantly under the circumstances. It was, in fact, prettier and more professional looking than the result would've been with my pre-Javascript and Javascript solutions.

As I embark on my next project, I've learned to flit around. I bounce from topic to topic because I inevitably hit on something that tells me I need to study this less and that more. I also am keeping in mind the big picture and I'm trying to do a better job of connecting the dots in advance.

Saturday, December 20, 2014

Use Javascript to upload csv file and chain replace method

Uploading the csv file was the easy part thanks to this code. (Just make sure you have appropriate code to display it since the author just uses console.log.)

Once the csv file was uploaded, my goal was to select certain rows and then, from those rows, select certain fields to display. We'll start with how the code to upload the csv file works.

Uploading the csv file:
Mounir Messelmeni's processData(csv) method takes the csv file you select as an argument and stores it in a variable as a string using split(). Once the string is appropriately split, the code then uses nested for loops to first split each record and then store each record as an element of an array. (You'll notice my code is slightly different regarding the separators I used.)

Regexp patterns
My problem was that I needed to access the individual fields within the records. That sounded a lot like accessing elements in an array, except I wasn't dealing with an array but an element in an array. Naturally, my first thought was to make each element its own array so I could access the fields as elements within the new array. You've probably already guessed the problem. When I created the new array and assigned an element to it, that didn't split anything up. I just had an array with one element.

I then considered separating each char and storing certain ones into an array and that array would then become an element in another array. That made me tired thinking about it. Plus, I still had the issue of figuring out how to target certain chars.

I also thought about saving the array element containing a record as a string, separating the string, and based on the separation, creating elements for an array. But I finally decided it was just easier to search for patterns. I am not claiming this is the best way, just that it is one way.

My code starts by storing lines.toString() in var x. I then create two patterns. (The csv file only contains 2 fields per record. For demonstrative purposes, text in both fields will be replaced.)

I also created an empty string, newstr which is then assigned the variable "x" with chained replace methods. The value of newstr becomes the value of the element with the id "list". I include an alert to show you the value of x before so you can compare that with the replace values.

The full code, including the csv file I used, is here.

Wednesday, December 17, 2014

Java command line

It's a basic concept, but it threw me at first. How do the command line and a Java program you wrote in an IDE interact?

First, the command line:
     a) Save your java file in a text editor as YourFile.java. Read this for more details.
     b) Get to the command line. If you're using Win8, for example, go to the Start menu and either type in "cmd" or use search and type in "command".
     c) On the command line itself, first change to the directory in which you saved your file. (See page I referred to above.)
     d) Set the path. The page referred to above addresses this but it didn't work for me. This is what worked for me. Proceed with caution.
     e) Compile by entering this at the command prompt - javac YourJavaFileName.java
     f) Run the interpreter by entering this at the next prompt - java YourJavaFileName command parameters
     ex. java InvestmentFile calculate .04 10 5000
    //calculate is the command;
   //.04, 10 and 5000 are the arguments

Entering the command: Just make sure the user knows which command to enter in the beginning and follow up in case they still enter the wrong thing.

if(user enters right command)
{//code}
else
{//tell them what to do or use a try-catch block instead}


Now, how do the parameters in the methods connect to the arguments on the command line?

Let's assume in the example above that .04 represents the interest rate, 10 represents the number of years and 5000 represents the amount invested.

Let's say you have a method that has these 3 things as parameters. Here is how you'd normally write the method:

public double calculateROI(double rate, int yrs, double money)
{
    //code
}
 But for the command line, here is how you write the method:
public double calculateROI(args[0], args[1], args[2])
{
    //code
}

Look familiar? Yes, finally, we see a point for those args in the main method.  Here is where exception handling comes in. If the first parameter in your method is the interest rate and, obviously, you want the first argument written on the command line to be the interest rate, you have to account for handling the error of someone not doing that. Otherwise, if the number of years is entered as the first argument, you clearly won't get the right result.

This isn't unlike dealing with parameters and arguments normally. Just make sure the user enters the arguments in the right order, after you've made sure they've entered the right command.