Platform: Windows (other platforms)
Version: Alpha 1.1.1
Release date: June 21, 2016
This alpha version is deprecated - It is no longer able to validate FSDL documents based on FSDL 3.0 - find the latest Windows version
This version of Frogans Player for Developers embeds version 1.0.1 of the FSDL Software Library (alpha).
Note: Frogans Player for Developers (alpha) is a preliminary version provided on an "as is" basis. The OP3FT cannot guarantee that the rendering performed by this alpha version will be compatible down to the last pixel with the rendering performed by the release version of Frogans Player.
To be informed of the distribution of versions of Frogans Player, subscribe free of charge to the Announcement read-only mailing list.
Frogans Player for Developers (alpha) is intended for developers wishing to contribute to the development of the FSDL language and Frogans Player by creating and testing their first Frogans sites using FSDL 3.0.
This Frogans Player version is not intended for the general public.
Any contribution to the development of the Frogans technology, in any form, is considered as acceptance of the Frogans Technology Development Contributor Policy and the commitments it contains, without restriction or reserve.
This alpha version represents an opportunity for developers to participate in the development of the Frogans technology.
To post questions or suggestions, or to report errors relating to the FSDL language or to this Frogans Player version, subscribe free of charge to the Early-questions mailing list. Please prefix the subject of any posts you make to this list concerning FSDL 3.0 with "[FSDL]" and prefix the subject of any posts concerning Frogans Player for Developers with "[FP-Dev]".
The OP3FT is looking for feedback from the developer community in two key areas:
- The FSDL 3.0 language
You can suggest improvements in the design of FSDL, such as:
- changes to the minimum, maximum, and default values of attributes
- changes to applicability rules for attributes
- new Frogans slide rendering constraints (intended to ensure useability for end-users)
- The implementation of Frogans Player for Developers
You can suggest improvements or report errors in the implementation of Frogans Player for Developers, in areas such as:
- validation of FSDL documents (including error messages)
- rendering of Frogans slides
- Frogans Player GUI (e.g. the contextual menu, entry of Frogans addresses, icons)
Your feedback can concern either a given platform (Windows, MacOS X, or Linux) or all platforms.
Operating System versions currently supported:
- Windows 2000
- Windows XP
- Windows Vista
- Windows 7
- Windows 8
- Windows 8.1
- Windows 10
- 133 MHz or more Pentium microprocessor (or equivalent)
- At least 512 megabytes (MB) of RAM
- At least 256 megabytes (MB) of available space for storage (e.g. HDD, SSD)
- Video adapter and monitor with 640x480 or higher resolution and 16 bit color
This version allows you to create and test Frogans sites whose Frogans slides are hosted either locally on your system or remotely on a server on the Internet (using the UCSR network 'IP_DNS_TCP_HTTP').
To create and test your Frogans sites, you need to configure test Frogans addresses, i.e. Frogans addresses starting with test*, via the configuration-for-testing.xml file in the Frogans Player directory. This configuration file is local to your system.
This version can also resolve Frogans addresses of public Frogans networks, i.e. Frogans addresses starting with frogans* (or a transcription of the name 'frogans' followed by an asterisk, such as 福更斯* or ФРОГАНС*) so that you can publish your Frogans sites on the Internet and make them available to others using your Frogans addresses (more information).
Note: The UCSR network 'IP_DNS_TCP_HTTP' that is currently used by Frogans Player to communicate with FNS servers (i.e. servers resolving Frogans addresses) and with servers hosting Frogans sites only supports direct connections to the Internet (no proxies).
This version implements both the graphical and the dynamic elements of FSDL 3.0.
The following elements are available for testing: <frogans-fsdl>, <resimage>, <respixels>, <resdraw>, <respath>, <setfont>, <font>, <restext>, <text>, <setfilter>, <filter>, <setrelief>, <relief>, <setshadow>, <shadow>, <resmerge>, <merge>, <layer>, <file>, <button>, <next>, <redirect>, <setdata>, <data>, <session>, <setentry>, and <entry>.
This version does not manage all Frogans slide rendering constraints (intended to ensure useability for end-users), which are currently under discussion.
Changes between 1.0.1 and 1.0.2:
- Resolved issue: The error reporting system for Frogans address resolution mistakenly used the title "Error in configuration-for-testing.xml file" instead of "Error resolving the Frogans address on the Internet".
- Resolved issue: An incorrect error message could be reported when an FSDL document or an image file was not found in the Frogans site root directory. This issue was introduced in alpha version 1.0.1.
- Resolved issue: When an FSDL-Request document was generated to load an image file dynamically, session information from the previous FSDL document was used rather than session information from the current FSDL document.
- Resolved issue: An internal error occurred if a redirection Frogans slide (i.e. an FSDL document with a <redirect> element) was loaded by clicking on a button. In addition, redirect loops (i.e. when a Frogans redirection slide redirects to another Frogans redirection slide) were not detected.
- Resolved issue/Linux only: In the user interface dedicated to entries, it was possible to enter more characters than the maximum number defined by the value of the "max" attribute of the <entry> element.
Changes between 1.0.2 and 1.1.1:
- The file containing the fonts defined in FSDL 3.0 has been updated. Four physical fonts have been replaced (122-6-sans-r, 122-7-sans-r, 122-8-sans-r, and 122-9-sans-r) and ten physical fonts have been added (109-2-mono-b, 110-2-mono-b, 111-2-mono-b, 112-13-mono-b, 112-14-sans-b, 122-29-sans-b, 122-30-sans-b, 122-31-sans-b, 122-32-sans-b, and 122-33-sans-b).
- The FSDL Recap v15 document was released to reflect the above changes (see FSDL 3.0 resources).
- Resolved issue: An internal error occurred if a <next> element referred to a <file> element where the value of the "nature" attribute was 'dynamic'.
- Resolved issue: An internal error occurred if an attempt was made to open more than 10 Frogans sites at the same time, which is the current limit. This issue was introduced in alpha version 1.0.2.
- Resolved issue: Management of the character encoding method used to encode FSDL documents and FSDL-Request documents has been improved. The default serialization has been changed to little-endian (UTF-16LE) for an FSDL document that uses UTF-16 and does not include a Byte Order Mark (BOM). The character encoding method used to encode an FSDL-Request document is now always identical to the method used to encode the FSDL documents of the Frogans site.
Known issues (as of June 21, 2016):
- The second and third steps in the optimization of Frogans Player for Developers have not been completed yet. (The second step consists in optimizing processes implemented in low-level functions, and the third step consists in optimizing the overall process for parsing and rendering Frogans slides.) Therefore, parsing and rendering can be slow. The release version of Frogans Player will be significantly faster. As a reminder, the first step was completed in alpha version 0.1.7. (This step consisted in enabling options that control optimization when compiling the Frogans Player runtime engine written in C.)
- The error reporting system of the XML parser and the FSDL validator can generate incomplete or inaccurate messages.
- The error reporting system of the validator of the configuration-for-testing.xml file can generate incomplete or inaccurate messages. This configuration file is used to set test Frogans addresses for use with Frogans Player for Developers.
- Since all Frogans slide rendering constraints are not managed yet, internal rendering errors can still occur. Such an error can occur, for example, if the placement of a button prevents it from being visible on the Frogans slide.
- Buttons leading to a Web site (i.e. <button> elements where the "goto" attribute equals 'web-site' and the "url" attribute contains a URL) and buttons leading to an email message (i.e. <button> elements where the "goto" attribute equals 'email-message' and the "email" attribute contains an email address) are not yet available for use. Currently, the only possible value for the "url" and "email" attributes of the <button> element is '' (the empty string).
- Frogans Player for Developers [noinstall] (archive in 7z format): FrogansPlayer4Dev-noinstall-alpha1.1.1-win32.7z - 45.9 MB - [ SHA1 ]
- Frogans Player for Developers [noinstall] (archive in zip format): FrogansPlayer4Dev-noinstall-alpha1.1.1-win32.zip - 66.7 MB - [ SHA1 ]
To create and test your own Frogans sites using Frogans Player for Developers, follow these steps:
- Download and decompress the archive on your system. A Frogans Player directory is created with the name of the archive.
Note: you should create this Frogans Player directory on the local drive of your system, and not on a networked drive; otherwise Frogans Player for Developers can be very slow at rendering Frogans slides.
- Open the Frogans Player directory and execute Frogans Player for Developers. A small, movable yellow circle representing Frogans Player is displayed in the center of the screen.
Note: if Frogans Player for Developers does not start or launch correctly, check whether your antivirus software is blocking the program or waiting for a confirmation. It has been reported that Avast! under Windows 10 prevents the program from launching correctly unless you disable the "scan program when executing" option. An Extended Validation certificate (EV) might solve this problem. This solution is currently being tested for Windows.
- Select "Open a Frogans site..." from the Frogans Player contextual menu and enter one of the following test Frogans addresses: test*helloworld or test*helloworld-live. The corresponding sample Frogans site appears, which you can move, resize, and navigate.
You can use the following Frogans addresses of public Frogans networks to access other demonstration Frogans sites online (these Frogans sites are not intended to be fully functional):
- Use the Frogans site contextual menu to reload the current Frogans slide (i.e. page of the Frogans site) or close the Frogans site. In order to display the Frogans site in the 640x480 resolution of the rendering canvas, disable the scaling factor (option for developers only in the Frogans site contextual menu).
- Each Frogans site is made up of one or more Frogans slides. The Frogans slides of a Frogans site (i.e. the FSDL documents and their auxiliary files) are stored in a specific directory called the Frogans site root directory. In this version of Frogans Player for Developers, Frogans site root directories can be located either locally on your system, or remotely on an HTTP server on the Internet.
For example, the Frogans site root directory of the sample Frogans site corresponding to the test Frogans address test*helloworld is located locally in the "helloworld" subdirectory of the "test" directory of the Frogans Player directory. The Frogans site root directory of the sample Frogans site corresponding to the test Frogans address test*helloworld-live is located remotely on an HTTP server on the Internet.
- To create and test your own Frogans site with the test Frogans address test*sitename, edit the configuration-for-testing.xml file in the Frogans Player directory. This configuration file is used to configure test Frogans addresses for use with Frogans Player for Developers. The "sitename" of your test Frogans address can contain up to 28 ASCII characters in the range from 'a' to 'z', from '0' to '9' inclusive, and the '-' character (no spaces allowed). For further information, read the guidelines in the comments of the configuration file.
- You can create and test as many Frogans sites as you wish. The number of Frogans slides in a Frogans site is unlimited. The Frogans site root directory can contain subdirectories.
- To modify an FSDL document, edit the corresponding file in your favorite text editor that supports XML (and remember to reload the Frogans slide afterwards). We suggest that you use the .fsdl extension for the file names of your static FSDL documents.
- For additional resources related to FSDL 3.0, including a recap and extracts of the technical specification, see FSDL 3.0 resources
- For a video presentation on the FSDL language and how to create Frogans slides, watch the FSDL tutorials given during the Frogans Technology Conference 5 (video).
- For a video presentation on how to create Frogans sites using a server-side scripting language (e.g. PHP), watch the presentation given during the Frogans Technology Conference 6 (video).
- You can also find inspiration and help in tutorials created by third parties, such as frogans-lab.com (in English). The OP3FT welcomes such initiatives!
Publishing your first Frogans site:
Now that you have successfully created and tested your first Frogans site, you can publish it on the Internet and make it available to others using a Frogans address of a public Frogans network.
To register Frogans addresses, you can make use of the services of the FCR account administrator of your choice in order to manage the registration of your Frogans addresses in the FCR (list here). Or, given your technical skills as a developer, you can become an FCR account administrator yourself.
Legal information / Credits
Frogans Player for Developers [noinstall]
Copyright ©1999-2016 OP3FT
All rights reserved
Frogans Player for Developers (the "Software") is developed by and belongs to the OP3FT.
The Software must be used in compliance with the Frogans Technology User Policy, accessible at the following permanent URL: https://www.frogans.org/en/resources/ftup/access.html.
By downloading and using the Software, you agree to and undertake to be bound by the version in force of the Frogans Technology User Policy.
Sample Frogans sites included in the "test" directory located in the Frogans Player directory are provided by the OP3FT to help you create your own Frogans sites. You are free to use, copy, distribute, modify, adapt, or share these sample Frogans sites.
The Software uses third-party source materials which are credited in the "COPYRIGHT-AND-LICENSE" directory available in the archive to be downloaded (see download).
© OP3FT - Home - Legal information