Announcement

Collapse
No announcement yet.

learning the fundamentals: progress report and question

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • learning the fundamentals: progress report and question

    {For those who have already read my previous posts, I hope the community doesn't laugh at this poor Mech/Met Eng in this latest post.}

    1) I was able to successfully create my first [semi-customized] Hello World! app:
    [insert really cool screenshot of "FTC 839 rocks!!" from the emulator here, which I have no clue how to do in this Forum]
    using the FTC Training Manual Section 7.7 and http://www.raywenderlich.com/78574/a...ginners-part-1 [didn't like the latter's parts 2 & 3 for FTC purposes].
    And it only took me a couple/few hours to do (I stopped looking at the clock and quit at 2AM)!
    I wish I had taken notes, but here are a few blurry recollections:
    * In the SDK Manager, I uninstalled everything except for API 19. When we were playing around on Thursday, it looks like several other APIs were installed [by mistake?, looking at samples found on the internet?]. [I got this clue from an error message that led me to http://stackoverflow.com/questions/1...ompiledebugai]
    * picked a low-resolution emulator because I was getting an error message that it was limited to 500MB [Tools/Android/AVD Manager]
    * tripped over res/values/strings to change the text
    * there were several times when I hit something for an action and I looked all over the screen and could not find that anything had launched - after a few tries, I just waited for a unreasonable length of time (or it would be for a 12-year-old ADD kid), and it did its thing
    * I got a (windows- 1252) error, which I dutifully searched for and found http://stackoverflow.com/questions/3...hes-by-default and kept hitting buttons/links until it went away
    * hardwired AS to API 19 [clue offered after error message that led me to http://stackoverflow.com/questions/2...dl-is-missing]
    * clicked any hyperlinks in the message screen down on the bottom [don't remember if they were in the Android and/or Run tabs/views] and did what I was told to.

    2) Having not yet found any really simple, fun, general, non-pretty-screen tutorials for AS for tonight's session, I guess I will have the Members transcribe the text in some samples so they can get used to the syntax. I am looking at the following samples [for API 19] {some seem to be in several categories}. Anyone tried these samples yet and have any opinions on their educational value for robot input-output interface functions?
    - Design
    - Interpolator
    - Getting Started
    - Action Bar?
    - Floating Action
    - Input
    - Basic Gesture
    - Basic Multitouch
    - Interpolator [again]
    - Location
    XYZTourist [needs phone GPS?]
    - Monetization
    - Ad Mob Banner
    - Double Click Banner
    - Notification
    - Custom
    - XYZTourist [again]
    - Renderscript
    - Basic
    - Sensors
    - BatchStep [needs phone accelerometer?]
    - Geofencing [needs phone GPS?]
    - Testing
    - Activity
    - Transition/s
    - Basic
    - Custom
    - Interpolator [again]
    - Ui
    - Basic Access
    - Basic Gesture
    - Basic Multitouch [again]
    - Basic Transition [again]
    - Custom Transition [again]
    - Done Bar
    - Floating Action [again]
    - Navigation Drawer
    - Reveal Effect
    - Sliding Tabs Basic & Color
    - Test Switcher
    - Views
    - Basic Multitouch [again]
    - Widgets
    - Custom Choice

  • #2
    It looks like the Forum deletes blanks, so my indented list got lost. Here is try #2:
    - Design
    -- Interpolator
    - Getting Started
    -- Action Bar?
    -- Floating Action
    - Input
    -- Basic Gesture
    -- Basic Multitouch
    -- Interpolator [again]
    - Location
    -- XYZTourist [needs phone GPS?]
    - Monetization
    -- Ad Mob Banner
    -- Double Click Banner
    - Notification
    -- Custom
    -- XYZTourist [again]
    - Renderscript
    -- Basic
    - Sensors
    -- BatchStep [needs phone accelerometer?]
    -- Geofencing [needs phone GPS?]
    - Testing
    -- Activity
    - Transition/s
    -- Basic
    -- Custom
    -- Interpolator [again]
    - Ui
    -- Basic Access
    -- Basic Gesture
    -- Basic Multitouch [again]
    -- Basic Transition [again]
    -- Custom Transition [again]
    -- Done Bar
    -- Floating Action [again]
    -- Navigation Drawer
    -- Reveal Effect
    -- Sliding Tabs Basic & Color
    -- Test Switcher
    - Views
    -- Basic Multitouch [again]
    - Widgets
    -- Custom Choice

    Comment


    • #3
      I was getting desperate and started looking for a book, and tripped over this website, http://www.i-programmer.info/program...id-studio.html.

      It has instructions for installation (which we can ignore), but then it goes on to a button app!, then a "calculator" app!!, and ... I was so excited, I am posting this for you at this point.

      If we can get it boiled down into a step-by-step tutorial, it should be fun tonight!

      Comment


      • #4
        I would be trying the following Youtube playlist:
        https://www.youtube.com/playlist?lis...EfOCbezi6vATIh

        Then, going into Material Design:
        https://www.youtube.com/playlist?lis...1XD8ELUs1KXaTD

        Also, the Synccuintly series by SyncFusion has the following (I consider the series to be more like a crash course):
        https://www.syncfusion.com/resources...ebooks/android

        Comment


        • #5
          Thanks!!!!!!!!

          With our current schedule**, tonight's 2.5 hour meeting will be our last whole-team orientation to AS, so I want the kids to successfully create at least 2 apps, and have some fun!



          ** last week was AI and next week is Creo, then school starts, then KickOff!

          Comment


          • #6
            I have nothing against learning Android development, but most of the items on the list above don't seem very relevant to programming robots using the FTC SDK. Perhaps the parts about sensor usage might be useful, but even then, the SDK includes classes such as GyroSensor which abstract away a lot of the information. Teams will need to go beyond the SDK; even things like multi-threading aren't in the SDK, and that may come in handy. I suspect really advanced teams may need to go beyond the SDK to do things like computer vision. In any case, I wouldn't really recommend building apps as a great way to learn about programming robots - there's just so much information that isn't needed.
            John McDonnell
            Co-Mentor, Team 5873
            https://www.facebook.com/Team5873

            Comment


            • #7
              final AS team pre-season orientation report:
              - walked through "Hello World" development (in FTC Training Manual) together as a whole team (and each individual student on their own laptop) so they could get used to the basic AS environment and pieces
              - tried the push button "tutorial" in link in post #3 above, but it appears that since it was written for 1.0, 1.3 has enough differences such that we couldn't get the app to work (yet - still working on it part time)
              - also found the following in addition to the youtube videos posted by dmssargent in post #4 above:
              http://www.vogella.com/tutorials/Android/article.html “Introduction to Android development with Android Studio – Tutorial” (online text)
              http://www.tutorialspoint.com/androi...d_tutorial.pdf “Android Tutorial - Simply Easy Learning by tutorialspoint.com” (download pdf)

              Comment


              • #8
                philosophical/strategic thoughts:

                I will admit that I'm a dinosaur and not a programmer, but when I learned FORTRAN on punch cards and a Sperry-Univac mainframe, we learned in pieces. First, figure out this small piece [display text]. Then add this small piece [push button to display text]. Then extend it with this small piece [do analysis of inputs]. I figured that would be a good way to learn the basics of Java/AS, too.

                As an ME Coach, I apply the same process for the mechanical stuff too. Hook up a battery to a motor to see it spin; reverse polarity to see it go backwards. Then add the motor controller with a single command. Then add the encoder to go a specific distance. Then ...

                And in manufacturing, build a wooden screwdriver holder to learn how to plan, measure, safety, cutting, fastening, etc. then move on to building robot hardware.

                Just like building LEGOs.

                I've also had trepidation (most of which has been borne out by other posts in this Forum), that slapping together a test bot and plugging in someone else's program has its own hydra of issues that doesn't simplify, but actually makes the problem more complex. And, without a firm foundation, diagnostics are impossible.

                With that said, the Programming Subteam should be trying to make hardware move the meeting after KickOff, so it'll be interesting!!



                "Robots are just a vehicle." (DK)

                Comment

                Working...
                X