Presentation on theme: "Karl Wilcox Tutorial Starts at 19:00"— Presentation transcript:
1 Karl Wilcox Tutorial Starts at 19:00 TT284: Web TechnologiesBlock 3: Mobile Content and ApplicationsKarl Wilcox Tutorial Starts at 19:00
2 Please run the audio setup. TT284-12B Block 3 TutorialIMPORTANT!Be sure to check the News section on the TT284 Website regularly........and check the TMA 03 Forum for clarifications and updates BEFORE you submit your TMA!Tutorial begins at 7pm and will be recorded.Please run the audio setup.
4 Agenda Review – Where are we & how did we get here? Feedback on TMA02 Mobile Devices – Some thoughtsMobile devices, handling and detectionXSLT Transforms(A note on XML name spaces)Apps for mobileTMA03 – Questions and queries?RemindersI have material for about 1 hour……can use additional time for Q&A if required
7 TMA02 Feedback Generally good – thank you and well done! Long extensions (> 1 week) didn’t really helpAs always – read the question, answer the questionIf in doubt, ask me!I can’t comment on your answers but I can say whether you appear to have understood the questionRegular expression misunderstanding, esp. ranges[1-9] is a range of characters not numbers[ ] does NOT work as some seemed to expect
8 TMA02 Feedback - 2 Don’t create unnecessary dependencies Examples Aim for maximum “abstraction” (independence)ExamplesDon’t rely on field width to restrict input lengthDon’t rely on database organisation for formattingDatabase tables can have new columns addedOrder of elements in an array may changeUse associative arrays for query results<td><?php echo $results[‘laptime’]; ?></td>
9 Health Warning!The following presentation contains personal opinion and some scepticismIt may not be suitable for those who like nice simple answers (and courses!) You will need to be able to make up your own mind…“I did not answer this questions as my tutor didn’t think it was worth it” Is NOT acceptable for the next TMA…
10 Mobile DevicesCharacteristicsDescribe them here please….!
11 Mobile Device Assumptions Awkward touch-screen inputLimited processor powerSmall keyboardLimited capabilitiesSome Web site navigation and usability features won’t work. For example, drop-down menus
12 WAP & WML A Warning from History 1999 – mobiles taking off in a big wayDemand (& hype) for mobile internetBut screens only display text…soDefine new markup language – WMLDesign new infrastructurePublish new comms protocol – WAP2003/04 WAP traffic doubles!(but from what to what?)2013 WAP / WML use - zero
13 The Lesson of WAP WAP & WML did not address what people wanted It addressed what the “lowest common denominator” of technology could doIt ignored everything that already existed (HTML, HTTP)It required new technologies and hardwareIt was designed to generate revenue for the telecoms operatorsIt did NOT succeed!Do not underestimate the ability of technology to provide what people actually want.
14 The Lesson of Mobile Broadcast TV It is equally hard to push technologies for which there is NO demandMobile broadcast TV is perfectly feasible over 3G networks, handsets had support built inBUT it turns out that nobody wants to watch broadcast TV on their phones (except in South Korea…)Will this lesson ever be learned…?Video calling on mobiles (“3”’s big selling point on launch)3D-TV ???
15 7 usability guidelines for Web sites on mobile devices Reduce the amount of contentSingle column layouts work bestPresent the navigation differentlyMinimise text entryDecide whether you need more than 1 mobile siteDesign for touchscreen and non-touchscreen usersTake advantage of inbuilt functionalitySlide used Last Year(accessed 21/06/12)
16 7 usability guidelines for Web sites on (small?) mobile devices Reduce the amount of contentWhy? Screens are near desktop resolution…Single column layouts work bestAre deeply annoyingPresent the navigation differentlyAs this will confuse and annoy your users!Minimise text entry Predictive text faster than typing for most…Decide whether you need more than 1 mobile siteBecause we all need MORE work to do!Design for touchscreen and non-touchscreen usersTake advantage of inbuilt functionalityLike I wasn’t doing this already…?What I think now…
17 Options for Mobile Do nothing Design one Web site but use a different style sheet or sheets for mobile devicesHave separate Web sites for mobile devices.Check-out the BBC Web site on several devices.
20 Detecting Mobile Devices (server) Browser id stringsSee also detector.dmolsen.com – tries to categorise broswer (desktop, advanced mobile, basic mobile) from browser string
21 Handling Mobile Devices Now we (think) we know the device, how can we deliver appropriate content?Switching stylesheetsTweaking classes and idsTransforming contentSeparate sitesFrameworks (e.g. Wordpress Themes)
22 More on Transformations XSLT capabilities – Good for:Re-ordering contentSelecting elementsModifying attributesXSLT shortcomings - Not so good at:Counting stuff (get first ‘n’ items from list)Being easy to write from scratchGood starting points at wwbota.free.fr/XSLT_models/README.html
23 XML Name Spaces - 1 May have come across these reading about XSLT One approach to problem of mixing different XML dataTo avoid confusion with same element namesIdea is to “prefix” each set of elements with a unique stringTypical GLOBALLY unique string is a URIToo long / messy to put in front of elementsSo provide a “shorthand” prefix, unique to THIS document<xml version=“1.0”xmlns:blazon=“xmlns:xhtml=“xmlns="<xhtml:body>….<blazon:body>Information….</blazon:body>
24 XML Name Spaces - 2 Having said all that… But not always necessary: Useful to know about namespacesBut not always necessary:Redefine your XML to avoid clashesRewrite your XML “on the fly” (e.g. use XSLT before merging)Work out meaning from contextWe have 2 title elements – is this really a problem?Is it simple to tell them apart?<order><customer><title>Mr.</title><surname>Smith</surname>….<items><book><title>XML In a Nutshell</title><isbn> — </isbn>…..
25 Moving on to Mobile Apps All the preceding discussionWas about the development of websites specifically for mobilesDevelopment of applications for mobiles is a different thing entirelyApps are great (but NOT always necessary)Is the Wikipedia app significantly more useful than the website?Discuss!
27 Developing Android Apps - 2 App Inventor is not a toy!A lot of commonality with professional Android development environmentApproach to User Interface buildingAttaching (Java) code to eventsDesktop based emulatorE.g. Eclipse “Indigo” with Android SDK(See next slide)
29 TMA Tips: Project Planning In developing your app there are several key-stages to follow:Have a good understanding of what is requiredWhat is essential?What are the nice haves?Produce a Structured planProduce progression versions.Critically appraise your workBe prepared to start again!
30 TMA03: You are going to need A stop watch to record the running dataAccess to a networkAccess to the server to upload the data
31 TMA03: Possible Approach Start small, take small, incremental steps - E.g.Display a timer that updates every secondAdd a start button that starts the timerAdd a stop button that stops the timerAdd a reset button…. And so onDon’t try to build everything at once!
32 TMA03: Notes Don’t get bogged down with App Inventor 50% of the marks are for narrative answers in your report!Your App will be tested by meSo read “what to submit” very carefullyDon’t try to do too muchMeeting the specification is sufficientUse sensible variable names / button labels etc.Help me understand your appIt should NOT need a manual!
34 Reminder about deadlines etc. TMA03 Deadline is noon 4th July(Grace period to midnight, but no support available)Make sure you understand what you need to submit!Block 4 available 2nd JulyWill include part 1 of EMA – the work planEMA materials available sometime in JulyWork plan submission date 22nd AugustFinal submission date 26th SeptemberNO extensions for EMA (either part!)Not from me anyway!You can try student support but you will need a really good reason!
35 Thank You For Attending! There will be a recording available in the elluminate room in a day or soDownloadable audio and video versions from a few days laterThank you, and goodnight!