BlitzWiki
BlitzMax Forums/BlitzMax Programming/BlitzWiki
| ||
| Last updated: # 17:20, 18 Mar 2005 194.169.153.219 # (cur) (last) 13:30, 7 Jan 2005 DivineDominion # (cur) (last) 13:29, 7 Jan 2005 DivineDominion # (cur) (last) 02:37, 6 Jan 2005 Todd # (cur) (last) 22:41, 5 Jan 2005 Sgtbilko M # (cur) (last) 22:37, 5 Jan 2005 Todd # (cur) (last) 22:37, 5 Jan 2005 Todd # (cur) (last) 20:10, 5 Jan 2005 217.44.168.218 # (cur) (last) 18:39, 5 Jan 2005 Todd What's the story ? It's a good resource but why is nobody using it? Lets bring it back by contributing to it in 2006! |
| ||
| why is nobody using it? Because a large amount of people don't know about it and more people don't want to do BRL's job for them. |
| ||
| http://www.blitzwiki.org/index.php/Special:Recentchanges |
| ||
| oh, thanks for pointing that link out. |
| ||
| Who's Todd? It looks like people are making changes and this person is changing them back again! There may be good reasons for doing this, but there's an awful lot of it going on, which might explain why it never seems to change. |
| ||
| Todds the poor guy who looks after the wiki, if you compare the current version with the last version of many of the reverted pages you'll see that he was removing a load of spam porn links, so it still is being maintained! |
| ||
| Can't the wiki be locked so that only registered users can make changes? I know this partly defeats the purpose of the wiki, but if someone really wants to contribute I can't see them having a problem registering. Just a thought... |
| ||
| Can't the wiki be locked so that only registered users can make changes? He locked the entire database just before christmas, but they found a way around it. I've suggested some alternative methods, but we'll need to see what happens there. |
| ||
| Hi! Sorry for digging up such an old topic, but I just finished Abitur (high school diploma) exams and decided to put some time into BlitzMax. Now i had to notice that BlitzMax still lacks a proper Wiki which is quite dissatifying to me. Currently, if you're looking for a good module or other help/documentation you need to search the forum which is slow, inefficient and causes traffic to the BRL servers. So i conclude that a well-populated Blitzmax Wiki is absolutely required. In the past, sustaining free and fast webspace without ads and fighting spam were considerable obstacles to such an intention. My proposal would therefore be, to implement the BlitzMax wiki as a wikibook. This gets us free and fast webspace and maintaining as well as good advertisement for new users (imagine BlitzMax as book of the month etc.). Currently there already is a German wikibook on BlitzMax which hasn't made much progress, though. There is no english one, not sure about other languages. What are your thoughts about it? |
| ||
| I would love to contribute to a new wiki, but I'm not sure if a WikiBook is the right way to go. There are plenty of other free (and paid) generic wiki hosting services available. Maybe Odd Wiki. The main site looks pretty active. None of these are going to have nice things like BlitzMax source highlighting. The best solution would be for BRL to provide a MediaWiki instance that they host -- customized for BlitzMax purposes. |
| ||
| I agree with Blueapples that a BRL wiki would be the best solution. However, I think a wikibook is a better idea than some free wiki farm, since it's more reliable. |
| ||
| I'm just not sure that we would comply with the requirements for a WikiBook. The work as a whole is supposed to have a narrative of some kind - pages as reference probably don't fall under that category. I'm having a hard time thinking of how a "book" would organize dozens of modules from different sources. I guess we could take an approach where we have a few introduction chapters on the language (history, syntax, operators, etc.) and then sections like the MaxIDE CE version has for help: Audio, Streams, Data, BASIC, Images, Graphics (2D and 3D), Events, Input/Output, Networking, Scripting (LUA, and other modules), Math, GUI, System, and Compression. The big difference would be to organize every module so it fits into one of the chapters -- adding a chapter if needed -- instead of having a "Misc" category to throw all the third party stuff into. It would be helpful if BRL authorized us to use their help text as a base. |
| ||
| I've started the cover/TOC skeleton for BlitzMax here: http://en.wikibooks.org/wiki/BlitzMax |
| ||
| First topic: http://en.wikibooks.org/wiki/BlitzMax/Data/Lists |
| ||
| marksibly: http://www.blitzmax.com/Community/posts.php?topic=43299 We have also decided to license the Blitz docs under a Creative Commons license - the "Attribution-NonCommercial-ShareAlike" license. This license allows you to freely copy 'n' paste from the Blitz docs into the Wiki. But WikiBooks uses GNU FDL, which is incompatible... |
| ||
| Hmm. I think the only problem is the NonCommercial part of the CC license. The FDL allows some (rather limited) commercial use of texts licensed under it. If we could get them to release the text as FDL then we'd have a great head start... |
| ||
| I haven't seen many free wiki hosting services yet, other than wikia, which is full of ads and slow. As for the license, I think working with GNU FDL is acceptable. Hopefully BRL will adopt that when one day a BRL mediawiki may be created. Being able to copy the BRL documentation right now isn't quite important to me, but i'd really like to have some of the authors of the tutorials in this forum put those into the wikibook. |
| ||
| The best solution would be for BRL to provide a MediaWiki instance that they host -- customized for BlitzMax purposes. I can host a MediaWiki/phpWiki on my server if anyone wants to set it up and maintain it (I don't really have the spare time to commit to it, but I can provide the bandwidth and the space). |
| ||
| Spam can be considered one of the greatest problems we'll face, as it was at the old wiki. It's not a problem at wikibooks, so we'd have find out what counter-measures to take at a private wiki. |
| ||
| WikiBooks does sort of seem like it will work. I don't have a problem writing fresh documentation... I've already run into cases where the List manual pages had somewhat incorrect or incomplete information. It may be better to write it from scratch anyway, but it will be slow going. I think if I really worked at it I could do one module every two days, but to be honest I don't know how long I can really work at it. I would prefer to not have anyone hosting it on their own servers, but that's just me. I see stuff disappear all the time. I know, FlameDuck, you aren't going to just up and vanish (hopefully), but what if your server takes a dive? WikiBooks isn't going anywhere... if whoever is maintaining it gives up, then someone else can take it up. The content will always be there and will always be editable. So I guess I vote for WikiBooks. |
| ||
| I agree with Blueapples, but maybe it would be nice to have some other opinions. A working wiki would be quite a help to many people so I think it's quite important to get it running.. |
| ||
| Someone who knows how to should add it to the relevant categories and bookshelves. |
| ||
| My 2 cents: the problem with the old wiki is that it seemed to be 95% cut-n-pasted from the BlitzMax docs. What help is that? We are already a single F1 keystroke away from getting all that information anyways. I would hope that a new Wiki would be comprised of better definitions and more importantly, more examples. Also topics on good programming techniques would be helpful because BlitzMax has some BASIC legacy commands that have better OO equivalent methods. The forums here are filled with wonderful examples and helpful descriptions on what certain commands do, but searching for them can be tedious. I would love to see a new wiki be built up as a reference point to these topics, so for example if I wanted to go to the wiki and search for help on the "Framework" command, I'd first get the generic BRL help text and then user contributed help and examples compiled from relevant topics here in the BRL forums. |
| ||
| TBH it would be nice to have some decent docs that were available through the MaxIDE, this would make coding much easier than having to troll through the forums and code archives to find nothing there then having to ask questions about the commands you dont quite understand. |
| ||
| What was the old wiki made with? I can set up another mediawiki on my server. I already one copy of it running. I would just set up the blank wiki and let you guys edit it. Is there an official BlitzMax wiki at this time? Which URL do you prefer?: blitzmax.leadwerks.com blitzwiki.leadwerks.com blitz.leadwerks.com www.leadwerks.com/blitzmax www.leadwerks.com/blitzwiki www.leadwerks.com/blitz |
| ||
| If you guys want to help out, we are writing documentation from scratch over at http://en.wikibooks.org/wiki/BlitzMax I think the site is pretty much perfect for what we need. Again, I just really strongly prefer a community controlled site as opposed to one hosted on an individual/charitable company's server. WikiBooks is going to be around for a long time. |
| ||
| Did it die already?!? |
| ||
| Certainly not. I've just been pretty busy, so I can't add a lot. I'm pretty much limited to documenting what I end up using in my current project, so it will be spotty for awhile (a long time?) unless a bunch of other people jump on. |
| ||
| I will set one up if people will use it. I already have another one on the server, so I know how to do it now. What happened to the BlitzWiki domain? That seemed like a good name. |
| ||
| yeah ill use it, it will be a great resource just point noobs to the relevant page instead of having to say the same things again and again |
| ||
| I still don't quite understand why people can't use the BlitzMax wikibook. It is much more likely to stay there than any user hosted one. |
| ||
| Yeah, the wikibook one is probably the best way to go. No worries about hosting/bandwidth, etc. Plus it's already been started so people can just start adding stuff immediately. |
   |