You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A preample containing references to journal entries would be very powerful. Something like You have read @"Bandit's Journal":4., where the text of page 4 of Bandit's Journal is inserted.
This approach has some open problems:
Journal names in Foundry are not unique. The unique identifiers are not displayed to the user (although we could of course expose them).
Journal names can probably contain arbitrary unicode symbols, which makes parsing the syntax hard. This also points towards using the identifiers.
Suggested approach:
Upon typing @ in a preamble, we open a context menu and offer the user a selection (hopefully Upon beginning to type the UnKenny text macro, offer a list of available UnKenny actors. If possible. #38 is implemented by then and the user is accustomed to this behaviour) of journal entries. The text contains the unique identifier. We also display it in journal entries for copy-pasting, but only subtly. The Colon- syntax is optional. If not present, all journal pages are included.
The text was updated successfully, but these errors were encountered:
A preample containing references to journal entries would be very powerful. Something like
You have read @"Bandit's Journal":4.
, where the text of page 4 of Bandit's Journal is inserted.This approach has some open problems:
Suggested approach:
Upon typing @ in a preamble, we open a context menu and offer the user a selection (hopefully Upon beginning to type the UnKenny text macro, offer a list of available UnKenny actors. If possible. #38 is implemented by then and the user is accustomed to this behaviour) of journal entries. The text contains the unique identifier. We also display it in journal entries for copy-pasting, but only subtly. The Colon- syntax is optional. If not present, all journal pages are included.
The text was updated successfully, but these errors were encountered: