FFWLD Frequently Asked Questions


Q. Does FFWLD support metric units (°C, km/h, mm, hPa, etc.)?

A. Indeed it does. In fact, FFWLD supports *all* of the display units
   available on the VP2 WeatherLink® console.

Q. Does FFWLD support internationalization (multiple languages)?

A. Not at present. The generated text is currently in English.
   Internationalization has not yet been implemented because the initial
   target audience is English-speaking users. If there is sufficient
   interest, non-English language support may be considered for a future
   release.

Q. Why does FFWLD generate HTML on the server instead of using
   the WeatherLink JavaScript API?

A. Because the way FFWLD works:

   • API credentials remain on the server
   • No client-side JavaScript dependency
   • Works with static pages, SSI, PHP includes, templates, etc.
   • Simpler deployment and less browser-side complexity

Q. Does FFWLD require a database?

A. No. It retrieves current observations directly from the WeatherLink
   API and generates output files. No database is required.

   However, FFWLD also generates a JSON file. This makes it
   straightforward to write additional server-side software to populate
   a database, generate historical reports, or integrate the data with
   other applications.

Q. Why doesn't FFWLD fetch historical data?

A. FFWLD is intentionally limited to retrieving the current conditions
   from the WeatherLink API and generating web-site content. Historical
   data collection, storage, reporting, and analysis are outside the
   scope of the project.

Q. Why did you choose to use Perl, rather than a "more modern" language such
   as Python, or a more web-centric language such as PHP?

A. The choice was based primarily on personal experience and long-term
   maintainability. The author has been writing Perl for many years and
   knows the language well, making it possible to develop and troubleshoot
   software quickly and confidently.

   Perl also has a long history of backward compatibility and interface
   stability, which is an important consideration for software intended
   to continue working for years with minimal maintenance.

   Python has its strengths and may be a better choice for many projects,
   but it is simply not the author's preferred language. Likewise, while PHP
   is well suited to web applications, the author's previous experience has
   been that supporting code across PHP versions required more maintenance
   than he considered desirable for this type of utility.

   Ultimately, the best language for a project is often the one that allows
   the author to produce reliable, maintainable software. For this project,
   the author felt that language was Perl.

Q. How do you pronounce "FFWLD?" It has no vowels.

A. I pronounce it "fwilled." Like "swilled," only with an f instead of the s.

   Yes, I know what "swilled" means. No, I couldn't think of a better
   mnemonic.

Trademark Notice

    WeatherLink® is a registered trademark of Davis Instruments Corporation.
    FFWLD is an independent, third-party utility that is neither affiliated
    with nor endorsed by Davis Instruments.