Reply to thread

Message

<blockquote data-quote="towngen" data-source="post: 422212" data-attributes="member: 1528">SM!RK, I think I agree with everything in your post except the part about the standard breaking down if they can decide what to export or not.&nbsp; Do I HAVE to export the individual churches that I create that are normally inside the town?&nbsp; The whole standard is for crap unless I can export individual barmaids?&nbsp; What about every possible weird permutation of the contents?&nbsp; I want a function to create towns, but this is a dry county so NO TAVERNS OR BARMAIDS!&nbsp; It just gets too crazy.&nbsp; I gotta be able to limit it somewhere.&nbsp; And the only reasonable way to do that is leave it up to the individual developer what to export or not to export.The only other caveat I would add is that (as a minumum) I'd like my program to appear as a minimized application, or maybe a little splash screen that can be turned off with a click to the &quot;don't show anymore&quot; option.&nbsp; Or something like that.&nbsp; But then perhaps I'm a bit more picky than most because I wish to sell my program.&nbsp; If it was something that I could just write in a couple days or hours I probably wouldn't even bring it up.&nbsp; But each application must have the right to implement it's own level of visibility.&nbsp; The market will decide and reward those who choose well.&nbsp; If &quot;Joe Bob's BarMaid Generator&quot; has horrible splash screens and constant nag buttons to register and plays the Marcarena while generating, people might be irritated with it and uninstall it.&nbsp; But again, let the individual program decide what to pop.&nbsp; The market will inform the pocket books of those who choose poorly.As for the question about what arguments a function call to create a town would take, well there are 2 ways I can think of off ahnd to define that.&nbsp; Either we (1) define &lt;waves hand like a Jedi&gt; &quot;All Town Generators will ....&quot; and we write it down and distribute it with the API, or we (2) create a method of the program telling the other program what it needs for arguments.&nbsp; Method 2 could take the form of an automatic query/response between the 2 programs (some extra program complexity required for this one, but it would be slicker), or it could be more simply implemented by publishing an actual human readable document that states what the parameters are.&nbsp; Or possibly some combination of the 2.</blockquote>

[QUOTE="towngen, post: 422212, member: 1528"] SM!RK, I think I agree with everything in your post except the part about the standard breaking down if they can decide what to export or not. Do I HAVE to export the individual churches that I create that are normally inside the town? The whole standard is for crap unless I can export individual barmaids? What about every possible weird permutation of the contents? I want a function to create towns, but this is a dry county so NO TAVERNS OR BARMAIDS! It just gets too crazy. I gotta be able to limit it somewhere. And the only reasonable way to do that is leave it up to the individual developer what to export or not to export. The only other caveat I would add is that (as a minumum) I'd like my program to appear as a minimized application, or maybe a little splash screen that can be turned off with a click to the "don't show anymore" option. Or something like that. But then perhaps I'm a bit more picky than most because I wish to sell my program. If it was something that I could just write in a couple days or hours I probably wouldn't even bring it up. But each application must have the right to implement it's own level of visibility. The market will decide and reward those who choose well. If "Joe Bob's BarMaid Generator" has horrible splash screens and constant nag buttons to register and plays the Marcarena while generating, people might be irritated with it and uninstall it. But again, let the individual program decide what to pop. The market will inform the pocket books of those who choose poorly. As for the question about what arguments a function call to create a town would take, well there are 2 ways I can think of off ahnd to define that. Either we (1) define <waves hand like a Jedi> "All Town Generators will ...." and we write it down and distribute it with the API, or we (2) create a method of the program telling the other program what it needs for arguments. Method 2 could take the form of an automatic query/response between the 2 programs (some extra program complexity required for this one, but it would be slicker), or it could be more simply implemented by publishing an actual human readable document that states what the parameters are. Or possibly some combination of the 2. [/QUOTE]

Verification