Flash Functionality not quite so flash
17th March 2003
What Do I Know points to Macromedia’s progress report explaining how thy have been responding to feedback on their recent site redesign. Todd Dominey makes the following insightful observation:
Perhaps most interesting, to me anyhow, was the crossroad of choosing which tool to use to solve a particular navigational problem, and the internal politics that likely surrounded their decision making. Case in point—the drop down option boxes on their index page. In Beta 1, the forms were created in Flash MX. In Beta 2, they have been completely replaced by tried and true, raw HTML option forms.
The Flash versions were styled nicely, with radius corners and a fancy diagonal light bevel, and some pretty nice interactivity. But did they solve any particular problem that a standard html form couldn’t handle? The answer was, and is, no. Sure, they looked nice, and were a good showcase of what you can do with Flash, but were they worth the extra bandwidth, page weight, and development time? Apparently not. They have been completely removed and replaced with much more familiar, lighter, and easier to update standard option boxes.
More recent articles
- Weeknotes: Llama 3, AI for Data Journalism, llm-evals and datasette-secrets - 23rd April 2024
- Options for accessing Llama 3 from the terminal using LLM - 22nd April 2024
- AI for Data Journalism: demonstrating what we can do with this stuff right now - 17th April 2024
- Three major LLM releases in 24 hours (plus weeknotes) - 10th April 2024
- Building files-to-prompt entirely using Claude 3 Opus - 8th April 2024
- Running OCR against PDFs and images directly in your browser - 30th March 2024
- llm cmd undo last git commit - a new plugin for LLM - 26th March 2024
- Building and testing C extensions for SQLite with ChatGPT Code Interpreter - 23rd March 2024
- Claude and ChatGPT for ad-hoc sidequests - 22nd March 2024
- Weeknotes: the aftermath of NICAR - 16th March 2024