v50 Steam/Premium information for editors
- v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
- Use this page to report any issues related to the migration.
This notice may be cached—the current version can be found here.
Editing User talk:Jifodus/Dwarf Fortress Utility Framework
Jump to navigation
Jump to search
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 311: | Line 311: | ||
:::[[User:Jifodus|Jifodus]] 15:37, 13 December 2007 (EST) | :::[[User:Jifodus|Jifodus]] 15:37, 13 December 2007 (EST) | ||
::::I'm just commenting based on the presumed desired outcome. No need to get there in one large leap. Small steps are fine. Not implementing that is ok too. It's nice to give more convenience to the end users, but it is not necessary, esp at a cost too great to be economic for the implementors :) Btw, I hope that your parser does have convenient ways to ignore parts that it doesn't recognize or use? If we are working towards a common persistent format, chances are, there may be data that are only used by one party and not by the other. Ideal case is that the unused data gets ignored safely (or just generate warnings without killing the whole process). I'll be occupied this weekend, but if I have time next week, I'll see if I can come up with a xml alternative to what you have. (xml easier for me if I'm using existing library, like tiny. otherwise, I'll have to define the lua grammar manually for the parser, which could take quite a few rounds of grammar debugging. Once the formats stabilizes, the next step could be a converter tool to freely transform one file format to the other. :) ) [[User:Sphr|Sphr]] 07:57, 15 December 2007 (EST) | ::::I'm just commenting based on the presumed desired outcome. No need to get there in one large leap. Small steps are fine. Not implementing that is ok too. It's nice to give more convenience to the end users, but it is not necessary, esp at a cost too great to be economic for the implementors :) Btw, I hope that your parser does have convenient ways to ignore parts that it doesn't recognize or use? If we are working towards a common persistent format, chances are, there may be data that are only used by one party and not by the other. Ideal case is that the unused data gets ignored safely (or just generate warnings without killing the whole process). I'll be occupied this weekend, but if I have time next week, I'll see if I can come up with a xml alternative to what you have. (xml easier for me if I'm using existing library, like tiny. otherwise, I'll have to define the lua grammar manually for the parser, which could take quite a few rounds of grammar debugging. Once the formats stabilizes, the next step could be a converter tool to freely transform one file format to the other. :) ) [[User:Sphr|Sphr]] 07:57, 15 December 2007 (EST) | ||
− | |||
− | |||
− | |||
− | |||
− |