Reply to thread

Message

<blockquote data-quote="n4orcer" data-source="post: 664106" data-attributes="member: 74094">Sure, i can upload an early version of it later today so you at least can try the parsing of XML files.Hmmm, perhaps it was agreed. But I not see why the application would not work or why your own editor would not work if you just support the purposed XML file.Basically to my understanding is that if I have the purposed XML file generated from your editor it should automatically work with the general one I am creating and any other editor that supports the XML file itself, that was my thought at least.So the way I understood it is that my application have nothing to do with your editor and there should not be anything you need to do on your side to make it work as long as you support the purposed XML file it would be up to my editor to support generating basichome.xml trough some kind of &quot;layout.xml&quot; or whatever for your skin if that is a function that is going to be implemented. I was just trying to make a unified tool for creating the structure of the purposed XML file. It's just a different way to generate and edit the file, the only difference is that I would want my general application to be able to generate a basichome.xml file for those skins that do not support the purposed XML file or at the very least be able to do most of the work so there is just basic editing left to do for the end user.The tool itself should ignore or disregard anything that are skin specific and it really dont even need a skin to work. All it needs is a &quot;WindowIDs.xml&quot; that contain ID and Filename of the available plugins and then it can create one of the purposed XML files or you can load one previously saved one and modify it.Perhaps I have misunderstood something? I do not want to step on anyones toes or anything like that, i just want to help out and make things easier.<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="n4orcer, post: 664106, member: 74094"] Sure, i can upload an early version of it later today so you at least can try the parsing of XML files. Hmmm, perhaps it was agreed. But I not see why the application would not work or why your own editor would not work if you just support the purposed XML file. Basically to my understanding is that if I have the purposed XML file generated from your editor it should automatically work with the general one I am creating and any other editor that supports the XML file itself, that was my thought at least. So the way I understood it is that my application have nothing to do with your editor and there should not be anything you need to do on your side to make it work as long as you support the purposed XML file it would be up to my editor to support generating basichome.xml trough some kind of "layout.xml" or whatever for your skin if that is a function that is going to be implemented. I was just trying to make a unified tool for creating the structure of the purposed XML file. It's just a different way to generate and edit the file, the only difference is that I would want my general application to be able to generate a basichome.xml file for those skins that do not support the purposed XML file or at the very least be able to do most of the work so there is just basic editing left to do for the end user. The tool itself should ignore or disregard anything that are skin specific and it really dont even need a skin to work. All it needs is a "WindowIDs.xml" that contain ID and Filename of the available plugins and then it can create one of the purposed XML files or you can load one previously saved one and modify it. Perhaps I have misunderstood something? I do not want to step on anyones toes or anything like that, i just want to help out and make things easier.:) [/QUOTE]

Verification