Talk:WikiTI Home

Discussion

What do you think about this wiki?

More!

I think it needs information on more calculators than just the Ti-83+ series, and general assembly information (like a good cathegorized tutorial overview for instance) wouldn't hurt either, I think :)

Timendus

I hope we can do that soon

Just, we don't want to waste time getting it all set up for that and have no one use it. If we see a lot of people milling around here, contributing, then by all means, we'll expand. But one thing we DON'T want to do is mirror 28 Days. We can link TO it, but we don't want it actually here.

--AndyJ 06:50, 27 Mar 2005 (PST)

Categories

On many pages, there is now a sizable blank space at the top due to several lines of category links. What, if anything, should we do about this? FloppusMaximus 19:06, 29 Mar 2005 (PST)

Move them?

Move the Category links to the bottom should do it. :) That, or put them all on one line.

--AndyJ 19:07, 29 Mar 2005 (PST)

Yeah, that sounds like a good idea. :) FloppusMaximus 20:18, 29 Mar 2005 (PST)

I think I officially qualify as a robot now. You can tell I was getting tired towards the end, as I missed the minor-edit button a few times... sorry about that... FloppusMaximus 21:28, 29 Mar 2005 (PST)

Actually, I was going to just mod the php code to fix this bug....keeping the category tags on the top might be a good idea actually. (JasonM)

That might still be a good idea. FloppusMaximus 13:18, 3 Apr 2005 (PDT)

Caching

Is it just me, or are there some serious caching problems here? FloppusMaximus 21:32, 1 Apr 2005 (PST)

In particular? --Dan Englender 21:42, 1 Apr 2005 (PST)

Ya, the wiki seems to have weird caching problems, especially since it appears the reload the page every time, even if it doesn't get changes. I don't know what's up. --AndyJ 22:35, 1 Apr 2005 (PST)

Considering the dynamic nature of a wiki (a page could be edited, at pretty much any time), I wouldn't mind not having it cached. (Though I would personally disable browser caching altogether if firefox would let me... :P ) --Aquanight 22:44, 1 Apr 2005 (PST)

Er... I think I see what you mean... stuff is getting cached when it shouldn't be. (I could've sworn I told firefox to only use 0 KB (aka none) for cache and it's still caching ... argh.) --Aquanight 22:46, 1 Apr 2005 (PST)

I've disabled caching myself as well. Perhaps we should just disable caching altogether? (JasonM)

Caching has been disabled. (JasonM)

I found a "Disable Caching" option in Misc. Preferences, if that helps. Gambit 00:28, 2 Apr 2005 (PST)

On Other Calculators

Just a random idea I had -- a lot of the ROM calls, RAM addresses, and ports are very similar, if not identical, between the 83 and 83+, and more generally, between all of the Z80 calculators. For some of them -- 83Plus:RAM:86D8 and 83:RAM:8253, for instance -- it may be possible to combine the two into a single page, though I'm not sure that would be a good idea, given the potential for confusion. So here's what I propose instead:

• For simple things like penRow, we can just have two copies of the page, as there isn't very much to keep synchronized.
• For more detailed pages such as GetKey, have a brief description with a link -- "This routine waits for the user to press a key and returns it. It is equivalent to GetKey on the TI-83 Plus." -- on one page, and the more detailed description on the other. Not a redirect in this case; I'm talking about a distinct page, which would point out the different call points and RAM addresses; in the case of GetKey, for instance, the address of keyExtend is different and should be noted.
• In either case, on both pages, add a new section "On Other Calculators" near the bottom, with appropriate links. This section serves two purposes: First, it's simply useful information to have available, both for people trying to write cross-platform code, and for those of us who are interested in researching the OS. Secondly, it would serve as a reminder to editors that there are multiple pages that may need to be updated.
• It's also important to maintain the distinction between routines/variables/ports that are identical as opposed to those which merely have related functions. For example, the widely used GetK routine on the 83 isn't known -- to my knowledge -- on the 73, but GetCSC serves as an adequate substitute in many situations. This is something that belongs in "See Also," not in this section.
• Some templates might be in order here.

FloppusMaximus 18:41, 24 May 2005 (PDT)

It's not a bad idea. The only problem is that it makes a lot more work for people who just want to make a simple addition to the wiki. There's already a fairly high initial barrier (figuring out the templates and categories) to overcome for someone who wants to stroll along and add something to the wiki. For you and I it wouldn't be a big deal, but I'm worried it's going to dissuade a random person who floats by from adding ErrMemory to 83 Plus, because then 83 (and 86 or 73, if someone decides to start them) will have to be added/changed as well. --Dan Englender 10:01, 25 May 2005 (PDT)

Wanted Pages

I decided it was too minor to post as news on the main page, but I modified the Wanted Pages page so that the threshold is 1 link instead of 2 links. A *lot* more wanted pages show up now, though there is some junk in the list now too (like fake links from templates). I figure wanted pages are as good a place as any to start adding, so I'm going to try to make a dent in the list. Anyone who would like to help is welcome to do so :) --Dan Englender 10:06, 25 May 2005 (PDT)

Not "hardware" specific documents

I was so free to edit the artilce over Emulator(s). I also created an article regarding PindurTI.

As I already stated on the MaxCoderz board (http://joepnet.com/hosted/maxcoderz/phpBB2/viewtopic.php?t=1521), I think WikiTI has a lot of potential to collect information about the TI community aswell. Thinks like PindurTI, GrayScale and maybe even information about all the Zelda attempts. In my opinion, people can benefit from that information. --Vincent Junemann 15:00, 21 February 2006 (CET)

Required logon

If the spam is being done by bots, perhaps instead of requiring a log-on, we can require either a log-on or a captcha? I realize there's additional coding involved, but we've had a fair number of useful contributions by non-logged in contributors, and it would be a shame to scare them off by prospects of account creation or the fact that we can track their activities, or what have you. --Dan Englender 13:55, 23 Feb 2006 (PST)

Agreed, if we can either find a mod for that or code one ourselves. Of course, maybe even a simple "check this box" thing would work if the bots are programmed just to hit mediawiki and not check for stuff... And if a botrunner ever finds it and fixes their bots, we can either just change it or go to a captcha... However, I think most of the legit anon edits were by people who have an account but just didn't notice they weren't logged in at the time. Andy Janata 18:40, 23 Feb 2006 (PST)

Wiki update

Whats this undefined link I see on a lot of the pages?--Jim e 06:07, 14 March 2006 (PST)

Example? --Dan Englender 06:12, 14 March 2006 (PST)

This page has it right under the contents.--Jim e 06:18, 14 March 2006 (PST)