How To Be Rich With Smalltalk


Published on

How To Be Rich With Smalltalk: Intregrating RIA & Smalltalk. Jorge Silva, ESUG09, Brest, France

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • 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
  • How To Be Rich With Smalltalk

    1. 1. How to be rich with Smalltalk Intregrating RIA & Smalltalk Ing. Jorge Silva Sept, Thursday 3 - ESUG 2009 – Brest, France
    2. 2. Schedule – how 2 be rich… <ul><li>The context </li></ul><ul><li>The problem </li></ul><ul><li>What’s RIA? </li></ul><ul><li>Why Smalltalk? </li></ul><ul><li>Recap </li></ul><ul><li>Our proposal </li></ul><ul><li>Live example </li></ul><ul><li>Benefits & shortcomings </li></ul><ul><li>Side work/future work </li></ul><ul><li>Conclusions </li></ul>
    3. 3. The context
    4. 4. The client… <ul><li>… wants a “cute” app. (A.K.A. rich app)… </li></ul><ul><li>… with focus on user experience … </li></ul><ul><li>… and they don’t have too much time </li></ul>
    5. 5. We are Smalltalk lovers [|] Reflective capabilities [|] Object Oriented Enviroment [|] Dynamic typing [|] Easy to express ideas
    6. 6. So, the challenge <ul><li>UI/UX </li></ul><ul><li>“ cute” </li></ul><ul><li>Few time </li></ul><ul><li>Smalltalk </li></ul>We were in a hurry…
    7. 7. Some previous definitions
    8. 8. Lil’ about RIA Rich Internet Application
    9. 9. User eXperience “… how it is perceived , learned , and used .” by Donald Norman
    10. 10. The research
    11. 11. UIs in Smalltalk based applications
    12. 12. UIs in Smalltalk based applications
    13. 14. Examples of UIs in Smalltalk based applications
    14. 16. Quick conclutions <ul><li>Similar layout </li></ul><ul><li>They aren’t user friendly </li></ul><ul><li>Form oriented </li></ul><ul><li>Windows default theme. </li></ul>
    15. 17. State-of-the-art in GUIs
    16. 18. Quick conclusions <ul><li>Visual interaction </li></ul><ul><li>Several colors and images </li></ul><ul><li>Graphic design </li></ul><ul><li>Intuitive interface </li></ul>
    17. 19. Recap
    18. 20. How our proposal works
    19. 21. Technologies used Front-end SOAP Back-end
    20. 22. Our proposal Proposed “architecture”
    21. 23. Showtime!
    22. 24. Now, a complete application
    23. 25. Live example
    24. 26. Traffic Jam Simulator Showtime!
    25. 27. Benefits, shortcomings & conclusions
    26. 28. <ul><li>Increases available controls, enriching user interaction </li></ul><ul><li>Eases prototype creation for the client. </li></ul><ul><li>WYSIWYG editor </li></ul><ul><li>Artistic features </li></ul><ul><li>Greater progress perception </li></ul>Benefits
    27. 29. <ul><li>Poor client performance </li></ul><ul><li>Two environments </li></ul><ul><li>May incur in high traffic load. </li></ul><ul><li>Edge technology </li></ul>Shortcomings
    28. 30. Problems we faced during development <ul><li>Cyclical reference not supported </li></ul><ul><li>AnyType not supported </li></ul><ul><li>Debug with multiple modules </li></ul><ul><li>Flex(AS) is not the state of the art in OOP </li></ul><ul><li>Security </li></ul>
    29. 31. Similar works <ul><li>GlareDS </li></ul><ul><li>Seaside </li></ul><ul><li>VistaSmalltalk </li></ul>
    30. 32. Final conclusions <ul><li>Best from both worlds </li></ul><ul><li>Better responsibility delegation </li></ul><ul><li>Power of distiction. </li></ul><ul><li>Better comunication with the user </li></ul><ul><li>This is not THE WAY, this is just ONE WAY </li></ul>The overall conclusion here is to use RIAs , and connect it with Smalltalk , through web services
    31. 33. queries (# Speaker) [aPerson hasQuery] whileTrue: [self answer]. ^ self timeToSayGoodbye
    32. 34. Reconnaissance
    33. 35. Jorge Silva – Merci beaucoup!