Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[madk]

Generally "token" is used to refer to a lexeme with attached meta-data (location in the file, type, ect).

A lexeme is a string of characters which forms a syntactic unit.[2]

Some authors (for example, [1], [2]), just call this a token, using 'token' interchangeably to represent (a) the string being tokenized, and also (b) the token datastructure resulting from putting this string through the tokenization process.

http://en.wikipedia.org/wiki/Lexical_analysis#Lexeme

Personally I've never heard someone actually refer to them as lexemes.

[madk]

Holy shit, just look at all that documentation!

[madk]

Finally put out a first release! https://github.com/pineapplemachine/PyDwarf/releases

A list of scripts included with the current release:

Spoiler (click to show/hide)

pineapple.adoptsowner
pineapple.bauxitetoaluminum
pineapple.boneflux
pineapple.butcherinorganic
pineapple.castanvil
pineapple.cavegrass
pineapple.deerappear
pineapple.diff
pineapple.discipline
pineapple.flybears
pineapple.greensteel
pineapple.maxage
pineapple.metalitems
pineapple.noaquifers
pineapple.noexotic
pineapple.nograzers
pineapple.nomaxage
pineapple.orientation
pineapple.skillrust
pineapple.stoneclarity
pineapple.subplants
pineapple.useablemats
pineapple.utils.addreaction
pineapple.utils.addtoentity
pineapple.utils.objecttokens
pineapple.woodmechanisms
putnam.materialsplus
putnam.microreduce
shukaro.creationforge
shukaro.higherlearning
smeeprocket.transgender
stal.armoury
umiman.smallthings.engraving
umiman.smallthings.prefstring
witty.restrictednobles
witty.restrictednobles.custom

[madk]

Here's the second release, v1.0.1: Strange Mood. Mostly it adds a lot of documentation and fixes/improves stuff that was already there.

I'm still trying to gain traction for PyDwarf! I believe the best way to do this is to add more mods. If you have a mod you'd like to see rewritten for PyDwarf, please let me know and I'll work with you to get it done. PyDwarf is very good at this sort of thing! Mods that might previously have been limited to a small range of Dwarf Fortress versions, and might have been troublesome to merge with other mods, can now be written in such a way that compatibility becomes almost a non-issue.

Changelog:

Spoiler (click to show/hide)

Fixed pineapple.boneflux reaction by being less bad at string formatting
Fixed pineapple.utils.addreaction not adding an OBJECT:REACTION token to created files
Fixed new grasses in pineapple.cavegrass not being recognized by DF
Fixed a small issue with logging in pineapple.cavegrass
Fixed non-raws files from input directory not being written to output
Fixed pydwarf.response casting to string always returning a string starting with "SUCCESS" even when unsuccessful
Added a lot more documentation
Added a shitty WIP tool for outputting docstrings as more readable html
Added a list method to queryable raws objects which acts as a shortcut for raw.tokenlist(something.tokens())
Added a file attribute to raws.token objects for tracking which file they belong to, if any
Added a bunch of helpful operator overloads
Added length and clear methods to raws.file
Added some convenience things to the raws package: raws.parse and raws.parseone refer to the raws.token static methods, raws.filter refers to raws.tokenfilter
Added index and slice functionality to raws.token and raws.file, most easily accessible via conventional notations like token[1] or token[-8:0:2]
Added step argument to tokens method for raws.token and raws.file
Improved error handling for bad config settings
Improved raws.tokenlist casting to string
Improved objdict method to return a dictionary of raws.tokenlist objects where previously they were regular lists
Improved handling of assignment of illegal strings to token text, now automatically resolves some common pitfalls
Improved argument handling for raws.boolfilter static methods all, any, one, and none
Tweaked grass colors in pineapple.cavegrass
Tweaked names, craftable items, and material values in pineapple.greensteel

[notfood]

Maybe it would be good to start with the popular graphic packs. The more complex do some generic changes to the raws.

[madk]

Coming in the next release: A major revising of the way PyDwarf handles files will provide modders with the ability to add or modify DFHack scripts, to work together with stonesense, to tinker with DF init settings and with speechfiles, and to add images for use with graphics packs or even just new tilesets, and still loads more. All of this with the ease and flexibility of Python!

[madk]

Recent mod additions which take advantage of the aforementioned major revision include omniclasm's State of Decay, pkdawson's df-vegan, and two more of umiman's smallthings mods. Expect a new release quite soon!

[expwnent]

Posting to watch.

[madk]

PyDwarf 1.0.2: Magma Forge is released!

[madk]

I've been hard at work on PyDwarf and a new release is coming soon: Prepare yourself for improved documentation and a GemSet installation script! Many thanks go to dragondeplatino for working with me to get that script working.

[madk]

Haha, "soon".

This is going to be the last major release of PyDwarf so I'm spending a lot of time making the documentation as helpful as I can and hunting down any remaining bugs. How does it go, the last 10% of the code takes 90% of the development time? But this polish is important: I understand that PyDwarf can look like a confusing mess and that's why I'm working hard to make it as accessible and as easy to use as possible. For anyone with any programming experience who wants to get into modding I believe PyDwarf is their best option by far. Included with the next release will be several tutorials for various aspects of PyDwarf, thorough documentation on its more complicated parts, and summaries and example usages for as many functions and methods as I can cover.

Want to help PyDwarf to attain its final form? I can always use help discovering bugs, writing code examples, making sure everything actually makes sense to someone who isn't me.

[madk]

PyDwarf v1.1.0: Chalcedony has been released!

Here's a step-by-step tutorial to guide you through your first time configuring and running PyDwarf, and here's another tutorial to help you get started creating your first mod. Also, here's a handy list of scripts with which PyDwarf comes packaged. And here's where all those scripts are actually located, in case you'd like to see what their innards look like.

Here's just a few examples of the mods included with this release of PyDwarf:

• Omniclasm's State of Decay.
  
• DragonDePlatino's Gemset.
  
• Umiman's Small Things.
  
• Stalhansch's Armoury Packs.
  

Normally you'd be bound to run into compatibility issues when trying to install so many of these mods at once, and you'd surely have to wait for authors to update their mods before reinstalling everything whenever Dwarf Fortress updates. Not so with PyDwarf. PyDwarf is highly capable of avoiding conflicts between mods, and it cares little about which version of Dwarf Fortress you're modifying. Not only does PyDwarf make it much easier for the player to install mods, it also makes it easier for the modder to craft something excellent. Instead of editing text files on your own, PyDwarf allows you to write scripts which edit them for you: What this means for you is an enormous reduction in tedium.

[madk]

Just a PSA that PyDwarf is 100% functional for DF 42.x. It's possible that some mods written for it may be incompatible with raws changes made, and mods depending on other utilities won't work until those have been updated - but PyDwarf itself requires no update.

All of the mods packaged with PyDwarf should work with DF 42.x without any changes, though some depend on DFHack or TWBT also being up-to-date.

[cryzed]

I'm just stopping by to tell you how cool and impressive your project is. I'm a Python enthusiast myself and have seen your project a few times on the forums and always thought so. I think it's unfortunate that this thread seems relatively inactive, which makes your continued progress and enthusiasm with the project even more impressive. Thanks for contributing really cool tools to Dwarf Fortress (even though I am not actively using them myself)!

[Xinael]

This project is awesome. This is going to make my life so much easier.

One question though, or suggestion for the documentation. I'm a definitely Python newbie, I've dabbled enough to know the syntax but I've never developed anything serious with it. I understand how to call scripts through manager.py well enough, so I think the documentation is great there, btw

But a big gap for me is understanding the best workflow to use when I'm developing a script. I want to be checking that my script is loading the right entities, amending them in the right way, and leaving them the way I want them to be after it runs. I could call the script over and over with manager.py but that seems inefficient and slow and it requires me to have a dev version as well as my real version of pydwarf (to have a different config). It will make debugging a nightmare too.

So if you could suggest a workflow for script development, that would be awesome. I assume you have some good advice to give since you've developed all the scripts that come with pydwarf. I assume that running raws.dir() to load the directory and then running scripts and functions against that to check it's working as I expect would be the best method - but I'd really appreciate any advice, help and tips you can share about ways to set that up that you found helpful.

I'm in the situation now where I have a good idea what I want my script to do, but I don't have a good process for making it happen and checking that it's working, except writing something I think will work in Sublime and then running manager.py over and over. Any help would be greatly appreciated