Skip to main content

Home/ ACSE Discussion/ Group items tagged intro

Rss Feed Group items tagged

Peter Beens

Small Basic Tutorial - 0 views

  •  
    Intro Small Basic tutorial from Microsoft. Excellent place to start.
Peter Beens

App Inventor - 0 views

  •  
    A quick intro to App Inventor
Doug Peterson

Learn to Code with Harvard's Intro to Computer Science Course And Other Free Tech Class... - 1 views

  •  
    "Topics include abstraction, algorithms, encapsulation, data structures, databases, memory management, security, software development, virtualization, and websites. Languages include C, PHP, and JavaScript plus SQL, CSS, and HTML. Problem sets inspired by real-world domains of biology, cryptography, finance, forensics, and gaming. Designed for concentrators and non-concentrators alike, with or without prior programming experience."
Peter Beens

ICS2O - Understanding Your Computer - Google Docs - 0 views

  •  
    An activity created by Peter McAsh for the ICS2O class. Thanks Peter! 
Peter Beens

Build Your Own Blocks (BYOB) - 0 views

  •  
    Welcome to the distribution center for BYOB (Build Your Own Blocks), an advanced offshoot of Scratch, a visual programming language primarily for kids from the Lifelong Kindergarten Group at the MIT Media Lab. This version, developed by Jens Mönig with design input and documentation from Brian Harvey, is an attempt to extend the brilliant accessibility of Scratch to somewhat older users-in particular, non-CS-major computer science students-without becoming inaccessible to its original audience. BYOB 3 adds first class lists, sprites, and procedures to BYOB's original contribution of custom blocks and recursion.
Peter McAsh

Java Basics: GUI: Lesson 1 - Introduction - 0 views

  • Giving up control - Event-driven programming. The GUI programming style is referred to as event-driven programming. In this style of programming you set up the graphical user interface and initialize things. It appears that the program just stops and sits there doing nothing! There is no input loop; your program isn't trying to read from the user. You, the programmer, have to learn to give up control in two ways. Your program gives control to the GUI system, and you only get control back to when your listeners are called. At an even higher level, your program has given control to the user. It's the user who selects which of your methods to call by their choice of buttons to click on, menu items to select, etc. Listeners. When the user clicks a button (or uses another GUI component), an event is sent to listener method. Your job as a programmer is to write a listener method for each component. It's the user, not the programmer, who has control, indirectly choosing methods in your program to execute by interacting with graphical user interface components.
1 - 7 of 7
Showing 20 items per page