Numbers Guessing Game
Your Numbers Game
Get
clueYour
answerYour
ScoreClue? Score 0/0
-
Recent Posts
- Health App on iPhone Gait Checking Tutorial
- Cowsay Revisit Textarea Event Rearrangements Tutorial
- Cowsay Revisit Data Type Tutorial
- Cowsay Revisit Regarding Temporaries Tutorial
- Cowsay Cartoon Cell Edit Image Tutorial
- Cowsay Cartoon Cell Data Type Tutorial
- Cowsay Cartoon Ordered Recursion Tutorial
- Electric Vehicle Charging via Evie Primer Tutorial
Categories
- Ajax
- Android
- Animation
- Anything You Like
- Code::Blocks
- Coding
- Colour Matching
- Data Integration
- Database
- Delphi
- Eclipse
- eLearning
- ESL
- Event-Driven Programming
- Games
- GIMP
- GUI
- Hardware
- Installers
- iOS
- Land Surveying
- Moodle
- Music Poll
- NetBeans
- Networking
- News
- Not Categorised
- OOP
- Operating System
- Photography
- Projects
- Signage Poll
- Software
- SpectroPhotometer
- Tiki Wiki
- Trips
- Tutorials
- Uncategorized
- Visual Studio
- Xcode
Meta
Tags
Ajax animation background button canvas command line CSS Did you know DOM dropdown email emoji event form game Google Google chart hashtag HTML IFRAME image iOS Javascript MAMP media mobile navigation onclick overlay PHP popup programming select share sharing SMS SVG table text textarea tutorial url video web browser webpageYour Background Image
OnTopList
Tag Archives: theodolite
HTML and Javascript and CSS Survey Traverse Canvas Tutorial
Onto yesterday’s HTML and Javascript and CSS NSW State Survey Traverse Tutorial progress with our Survey Traverse web application functionality we wanted to augment … the existent tabular data … with … new canvas graphics to show the (Easting,Northing) co-ordinate … Continue reading →
Posted in eLearning, Event-Driven Programming, Tutorials
|
Tagged amg, angle, app, australian map grid, bearing, canvas, co-ordinates, datum, decimal degrees, degrees, elevation, ellipsoid, Google, HTML, iOS, iPhone, Javascript, Land Surveying, linear gradient, map, minutes, mobile, mobile app, NSW Survey Marks, programming, reduced level, seconds, sketch, state survey, survey mark, theodolite, tutorial
|
Leave a comment
HTML and Javascript and CSS NSW State Survey Traverse Tutorial
Yesterday’s HTML and Javascript and CSS Survey Traverse Co-ordinates Tutorial was kind of “mathematical” by nature. Today we add some realism. This realism stems from the discovery of a NSW State Survey mark in the local area (to the right … Continue reading →
Posted in eLearning, Event-Driven Programming, iOS, Land Surveying, Tutorials
|
Tagged amg, angle, app, australian map grid, bearing, co-ordinates, datum, decimal degrees, degrees, elevation, ellipsoid, Google, HTML, iOS, iPhone, Javascript, Land Surveying, map, minutes, mobile, mobile app, NSW Survey Marks, programming, reduced level, seconds, sketch, state survey, survey mark, theodolite, tutorial
|
Leave a comment
HTML and Javascript and CSS Survey Traverse Co-ordinates Tutorial
Today we revisit our HTML and Javascript and CSS Survey Traverse Tutorial web application because we want to allow it to be able to … do its usual entering of theodolite measured angles and distance measurements to glean Easting,Northing co-ordinates … Continue reading →
Posted in eLearning, Land Surveying, Tutorials
|
Tagged angle, bearing, co-ordinates, distance, HTML, Javascript, Land Surveying, measurement, polar co-ordinates, programming, theodolite, total station, tutorial
|
Leave a comment
The distinction between course-driven and immersion-driven learning is useful. A small extension to the australia.htm exercise would be a set of named map markers and a text filter: first update the visible markers on an input event, then add a collected/uncollected toggle, and finally persist only that toggle state in localStorage. That gives beginners a concrete reason to learn arrays, DOM updates and browser storage without needing PHP or MySQL first. It is also worth testing empty searches, a page reload and disabled storage separately; those are different failure cases. Disclosure: we maintain the GTA 6 interactive map. I am suggesting it as an example of a map-and-progress interface, not claiming that we used the tutorial code. Would you introduce persistence after the first working interaction, or keep the initial exercise entirely stateless?