I would, but you have to understand that I'm not a magician!!! I can't make several weeks worth of coding in a day!
I'm just making suggestions.
Quote:
The first can already be done, though if you mean you want to read out the XML files into an interface, then yeah that's the only thing we can't do with it yet, and I will try to look into making that possible (but vB3's functions can't be used for that, so I'd have to write my own xml parsers entirely for that, that === more time once again).
XML files can be parsed and printed using opensource XML PARSERS. There are a few out on the market that do a great job. You will not need to do anything .. just add a place (upload file input) to the htl interface to upload/parse the xml file.
The output can be modified to fit your needs. This can be added within a day.:up:
Quote:
Would that be sufficient? If not, what more do you want? :\
that's good but I would rather have no data inserted into the database ... for example, if there needs to be a vbulletin upgrade .. I can go into the htl and check for hacks installed. The htl will get the information from the original .htl file NOT from the database ... storing the information into the database is not needed.
Quote:
The new feature `Make .txt Installer` alone will already take care of those 5, so I guess I'll be releasing that version soon. Would that please you?
the txt installer would please me ... but you have to think of the BIG picture. If you enable a "standalone installer" feature you will have a great piece of software that everyone can use in one form or another.
PS. I would also recommend an easier way for hackers to create a "temporary phrase file".