I would use a realistic approach that they can relate to and understand. I would use the Lego analogy The following would be the basic elements:
Components - Building block (black boxes to do something). For instance a component that add numbers. Messaging - A way of communication between components (like in the real world). You need to pass a message (2 numbers) to the component above in order to get the correct answer. You may wan to check the following paper for additional information about the messaging/realistic approach: b) Messaging Design Pattern (MDP) and pattern implementation - Published in the 17th conference on Pattern Languages of Programs (PLoP 2010). https://jt.dev.java.net/files/documents/5553/150311/designPatterns.pdf c) Messaging Design Pattern and a distributed Component/Service Model https://jt.dev.java.net/files/documents/5553/149793/MDPdistributedModel.pdf The IDE is mainly a tool (there are many) to "build the black boxes and glue them together". In my opinion some of the main elements are the object oriented paradigm and messaging. It would be nice if they realize that they are able to build their cell phone applications by taking the components (lego) pieces and putting them together. I would also try to avoid "too much abstraction" as part of the session. .... Just a thought On Nov 29, 7:04 pm, cellurl <[email protected]> wrote: > I am teaching a bunch of kids how to program cellphones. > > What is the simplest way to get kids running on Eclipse/SDK? > This will probably take place in a library without individual laptops. > > Has anyone created a live-CD for Ubuntu? > e.g. Damn Small Linux (DSL) bootable CD with Eclipse perhaps.... > > Any suggestions appreciated. > > -jim -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
