🚀 go-pugleaf

>Comment by Steven Vincent:
>2.  Would it be possible for future versions to store reference types in a
>folder, similar to the way styles are now handled, instead of in the prefs
>file?  And, of course, it is absolutely essential that there be more than the
>current number of reference types.  I have had to create a couple of types
>for materials I use frequently, which has meant losing a couple of the pre-
>defined types.  Were I to share my types with someone else, or if they were
>to share theirs with me, our prefs, including our own types, would be
>overwritten.  If one could add or create types in much the same way one adds
>or creates styles, it would be a major enhancement.

I like this idea. A standard reference types file could be distributed with
endote, and could be updated as necessary (like the sam virus definitions
file). The custom types should also be mappable to a standard type. Files
which use a custom type, store minimal information about the type. An alert
should be presented if that type is not present, like when adobe
illustrator encounters a missing font.