Closed mgrandi closed 10 years ago
You need to define the format data model first, see https://github.com/niftools/pyffi/tree/master/pyffi/formats. Additional information has to added for to the data model for QSkope. It should still work but not actively maintained as it was it was superseded by NifSkope.
The format description for the .dds format although descriptively complete still has some functional implementation to fully support. https://github.com/niftools/pyffi/issues/3
I haven't used QSkope myself but will check it out later to see what is supported. Reading through the nif
format I could not really see anything for visualisations, so it seems to only describe the model data view, much like NifSkope's list/tree view. I suspect it is much more of a data editor than object viewer.
I just installed the latest official build as I am not on my dev machined. The offiical installer seem to have stripped out any QSkope supported and dependencies.
I installed pyffi from pip and it still has qskope, it puts a python file in the bin directory of the python folder
Also, is nifskope supposed to be a replacement, or does it only work with one file format? I have a object model defined, its just annoying that opening the file shows nothing in qskope and I can't figure out why, as I appear to be implementing the right methods like the tga object model does
-----Original Message----- From: "neomonkeus" notifications@github.com Sent: 6/12/2014 10:40 AM To: "niftools/pyffi" pyffi@noreply.github.com Cc: "Mark Grandi" markgrandi@gmail.com Subject: Re: [pyffi] Format support in qskope - .tiff & .dds (#10)
I just installed the latest official build as I am not on my dev machined. The offiical installer seem to have stripped out any QSkope supported and dependencies. — Reply to this email directly or view it on GitHub.
Well NifSkope is a replacement in so far as a visual data editor, but only supports .nif format.
If you installed via pip you should have gotten pyffi-2.2.2
. I will check it out if I ever get home.
The other thing would be to make your code available either by forking the repo, gist pastebin etc.
Yeah, it is pyffi-2.2.2, i don't see anything related to NifSkope but i do see the nif object model files and whatnot.
I think its just a general lack of documentation, I still have a lot of questions about the library, various things about implementing data models and the specifics of getting them to show up in QSkope (i actually sorta figured it out, but there are still questions), and i'm not sure if you guys are interested in maintaining this library past supporting NIF since that appears to be your whole github organization thing
What is the difference between QSkope and Nifskope? is it just a rewrite to make it better or something?
Although nif related formats are the main goal of the organisation, with pyffi being integrated as part of our tool pipeline; @amorilia the original author is no longer actively coding, so we are its adoptive home.
Any contributions are greatly welcome, in any form, documentation, code improvements, etc. If you want to drop into our IRC channel as the issue is slightly tangenting.
ok! back to the original issue, is NifSkope basically aimed to be a replacement for QSkope? As in should i not bother working on QSkope and just work on NifSkope? I obviously don't want to spend time on something that is planning on being phased out!
No, but QSkope has not been actively maintained due to the latters development. I dont see any reason to phase it out if is useful to people.
@mgrandi - Any update on this issue or should I close it
Hey, I'm probably going to do some work on qskope to better support custom formats as well as a few other quality of life stuff, so I think its probably fine to close these, i'll make separate issues with pull requests when they are done.
(I am assuming this is the only active fork of pyffi as someone else mentioned it)
anyway, adding new formats to qskope is currently not really supported, or I can't figure it out. Even if i manually add a new pyffi format to
openFile()
in__init__.py
, it still doesn't correctly show the 'structure' of the file, as i'm not sure how you define that (like you see if you load a tiff file, or dds file in qskope)