h
occasionally subtle
taylor price
#extradirty
he wasn't even looking at me and he found me
let's talk about Bridgerton tea, my ask is open
AnasAbdin
2025 on Tumblr: Trends That Defined the Year
if i look back, i am lost
Misplaced Lens Cap
we're not kids anymore.
No title available
oozey mess
Sweet Seals For You, Always
Cosmic Funnies
blake kathryn
tannertan36
cherry valley forever
Xuebing Du
Jules of Nature
seen from Argentina
seen from United States
seen from United States
seen from United States
seen from United States
seen from United States
seen from United States
seen from Tunisia
seen from Canada
seen from United States
seen from United States
seen from United States
seen from United States
seen from United States
seen from United States
seen from United States
seen from Germany
seen from France
seen from Algeria
seen from Italy
@m2mtech-blog
#cs193p #assignment2 #extraTask3Create a launch screen for your Calculator in LaunchScreen.storyboard.Remember that you will want to use some simple autolayout to make your launch screen look good on all platforms.https://cs193p.m2m.at/cs193p-assignment-2-extra-task-3-winter-2017/
#cs193p #assignment2 #extraTask2Add app icons to your Assets.xcassets file (which we moved to Supporting Files in Lecture 1). The only trick here is to provide versions of your icon in all the right sizes.https://cs193p.m2m.at/cs193p-assignment-2-extra-task-2-winter-2017/
#cs193p #assignment2 #extraTask1Have your calculator report errors. For example, the square root of a negative number or divide by zero. There are a number of ways to go about “detecting” these errors (maybe add an associated value to the unary/binaryOperation cases which is a function that detects an error or perhaps have the function that is associated with a unary/binaryOperation return something that is either an error or a result or ???). How you report any discovered errors back to users of the CalculatorBrain API will require some API design on your part, but don’t force users of the CalculatorBrain API to deal with errors if they don’t want to (i.e. allow Controllers that want to display errors to do so, but let those that don’t just deal with NaN and +∞ appearing in their UI). In other words, don’t break any callers of the API described above (who don’t care about errors) to support this feature (i.e., add methods/ properties as needed instead). You are allowed to violate Required Task 11 to implement this Extra Credit item, but not Required Task 1 (you can enhance that data structure, but not switch to a new one).https://cs193p.m2m.at/cs193p-assignment-2-extra-task-1-winter-2017/
#cs193p #assignment 2 #task 10Add an Undo button to your Calculator. In Assignment 1’s Extra Credit, you might have added a “backspace” button. Here we’re talking about combining both backspace and actual undo into a single button. If the user is in the middle of entering a number, this Undo button should be backspace. When the user is not in the middle of entering a number, it should undo the last thing that was done in the CalculatorBrain. Do not undo the storing of M’s value (but DO undo the setting of a variable as an operand).https://cs193p.m2m.at/cs193p-assignment-2-task-10-winter-2017/
Depricate result, resultIsPanding and description in CalculatorBrain and do not use them anywhere else.
#assignment #2 #task #5 We made the result, description and resultIsPending vars non-private API in Assignment 1. That means we signed up to continue to support them even though we are now adding a new feature (variables) in this assignment which sort of makes them irrelevant. Really what we want to do is deprecate these (you’ll see all sorts of deprecated iOS API in Xcode), but for now we will keep the old result, description and resultIsPending vars around and just implement each of them by calling evaluate with the argument nil (i.e. they will give their answer assuming the value of any variables is zero). However, do not use any of these vars anywhere in your code in this assignment. Use evaluate instead. https://cs193p.m2m.at/cs193p-assignment-2-task-5-winter-2017/
Now that you allow variables to be entered as operands, add a method to evaluate the CalculatorBrain ...
#assignment #2 #task #4Now that you allow variables to be entered as operands, add a method to evaluate the CalculatorBrain (i.e. calculate its result) by substituting values for those variables found in a supplied Dictionary … func evaluate(using variables: Dictionary<String,Double>? = nil) -> (result: Double?, isPending: Bool, description: String)Note that this takes an Optional Dictionary (with Strings as keys and Doubles as values) as its argument and that that argument defaults to nil if not supplied when this method is called. Also note that it returns a tuple (the first element of which is an Optional Double). This method is not mutating and you are not allowed to make it so. If a variable that has been set as an operand is not found in the Dictionary, assume its value is zero.https://cs193p.m2m.at/cs193p-assignment-2-task-4-winter-2017/
Add the capability to your CalculatorBrain to allow the input of variables.
#assignment #2 #task #3Add the capability to your CalculatorBrain to allow the input of variables. Do so by implementing the following API in your CalculatorBrain … func setOperand(variable named: String)This must do exactly what you would imagine it would: it inputs a “variable” as the operand (e.g. setOperand(variable: “x”) would input a variable named x). Setting the operand to x and then performing the operation cos would mean cos(x) is in your CalculatorBrain.https://cs193p.m2m.at/cs193p-assignment-2-task-3-winter-2017/
#assignment #1 #extraTask #3Make one of your operation buttons be “generate a #randomDoublePrecision floating point number between 0 and 1”. This operation button is not a constant (since it changes each time you invoke it). Nor is it a unary operation (since it does not operate on anything). Probably the easiest way to generate a random number in iOS is the global Swift function arc4random() which generates a random number between 0 and the largest possible 32-bit integer (UInt32.max). You’ll have to get to double precision floating point number from there, of course.https://cs193p.m2m.at/cs193p-assignment-1-extra-task-3-winter-2017/
#cs193p – #Assignment #1 #ExtraTask #2Figure out from the documentation how to use the iOS struct NumberFormatter to format your display so that it only shows 6 digits after the decimal point (instead of showing all digits that can be represented in a Double). This will eliminate (or at least reduce) the need for Autoshrink in your display. While you’re at it, make it so that numbers that are integers don’t have an unnecessary “.0” attached to them (e.g. show “4” rather than “4.0” as the result of the square root of sixteen). You can do all this for your description in the CalculatorBrain as well.https://cs193p.m2m.at/cs193p-assignment-1-extra-task-2-winter-2017/
#cs193p – #Assignment #1 #ExtraTask #1Implement a #backspacebutton for the user to touch if they hit the wrong digit button. This is not intended to be “undo,” so if the user hits the wrong operation button, he or she is out of luck! It is up to you to decide how to handle the case where the user backspaces away the entire number they are in the middle of typing. You will probably find the Strings and Characters section of the Swift Reference Guide to be helpful here.https://cs193p.m2m.at/cs193p-assignment-1-extra-task-1-winter-2017/
#cs193p – #Assignment #1 #Task #8Add a C button that clears everything (your display, the new UILabel you added above, any pending binary operations, etc.). Ideally, this should leave your #Calculator in the same state it was in when you launched it.https://cs193p.m2m.at/cs193p-assignment-1-task-8-winter-2017/
#cs193p – #Assignment #1 #Task #7Implement a #UILabel in your UI which shows the #sequenceOfOperands and operations that led to (or is leading to if resultIsPending) what is (or “will be” if resultIsPending) showing in the display. If resultIsPending is true, put . . . on the end of the UILabel, else put =. If the userIsInTheMiddleOfTyping, you can leave the UILabel showing whatever was there before the user started typing the number. Examples ...a. touching 7 + would show “7 + ...” (with 7 still in the display)b. 7 + 9 would show “7 + ...” (9 in the display)c. 7 + 9 = would show “7 + 9 =” (16 in the display)d. 7 + 9 = √ would show “√(7 + 9) =” (4 in the display)e. 7 + 9 = √ + 2 = would show “√(7 + 9) + 2 =” (6 in the display)f. 7 + 9 √ would show “7 + √(9) ...” (3 in the display)g. 7 + 9 √ = would show “7 + √(9) =“ (10 in the display)h. 7 + 9 = + 6 = + 3 = would show “7 + 9 + 6 + 3 =” (25 in the display)i. 7 + 9 = √ 6 + 3 = would show “6 + 3 =” (9 in the display)j. 5 + 6 = 7 3 would show “5 + 6 =” (73 in the display)k. 4 × π = would show “4 × π =“ (12.5663706143592 in the display)https://cs193p.m2m.at/cs193p-assignment-1-task-7-winter-2017/
#cs193p – #Assignment #1 #Task #6Add a String property to your #CalculatorBrain called #description which returns a description of the sequence of operands and operations that led to the value returned by result (or the result so far if resultIsPending). The character = (the equals sign) should never appear in this description, nor should … (ellipses).https://cs193p.m2m.at/cs193p-assignment-1-task-6-winter-2017/
#cs193p – #Assignment #1 #Task #5Add a Bool property to your #CalculatorBrain called #resultIsPending which returns whether there is a binary operation pending.https://cs193p.m2m.at/cs193p-assignment-1-task-5-winter-2017/
#cs193p – #Assignment #1 #Task #4Use #color to make your #UI look nice. At the very least, your operations buttons must be a different color than your keypad buttons, but otherwise you can use color in whatever way you think looks nice.https://cs193p.m2m.at/cs193p-assignment-1-task-4-winter-2017/
#cs193p – #Assignment #1 #Task #3Add some more #operationsButtons to your #calculator such that it has at least a dozen operations total (it can have even more if you like). You can choose whatever operations appeal to you. The buttons must arrange themselves nicely in portrait and landscape modes on all iPhone 6’s and 7’s.https://cs193p.m2m.at/cs193p-assignment-1-task-3-winter-2017/
#cs193p – #Assignment #1 #Task #2 Your #Calculator already works with #floatingPointNumbers (e.g. if you touch 3 ÷ 4 =, it will properly show 0.75), however, there is no way for the user to enter a floating point number directly. Fix this by allowing legal floating point numbers to be entered (e.g. “192.168.0.1” is not a legal floating point number!). You will need to have a “.” button in your calculator. Don’t worry too much about precision or significant digits in this assignment (doing so is Extra Credit).
https://cs193p.m2m.at/cs193p-assignment-1-task-2-winter-2017/