Tag: HTML5

Posted on

List of Standard HTML 5 Elements

All standard HTML5 elements are listed here, described by their opening tag and grouped by function. Contrary to the HTML Element index which lists all possible tags, standard, non-standard, valid, obsolete or deprecated ones, this list only the valid HTML5 elements. Only the elements listed here should be used in new Web sites.

The symbol This element was added as part of HTML5 indicates that the element was added in HTML5. Note that other elements listed here may have been modified or extended in their meaning by the HTML5 specification.

via HTML5 element list – Web developer guide | MDN.

Good list of standard HTML 5 elements, maintained by the folks at Mozilla.

Posted on

Intention.js Allows You To Restructure HTML In Response To Just About Anything

Intention.js offers a light-weight and clear way to dynamically restructure HTML in a responsive manner.

Easily increase layout options and flexibility, reducing development time and lessening the necessity of media-query-driven stylesheet overrides.

via intention.js.

Very interesting JavaScript library that promises to provide developers with tools to dynamically restructure HTML on a page based upon the context that the page is opened in. Built in are the responses to device contexts that allow you to swap out assets and HTML based upon screen size. The really interesting thing is that you can extend it to respond to other contexts, like time of day, touch capabilities, and more.

Intention.js requires jQuery and Underscore.js to work.

Posted on

He’s Back! Dave Winer Teases A JS HTML5 In Browser Outliner

On Monday of this week, somewhat quietly, we released the docs for the outliner we’ve been developing at Small Picture, Inc.

http://smallpicture.com/outlinerHowto.html

The docs are interesting, if you like outliners — but also interesting because they illustrate something important about the outliner. It’s very easy to include in a web page.

There’s a practice outliner right there on the docs page. Kind of subtle. 😉

via Scripting News: It’s an outliner!.

If I were looking for a killer app, an outliner that runs completely in the browser and is always on the network would certainly fit the bill. And that is just what Dave Winer and his programming partner Kyle Shank are bringing us from their new startup Small Picture. Their goal is “to bring outlining software to the browser environment, in JavaScript, through the power of HTML 5.”

The outliner in a browser that’s linked in the quote above seems to really deliver. It offers all of the features that you’ve come to expect in a Winer Outliner and includes features that will appeal to programmers too. Dave promises to reveal new bits of the browser outliner over the coming Mondays, so there’s something to look forward to.

I’ll be very interested in seeing just how this outliner rolls out. A quick peek into the JavaScript that makes it go shows it’s reading/writing from a given OPML file. Going forward the ability to create, share, and collaborate on a network of OPML files is going to be where the “killer app” aspect of this product lies. I hope this means a distributed network of OPML hosts offering browser based access to the outlines.

And boy would it be nice if the server side would run on Linux.

Posted on

Notes from Drupalcamp Atlanta 10/27/12

These are my notes from dcATL.
  • Josh Clark @globalmoxie
  • The mobile future
  • Mobile is a new platform. What do we do with the new platform?
  • How do we do more with mobile?
  • Sensors give us super powers.
  • Mobile provides the opportunity to interpret the environment, think of augmented reality.
    • Think of ways to use camera and audio in classroom, like prof mentions case and it pop ups on device.
  • Table Drum app usess augmented audio.
  • AnyTouch turns everyday objects into interface objects.
  • Leap Motion moves touch interface into 3d space, natural gestures.
  • Natural gestures are the next break through in interfaces.
  • We need to design for natural gestures.
  • Windows 8 is intended to work with any input interface. Hugely challenging.
  • Medical field is using all sorts of special sensors with mobile devices to drive data collection.
  • Personal sensors make sense of our environment.
  • But we don’t need more operating systems, interfaces.
  • Remote control is an answer.
  • Ambiguous control among devices is coming, think of phones in cars. Your car rings. When you park the car, the interface follows you. Migrating interface.
  • http://bit.ly/day-glass– A day made of glass from Corning.
    • One smart device somewhere that is driven by ambiguous interfaces
  • Wii U
  • Grab Magic http://bit.ly/grab-magic
  • http://bitly.com/proto-gestures
  • Sifteo cubesare social toys.
    • Download software as it needs it.
  • Web is just in case, everything is loaded in case we need it. Needs to move to just in time, software loaded when we need it.
  • Passive interfaces just work on their own, doing the things they need to do to perform the functions they are designed to do.
  • Devices will get both dumber and smarter.
  • Metadata is the new art direction – Ethan Resnick @studip101
  • A cloud of social devices
  • Look beyond the interface, beyond the device, the presentation to the content and the services.
  • Push sensors
  • Think social not FB
  • Your ecosystem
  • We’re all cloud developers
  • Mind your metadata
  • New input methods
  • The future is here
  • Eric Webb @erikwebb
  • See slideshare
  • Evaluating modules
    • Supported version, maintainer rep, usage, # of open issues, usage over time.
    • Record before and after install using Devel module
    • Search for tag ” performance ” to weed out general issues.
    • What to look at
      • When does it run?
      • How does it scale?
      • What if it fails?
      • Does my site care?
      • Do I need this module?
    • ID the problem
    • Where problems occur
      • Page building like views and panels
      • External web services
      • Overall complexity
        • Views in panels in panels….
      • Misconfigured components
    • Keep records, establish a metric, adopt a definition of done, don’t hide behind infrastructure
  • Types of caching
    • App level caching is not really configurable. Tings like menus, forms
    • Component level caching, user facing stuff like blocks, views, panels
      • Best to speed up for authenticated users
    • Page level caching is important mostly for anon users
  • Configuring Drupal

  • Randall Kent @randallkent rkent@sevaa.com
  • http://bit.ly/dcatl-services
  • Web services as the tip of the iceberg.
  • REST is the key to getting at the stuff in Drupal. REST is one way to create an API on Drupal.
  • REST
    • built on http
      • GET, POST, PUT, DELETE
    • Client/Server
      • Separates ui from data storage
    • Stateless
      • All info necessary to process request must be included in the request itself
    • Cacheable
    • Layered
    • Uniform interface
  • /myapi/node – gets XML
  • /myapi/node.json – get JSON
  • REST console for Chrome
  • http://github.com/randallkent
    • DrupalREST.php
    • DrupalREST.net
  • See http://drupanium.org
  • David Bassendine @dbassendine
  • Open data, social, business tools
  • Few modules for consuming services
  • Always start with looking on line for a module
  • REST vs SOAP
  • Get to know the API you are working with
    • URL and path structure
    • Testing in browser for GET, POST requires extension/plugin
  • Services client for D7 will consume Services from another Drupal instance
  • REST API and Query API handle some RESTful APIs that serve json
    • See red mine module for example
  • Core HTTP API for other services
    • drupal_http_request($url,$options(headers,methods,data))
    • Slightly diff D6 & D7
  • Last 2 require custom modules to do the work
  • Krumo – http://krumo.sourceforge.net/

  • Talking to Web Services – Resources

  • Matthew Connerton @connerton
  • AJAX allways for there fresh of data in the browser page with refreshing the whole page.

    Sample code for AJAX in Drupal7
  • Replaces AHAH, which is a good thing. Pulls lots in crooks stuff
  • “use-ajax” class
    • drupal_add_library(drupal.ajax) to get Ajax in.
    • Pulls jquery in
  • $form[‘#ajax’]
    • drupal_add_library(drupal.ajax) to get Ajax in.
    • Blur is the default trigger.
  • It’s may ease the pain of the auth code stuff.
  • Check Drupal API for AJAX Framework docs.
    • includes/ajax.inc
  • Using #states in Form API
  • Ctools modal to open modal boxes for editing and such.
    • “ctools-use-modal” class
  • Doug Vann dougvann.com
  • Module filter is cool
  • DraggableViews
    • Makes rows of views draggable
    • Can be rearranged by drag and drop
    • Has AJAX
    • No relationship required
    • Could use this to provide a sort on Lesson topics based on order in the topic grid
    • Use this to rearrange stuff on the topic list view itself on the home page
    • No subsets or at least not easily handled
  • Nodequeue
    • Collect nodes in an arbitrary order
    • Requires relationship in order to bring stuff into proper scope


Posted on

Some HTML5, CSS3, and jQuery Resources

Here are a few sites that provide some good info on HTML5, CSS3, and jQuery.