source-foundry / filterlistmanager Goto Github PK

I got this from a user:

Details:
Traceback (most recent call last):

 File "~/Library/Application Support/Glyphs/Repositories/Filter List Manager (FLM)/FilterListManager.glyphsPlugin/Contents/Resources/plugin.py", line 88, in <module>
   shutil.copy(GLYPHS_PLIST_FILE, FLM_BACKUP_ORIGINAL_FILE)

 File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py", line 139, in copy
   copyfile(src, dst)

 File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py", line 96, in copyfile
   with open(src, 'rb') as fsrc:

IOError: [Errno 2] No such file or directory: u'~/Library/Application Support/Glyphs/CustomFilter.plist'

App:2.6.5-1342 Plugin:0.5.1-51

Add logging support that includes:

• INFO: for definition files that are parsed
• INFO: for new filter lists that are created
• ERROR: for errors in execution
• ERROR: for exceptions that are caught

Logs will be maintained on the path: ~/GlyphsFilters/logs/flm.log

Comments from Georg Seifert on the Glyphs app forum:

And I would strongly advise agains putting something in ~/GlyphsFilters. Those things belong in the App Support folder.

I really meant it when I when I said to not store stuff in the users main folders. That is like office marking a folder with internal shit in my documents folder. That is so annoying.

Shall we move the entire GlyphsFilters directory to a Glyphs application specific path on the path Application Support/Glyphs as Georg recommended?

Pros:

1. eliminates an application-specific directory under a user's $HOME directory

Cons:

1. makes the directory less accessible to the average user for modification of the contents, review of logs, access to their backup files.
2. anyone who begins to use the plugin with the current approach has to modify their setup following the change, or we have to create a transition approach...

Con (1) is addressed by the existing plugin menu item under the Glyphs Edit menu that automates opening of this directory in the macOS Finder window. This could be easily changed to the path that he suggested. That doesn't make it simple for many users to open through text editor menus/dialogs in order to edit their files, though most support drag/drop of the file on the editor icon. By design, users must directly modify the text file contents of this directory in order to use the plugin.

We could consider saving the backup files and logs under Application Support/Glyphs if this is felt to be a better approach for infrequently accessed but occasionally necessary data related to the plugin?

What languages? Need native speaker/writer assistance to support this.

Will need language codes for all languages that we support: https://docu.glyphsapp.com/#localize

For those who are interested in transitioning to this approach to filter list management and have existing lists defined in Glyphs, it would be helpful to have a tool that automatically exports existing Glyphs filters to the Filter List Manager definition file format (i.e., newline-delimited lists that support comments) and installs them on the proper directory path so that the plugin can use them immediately for updates (and importantly so that they are not lost and need to be re-created).

The approach to begin using this plugin would then be:

• Use export tool to export all existing filter lists to filter list definition files that are contained in the directory on the path ~/GlyphsFilters
• Install Filter List Manager plugin
• Add any desired additional definition files to ~/GlyphsFilters directory
• Create the new filter lists with Edit > Update Filter Lists in the Glyphs application menu

I would like to create a separate section with dividers in the Glyphs app Edit menu above and below the three new menu items that are added by this plugin so that it appears as follows:

---divider---
FLM menu item 1
FLM menu item 2
FLM menu item 3
---divider---

Currently the menu items under the Edit menu are intermixed with other menu items.

What languages? Need assistance from native speaker/writers to support this.

We will need language codes for all languages that we support: https://docu.glyphsapp.com/#localize