Version Date: Dec. 16, 2015
This release has been superseded by a subsequent release.
- Upgrade mercurial to fix some Send/Receive problems. The FLEx Send/Receive functionality is now using a new version of the underlying version control system. While most users were not experiencing problems before, there were a few serious issues that could only be addressed by changing to a new version.
- Build natively on Ubuntu 14.04. Until now, there have been many issues with the version of FieldWorks on the current Long Term Support version of Linux, but we now believe many of these have been solved.
- Many keyboard improvements on Linux. Most of the known problems and crashes on Ubuntu 14.04 related to automatic keyboard switching have been fixed. All of this is greatly improved.
- Make FLEx work with Keyman 9.0.
- Upgrade Graphite to Graphite2. Now Graphite is fully integrated into the Linux version of FLEx (including Font Features), and the performance in Windows should be faster.
Bugs fixed since 8.2.3
- Correct misplaced cursor when splitting Morphemes using Keyman 9. LT-16766
- Localization for “Append to Gloss” field can now be shared across projects. LT-16734
- Hermit Crab now requires graphemes to be specified for phonemes. LT-16771
- Solve problem with deleting entries when collaborating with WeSay. LT-16804
Bugs fixed since 8.2.2
- Update the semantic domains for Chinese and Spanish.
- Add translated Semantic Domain lists for Burmese and Malay.
- Fix a rare bug where a lexical relation link pointed to the wrong sense. LT-16254, LT-16283
- Fix a crash with the Korean keyboard. LT-16673
- Enable viewing S/R project messages on Linux. LT-16675
- Fix two internal errors in the Hermit Crab parser. LT-16697, LT-16698
- Fix a problem with footnotes when accessing Paratext texts in FieldWorks Texts & Words. LT-16661
- Prevent error message about pictures when accessing Paratext texts in FieldWorks Texts & Words. LT-16662
Bugs fixed since 8.2.1
- In Linux, correct a crash when attempting to import texts from ParaTExt. LT-16615
- Correct SFM import error when mapping to a custom variant field. LT-16624
- In Linux, correct crash when typing in pronunciation fields that are not yet expanded. LT-16255
- Display complete “Cannot open project’ message when this error is encountered. LT-16571
- Correct crash on Linux when cancelling import of ParaTExt data. LT-16647
- Correct problems when using Keyman 9 with tables using NFD context. LT-16637
- Prevent Choose Texts dialog from importing texts before they are selected. LT-16636
- Add translated list for semantic domains for Swahili.
Bugs fixed since 8.1.4
- Correct some message processing in the conflict message dialog box. LT-16600
- Fix display glitches in the welcome dialog. LT-16571
- Fix for Duplicate Guid when sharing through LIFT. LT-16201
- In Linux, fix backspacing in Morphemes. LT-16593
- Fix SFM import transform to handle inline markers in String fields. LT-16590
- Allow inserting multiple media files at the same time. LT-16566
- Correct Lexical relation name in Paratext Related Words. LT-16288, LT-16576
- Improve Error Message when associating Paratext 7.6 with an open Flex project. LT-16119
- Allow association of Flex with Paratext 7.6 in Linux. LT-16281
- Correct Help button for researchers field.
- Allow Send/Receive of projects with non-ascii characters in their names. LT-16306, LT-15659
- Add a utility to sort reversal subentries. LT-16468
- Correct crash merging senses in another window.LT-16403
- Refresh Inflection Features after insertion or deletion of a feature value. LT-14629
- Change default for Rapid Word Collection to Gloss instead of Definition. LT-16490
- Prevent user from entering illegal characters in dictionary configuration which will cause problems later. LT-16525
- Allow attaching and playing .mp3 files in audio writing system. LT-15766
- Prevent crash when undoing Approve in the interlinearizer. LT-15320
- Correct circular reference in Try a Word in Linux. LT-16250
- Correct Burmese rendering problems with Ekaya keyboard. LT-15565
- Correct a race condition when entering a lexical entry. LT-15878
- Correct an error in drop-down control processing. LT-15809
- Save a busy user’s work at least every 5 minutes.LT-16553
- Don’t reset Free Translations on Replace All. LT-16331
- In Linux, restore default keyboard when switching to another app.
- In Linux, correct a crash when clicking Try it button [HermitCrab]. LT-16080
- In Linux, don’t insert text into active field when the Find dialog is open. LT-16452
- Correct many Linux keyboard errors. LT-16242, LT-15870, LT-16237
- You can collaborate on the entire project (advised) or just on the lexicon (LIFT – for use with other programs).
- The Send/Receive Lexicon option is designed for collaborating with team members who use WeSay. Using the Send/Receive Lexicon option for sharing lexical data between FLEx users when there are no WeSay users in the team is not recommended. FLEx users should use Send/Receive Project to share the full data set, rather than using the more limited Send/Receive Lexicon, which is limited to what is covered by the LIFT format.
- You can use both kinds of Send/Receive if you are working in a team which uses both FLEx and WeSay. In this situation, it is recommended to have only one FLEx member use Send/Receive Lexicon, and then use the Send/Receive Project to share that data with the other FLEx team members.
- You can collaborate using a USB flash drive, an Internet server or Chorus Hub (a special network folder.)
- Before using Send/Receive Internet using the default server, you need to go to languagedepot.org and create a user account. For each project you want to Send/Receive, you also need to contact firstname.lastname@example.org so they can create an online repository for you. They need the name and ISO code of the language plus whether you will be using the option Send/Receive Project (FLEx only) or Lexicon (for use with other programs).
- When using Send/Receive Internet for the first time, you need to click the Settings button before you can use it, in order to enter the details of the remote server and the project’s repository id, etc.
- To use Chorus Hub for local area network, one computer on your network needs to start the Chorus Hub program. Instructions are on the Settings dialog on the Chorus Hub tab.
- Concept: all start from one copyof the project. Someone sends it. Others receive it. All can then send/receive.
- Someone sends it
The person who already has the project – the master everyone is going to start working with – uses Send/Receive > Send this Project (or Lexicon) for the first time. This will create the special collaboration “repository” on the destination they choose (USB, Internet, Chorus Hub.)
- What if there were multiple copies of the project already? Can we merge them? No, not automatically. You need to do any importing or exporting you need to do to come up with a master project which is the best version of the project. Delete the now outdated copies of the FieldWorks project from other computers.
- Others receive it
- The person who doesn’t yet have the (master) project uses Get Project from a Colleague on the Welcome dialog or Send/Receive > Get Project from Colleague. This is a one-off step!
- If you want to join a Lexicon (LIFT) repository from a project you already have in FLEx, use Send/Receive > Get Lexicon and Merge with this Project. This is a one-off step!
- Everyone uses send/receive to collaborate
Once the project has been sent, and each collaborator received it the first time, all collaborators can continue to work together and share data using Send/Receive > Project, or Lexicon. The settings are saved and do not need to be re-entered. There is a toolbar button which will open the Send/Receive dialog to the last type of Send/Receive you did (project or lexicon).
- Someone sends it
- The Messages (a.k.a. Conflict Report) will be displayed after Send/Receive if there are new messages to review. You can also open it at any time with Send/Receive > View Project Messages, or View Lexicon Messages, as appropriate.
- Many merge-related messages are hard to understand. This is probably going to be an ongoing area of improvement, depending on feedback – how problematic the messages are in practice.
- Send/Receive does a really good job of automatically merging data when users have changed different parts of the project. When two people have edited the same or very closely related data in the same sync cycle, send/receive keeps the data entered by the current user. A conflict message is generated and includes information of the other user’s change for comparison. If you prefer the other user’s change, you will need to copy and paste the data manually into the appropriate place in FLEx; there is not yet a tool to select one change over another and have the FLEx project automatically updated.
- If one user adds word glosses to a text at the same time as another user adds word categories to it, this will not be merged conveniently because in the FLEx database these separate pieces of data are both part of a word’s analysis.
- If one user modifies an entry, sense, etc. at the same time as another user deletes that same item, send/receive will keep the modification rather than the deletion.
- If a team needs to use the global change tools in FLEx, such as Bulk Edit, merge conflicts will be reduced if the team first does a series of Send/Receives to get all sync’ed to the same state. Then one user can do the global changes, and the team then re-syncs to get those changes and continue on with their tasks.
If you have used older-style sharing over a local area network (projects have the extension fwdb), you need to turn off that way of sharing (revert to fwdata format) in order to try Send/Receive for collaborating. You can do this in File > Project Management > Project Locations and Sharing. Uncheck the box labelled “Share projects stored on this computer.”
If you want to track our progress on these and other issues, follow one of the links below and sign up for an account on our JIRA system.
- It is strongly not recommended to restore over (replacing) an existing project with which you are collaborating using send/receive. The subsequent send/receive would send a huge number of changes to all the other team members, effectively restoring the old version of the project on every team member’s computer.
- You cannot have non-ASCII characters in the FLEx project name to use Send/Receive.
- The menu item “Copy (Ctrl+C)” isn’t working on the “Conflict Detail” dialog box. LT-14327
- The Text Chart is changed incorrectly (words are moved to emptied cells) after another user deletes some charted words from the text. LT-14317
- If both users edit the same phonemes, or add inflection features to the same lexical entry, the results may need subsequent editing. E.g. A phoneme may have incompatible phonological features and an entry may have incompatible inflection features.
- If you add a question or add a message to a merger conflict/notification, it is not possible to edit or delete those comments subsequently. LT-14076
- Using any Send/Receive commands in quick succession usually causes a message to pop up which claims that FLExBridge is already running. If it is not (e.g. you closed the Messages window then need to reopen them) wait for 5 seconds and try again.
- Linked media files over 1MB in size are not being transferred. No movie files of any size are being transferred. If a user subsequently removes the link to the file due to the current restrictions, the warning messages continue to be displayed at each send/receive operation if the file is still in the project folder.
- When both users change the properties of the same style, the resulting merge conflict message does not state the conflicting style settings.
Send/Receive Lexicon (LIFT) with e.g. WeSay
- Send/Receive Lexicon should not be used to pass data between two or more FLEx users. You should use Send/Receive Project.
- Send/Receive Lexicon depends on the LIFT standard. Some FLEx data is not handled well yet by this collaboration method. E.g. Which entries belong in which inflection template slots and some other morphological grammar facts stored on a lexical entry. Components of a complex form. Custom lexical relations.
- If you created a custom field in WeSay and used a previous version of LIFTBridge with FLEx (e.g. in 2012), FLEx will crash when you try to open the project. Please contact us for help. LT-13850
- In Dictionary Configuration, the check box under sense that says “display each sense in its own paragraph” is not working properly. This will be addressed in a development effort to redo Dictionary Configuration.
- The Sena 3 (sample project) link doesn’t work on the new Welcome dialog box the first time the dialog opens. Workaround: Use Open and then select Sena 3. LT-14324
- Semantic Domain’s Suggest feature is too prolific when there is more than one word in the Gloss field. LT-14243
- Interlinear SFM import fails with Unicode to Unicode converter. LT-13741
- Right-click menu is inappropriate for Status and Confidence fields. LT-14195
- Unicode Character Editor fails to process code points out of plane 0. LT-14263
- Type-ahead doesn’t work on custom fields referring to custom lists. LT-13248
- To use Phonology Assistant with this version of FieldWorks, you need to upgrade Phonology Assistant to version 3.4.6 or later.
- To use FLExTools with this version of FieldWorks, you will need to upgrade to version 1.1.4.
A Full package contains .NET 4.0 and Windows Installer 3.1; a Minimal package does not.
Users can probably use the minimal package unless this is the first installation of FieldWorks and their operating system is older than Windows® 8.
No patch is available for this version.
- Download one of the Full or Minimal installation packages above.
- Double-click the exe file you downloaded. After it extracts files, the first installation screen appears.
- Follow the on-screen instructions. Make sure you allow the SIL Software installer to install FLExBridge and any other required third party software it says is required.
- If you have used FieldWorks 6.0.6 or earlier on this computer before, you may see two further steps:
- Select which if any projects you wish to migrate from FieldWorks 6.0.6 or earlier format.
- Choose whether to uninstall the last version of FieldWorks or its desktop shortcuts. Help.
For more information on upgrading to FieldWorks 7 or 8 from an older version (6 or earlier), see here.
Please check the Known Issues section above.
Note: The movies have not yet been updated since FieldWorks 6.
- Sena 2 – 14 MB (Lexicon and Texts for training)
- Sena 3 – 15 MB (Lexicon and Texts data)
- Lela-Teli 2 – 2 MB (Data Notebook for training)
- Lela-Teli 3 – 2 MB (Data Notebook data)
- Click one of the sample projects, such as “Sena 3″. Download and save this file to your computer. If you find that your browser (e.g., I.E.) has renamed the files to .zip, you will need to rename them first to .fwbackup in order for the FieldWorks restore function to work.
- Launch FieldWorks Flex.
- Open the Restore a Project dialog by doing one of the following:
- If the welcoming Language Explorer dialog appears, click “Restore a project from a backup file”.
- Or if the main FieldWorks Language Explorer window appears, choose File > Project Management > Restore a Project.
- On the Restore a Project dialog, click “Another location” and click Browse.
- Navigate to the downloaded sample project file (which may be in your Downloads directory by default), click the file, and click Open.
- Click OK.
Here is the MD5 hash of each of the download packages, should you wish to use this to verify the download completed successfully.
Recommended System Configuration
- Operating system: Microsoft Windows® 7 with Service Pack 1
- Computer and processor: Computer with Intel Core® (or equivalent) processor running at 2.2 gigahertz (GHz) or higher
- Memory: 2 gigabytes (GB) of RAM or more.
Note: The more RAM and the faster the CPU, the better FieldWorks will perform, especially with larger projects.
Minimum System Requirements
- Operating system: Microsoft Windows® XP Professional with Service Pack 3 or later, Windows Vista® with Service Pack 2 or later, Windows® 7 with Service Pack 1, Windows® 8, Windows® 10.
- Computer and processor: Computer with Intel Pentium® (or equivalent) processor running at 1.5 gigahertz (GHz).
- Memory: 500 megabytes (MB) of RAM.
- Hard disk: Hard disk space requirements will vary depending on existing machine configuration and custom installation choices. As a guideline figure, you should have at least 1.5 gigabytes free prior to installation. In any case, you are recommended to have at least 10% of your hard drive free in order to allow Windows to run properly.
- Display: 1024 by 768 pixels screen resolution or greater (for laptops, use native display resolution).
- Offline storage: An external USB drive, network drive, or writeable CD-ROM to allow offline data backups.
- Peripherals: Mouse or compatible pointing device.
This version of FieldWorks is available on both Windows and Linux. Send/Receive became available for Linux starting with 8.0.5. Data created in one can be opened (or restored) in the other, and vice versa. (Note that data created in any version cannot be opened by any older version on either platform.)
Instructions for installing the Linux version are available on the LSDev Linux wiki.