OK, that sounds reasonable to me.
-Darin

On Tue, Oct 20, 2009 at 9:51 AM, John Gregg <john...@google.com> wrote:

> Not precisely embedding a TabContents; I'm drawing a custom toast using
> views and putting a RenderViewHost+RenderWidgetHostView in it.
>
>  -John
>
>
> On Tue, Oct 20, 2009 at 12:27 AM, Darin Fisher <da...@chromium.org> wrote:
>
>> Is this accomplished by embedding a TabContents in a custom drawn (using
>> Views) toast?
>> -Darin
>>
>>
>> On Mon, Oct 19, 2009 at 2:17 PM, Drew Wilson <atwil...@chromium.org>wrote:
>>
>>> To be clear - our priority is to support HTML notifications on all
>>> platforms *before* investigating support for native notification platforms
>>> (like Growl/libnotify).
>>>
>>> -atw
>>>
>>>
>>> On Mon, Oct 19, 2009 at 11:25 AM, Ian Fette <i...@chromium.org> wrote:
>>>
>>>> We're trying to come up with a way to display html notifications on
>>>> these platforms, once we get the windows one checked in. (Likely code that
>>>> we will have to write.)
>>>>
>>>> 2009/10/19 Evan Martin <e...@chromium.org>
>>>>
>>>>
>>>>> On Mon, Oct 19, 2009 at 11:16 AM, John Gregg <john...@google.com>
>>>>> wrote:
>>>>> > The implementation of notifications is nearly complete for Windows
>>>>> chromium
>>>>> > with the final pieces being reviewed right now.  Hopefully it will be
>>>>> > available on the dev channel very soon behind a command-line switch
>>>>> for
>>>>> > developers to start using.
>>>>> > If you have questions about the specifics of the API, let me know,
>>>>> I'm happy
>>>>> > to answer them and/or provide more documentation.
>>>>>
>>>>> I had alluded to this before, but I don't still see a good answer:
>>>>> what is the plan on Mac/Linux when the API is called with HTML?
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>> >>>
>>>
>>
>

--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to