28 réponses à ce sujet

[meaglyn]

@KMdS! Yes, I did the experiments once I got on a system where I could save an object. And updated one of my earlier posts with to that effect. I had just not ever seen it said before so needed to see it for myself

 

nwn-lib, which is actively supported, does the conversion of GFF to editable text too. The yml support is better than the xml and is used more. YAML is also not as painful to look at as XML

 

nwn-tools XML support has some bugs. It fails to handle some of the files like module.jrl.

[Baaleos]

Note - I only mention this because I did experiments on it before.

nwnx_odbc StorePersistentObject does persist the gff object, albeit in the blob data field.

One way to export directly to its GFF file type is to Save the object to database, but grab an ID for where it is going (eg: its row/record number)

Then execute : 

 

select VAL into outfile "C:/mySword.uti" FIELDS TERMINATED BY '' ENCLOSED BY '' ESCAPED BY '' LINES TERMINATED BY '' STARTING BY '' from pwobjdata where id = 1; 

 

I tested this a few years ago, I was then able to take the uti file and use it successfully in toolset by dropping into the temp0 folder.

 

The inverse also works - taking a GFF object and putting it into the database, for spawning in nwn.

update pwobjdata set val = LOAD_FILE('C:/mySword.uti') where id = 1;

[virusman]

Yup, SCO/RCO serializes to and from GFF. You can convert that to JSON with nwn-lib and use any tool that works with JSON to make a fancy GUI around it. Then just convert JSON back to GFF to use with RCO or resman.

[KMdS!]

select VAL into outfile "C:/mySword.uti" FIELDS TERMINATED BY '' ENCLOSED BY '' ESCAPED BY '' LINES TERMINATED BY '' STARTING BY '' from pwobjdata where id = 1; 

 

 

 

 

 

update pwobjdata set val = LOAD_FILE('C:/mySword.uti') where id = 1;

 

Thanks, never got around to writing the SQL statements myself. Should come in handy when I get around to tinkering.