How To Be Rich With Smalltalk

agile software development & services

How to be rich with Smalltalk

Intregrating RIA & Smalltalk

Ing. Jorge SilvaSept, Thursday 3 - ESUG 2009 – Brest, France

The context

The client…The client…

► … wants a “cute” app. (A.K.A. rich app)…

► … with focus on user experience …

► … and they don’t have too much time

We are Smalltalk loversWe are Smalltalk lovers

[|] Reflective capabilities

[|] Object Oriented Enviroment

[|] Dynamic typing

[|] Easy to express ideas

So, the challengeSo, the challenge

► UI/UX► “cute”► Few time► Smalltalk

We were in a hurry…

Some previous definitions

Lil’ about RIALil’ about RIA

User User eXperienceeXperience

“…“…how it is how it is perceivedperceived, , learnedlearned, , and and usedused.”.”

by Donald by Donald NormanNorman

The research

UIs in Smalltalk based UIs in Smalltalk based applicationsapplications

UIs in Smalltalk based UIs in Smalltalk based applicationsapplications

Examples of UIs in Smalltalk based Examples of UIs in Smalltalk based applicationsapplications

Quick conclutionsQuick conclutions

►Similar layout►They aren’t user friendly►Form oriented►Windows default theme.

State-of-the-art in GUIsState-of-the-art in GUIs

► Visual interaction► Several colors and

images► Graphic design► Intuitive interface

Quick conclusionsQuick conclusions

Recap

How our proposal works

Technologies usedTechnologies used

Front-end

SOAP

Back-end

Our proposalOur proposal

Proposed “architecture”

RIA Front-end

Smalltalk Back-end(Image)

Web server

HTTP + XML = SOAP

Metadata

Model

Browser(Flash VM)

HappyUser

Showtime!

Now, a complete application

Traffic Jam Simulator Showtime!

Benefits, shortcomings & conclusions

► Increases available controls, enriching user interaction

► Eases prototype creation for the client. ► WYSIWYG editor► Artistic features► Greater progress perception

BenefitsBenefits

► Poor client performance► Two environments► May incur in high traffic load. ► Edge technology

ShortcomingsShortcomings

Problems we faced during developmentProblems 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

Similar Similar worksworks

►GlareDS

►Seaside

►VistaSmalltalk

Final conclusionsFinal 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 Smallta

lk,

through web services

ReconnaissanceReconnaissance

agile software development & services

Jorge Silva – [email protected]

MerciMerci beaucoup!beaucoup!