New Aquaria Wiki

[ryos]

As per DangerMouse's request, here's a new thread about the new wiki. The old thread for the old wiki was here. Access the new wiki here. And, uh, have fun?

[Xiagan]

Maybe you should change the name to "Aquaria Modding Wiki"? Or are there plans to include the normal wiki stuff too?
Sorry if this is already explained in another topic, since I'm not into modding I only read the releating topics from time to time...

[Danger Mouse]

Thanks Ryos.

[ryos]

I see little reason to limit the scope to modding, beyond avoiding stepping on the other wiki's toes. And if I were running the strategy wiki, I wouldn't mind an upstart with a broader scope competing for information...but that's me, and I'm willing to listen to reason. Do we know who started the strategy wiki? I'd love to hear what they think.

[delve]

(cur) (last)  22:03, 12 December 2007 Ixis (Talk | contribs) (New page: {{stub}} {{needinfobox}} {{needcat}} {{Header Nav|game={{subst:PAGENAME}}|num=0}} {{Infobox |title=Aquaria |image= |developer=Bit-Blot |publisher=Indie |released=12/07/07 |genre=Action Adv...)

(emphasis mine)

The first few main page edits are attributed to 'Ixis', a user that apparently doesn't exist at StrategyWiki (though may have at one point, I don't know enough about Wikis to say). However, there is certainly an Ixis here, though they appear not to have been active since Feb 08.

Personally, I've made a few edits on SW and contemplated several more. But I'm perfectly agnostic about it. If this community would rather dump all data into a single wiki I'm fine with that. I'm definitely not keen on replicating the data in a second location though, that would be obscene.

[Particlese]

Thank you very much for this, Ryos!  I love all the function documentation, and I'll definitely be adding descriptions if no one beats me to it.  They were very nice to have last weekend while I was mucking about with Lua for the first time.

As for the content, I'd be happy either way.

[Dolphin's Cry]

I see little reason to limit the scope to modding, beyond avoiding stepping on the other wiki's toes.

I see no problem in extending the new wiki beyond modding, but pragmatically thinking, I also see no reason to duplicate the information that is already available on StrategyWiki. It might even be a good idea to put a link to the Aquaria page on StrategyWiki on the main page, just so that visitors know it's there.

[delve]

I've already done that. They get picky about external links there, so I made an external link page in the appendices that includes a link to the new one.
Unless they've deleted that too. I haven't looked today. 

[Chibi]

I can understand why they would be cautious about links - somebody could post a link to an infected or fake site.

[delve]

I think they're more concerned about 'style'. Basically they want external links in their own page I think. I assume they have reasons.

[Particlese]

I like the new wiki, and I've added some info, but now I have some questions.  My edit caused the function to run beyond the edge of its allotted box on a 1280-wide screen in FireFox3, so I put in a carriage return and added some white space to make it more readable, since Lua doesn't seem to care about white space within function calls.  The function I did this to was setControlHint().

My questions after making the change are:
1.  For long functions like this, should we put in carriage returns, and if so, is there a characters-per-line limit we should go by, and should we put an ellipsis or something at the end of each broken line?  If Lua has a line-continuation character, that might be good to use so people can copy+paste+edit more directly.
2.  Is it okay to add white space like I did?  I know some languages are very picky, and I'm new to Lua, but spaces don't seem to mess up my function calls.
3.  If you refer to a function call in the text portion of a topic, should you write it like "myFunction", "myFunction()", or "myFunction(...)"?  In my case, I put the ellipsis there since calling it without parameters crashes Aquaria.  Not that it would have been very useful if it didn't crash, but still.
4.  Should optional parameters be indicated somehow in the function line?  For example:

Code: [Select]

setControlHint (string text,  [boolean leftButton], [boolean rightButton], [boolean middleButton],
               [number time], [string  texture],    [number  songID],      [number  scale])

setControlHint (string text[,  boolean leftButton[, boolean rightButton[, boolean middleButton[,
                number time[,  string  texture[,    number  songID[,      number  scale]]]]]]])5.  Syntax highlighting would be nice, even just for indicating variable types, but I doubt it would be worth it to do it manually.  If you're willing and/or able, there's something like this that could be used, I think.  If it's a pain to add or you don't want it in for other reasons, don't worry about it.

[Dolphin's Cry]

1.  For long functions like this, should we put in carriage returns, and if so, is there a characters-per-line limit we should go by, and should we put an ellipsis or something at the end of each broken line?  If Lua has a line-continuation character, that might be good to use so people can copy+paste+edit more directly.

Lua does not care about line breaks in most cases, so this is perfectly fine. There also is no line-continuation character, because Lua simply does not need one. (The cases where a line break is significant in Lua are rather esoteric.)

2.  Is it okay to add white space like I did?  I know some languages are very picky, and I'm new to Lua, but spaces don't seem to mess up my function calls.

Lua cares about spaces and tabs even less than it cares about line breaks. Adding white space is never an issue, leaving it out only in some cases. In particular, if you use .. (the string concatenation operator) to concatenate two number (they will be converted to strings implicitly), you may not leave out the white space between the first number and the .. operator:

Code: [Select]

1 .. 2 -- gives "12"
1..2 -- syntax error, as Lua considers the first . to be a part of the first number (1.).

3.  If you refer to a function call in the text portion of a topic, should you write it like "myFunction", "myFunction()", or "myFunction(...)"?  In my case, I put the ellipsis there since calling it without parameters crashes Aquaria.  Not that it would have been very useful if it didn't crash, but still.

I usually go with "myFunction" or - if I want to stress that I'm talking about a function - "myFunction()". If you want to use it in a script, you should look at the signature instead of just copying a reference from some explanatory text anyway.

4.  Should optional parameters be indicated somehow in the function line?

The practice so far has been to specify the default value of an optional parameter using the "Type name = value" notation. In cases where I wasn't sure about the default value, I have used a question mark ("Type name = ?").

[Guy]

I just tried signing up but I get a MediaWiki internal error.

Danger Mouse, you said you had copies of all the old stuff, have you put any of that up?

[Particlese]

That clears up everything.  Thanks!

[ryos]

5.  Syntax highlighting would be nice, even just for indicating variable types, but I doubt it would be worth it to do it manually.  If you're willing and/or able, there's something like this that could be used, I think.  If it's a pain to add or you don't want it in for other reasons, don't worry about it.

I installed that extension a while ago, based on feedback from Titch.