Reply to thread

Message

<blockquote data-quote="Klintus Fang" data-source="post: 419249" data-attributes="member: 3580">Now I am misunderstanding.&nbsp; If the program in question requires a user interface in order to do anything, then why is it listening to the TCP/IP port?&nbsp; Are you suggesting that if program X want to create an NPC wizard that the user has to open up the &quot;npc creation program&quot;&nbsp; manually instruct the program to create the wizard, and then manually instruct the program to send the data across to program X?&nbsp; If that's the usage model you are envisioning then I don't see it being useful at all.Well, what I meant to say was that I played with the gui and decided the final product would only be marginally useful because it required everything to be manually configured and wasn't compiled as a library.that is not true.&nbsp; all you have to do is compile it as a library and then provide an external api that looks like this:bool createTown(town_configuration_data_t&amp; input, completed_town_t&amp; output);then somewhere above that define the structure town_configuration_data_t so that all the options that the user currently has to manually enter through the gui are variables in this structure.&nbsp; then define the structure completed_town_t so that all the information about the completed town are variables in that structure.Then you compile your town generator as a dll and distribute it with a header file that defines the things above.&nbsp; Then I install that dll on my machine and I write a program that wants to create a town.&nbsp; I instantiate a town_configuration_data_t structure.&nbsp; I fill in the fields that instruct the town generator what sort of town I want.&nbsp; I instantiate an empty completed_town_t structure.&nbsp; Then I call createTown.&nbsp; The town generator looks at the configuration data, builds a town based upon what the configuration struct says, puts the results in the completed_town_t structure and returns true to let the calling program know that it was successful.</blockquote>

[QUOTE="Klintus Fang, post: 419249, member: 3580"] Now I am misunderstanding. If the program in question requires a user interface in order to do anything, then why is it listening to the TCP/IP port? Are you suggesting that if program X want to create an NPC wizard that the user has to open up the "npc creation program" manually instruct the program to create the wizard, and then manually instruct the program to send the data across to program X? If that's the usage model you are envisioning then I don't see it being useful at all. Well, what I meant to say was that I played with the gui and decided the final product would only be marginally useful because it required everything to be manually configured and wasn't compiled as a library. that is not true. all you have to do is compile it as a library and then provide an external api that looks like this: bool createTown(town_configuration_data_t& input, completed_town_t& output); then somewhere above that define the structure town_configuration_data_t so that all the options that the user currently has to manually enter through the gui are variables in this structure. then define the structure completed_town_t so that all the information about the completed town are variables in that structure. Then you compile your town generator as a dll and distribute it with a header file that defines the things above. Then I install that dll on my machine and I write a program that wants to create a town. I instantiate a town_configuration_data_t structure. I fill in the fields that instruct the town generator what sort of town I want. I instantiate an empty completed_town_t structure. Then I call createTown. The town generator looks at the configuration data, builds a town based upon what the configuration struct says, puts the results in the completed_town_t structure and returns true to let the calling program know that it was successful. [/QUOTE]

Verification