As is, the functionality of tokens in the Save Text File and Save Image nodes is really useful. I think adding ability to define a token through the workflow will have profound impact.
Consider an ASCII to Token Create node similar to concatenate. One ascii input sets the token name and the other sets the token definition. Then the Text Parse Token node can be used to parse many of these dynamically created tokens. Users can use this to create dynamic save image paths/prefixes using other parts of their workflow.
The use case that gave me this idea: . Currently it has random text lists and strings that go through 8 concatenate nodes to produce a prompt at the end. If I could generate tokens from the random lists, it would greatly simplify the prompt creation.
(In this use case, I'm deliberately avoiding Text Parse Noodle Soup Prompts since I want everything contained in the workflow written to images without extra files.)
As is, the functionality of tokens in the Save Text File and Save Image nodes is really useful. I think adding ability to define a token through the workflow will have profound impact.
Consider an ASCII to Token Create node similar to concatenate. One ascii input sets the token name and the other sets the token definition. Then the Text Parse Token node can be used to parse many of these dynamically created tokens. Users can use this to create dynamic save image paths/prefixes using other parts of their workflow.
The use case that gave me this idea: . Currently it has random text lists and strings that go through 8 concatenate nodes to produce a prompt at the end. If I could generate tokens from the random lists, it would greatly simplify the prompt creation.
(In this use case, I'm deliberately avoiding Text Parse Noodle Soup Prompts since I want everything contained in the workflow written to images without extra files.)