Generator Public Interface Definition

Hannu

Mythras Guru
CL Add-on Dev
#1
I am creating a fleet / army generator

Should we agree syntax for call points. For example the generator could include "interfaces:" that would be similar to tags.

In the interfaces one could list those of the subtables that are meant to be exposed to external parties.

For example I have: generator file called Ship. It has within it a (large) number of ship types that could be called externally (and others I do not advertise).

interfaces: SuamChowBarge, HolyCountryTrireme

Then I could query the Json for any public interfaces and expose these as possible generation calls on the user interface...

and generate now one ofl them with:
Ships#HolyCountryTrireme

{
"name": "SuamChowBarge",
"entries": [
"...." ]
},
{
"name": "HolyCountryTrireme",
"entries": [
"...."
]
},
 

JochenL

CL Byte Sprite
Staff member
CL Add-on Dev
Wizard of Adventure
#2
Should we agree syntax for call points. For example the generator could include "interfaces:" that would be similar to tags.
Can you quickly check whether the new UI preserves this field or not?
 

ELF

Generator Sage
Staff member
CL Add-on Dev
#3
This is an excellent idea.

But I think it would be better to have the interface property as part of the table structure than as a manually maintained, separate list. It is not uncommon for me to edit the table names when working on a generator, and updating also the interfaces list every time would be too easy to forget, or typo.
 

ELF

Generator Sage
Staff member
CL Add-on Dev
#4
Maybe the user interface could scan the generator for these access points and automatically create a dropdown menu entry for each available table call? :unsure:

By default the generator would use the resultPattern, but the user could also interactively select another supported option.
 

Hannu

Mythras Guru
CL Add-on Dev
#5
Maybe the user interface could scan the generator for these access points and automatically create a dropdown menu entry for each available table call? :unsure:

By default the generator would use the resultPattern, but the user could also interactively select another supported option.
That is the reason I ask it for...
 

Hannu

Mythras Guru
CL Add-on Dev
#6
This is an excellent idea.

But I think it would be better to have the interface property as part of the table structure than as a manually maintained, separate list. It is not uncommon for me to edit the table names when working on a generator, and updating also the interfaces list every time would be too easy to forget, or typo.
Then you would need a marker to say which of these are published, which are public but not published and which are private...
 

Hannu

Mythras Guru
CL Add-on Dev
#7
We would probably need a reminder that when these are published they probably need to be human readable
 
Top