Print

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

[Pidgeot]

PyLNP 0.5.2 is out, fixing the Entomb Pets option.

[Beautato]

I am really loving the upgrades you have been making. Thank you for your really great work! I am planning on switching the Linux lnp to PyLNP in a future update.

[Pidgeot]

Thanks, Beautato!

And speaking of upgrades... PyLNP 0.6 is out! This has been bubbling for a while now, and I think it's about ready to get it out there.

The main change in this version is a fairly large restructuring of code, which opens up new possibilities and hopefully makes it a little easier to extend.

Part of that includes the ability to handle different DF versions differently, e.g. by hiding options that don't exist - for now, at least 40d and up should work; earlier versions may also work, but they are not explicitly handled yet. Additionally, there's also some infrastructure in place to handle variations to the install, such as DFHack and TWBT, as well as the legacy Windows builds, allowing the UI to adapt accordingly.

This system will ilkely be refined a bit further in the future, and most likely I'll even add proper support for even older versions of DF (someone out there is probably still playing 23a).

Additionally, there are various other refinements: DFHack can be disabled from the UI; the launcher is more flexible in its placement relative to Dwarf Fortress, and you can now see which color schemes, embark profiles, etc. are currently installed through a red highlight.

Of course, any questions are welcome, as well as bug reports and feature requests.

I am just going to leave this picture here

[Beautato]

I am having some trouble configuring the utilities folders on linux. It auto-detects the .sh / jar files of all the lib jars. Is there a way right now that I can narrow down the listed items that show up in utilities?

screenshot of how it looks without editing code:
 

[Pidgeot]

I am having some trouble configuring the utilities folders on linux. It auto-detects the .sh / jar files of all the lib jars. Is there a way right now that I can narrow down the listed items that show up in utilities?

In the LNP/Utilites folder, create a new text file named "exclude.txt". Any filename listed in brackets here will be excluded from the list. Example from an old LNP version (I believe it contains everything you need, actually):

Code: [Select]

File Exlcusion List
Any file name inside square brackets will not show up in LNP's utilities list.

SoundSense Exclusions
[soundSense.jar]
[jl1.0.jar]
[mp3spi1.9.4.jar]
[jogg-0.0.7.jar]
[jorbis-0.0.15.jar]
[vorbisspi1.0.3.jar]
[tritonus_share.jar]
[autoUpdater.jar]
[commons-codec-1.4.jar]
[jansi-1.8.jar]
PyLNP also allows you to add files not otherwise detected automatically using a file named include.txt - it follows the same format. This is particularly useful on Linux and OS X, since executable files don't necessarily have a specific extension.

[Beautato]

PERFECT! thanks I should have realized that. Great work by the way! I am loving the way this LNP interface is so well maintained

[Beautato]

Another question :

Specifically about the lists, is there an override to change the display name of the executable in the utilities list?

[Pidgeot]

Another question :

Specifically about the lists, is there an override to change the display name of the executable in the utilities list?

There are two options in PyLNP.json, hideUtilityPath and hideUtillityExt, which can hide the path and extension, respectively, of the utilities - there's no override beyond that, but hiding both should get you some meaningful names anyway.

Example:
With both options disabled: Dwarf Therapist 21.8\DwarfTherapist.exe
With hidden path: DwarfTherapist.exe
With hidden extension: Dwarf Therapist 21.8\DwarfTherapist
With both options enabled: DwarfTherapist

[Beautato]

I am going to be switching the my linux pack to only be using PyLNP for future versions, sent you an invite to the organization i am hosting the package from.

Thanks for quick answers. Its really a minor thing right now as there are other more important features but it would be great to allow an editable override for the various lists possibly in a future version.

[Pidgeot]

Its really a minor thing right now as there are other more important features but it would be great to allow an editable override for the various lists possibly in a future version.

Please add it to the issue tracker as a request, preferably with an idea about how you imagine those overrides should be specified. It's easier to keep track of that way.

[Dirst]

Its really a minor thing right now as there are other more important features but it would be great to allow an editable override for the various lists possibly in a future version.

Please add it to the issue tracker as a request, preferably with an idea about how you imagine those overrides should be specified. It's easier to keep track of that way.

My guess would be something akin to the include.txt and exclude.txt files

Code: (relabel.txt) [Select]

[soundSense.jar:SoundSense]
[foo_1_03.jar:Foo Manipulator]
[bar-0.0.7.jar:Bar Filter]
[baz_experimental_01.jar:Baz]


[Pidgeot]

My guess would be something akin to the include.txt and exclude.txt files

Code: (relabel.txt) [Select]

[soundSense.jar:SoundSense]
[foo_1_03.jar:Foo Manipulator]
[bar-0.0.7.jar:Bar Filter]
[baz_experimental_01.jar:Baz]


Sure, but what about wildcard support to handle version numbers? Do we want any other information? Should we use a file next to the utility itself instead? Should we use PyLNP.json?

It's stuff like that which isn't a given, and it's easier to keep track of people's wishes by having it on the issue tracker

[PeridexisErrant]

https://bitbucket.org/Pidgeot/python-lnp/issue/33/allow-overriding-of-file-names-in-utility

Issue with proposed details.

[Pidgeot]

Tiny walk down memory lane:

Spoiler: "0.21.93.19a" (click to show/hide)

Spoiler: "0.22.123.23a" (click to show/hide)

Spoiler: "0.23.130.23a" (click to show/hide)

Spoiler: "0.27.169.32a" (click to show/hide)

Spoiler: "0.28.181.40d" (click to show/hide)

Spoiler: "0.31.01" (click to show/hide)

Spoiler: "0.34.11" (click to show/hide)

Spoiler: "0.40.13" (click to show/hide)

Yes, this means all DF versions are supported now.

This'll be live in 0.7, which will go up shortly after Toady releases the next DF version.

[kahrkunne]

I'm probably just really stupid, but how do I use this?
I have no idea what I'm doing, and the readme isn't really helping either.
Dowloaded the source code, but trying to run it just gives me this error

kahr[python-lnp]>./launch.py
WARNING: LNP folder is missing!
Traceback (most recent call last):
  File "./launch.py", line 11, in <module>
    lnp.PyLNP()
  File "./core/lnp.py", line 66, in __init__
    self.userconfig = JSONConfiguration('PyLNP.user')
  File "./core/json_config.py", line 21, in __init__
    self.data = json.load(open(filename), encoding='utf-8')
  File "/usr/lib/python3.4/json/__init__.py", line 268, in load
    parse_constant=parse_constant, object_pairs_hook=object_pairs_hook, **kw)
  File "/usr/lib/python3.4/json/__init__.py", line 318, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python3.4/json/decoder.py", line 343, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python3.4/json/decoder.py", line 361, in raw_decode
    raise ValueError(errmsg("Expecting value", s, err.value)) from None
ValueError: Expecting value: line 1 column 1 (char 0)