Return-Path: X-Original-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9B4A29977 for ; Wed, 28 Mar 2012 20:06:07 +0000 (UTC) Received: (qmail 51172 invoked by uid 500); 28 Mar 2012 20:06:07 -0000 Delivered-To: apmail-incubator-callback-dev-archive@incubator.apache.org Received: (qmail 51064 invoked by uid 500); 28 Mar 2012 20:06:07 -0000 Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: callback-dev@incubator.apache.org Delivered-To: mailing list callback-dev@incubator.apache.org Received: (qmail 51056 invoked by uid 99); 28 Mar 2012 20:06:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Mar 2012 20:06:07 +0000 X-ASF-Spam-Status: No, hits=0.3 required=5.0 tests=FRT_ADOBE2,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of brian.leroux@gmail.com designates 209.85.214.175 as permitted sender) Received: from [209.85.214.175] (HELO mail-ob0-f175.google.com) (209.85.214.175) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Mar 2012 20:06:01 +0000 Received: by obbwc20 with SMTP id wc20so275184obb.6 for ; Wed, 28 Mar 2012 13:05:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=XIXQrlekxAjGCQ5MWqmZwObcFlhqcS12/jdRf+KI1RA=; b=BFORrJVgpxoJQ6wKMmviG8nGJOcoLwfO2vHd7CzTm4+frNzP8yz2WYbyPRb7j0knmt zVXek6dpKqK5YfdQx+0vEZq/29diI67GM/7W0oPi3Lf7UeEnEgztGyoFReJZp/LVgLR2 VhPcW0XPa95xrDI2fIz/y4NzzZqJlP+KXtH4aN3xKMd0Xs6W0V9cFHrdDAmGrRi/Ngvw dIq4t0UELMLZujC9C+qKScIH9S74kGFN1eIE7456Wwq3U/Da7Iwe0ApRxXae9bbDDEkL QonaRJfHTtYz7id3kGZ+2i3qUj+w+9O1aa+Jl61mMUwhHuci9xt4amZk09ypBh240EIP pbPw== MIME-Version: 1.0 Received: by 10.60.24.170 with SMTP id v10mr41095125oef.60.1332965140867; Wed, 28 Mar 2012 13:05:40 -0700 (PDT) Sender: brian.leroux@gmail.com Received: by 10.60.63.167 with HTTP; Wed, 28 Mar 2012 13:05:40 -0700 (PDT) In-Reply-To: References: <4F7311E2.7030600@linux.intel.com> Date: Wed, 28 Mar 2012 13:05:40 -0700 X-Google-Sender-Auth: pWKZCT8DVqFdlZ3XxUgbo-sOiuc Message-ID: Subject: Re: About porting Notifications to Codova-Tizen From: Brian LeRoux To: callback-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Its kinda funny b/c our 'notification' api pre-dates the concept of notifications as they've grown to be in mobile. I can definitely see us looking to clean that up post 2.x On Wed, Mar 28, 2012 at 10:35 AM, Filip Maj wrote: > Do you mean you want to implement your own HTML/CSS dialogs for enabling > this functionality? If so, styles would be susceptible to be overridden b= y > the user's stylesheet... > > On 3/28/12 6:28 AM, "Paul Plaquette" > wrote: > >>Hi folks, >> >>I am implementing Notifications alert and confirm methods on our >>Codova-Tizen JavaScript shim-layer. >> >>As you may know Tizen is a web based OS (www.tizen.org) >> >>at first the plan was to use W3C Web Notifications. >> >> =A0I saw that the Web OS implementation that is indeed very similar to >>our Codova- Tizen =A0shim-layer is implementing these alert and confirm >>methods providing its own UI . >> >>Moreover using Web notifications requires user authorization, and is not >>providing >>the same level of user interaction. >> >>Actually I think =A0I should used a specific UI too as Web Notifications >>Semantic is quite different from having an alert or a confirm dialog >>that pop within the context of an application. >> >>Any Advices/Suggestions on this point? >> >>Regards, >>Paul >> >> >