How To Be Rich With Smalltalk.1
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

How To Be Rich With Smalltalk.1

on

  • 1,272 views

 

Statistics

Views

Total Views
1,272
Views on SlideShare
920
Embed Views
352

Actions

Likes
1
Downloads
3
Comments
0

8 Embeds 352

http://www.10pines.com 320
http://10pines.com 11
http://localhost 8
http://tenpines-sitev2.herokuapp.com 4
http://blog.10pines.com 4
http://68.166.223.4 3
http://webcache.googleusercontent.com 1
http://translate.googleusercontent.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • 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?
  • 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 Presentation Transcript

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