sweater:plain-old_web_tech_implementation
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
sweater:plain-old_web_tech_implementation [2019/03/05 02:27] – mithat | sweater:plain-old_web_tech_implementation [2019/03/05 03:41] (current) – mithat | ||
---|---|---|---|
Line 6: | Line 6: | ||
The Sweater app's structural needs, at least for now, are quite modest. That makes it a good candidate for using just plain-old HTML/CSS/JS for the app's structure. In this next section, I will try to develop a basic app structure and implement data-handling using plain-old JS. If nothing else, this will give us a better understanding of the problem and where various libraries might be helpful. | The Sweater app's structural needs, at least for now, are quite modest. That makes it a good candidate for using just plain-old HTML/CSS/JS for the app's structure. In this next section, I will try to develop a basic app structure and implement data-handling using plain-old JS. If nothing else, this will give us a better understanding of the problem and where various libraries might be helpful. | ||
- | If this turns out to actually be a manageable situation, we can then bring in the [[design]] specifications for the UI and functionality. | + | If this turns out actually |
+ | |||
+ | ==== Weather APIs ==== | ||
+ | |||
+ | The project will need to periodically get updated weather conditions and then update the UI. So maybe a good next step is to start is surveying the the available weather APIs and pick the one that is well-suited to the project (as we currently understand it). | ||
==== The HTML ==== | ==== The HTML ==== | ||
Line 12: | Line 16: | ||
Because the [[design]] specification for the app may still be in flux, the focus of the current work will be limited to getting the needed data from a data source and letting it update the UI. We start out with a very plain, text-only HTML page that has only enough markup in it to let some fields be updated with JS. | Because the [[design]] specification for the app may still be in flux, the focus of the current work will be limited to getting the needed data from a data source and letting it update the UI. We start out with a very plain, text-only HTML page that has only enough markup in it to let some fields be updated with JS. | ||
- | The determination of outerwear will require the knowledge of the current " | + | It's a fair guess that the determination of outerwear will require the knowledge of the current " |
<file html sweater.html> | <file html sweater.html> | ||
Line 20: | Line 24: | ||
</ | </ | ||
- | ==== Weather APIs ==== | + | ==== The CSS ==== |
- | The project will need to periodically | + | How about no CSS? This phase of the work isn't about how things look. We're really just trying |
==== The JavaScript ==== | ==== The JavaScript ==== | ||
- | |||
- | The project' | ||
<file html sweater.js> | <file html sweater.js> | ||
// TODO | // TODO | ||
</ | </ |
sweater/plain-old_web_tech_implementation.1551752863.txt.gz · Last modified: 2019/03/05 02:27 by mithat