![Schedule – how 2 be rich… ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
Viewers also liked
Similar to How To Be Rich With Smalltalk
Similar to How To Be Rich With Smalltalk (20)
More from ESUG
More from ESUG (20)
Recently uploaded
Recently uploaded (20)
How To Be Rich With Smalltalk
- 1. How to be rich with Smalltalk Intregrating RIA & Smalltalk Ing. Jorge Silva Sept, Thursday 3 - ESUG 2009 – Brest, France
- 3. The context
- 5. We are Smalltalk lovers [|] Reflective capabilities [|] Object Oriented Enviroment [|] Dynamic typing [|] Easy to express ideas
- 8. Lil’ about RIA Rich Internet Application
- 9. User eXperience “… how it is perceived , learned , and used .” by Donald Norman
- 10. The research
- 11. UIs in Smalltalk based applications
- 12. UIs in Smalltalk based applications
- 14. Examples of UIs in Smalltalk based applications
- 19. Recap
- 20. How our proposal works
- 21. Technologies used Front-end SOAP Back-end
- 22. Our proposal Proposed “architecture”
- 23. Showtime!
- 24. Now, a complete application
- 25. Live example
- 26. Traffic Jam Simulator Showtime!
- 27. Benefits, shortcomings & conclusions
- 33. queries (# Speaker) [aPerson hasQuery] whileTrue: [self answer]. ^ self timeToSayGoodbye
- 34. Reconnaissance
- 35. Jorge Silva – jorge.silva@10pines.com 10Pines.com Merci beaucoup!
Editor's Notes
- We have to focus on UI/UX The app has to be “cute” Few time We wanted to use Smalltalk
- Esto estaria bueno hacer algo como que se fusionen las dos frases y salga RIA.
- RIA, rich Internet applications, are Web applications that have the features and functionality of traditional desktop applications. The term "Rich Internet Application" was introduced in a Macromedia white paper in March 2002, though the concept had been around for a number of years before that under different names such as: Remote Scripting, X Internet, Rich (web) clients, Rich web application UX: The scope of the field is directed at affecting "all aspects of the user’s interaction with the product: how it is perceived, learned, and used." After defining all of this ria stuff, we do some research on how to work with this concepts on smalltalk…
- ST is good for modeling and think new domains Flex is good for UI and is a great tool to maximize the UX concepts Anyway/actually, i dont have to say here why ST is good, right?
- Falta traducir Quizas cambiar los graficos a como esta el otro. Agregar una union entre los dos mundos
- Increases available controls, enriching user interaction: Drag & drop, tabs, sliders, rich text editors. Eases prototype creation for the client. Making easy to work in an iterative way Just for Flex, documentation is great! WYSIWYG editor Graphical facilities allows artistic features Greater progress perception. Facilitates user satisfaction
- Cyclical reference not supported (?) AnyType not supported (?) Singleton in Flex Debug with multiple modules (mainApp-debug.swf) AS is not the state of the art in OOP (for example you can’t have many constructors) Security
- This model explote best from both worlds This is like a good model where you delegates responsibilities to who is better for each work This is not THE WAY, this is just ONE WAY The overall conclusion here is to use RIAs , no matter wich one, and connect it with Smalltalk , no matter wich one, through web services Power of distiction. Better comunication with the user