Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

WebCenter: A Web Developer's Playground

HTML5, REST APIs, JavaScript, JSON, Canvas, SVG, and WebCenter
by

Rich Manalang

on 12 September 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of WebCenter: A Web Developer's Playground

Who we are?
theappslab.com
twitter.com/theappslab
WebCenter: A Web Developer's Playground
rich.manalang@oracle.com @rmanalan
anthony.s.lai@oracle.com @anthonyslai
jake.kuramoto@oracle.com @jkuramot
Our work
Our tools...
html(5), css3, javascript, jquery, sammyjs, (j)ruby, rails, sinatra, java...
HTML5
The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions.The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.
What is WebCenter?
Social
Networking
Blogs
Wikis
Forums
Events
Lists
Content
Management
Activity
Streams
all of these services are exposed as a RESTful API following the HATEOAS principles
Hypermedia as the Engine of Application State
in other words...
Rather than the actions and interfaces a client may use being defined elsewhere, such as in a WSDL file or predefined in the client code, the principle is that the hypermedia in each server response will contain links that correspond to all the actions that the client can currently perform.
"...so what? Why should I care?"
#oldtwitter == standard
Ruby on Rails app serving
dynamic pages

#newtwitter == fairly static pages accessing Twitter's REST APIs
...but, that's not all...
Web Development in 2004 (or earlier*)
Server based page generation
Lots and lots of pages
Little to no Javascript
Web Development Today (and in the future)
Single page web apps
Lots of Javascript
HTML5/CSS3
... other examples: Gmail, Google Instant, Google Docs, Google Reader, Yahoo! Mail, etc...
Case in point...
* http://blog.twitter.com/2010/09/better-twitter.html
~= HTML + CSS3 + JavaScript APIs
client side storage (web sql db, app cache, web storage)
communications (web socket, web workers)
desktop experience (notifications, drag and drop api)
geolocation
Semantics (New tags, Link Relations, Microdata)
Accessibility (ARIA roles)
Web Forms 2.0 (Input Fields)
Multimedia (Audio Tag, Video Tag)
2D and 3D drawing (Canvas, WebGL, SVG)
Typography
Visuals
Transitions, transforms and animations
Examples...
Full transcript