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
an absolute name formed by the absolute name of their parent and their own one
a relative name in the context of any other storypoint (a path to them in the story tree starting from that other storypoint)
Names of any StoryItem will be useful for future scripting support
Names of StoryPoints will be useful for branching stories / navigation inside a Story, that is apart from the current linear navigation that goes between Previous/Next (including the depth-first graph traversing in case of nested StoryPoints)
The text was updated successfully, but these errors were encountered:
Hierarchical names could use . or maybe even / (to be like paths so that they can contain spaces more easily) or both
Probably better not use internal Delphi object names (that are limited to A-Z, 0-9 [not as first character] and _ chars) and implement own naming manager (that works on the graph of StoryItems, either cached and updated on changes [maybe combined with undo/redo system too], or extracted dynamically from the "scene" graph of all the Delphi FMX objects [partially and as needed, would take too much cumulative time to reextract often])
birbilis
changed the title
Allow changing name of StoryItem
Hierarchical names of StoryItems and absolute/relative navigation paths
Feb 10, 2025
If / is used for separator, then could use ".." to refer to parent like one does for filepaths and URLs (there is also ./ for current position but not sure if needed at all [can be implied], and / as prefix for a naming path would mean from root of Story)
StoryItems should have:
Names of any StoryItem will be useful for future scripting support
Names of StoryPoints will be useful for branching stories / navigation inside a Story, that is apart from the current linear navigation that goes between Previous/Next (including the depth-first graph traversing in case of nested StoryPoints)
The text was updated successfully, but these errors were encountered: