Thanks for pointing out the depth thing. That explains it.
The object looks good to me, suggest you release it. I will replace my use of the prior XML object with this one.
Thanks for pointing out the depth thing. That explains it.
The object looks good to me, suggest you release it. I will replace my use of the prior XML object with this one.
I really like the idea of XML for storing data and its about time we moved away from INI.
What I was want is an easy way to read and write data to xml format. To get people using it over INI it needs to be as simple as INI (because people seem to have enough trouble with that!)
I liked the examples, especially the bbc news reading one, but when I came to try and create an XML file from within the extension I just dont seem to get anywhere. Could you make an example that creates a new file with a structure like your example:
<People>
<Person Age="50">Bob</Person>
<Person Age="20">Ashley</Person>
</People>
As all I have managed to do is write a comment into the file. I am just basically randomly trying actions which sound like they might add content then seeing what the output file looks like and getting nowhere fast.
Maybe the menus could be split into read tasks, write tasks, tree navigation and file I/O.
As far as release goes, that is always up to the developer, though I prefer, for several reasons to have them debut in Platinum Bonus Packs.
One reason is, (as someone related on the forums recently) accessibility and organization. We can't eliminate that problem for users, but the BP's have always been an attempt to coalesce and concentrate useful extensions.
I was hoping that even our early work here would get us a decent PHP by the Holidays ... maybe around Halloween.
On the other hands, I can understand and appreciate a Developer's desire to get an extension finished and released to the public for that "sense of accomplishment".
I am thinking that we need a new system. I was thinking of your public beta idea and I might have something new to add to it.
My idea is as follows:
We have a special site devoted to extensions. This site could be a subset of the clickteam site. On this site we have a special "beta" system that would require users to register and we would need to confirm that they are using a legit copy of MMF. The system would then work as follows:
An extension would be introduced into the system as an alpha (Kind of like a download on TDC). The extension would then have it's own bug list, comments section, and download link. Once the author feels comfortable with the extension (as in all of the bugs are worked out and it has moved out of beta) the author could then move his work out of beta and into a full release. The extension would then be on an "extension list" just like the clickteam extension list <img src="/center/images/graemlins/smile.gif" alt="" />. This system would automate the task of managing builds, posting new builds, managing the public "testers", and it would provide sections for bugs, examples, online documentation, ect.
The authors would have the ability to invite users to the "testing" or make it a public beta. This way the author can control who gets to see the beta and who doesn't. Some of the options could be inviting developers only to test the extension, or perhaps individuals. By registering their source with Clickteam, authors could get "Certified" next to their extension on the list and perhaps a logo if they want one, that would assure people that their extension is approved for safety by Clickteam <img src="/center/images/graemlins/smile.gif" alt="" />.
The extension list could also have a developers section with links to the tools required, perhaps the extension wiki, and other useful information and programs.
We would all have accounts on there, but new developers would have to register for the EDT or with Clickteam or something.
This system would basically provide a very organized system designed specifically for the tasks associated with the development, testing, and release of MMF 2 extensions.
A special program would be made that would allow the users to download the extensions. This program would basically make sure that the users copy of MMF 2 is legit and it could automatically serach for new extensions. The program and the site would work together hand and hand.
This system would eliminate the need for bonus packs all together and instead would just protect the extensions from pirates. This system would require little mantinance after intital setup and it would free Yves from having to make bonus packs constantly. Also the program could automatically update the extensions.
What does everyone think of this idea?
Its a great idea Vortex.
Where do we get such a system?
In the short time I was thinking of having Yves add a help menu choice that would open a browser window -- This browser window would open up a web page something like the old extension list. Just a list of downloads for TGF2/MMF2 -- Not something quite as snazzy as what you describe.
A holiday release is fine for some of my other extensions, but I want to get this one released fairly quickly. Any chance of a smaller bonus pack coming out in like a week or so?
I might get several of my extensions ready and then have you release a PBP of just my extensions if no other developers have anything by then <img src="/center/images/graemlins/wink.gif" alt="" />.
Posting Permissions
Reply With Quote