Open main menu

Bulbapedia β

Talk:Feature registration


This really doesn't warrant its own page. It's three sentences and could easily be condensed into two. While it is true that this isn't physically on the menu, it's use intrinsically ties it to the menu (and in fact, is a menu in-and-of itself) so saying that it's wholly apart is inaccurate. glikglak 23:21, 13 July 2015 (UTC)

I think it should be merged into the Menu page. This page cannot thrive on its own when it's that small. Berrenta (talk) 00:23, 14 July 2015 (UTC)
Do we have a page/section about the use of the Y/Select button for registered key items in other generations? This could just as well go there. --Abcboy (talk) 05:52, 14 July 2015 (UTC)
A list of shortcuts is not a menu because it's not a hierarchical preset list of commands, which is what menus are by definition (regardless of the user being able to customize it or not). The Ready button is not related to the menu at all. SatoMew2 (talk) 10:25, 15 July 2015 (UTC)
I think it would be worthwhile to expand this page to cover all kinds of item registration as well. I don't think it would be appropriate to merge this page with Menu since it's not part of the Menu nor particularly related to it. --SnorlaxMonster 11:11, 15 July 2015 (UTC)
I don't think I've ever heard of a definition of menu that demands that the list be rigidly fixed... The idea seems a bit ridiculous to me. Insofar as it offers a list of entries to choose from, it is perfectly correct to call it a type of menu.
Between the facts that you have to use the menu to register items/menu functions, that you can indeed register "menu" functions, and that Ready button registration is a way to actually bypass the "menu", I think one or more of those makes a good reason this page could currently be merged into Menu.
That said, I could also approve of expanding it to button registration in general. The main problem there is, I'm not really sure what that page should be called. (And more generally, I'm not 100% sure there's enough to say or include about other types of button registration to make this a decent-sized page anyway.) Tiddlywinks (talk) 11:36, 15 July 2015 (UTC)
A menu requires a hierarchy. It is preset in the sense that the user does not program the UI (he or she may be able to customize it but it is usually in a limited fashion); this is of course not a requirement. The Ready button just lets you randomly pin any feature or item onto it so it's not a menu. SatoMew2 (talk) 12:27, 15 July 2015 (UTC)
I don't understand what you think a "hierarchy" is. (The menu doesn't seem to have any hierarchicy to me... There's just one "level".) At the very least, you can register the Pokémon List, Pokédex, Bag, Trainer Card, and Options to the Ready button and end up with just a subset of the full "menu". If you think the "menu" is hierarchical, how would that subset not be? Or does it just lose any "hierarchy" if you add items to this menu?
It mostly sounds to me like you have a a very specific idea of what a menu is, but I don't see that supported in popular definitions of the term. Tiddlywinks (talk) 12:42, 15 July 2015 (UTC)
The menu is a bit misleading as it's actually more of a context menu than a regular menu, which doesn't need to have a hierarchy, only a single level with entries that change based on the context (and the menu indeed presents other entries under specific circumstances). The Ready button is a mere list of pinned functions or items that the player organizes in any way and order he or she wishes, thus making it similar to a list box or even the Jump Lists on the taskbar of Windows 7 and later.
Here are the guidelines on menus in Windows from Microsoft and in OS X from Apple as examples. SatoMew2 (talk) 15:03, 15 July 2015 (UTC)
I think expanding it to include other generations and moving it to Registration or something would be the best course of action. --Abcboy (talk) 15:11, 15 July 2015 (UTC)
Drafted here. --Abcboy (talk) 15:37, 15 July 2015 (UTC)
I support this idea. It makes far more sense than merging the Ready button info into Menu. SatoMew2 (talk) 16:15, 15 July 2015 (UTC)
Your Apple guidelines explicitly say that a "hierarchy" (submenus) is optional, for any type of menu. And Microsoft explains its Jump Lists as being presented through a menu ("Jump Lists provide quick access to frequently used destinations (like files, folders, and links) and commands through a context menu"), neatly analagous to the Ready button items in their menu. As for list boxes, items there are generally just selectable, not directly actionable (which should be even more apparent in the types of list boxes where multiple selections are possible at once).
At any rate, that's probably enough on this tangent (for me). Convincing anyone of anything contrary to their belief is usually an uphill task at the best of times. I'm happy to just know a bit more about where your concept comes from. =) Tiddlywinks (talk) 21:29, 15 July 2015 (UTC)
I understand what you're saying but the game's documentation does not refer to it as a menu or specifies a relation to the menu anywhere. The Help System's section on the Ready button has 4 pages, with page 2 starting with You may see boxes on the Touch Screen when you open the menu by pressing the X Button. (Ⅹボタンを ()して メニューを (ひら)くと 下画面(したのがめん)に 四角(しかく)い マークが 表示(ひょうじ)されている ことが あります), thus explaining how you register entries to the Ready button; however, it's not inherently part of the menu because key items can be registered from the Bag as well, which is not a menu but a modal window (the game calls it the Bag function in English and バッグの機能(きのう) in Japanese).
Also, Microsoft defines a menu as "hierarchical lists of commands or options available to users in the current context." and never refers to submenus as "hierarchical menus", which is apparently an Apple thing after checking the human interface guidelines of GNOME and KDE regarding menus, with KDE also calling them "cascading menus". My stubbornness notwithstanding, it's safe to say that there are inconsistencies on what menus are even among official uses of different popular products (and, if you look closely, you notice that regular menus are usually grouped by standardized categories placed on a menu bar, etc. and triggered by pull-down menus, thus presenting a hierarchical structure of sorts, which user interface guidelines hint at due to their recommendations against random behavior and organization). The comparison I made with list boxes and Jump Lists was also meant to provide examples of similar interfaces, not exact replicas. SatoMew2 (talk) 00:17, 16 July 2015 (UTC)

(resetting indent)Besides moving the draft to some new title, we could also pull a Gym guide/Gate and say that the function has always been the Ready button, but was only named in BW. --Abcboy (talk) 23:52, 16 July 2015 (UTC)

That's fair. FWIW, if that's the case, I think if we try to link this page somewhere that's only about games where it was not explicitly named such, it might be better to link something like [[Ready button|register]] an item rather than shoehorning in a plain [[Ready button]] link. Something like "gym guide" or "gate" is basically just a generic term, but this is more of a title, making it a bit more awkward to use in any and all contexts given its history (or lack thereof). Tiddlywinks (talk) 03:38, 17 July 2015 (UTC)


The current title is already the official name, even if it doesn't apply to all generations, which is explained in the lead anyway. Is a move really necessary? SatoMew2 (talk) 20:34, 23 July 2015 (UTC)

Return to "Feature registration" page.