Jump to content

Talk:Pop-up notification

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Fair use rationale for Image:Gmail Notifier.png

[edit]

Image:Gmail Notifier.png is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.

Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Wikipedia:Fair use rationale guideline is an easy way to insure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.

If there is other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page. Note that any fair use images lacking such an explanation can be deleted one week after being tagged, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.

BetacommandBot (talk) 17:16, 2 January 2008 (UTC)[reply]

Origin?

[edit]

What is the origin of that word (both symbolic and historic usage in user interfaces)?

In the French equivalent of that wiki page, the word Toast is credited (but unfortunately without a reference) to a Microsoft employee who described the name being linked to how that graphical element is similar to how toasts come out of a toaster.

Even though this may be stating the obvious, this is not strictly speaking obvious since that display method is not described in the article, more essentially since it is not an essential characteristic of a toast ("a toast is a small, informational window [...] notify users of various kinds of events" is the essence of a toast): in the Android-based user interfaces for instance, it is generally accepted that toasts fade in and out. Therefore it should make sense to mention both the symbolic and historical origin of the word.--138.231.140.26 (talk) 06:38, 21 February 2012 (UTC)[reply]

Good question. Kotz (talk) 14:10, 15 July 2013 (UTC)[reply]
no cites, but my guess is it was from Mortal Kombat (where a figure pops in from the side and says "Toasty!" and disappears again). 128.237.246.68 (talk) 22:39, 19 November 2021 (UTC)[reply]

Proposed merge with Pop-up notification

[edit]

Hi. I think Toast (computing) and pop-up notification must be merged because their subjects are the same thing. (Exactly the same thing.)

To be certain, I asked one of my fellow admins "what is the difference between a "toast" and a "pop-up"? (This is a trick question, since it implies there must be a difference.) He mumbled something about pop-up notifications are like comic book balloons but that's it. Well, the fact that the two articles show wrong images (File:GNOME-Music-Applet-screenshot.png in "toast" and File:Lubuntu Desktop Notification 01.png in "pop-up notification") is telltale sign that they are the same. Best regards, Codename Lisa (talk) 01:45, 19 July 2013 (UTC) Codename Lisa (talk) 01:45, 19 July 2013 (UTC)[reply]

I agree. To my astonishment, I've never ever heard the name toast in this context before but it's clear that they are the same. The information given in the articles has a huge overlap, too. The only question that remains is: who does the merging? I had a little bit of time to write down a few facts about popup notifications and was hoping that others would extend the article. Given that toast (computing) is even shorter, this is unlikely to happen soon but well. In any case, a careful merger is a different thing, time-wise. So I probably won't be doing this any time soon. --Mudd1 (talk) 15:24, 19 July 2013 (UTC)[reply]
The "toast" wording was popularized by the Android operating system and its API. In general, these should be called pop-up notifications. Therefore the stub article Toast (computing) should be changed to an automatic redirect (or disambiguation) to Pop-up notification, and any parts of its content worth keeping should be merged into the redirect target article. (A more radical approach would be to de-link all links to Toast (computing) and change them to point to Pop-up notification instead, providing proper explanations such as "A term used to refer to pop-up notifications in the Android UI" in Toast (disambiguation) page. But this may risk creation of deleted page at a later date.) I can do the merging at a later date if there are no objections (and I hopefully remember - please remind me on my talk page). -- ADTC Talk Ctrb 19:21, 8 August 2013 (UTC)[reply]
Hi. I agree. Just a note though: The "more radical approach" is discouraged in Wikipedia. We keep telling people that redirects are not evil. Best regards, Codename Lisa (talk) 01:23, 9 August 2013 (UTC)[reply]
I have completed the merger. I changed to an automatic redirect and salvaged parts of the article that I deemed as worth keeping, placing them (edited and update appropriately) in the target article. If you have any further contributions to make, please feel free to do so. @Lisa, note duly noted and followed :) -- ADTC Talk Ctrb 14:29, 20 August 2013 (UTC)[reply]
Lisa, what do tags like {{R from merge}} do in an automatic redirect page? I can see that it adds a textual explanation on a non-redirect page (like this talk page) but it seems to do nothing where you had put it. So why have it there?-- ADTC Talk Ctrb 04:44, 22 August 2013 (UTC)[reply]
Hi. It is a maintenance tag and its lack of text in redirect pages is by design. (After all, what's the point of adding text that nobody reads?) Its job is to tell maintenance bots that there was contents there but now its merged elsewhere. Best regards, Codename Lisa (talk) 06:09, 22 August 2013 (UTC)[reply]
Lisa, thanks for the explanation. The maintenance thing makes sense. As for "what's the point of adding text that nobody reads?" I would argue that editors could still read the text by stepping back from the target page with the &redirect=no option (this special link is made available on the target page below the title). Similar to telling maintenance bots, it can also inform users arriving as no-redirect at the redirect page that there were contents there but now it's merged elsewhere. Anyway that's something for another day :) -- ADTC Talk Ctrb 06:29, 22 August 2013 (UTC)[reply]

Android Toast or Windows Balloon Notification example images

[edit]

Can I add the example image from here to show an Android "toast" in the section Support on Different Systems? I will crop the image to show only the screen, rather than the whole phone. I would upload it with similar bibliography information to the existing image in the section. I'm only worried that it might increase focus on Android while the article is too general for it. But I believe the "toast" example is a better fit for the article than the notification drawer example (so we can consider replacing instead of addition). For balance, I could also create and include a Windows balloon notification example too.-- ADTC Talk Ctrb 06:37, 22 August 2013 (UTC)[reply]

The term “toast”

[edit]

This page is listed as “toast” in the widget template. Can somebody please explain where this name comes from? It seems very unconventional and uncommon to me, and this page does not even include the word “toast” but only “toastings” (which I also never heard before). The term “pop-up notification” is much more spot on and easier to understand and recognize for me, although I don't know how popular it is. so I think the template should be edited to use the term “pop-up notification” instead. --Wiki-Wuzzy (talk) 00:49, 9 July 2015 (UTC)[reply]

Okay, I have now discovered where the term “toast” is used. It is a term used in Android development. But I am too lazy to put references or to edit the article. :P --Wiki-Wuzzy (talk) 14:28, 14 July 2015 (UTC)[reply]