A string can be logged and easily understood. It keeps the inside loop block as simple as possible to focus on the process of looping. This is the same reasoning behind letting the code do the full string concatenation and then whacking off the ending comma. I’m a super-guru Microsoft Access VBA developer. I liked the additional reinforcement of string concatenation (true beginners struggle with it a bit), but array/join is more efficient. I added your array / join to the downloaded zip and put a note about it on the page, because it’s definitely worth noting. Google and V8 drove that optimisation which meant everyone else (including Apple) picked it up.” I learn something new every day. length property is generally cached these days by the runtime. Swift data types (when I played with it) were pure. Oddball syntax but once you got used to it, it was nice enough. “As an aside third parameter comment” I liked Objective C data types. “For Section 6, why did you pick the basic loop over the child records loop?” – Failure to remember that such a thing existed until after I’d already done it and too lazy to go back and change it. I hope you don’t mind that I added your description for console.log and JavaScript as a footnote. As a teacher for the utter newbie, the concept works. At the point in their programming career where they have jumped to a compiled language, they’ll know enough to be able to appreciate the difference. If I explain it as OOC, it adds a ton of web tutorials that can help explain objects which is a useful concept for grasping how to use forms, records, fields, etc. For example, console.log and JavaScript – a true beginner will not understand the nuances of the under-hood implementation of JavaScript/Objective C. I made some decisions to “keep things as simple as possible”. I ran out of time (time-sensitive projects queued) and I figured for 101, this bridges the gap between “I have never written a script in anything in my life… Help!” and “ok, I’m capable of figuring out code posted to the forums…”. I wanted to add many more things (walk-throughs of all of the snippets, not just a couple, and some more useful examples). Thank you for the feedback, Sam! It’s never possible to proofread your own work and find all of the errors (I did try). Looking forward to seeing what you tackle next though! Fan noise is the bane of my own recording existence. Saves you having to deal with substring and let’s Javascript do the heavy lifting for you.Īn alternative trick is to check if the string has a length and append the join characters in the middle after the first iteration of the loop: if (current_chores.length) current_chores += ", " Ĭurrent_chores += chores.getFieldValue(chore_id) įor the audio it sounds like fan noise, try grabbing Audacity and using it’s noise reduction plugin on the audio to see if it can clean it up. Instead of doing string concatenation, I’d use an array and join: let current_chores = Ĭurrent_chores.push(chores.getFieldValue(chore_id)) Ī similar one solution would work for the name list as well which would make it easy to prefix or suffix titles, add middle names or more. Google and V8 drove that optimisation which meant everyone else (including Apple) picked it up. I wouldn’t be surprised if it’s not coerced to a boolean before being marshalled back to Objective-C.įor Section 7, the. It’s a slightly different approach than class based object orientated programming hierarchies.įor Section 6, why did you pick the basic loop over the child records loop? As an aside third parameter comment is probably more correct than wrong because of the way Javascript treats falsey types. Javascript is also generally referred to as a prototype based language and as such doesn’t have classes, just objects that you can extend upon (in a sense they’re all just dictionaries with some self referential sugar). Additionally console.log will return to you the value of the property, for built-ins it’ll be a wrapper around native code though pure Javascript functions will return the implementation. Minor bug on the functions page, you reference console_log not console.log. Perhaps you’ll end up writing “Tap Forms 5: The Missing Manual” at the end of it all. Look forward to seeing more expansion here though! Walk through guides for Tap Forms is something that I feel is missing but could be very useful. Love the styling on the pages though I would have liked a more obvious “next” button to go to the next section.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |