Talk:Wii Homebrew Cursors

Buttons

Could you make images for each Wiimote and Nunchuk button? This would help About/How To Play pages. Having images that show a wiimote with directional arrows to show rotation or motions would be really handy too --Paril 19:20, 11 February 2009 (UTC)

While this being a valid request, it doesn't have anything to do with the cursors. It would be a different and most importantly vector based project, some of which has already been done here in the Wiki by others. Maybe, but certainly not anytime soon. --Drmr 22:04, 11 February 2009 (UTC)

More Cursors

busy

I think somebody might be able to use a busy pointer too.--henke37 13:00, 7 July 2008 (CEST)

Commonly, Wii software doesn't have "busy pointers" but rather all sorts of different throbber animations. I'd gladly do a "busy pointer" if you could provide me with an example that fits into the pointer scheme. Drmr 16:17, 7 July 2008 (CEST)

I am thinking of something that's only slightly a rip of the oldschool mac design, a watch on the wrist of a hand.--henke37 18:43, 7 July 2008 (CEST)

That would be probably too small of a visual cue. Anyway, if the existing cursors get used at all, I will amend the cursor pack with custom produced variants when the need arises (i.e. if a developer requests them). Drmr 22:42, 7 July 2008 (CEST)

Tapping fingers or some general movement of them? would be nice JD 12:10, 8 July 2008 (CEST)

Why not just include a throbber centred at the same hotspot as the finger. When the program is busy, it shows the throbber rotating around the pointer position. Xeron 12:51, 8 July 2008 (CEST)

What about a blue cycle with a rotating dot like that one the Wii uses for loading (see Wii Shop channel)? Matti-Koopa 05:45, 24 July 2008 (CEST)

From a usability and best practice point of view, a busy cursor is a big no no. if you can animate a cursor while doing something, you can probably also implement a cancel button. so just leave the default cursor and show something in the screen. just like nintendo already does with all games. You always have a loading animation on the back (5 orbs rotating) and a back button (circular with a twisted arrow). --gcb

aim

some crosshairs like zelda would be useful. --gcb

forbidden

some cursor that denotes an action is forbidden. Like you cant drag this here, or you can't select this button at this time. --gcb

License

The page said the images are under a Attribution-Share Alike licence, but the link is to a Attribution-Noncommercial-Share Alike licence? Felix 12:31, 8 July 2008 (CEST)

You are perfectly right, corrected (although I will not update the readme in the archive for this, since noncommercial is mentioned in the text anyway). I am, however, still thinking about the license, generally. For the time being, Attribution-Noncommercial-Share Alike seemed like a safe route to go, but I don't have a problem releasing it under another license if someone could point out a better suited one. Drmr 15:50, 8 July 2008 (CEST)

As I understand it, under the LGPL I would only be able to use these cursors if I either provide the source code for my program or load the cursors from files included with the program. So I would not be able to embed the cursor into my binary unless I released the source? Chris 16:34, 9 November 2008 (UTC)

Aside from complete source disclosure, section 4 of LGPLv3 offers you two other possibilities. One you mentioned already: Including the "library" and "dynamically linking" it, i.e., load the PNGs from included files. The other, perhaps less practical, would be to provide the possibility to compile your program with the library, e.g. with pre-compiled files of the parts you want to keep closed-source. All in all, you are quite correct, tho, and encouraging open-source has been kind of the point to make the icons LGPL. Is it a problem for you to release the source code? --Drmr 02:56, 10 November 2008 (UTC)

I just prefer not to, mainly because my code is inefficient and messy! Thanks for the clarification though. Chris 17:24, 10 November 2008 (UTC)

I hear that argument so very often, but that is actually even more reason to release the source code. Both you and the source can only gain from it. --Drmr 01:13, 11 November 2008 (UTC)