> Despite President Obama telling black voters that he would take it as a "personal insult" if they didn't cast their ballot for Hillary Clinton, 2016 black voters didn't coalesce behind Clinton the same way they did Obama, with Clinton earning 88% of their vote (to Trump's 8%) as compared to Obama's 93% in 2012. That being said, the overwhelming majority of African-Americans did show their support by voting for Clinton, particularly as compared to white Americans, who ultimately won Trump the election by giving him 58% of the white vote.
I follow politics but I'm not sure I would like a political forum
I probably follow politics more these days than I used to, because it's more entertaining than ever
I think life gets lonelier as you get older. My friends all have partners and they're busy between that and work. I have several friends in Chicago but I only see them once a month.
Objects can also hide functions from other objects by declaring them private. It can do the same with data, by declaring it private. It's useful to hide implementation details that other objects don't need to know about.
In JavaScript, you can create a local variable by declaring "var xxx = ..."
This variable is local to the function it's in.
The variable is hidden from other functions.
You can also use the "this" keyword to create a variable/function that other functions can access. Between "var" and "this" you have private and public scope.
When you use "this" in a function, it refers to the object that owns the function. So for example if you use this in a keydown(...) function, the object that owns the function is the input field that you're typing into.
The main idea is that onKeyPress(format) returns a function which takes an event as an input.
That function can be invoked each time a key is pressed.
By creating a "wrapper function" around that, you can customize how it works, by accepting different inputs (in this case, we receive the Regular Expression as an input)
The RegExp '^[0-9]*$' only accepts characters 0-9.
You might write that RegExp in your function(event) {...} body where you add the event listener.
But what if you want to change that RegExp? Sure, you can use an if. But what if you want it to accept any RegExp that the user supplies? i.e. make it generic.
This is true for all three input fields. As I type in the unabbreviated name, it updates that property of the folder, and as I type in the folder level, it updates the folder level as I'm typing.
The advantage of this is you don't need a "save" or "cancel" button when you change the folder properties, since they update on each key press.
Now... I have three input fields, and they all listen for the keypress event.
If a user pastes something into the input field, it has to update the folder automatically.
It would be ugly to create three different keypress functions and three different paste functions.
Better to have one keypress function and one paste function that all the input fields use.
That requires a generic function that updates the folder based on a keypress or a paste.
The less code the better, less is more.
But now I have a generic keypress function which behaves differently based on which input field is being typed into... so I need to pass it some parameters that tell it how to behave.
For one, I need to pass it the property to update (abbreviated name, unabbreviated name, or folder level)
For another, I need to tell it what characters are acceptable (the name fields can take any character but the folder level can only take numbers)
I think it's possible to use three if statements
But you would have to discern which input field you're in, most likely using the "this" keyword.
If you pass all three input fields the same keypress function, that keypress function would need an if statement that discerns whether the field is numeric or not, etc.
The if statement would have to say "Hey, I'm in the numeric input field, so I'm only accepting numbers and I'm updating the 'level' property for the folder object".
You might have format = new RegExp('^[0-9]*$') and target = 'level'
if (inNumericField) { format = new RegExp('^[0-9]*$') and target = 'level' }
something like that.
I concur, you can do it this way too, with three if statements.
The other reason is subjective, but it seems cleaner.
There's a third reason
Let's say your requirements change and the acceptable characters are no longer numbers but numbers from 0 to 100.
If you do it with a function inside a function, you can just pass it a different numericFormat argument.
But if you do it with if statements inside the function(event) you need to modify those if statements and add a separate case for numbers from 0 to 100.
I just know that there are some thing I find it hard to wrap my heads around, such as functions inside functions, whereas others are immediately clear, such as case switch.
CONLOQVIVM
CONLOQVIVM