So I've started and gotten a fair bit of work done on data wizards. The question now becomes: How to distribute them?
The nature of them makes them very small and also quite easy to change, so I'm thinking of putting in Assets, and as a Tool, but I also would prefer someway for people to easily contribute their own wizards.
We could either make a general forum thread or a data assets thread to fill with them. Personally I'm waiting on blizzard to reply to my posts about C"Catalog"Link not working when it should be in wizards. Also I need to find more time for them.
I would prefer a git repository. I tried setting up one here, but failed. Since its just xml (textfiles) it should be the smoothest. Then mappers can point their wizard folders to this repository folder directly or maintain their own clone. When bigger updates happen you sync it, or publish it. It's also a great opportunity to introduce students to proper versioning which we saw was an issue in patch 3.0.
The smoothest tools for this is GitHub with the easy to use GitHub client. It provides versioning, bug tracking, milestones, task management, wiki and other things. Using that systematically might be frowned upon by Curse.
Curse would be fine with such a thing, because they also maintain git/mercurial/svn repos themselves. ANd they provide a similar setup to Github with their repos (Tickets, tracking, task management).
And I agree, for the developers of such wizards, Git is HIGHLY preferable. The issue I have is getting it to end users, people who know little or nothing about data and want something simple and fast. I guess we can point them to the git repo and tell them to just DL files
@ArcaneDurandel: Go
From UX point of view I think using URL as a wizard-source would be most elegant. That might cause security problems though, as transparency and client dependencies becomes complex.
IMHO, Git is better. It has educational value as well.
They may include this later. I'm hoping they add support for data tokens.
For now though, we can still still use wizards quite effectively, it is just one will have to step outside a wizard to do data links to existing data objects.
So I've started and gotten a fair bit of work done on data wizards. The question now becomes: How to distribute them?
The nature of them makes them very small and also quite easy to change, so I'm thinking of putting in Assets, and as a Tool, but I also would prefer someway for people to easily contribute their own wizards.
Thoughts?
Tutorials are great too!!
We could either make a general forum thread or a data assets thread to fill with them. Personally I'm waiting on blizzard to reply to my posts about C"Catalog"Link not working when it should be in wizards. Also I need to find more time for them.
Still alive and kicking, just busy.
My guide to the trigger editor (still a work in progress)
GitHub.
I would prefer a git repository. I tried setting up one here, but failed. Since its just xml (textfiles) it should be the smoothest. Then mappers can point their wizard folders to this repository folder directly or maintain their own clone. When bigger updates happen you sync it, or publish it. It's also a great opportunity to introduce students to proper versioning which we saw was an issue in patch 3.0.
The smoothest tools for this is GitHub with the easy to use GitHub client. It provides versioning, bug tracking, milestones, task management, wiki and other things. Using that systematically might be frowned upon by Curse.
What tools does Curse provide?
@Monkalizer: Go
Curse would be fine with such a thing, because they also maintain git/mercurial/svn repos themselves. ANd they provide a similar setup to Github with their repos (Tickets, tracking, task management).
And I agree, for the developers of such wizards, Git is HIGHLY preferable. The issue I have is getting it to end users, people who know little or nothing about data and want something simple and fast. I guess we can point them to the git repo and tell them to just DL files
@ArcaneDurandel: Go From UX point of view I think using URL as a wizard-source would be most elegant. That might cause security problems though, as transparency and client dependencies becomes complex.
IMHO, Git is better. It has educational value as well.
Agreed and thus I have setup one and added my current WIP wizards to it
[email protected]:ArcanePariah/Starcraft-2-Data-Wizards.git
Go nuts people. Hand out the url to whoever asks and is interested in making them. I'll add the official blizzard docs to it as well.
@willuwontu: Go
They may include this later. I'm hoping they add support for data tokens.
For now though, we can still still use wizards quite effectively, it is just one will have to step outside a wizard to do data links to existing data objects.
Truth. The number of times the Antioch SVN server has saved our asses is pretty hard to overstate.
Yes, agreed. Git has also made my life easy, I dodged the mod delete bug of 3.0 because of it (simple revert).