Zugg Software :: View topic

Beginner Joined: 20 Mar 2007 Posts: 27

I see that XML is the oly option to export scripts out in. Is there anyway to get them to txt files? I looked at a few XML converters, and they either just clean up the file making it pretty or they are way over my head honestly. I just need a simple txt export like old Zmud. Any thoughts?

Posted: Mon Dec 31, 2007 5:08 pm

The short answer is another question: why? There's no way to export to text because some of the options in CMUD (like language options) don't convert to text. The text export in zMUD was also notoriously buggy, whereas the XML export in CMUD is pretty reliable. There's no easy way to export CMUD settings to text, but why would you want to?

Posted: Mon Dec 31, 2007 6:22 pm

The answer to that, Fang, is simple.

Not everyone understands nor can read xml format. For instance, it's easier for me to look at a code in text format than to try reading it from xml format. I understand/can read xml format, but truthfully, it hurts my eyes. :P But I also know of the functionality that xml serves for CMUD, and I can appreciate that. Nowadays, what I do (I don't mess with the language options much yet) is if I want to write a script, I'll write it in zMUD, export it, modify it for CMUD, then install it that way. Makes some things easier.

Charneus

GURU Joined: 10 Oct 2000 Posts: 1116 Location: USA

I wouldn't mind seeing an export to text as well. The way I figure it, any part of a script should be able to be added from the command line. If that's true, then that means the ability to go from regular text to cMUD xml is there. I would then think it could be taken a little further to go from cMUD xml to regular text. But, if it isn't there now, I'm not sure how hard it would be to put it in, or if Zugg would even have the time to do it. One can only hope.

Posted: Tue Jan 01, 2008 10:44 pm

Beginner Joined: 20 Mar 2007 Posts: 27

Agreed to the above. When i want to look over several things, text is still eaiser. Or I want to post a script or something to my MID fourm, people can read text layout better then XML. It would just be a nice oprion to have.

Posted: Mon Jan 07, 2008 10:46 pm

Sorry, but not going to happen. As Fang has tried to explain, a plain Text format export would lose important values in CMUD that cannot be defined by the simple command line text format. There are lots of new options added to CMUD that cannot be represented by the plain text command line. Fang mentions many of them, but most new features added to CMUD that are not part of zMUD have this problem.

I spent a *lot* of effort in v2.x making the XML more human-readable, and that's about as much help as I can provide.

Posted: Mon Jan 07, 2008 11:04 pm

One thing that really helps me is opening XML files (or copying and pasting XML from the forums) into SciTE with the language set to XML. Its tag highlighting really helps to differentiate the script from the XML.

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

Could the default language be set to XML within the CMUD editor when you're viewing the XML tab?
It's based on Scintilla afterall, so surely fairly easy?

Posted: Tue Jan 08, 2008 12:01 am

Actually, it already is. CMUD sets Scintilla to XML when in the XML tab, which allows it to do the syntax highlighting and tag folding just like you'd expect.

Posted: Tue Jan 08, 2008 4:32 am

One thing I've noticed about exporting to xml is that it doesn't seem to like record values very much. I'll export it to XML, but instead of

Posted: Tue Jan 08, 2008 5:45 pm

If you are getting an export in the second format, that means you have an old database record variable from an older version of CMUD that hasn't been converted to the newer hash table format. Notice that it says 'type="String"' instead of 'type="Record"'.

Posted: Tue Jan 08, 2008 6:48 pm

The first doesn't actually say type="Record", it says string="Record". I wonder if that's a typo on Charneus' part.

Posted: Tue Jan 08, 2008 7:27 pm

I assumed it was a typo since I don't see any way for CMUD to show 'string="Record"'. But hopefully he'll reply and let us know for sure.

Posted: Wed Jan 09, 2008 4:34 am

Yeah, that was a typo on my part. I thought I had copied/pasted it, but I remember typing the first one. My fault. However, I remember that the above was created in 2.18, not any earlier versions. To test this out, I created a new database and exported the information. This is what I came out with after exporting it:

Posted: Wed Jan 09, 2008 8:42 pm

Can you give me the exact steps that you used to create this? The record that you show doesn't look like a proper database variable format since it doesn't have any "key=value" format. This might be specific to the database module which doesn't use the new hash-table record variable structure. But if you can give me the exact step-by-step procedure for creating a new database and getting this error then maybe I'll be able to fix it.

Posted: Wed Jan 09, 2008 10:17 pm

Actually, I found out the error myself. I was using a text file that I thought I had converted to XML to upload the settings, but I was using the older version. My apologies.

However, I did notice that unless the variable is changed to Type: Database manually, it'll output