Your SlideShare is downloading. ×
Overview
Overview
Overview
Overview
Overview
Overview
Overview
Overview
Overview
Overview
Overview
Overview
Overview
Overview
Overview
Overview
Overview
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Overview

1,554

Published on

Sheets of a lecture.

Sheets of a lecture.

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,554
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Technical overview RIA projects RIA projects Raymond van Dongelen, NHL , www.webxy.nl
  • 2. Characteristics of the web
    • Unbound in space/time: Information provided on the Internet is available every day, around the clock, and around the world
    • Anything can be linked. Adding meaning to relations.
    • Distributed, non-hierarchical: There is no begin no end and no order.
  • 3. Initial implementation
    • HTML
    • HTTP
    • TCP/IP
  • 4. Problems
    • HTML is static
    • Need to change pages, need to automate small problems
    • Introduction CGI bin
    • Introduction JavaScript client
    • Introduction Java/ Flash plugins (plugin hell)
    • Gap between the web and good programming
  • 5. Development problems
    • Many disciplines involved
    • Easy to build a prototype, hard to build a working site
    • Interface changes frequently
    • Browser problems
    • Usability problems
    • Easy to store data, but how to manage it?
  • 6. Solutions
    • Find out how the roles should be distributed.
    • Find out what should be done in what order.
    • Use techniques that are designed to overcome common problems.
    • Use techniques that are targeted at professional software developers
  • 7. What roles in a team?
    • Server programmer
    • Client programmer
    • Technical lead
    • Visual designer
    • Information architect
    • Business architect
    • ==> One person can have multiple roles!
  • 8.  
  • 9. Describe the roles
    • Pick a step and describe how the step should be done.
  • 10. Technical solutions
    • Better usability: Flash (bad tool for developers), Flex, Ajax
    • Build faster: Ruby on rails, .Net, J2EE offer advanced data frameworks.
    • Build better: Agile development, eXtreme programming e.d.
  • 11. Relational Databases
    • Good at managing large amounts of data
    • Good at managing certain types of relations
    • Can become an information graveyard.
    • Can be a danger to privacy of users.
  • 12. Selecting tools
    • A tool or environment should support:
    • Working in teams (managing versions, concurrency problems)
    • Help find and prevent problems (meaningful errors and warnings, debugging, types)
    • Structuring your application in meaningful layers
    • Environment is designed to be object-oriented
    • Documenting your work
  • 13. Because
    • You make lots of mistakes
    • You are learning and need meaningful feedback to reflect
    • You always work in teams
    • You create applications that have to be supported
  • 14. Hall of shame
    • Fortran: DO 5 K = 1. 3
    • Ignoring error construction (php, “on error resume next” basic)
    • Include
    • functions.php
  • 15. Example 1
    • var x = 5;
    • var y = “10”;
    • var z = x + y;
    • trace (z);
    z = 510 (Type problem!)
  • 16. Example 2
    • if (x > 3) { trace (“bla”);}
    • else if (x <= 3) {trace (“bla2”);}
    • else { trace (“This code is unreachable”);}
    Why doesn’t the environment give a warning?
  • 17. How rich is “the rich web”
    • Does not use many senses
    • It does not react on the context
    • Hard to protect what is your (privacy, security)
    • ==> We have go a long long way to go

×