Furthermore, the case used in the program matches the current Starter Pack/old LNP exactly, so it is only an issue to people who create a new pack without using an exisiting pack as a template.
Actually, the starter packs I checked (i.e. http://dffd.wimbli.com/file.php?id=7622 and http://dffd.wimbli.com/file.php?id=8936) both use lowercase for their LNP subfolders (like graphics and utilities), the program uses uppercase, that's why I came up with that issue to begin with.
I just checked both of them, and you're right. (The Starter Pack USED to have the first letter in upper case...)
I'll think about what seems like the best choice. I don't really like forcing case-insensitivity on case-sensitive file systems, so maybe I'll just end up allowing all-lowercase as well - we'll see.
That sounds very nice. If you think you can integrate it yourself, feel free to submit a patch (or pull request); leave the download part out, though (that would probably be relevant once auto-updating gets added, but for now it's just *checking*).
The version check is currently only for the pack as a whole, because there's no automated download anyway. (D)DOSing risk is minimal, and there's no requirement to use DFFD at all in the code, so I'm not too worried about that.
Will do that once I'm done, time to create a bitbucket account or are there plans to move to github? ![Smiley :)](http://97.107.128.126/smf/Smileys/aaron/smiley.gif)
I prefer Bitbucket to Github, so no plans to move.
![Smiley :)](http://97.107.128.126/smf/Smileys/aaron/smiley.gif)
Right now I'm working with a JSON file that is read and saved with all the details, i.e. packages(i.e. graphics, utilities etc.) installed, where to find them online (dffd id) and installed version. I plan to extend this to allow for checks of manually installed packages and a way to incorporate them into the version check/upgrade routine.
Currently I only plan to work with dffd as this is probably the most used way and also the easiest way to check for new versions. Not sure if it is worth it to go on with a universal version checker and I have no idea how to approach this...
The only thing you need to make it universal is a complete download URL instead of just a DFFD ID. DFFD is certainly used a lot, so it would be great to support it, but it's not perfect, so pack distributors should be able to use other sources.
Btw the goal is to have it running under Win/Linux/OSX and with python 2 and 3, right?
Currently it doesn't work on my machine with python2 due to some errors with the imagetk library. I will try to write my code python2 compatible anyways, but can't test it under Win or OSX.
That is the goal, yes - many systems still have Python 2 as the default, so I do most of my testing, etc. on that, but try to keep the code Python 3-compatible as well.
It is possible that there are some bugs I didn't catch when running on Python 3, so if you find anything, please submit a bug report.
Regarding your ImageTk issues, throw me a PM or something if you want me to take a look.
Any suggestions where to get started with the UI development/modification? Never did stuff like that before ![Smiley :)](http://97.107.128.126/smf/Smileys/aaron/smiley.gif)
This is my first Python GUI program, so I'm pretty much learning as I go, too
![Smiley :)](http://97.107.128.126/smf/Smileys/aaron/smiley.gif)
The best advice I can give is to just read code and try to see how that leads to whatever layout it puts on screen. When you're trying to add something yourself, make a sketch or mental picture of the UI you want, then add the necessary controls in code and fiddle with the layout until it gets to what you want.