User talk:BryanDerksen

From Dragon Age Toolset Wiki
Jump to: navigation, search

Function article conventions

Moved to Template talk:dafunction

Collisions and Disambiguation

Your change to the Vector page and categorisation of Bool as a Data type started me thinking about how to best handle these.

Putting information for both Vector and vector on the same page would be very confusing especially if GeSHi is configured to create links for functions and data types (which is what I've set it up to do). Which ever way we do it half of the time a user will be taken to what initially appears to be the wrong page which will be frustrating for the user. Moreover since there are other such collisions: Effect vs effect; Event vs event; and Location vs location a simple and consistent solution is desirable.

Similarly while Bool itself doesn't present any problem, unless people try to use it in dascript, there will be collisions with the other 2da data types: int, float, string, etc. Again if someone is wanting information on 2da we don't want them having to wade through the dascript information first.

Consequently suggestion would be to leave the functions undecorated but add a suffix to the data types to differentiate them from the functions and from each other. I've seen this on wikipedia where you get Iron Maiden, Iron Maiden (album) and Iron Maiden (song). In this case I would suggest adding "(dascript type)" or "(data type)" and "(2da type)" as appropriate.

This suffix would be supported in the GeSHi config file so for the most part it would be invisible to the user. Only when they were searching specifically for a Vector or vector would they actually become aware of what was going on.

What do you think? --Sunjammer 18:44, 27 July 2009 (UTC)

I like it, and was thinking something similar. However, I wonder if perhaps the data type should get the unadorned title rather than the function, since they're going to be linked to far more frequently - they're linked to from the variable table templates and the 2da templates, for example, and I expect that in ordinary written prose a link "vector" is more likely to be aimed at the data type than the constructor function. Ultimately it's not that big a deal which way we pick since we have redirect capabilities in this wiki, and since most of the links will be generated via templates or scripts so they can be easily changed if we end up picking the suboptimal approach. BryanDerksen 19:06, 27 July 2009 (UTC)
I'd be inclined toward decorating the data type if for no other reason than I want to differentiate between the dascript data types and 2da data types. Since we have to decorate one regardless of the approach it makes sense to decorate both and leave functions alone. "One rule to ring them all and in the wiki find them" as Tolkien might have said. It also means I don't have to change the code that updates generates the dascript.php only the template (j/k)! --Sunjammer 19:22, 27 July 2009 (UTC)
Heh. Well, I'm not sure that we really need separate articles for 2da and script types - the only differences I can think of offhand are bool and comment lacking a scripting equivalent (which renders them a moot problem since scripts will never have a link to them in the first place) and the way a resource literal has an 'R' prefix in scripting but not in 2das. But again, since we've got access to redirects now I guess it's easier to start with them separate and merge them later if that turns out to be better.
In the final analysis there's only going to be a handful of conflicts, and there are tools out there for MediaWiki that are specifically designed to make disambiguation easy, so we can try out different solutions without worrying too much about getting locked into something suboptimal. Do what you need to do to get the raw data in, I can clean up afterward. :) BryanDerksen 19:31, 27 July 2009 (UTC)

Wacom tablets

A friendly poke to remind you that you were going to ask around for details on using Wacoms with terrain mesh editing. I also posted my settings to my talk page if you wish to take a look. Languard 17:56, 9 November 2009 (UTC)

Afraid I didn't get to it today. Now that the toolset's been released I'm getting unrelated tasks thrown at me. I'll try to catch a level designer tomorrow instead, sorry! BryanDerksen 01:21, 10 November 2009 (UTC)