Return-Path: Delivered-To: apmail-myfaces-dev-archive@www.apache.org Received: (qmail 57256 invoked from network); 13 Jan 2010 17:20:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 13 Jan 2010 17:20:25 -0000 Received: (qmail 40489 invoked by uid 500); 13 Jan 2010 17:20:25 -0000 Delivered-To: apmail-myfaces-dev-archive@myfaces.apache.org Received: (qmail 40400 invoked by uid 500); 13 Jan 2010 17:20:25 -0000 Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Development" Delivered-To: mailing list dev@myfaces.apache.org Received: (qmail 40392 invoked by uid 99); 13 Jan 2010 17:20:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jan 2010 17:20:25 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mwessendorf@gmail.com designates 209.85.219.225 as permitted sender) Received: from [209.85.219.225] (HELO mail-ew0-f225.google.com) (209.85.219.225) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jan 2010 17:20:13 +0000 Received: by ewy25 with SMTP id 25so2859767ewy.25 for ; Wed, 13 Jan 2010 09:19:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=19MooBmKJ9S94HqOoL55YI5aabGmMl5NnGeKDRINzh8=; b=XG4AlYLcATIFdNNZByRQUWmtnWKS7vVUkr+0KwZfuqTIl2ZXcy9dlKFcCd3Cy9GTWP NP6MPBhdTqdGjhPq/sd6xrOdCKHtMcHi+YOOpQ4GoEimiuAN+FtcYcVOB4SfCBfM71mD L1kb8iKxyKgtxm5sUfJY+ACPFJN6j3UyNYnhw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=O3BLcTHPbNywKGCrhjTkPYA3DTzPl6pyPN/VGiunLupdaMUpAqxOpwMQjXrumitKff OabJAUpx6vKUnbORXwigkyeCSNyNV5lML+hkswXmZZRAMcu6MgHY8i7fx9tXBa4l2P9O VrjTBXAcch1Y34ile82zcOns/QWV221cHxucE= MIME-Version: 1.0 Sender: mwessendorf@gmail.com Received: by 10.213.42.211 with SMTP id t19mr1412535ebe.10.1263403192727; Wed, 13 Jan 2010 09:19:52 -0800 (PST) In-Reply-To: References: <71235db41001072201h63f54634k51a20b763a241fd8@mail.gmail.com> <71235db41001080204u3c8b3608o70d47d71bff83a0@mail.gmail.com> <71235db41001122357p528d1aabm9a36a9b9f0b62670@mail.gmail.com> <4B4DFBA7.6060805@oracle.com> Date: Wed, 13 Jan 2010 18:19:52 +0100 X-Google-Sender-Auth: fcbeb77cce25de3b Message-ID: <71235db41001130919i7792f1a9l4ed4278c3c7053e3@mail.gmail.com> Subject: Re: Make the new skin part of Trinidad (was: Re: [Trinidad] New Component Showcase Demo and Casablanca Skin) From: Matthias Wessendorf To: MyFaces Development Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Jan 13, 2010 at 6:14 PM, Matt Cooper wrote: > Rather than having the casablanca skin as a separate jar file, I would > prefer to see it built-into the Trinidad jars (part of the impl project) = so > consumers could use it out-of-the-box without any extra jar configuration= . I want it to become default :-) > > Regards, > Matt > > On Wed, Jan 13, 2010 at 10:02 AM, Catalin Kormos > wrote: >> >> Hi Jeanne, >> >> Thanks for the information, the thing is the custom resource loader is >> able to locate resource files in custom location, but the main entry >> point it is still the resource servlet, which intercepts the request >> to a /adf/* and then delegates to various resource loader to actually >> locate them, right? >> >> I was thinking maybe there is a feature like you can have EL >> expressions in the css, to resolve the context where the resource >> servlet is mapped... >> >> For now we will stick with the default /adf, i think this mapping of >> the resource servlet is required by other trinidad stuff also...so >> it's like a best practice to have it declared in web.xml. >> >> regards, >> Catalin >> >> On 1/13/10, Jeanne Waldman wrote: >> > >> > >> > Matthias Wessendorf wrote, On 1/12/2010 11:57 PM PT: >> >> >> >> On Tue, Jan 12, 2010 at 10:33 PM, Catalin Kormos >> >> wrote: >> >> >> >>> >> >>> Hi, >> >>> Was wondering if it would be possible to package a skin in its own j= ar >> >>> file, >> >>> >> >> >> >> yes, put the skinning xml/cfg in the JAR_FILE.jar/META-INF/ >> >> >> >> >> >>> >> >>> so that we wouldn't need to package the skin witht the actual webapp >> >>> that >> >>> uses it, so that we could start having separate modules for skins? >> >>> >> >> >> >> in theory yes. >> >> >> >> >> >>> >> >>> it would >> >>> make sense for the new Casablanca skin IMHO. What do you think? >> >>> >> >> >> >> I think we should make the new Casablance skin the default; >> >> the old skin we can place into a "skinning module" >> >> >> >> /trinidad-skins >> >> =A0-/old-and-ugly-green-skin >> >> :-) >> >> >> >> >> >>> >> >>> About packaging skins, it seems possible, but I have a question: >> >>> =A0=A0- for example in the skin's css file, if background image urls= are >> >>> specified, for example, with a property "background: white >> >>> url(/adf/skins/casablanca/images/backgrounds/buttonLikeHeadHover.png= ) >> >>> repeat-x bottom left;" this will work also when the images are >> >>> packaged >> >>> in a >> >>> jar available in the classpath, but only if the Trinidad Resource >> >>> Servlet >> >>> is >> >>> mapped to /adf/*; what happens if the servlet is mapped to another u= rl >> >>> pattern? is there another approach, mapping independent, or are we >> >>> stuck >> >>> with /adf? >> >>> >> >> >> >> I think we are stuck with the (odd) /adf >> >> >> >> Regarding its refactoring, I think it takes quite a while and maybe >> >> error-prone. >> >> Jeanne may know more on that item. >> >> >> > >> > I would stick with /adf in your path since that is the easiest. >> > >> > If you want to use a different mapping, say /foo, then you probably ha= ve >> > to >> > do this (I haven't confirmed): >> > 1. add a new foo.resources file to \META-INF\servlets\resources >> > directory >> > =A0 - currently there is an adf.resources file and it has this one ent= ry >> > org.apache.myfaces.trinidadinternal.resource.CoreRenderKitResourceLoad= er >> > 2. add your new mapping to Trinidad's ResourceServlet to the web.xml. >> > =A0- currently there is: >> > =A0 >> > =A0=A0=A0 resources >> > =A0=A0=A0 /adf/* >> > =A0 >> > 3. I don't think there are dependencies on /adf in any of Trinidad's >> > ResourceLoaders, but if so, then you'll need to write your own >> > ResourceLoader as well. >> > >> > >> >> >> >> >> >> -Matthias >> >> >> >> >> >>> >> >>> regards, >> >>> Catalin >> >>> On Fri, Jan 8, 2010 at 12:11 PM, Catalin Kormos >> >>> >> >>> wrote: >> >>> >> >>>> >> >>>> Ok, sounds good. >> >>>> >> >>>> regards, >> >>>> Cata >> >>>> >> >>>> On 1/8/10, Matthias Wessendorf wrote: >> >>>> >> >>>>> >> >>>>> once the JIRA is up, I will ping general@incubator.a.o regarding t= he >> >>>>> software grant >> >>>>> Note: this is only discussed at the incubator committee, but no >> >>>>> incubation for that piece is >> >>>>> needed. Maybe (only) a software grant. >> >>>>> >> >>>>> -M >> >>>>> >> >>>>> On Fri, Jan 8, 2010 at 11:00 AM, Catalin Kormos >> >>>>> wrote: >> >>>>> >> >>>>>> >> >>>>>> Hey Matthias, >> >>>>>> >> >>>>>> Great :), we'll look into the tasks you mentioned. >> >>>>>> >> >>>>>> regards, >> >>>>>> Catalin >> >>>>>> >> >>>>>> On 1/8/10, Matthias Wessendorf wrote: >> >>>>>> >> >>>>>>> >> >>>>>>> Hi Catalin et al, >> >>>>>>> >> >>>>>>> as promised, I hijacked the thread... >> >>>>>>> >> >>>>>>> thanks again for contributing this skin to Trinidad. >> >>>>>>> >> >>>>>>> The following tasks are needed: >> >>>>>>> -A JIRA ticket that contains the patch(es) >> >>>>>>> =A0- for the Skin itself >> >>>>>>> =A0- for the GREAT demo >> >>>>>>> =3D> maybe a software grant is needed; If so, I will handle the >> >>>>>>> paperwork stuff for you guys. >> >>>>>>> >> >>>>>>> Once the things above are sorted out, we can apply it to TRUNK. >> >>>>>>> However, I'd like to do a RELEASE before we integrate the new >> >>>>>>> Skin/Demo. >> >>>>>>> I also don't mind to pretty much do a "sub-release" once the new >> >>>>>>> stuff >> >>>>>>> is in. (With maven, release are not expensive) >> >>>>>>> >> >>>>>>> Thanks, >> >>>>>>> Matthias >> >>>>>>> >> >>>>>>> On Thu, Jan 7, 2010 at 11:37 PM, Catalin Kormos >> >>>>>>> wrote: >> >>>>>>> >> >>>>>>>> >> >>>>>>>> Hello there, >> >>>>>>>> I have the pleasure to inform you about the work we did to >> >>>>>>>> develop a >> >>>>>>>> new >> >>>>>>>> skin for Trinidad and based on this a brand new, Trinidad >> >>>>>>>> components >> >>>>>>>> showcase application. You can see it all in action at [1]. It i= s >> >>>>>>>> still a >> >>>>>>>> working in progress, in advanced state though...i mean there is >> >>>>>>>> always >> >>>>>>>> something to be improved; nevertheless we would like to donate >> >>>>>>>> the >> >>>>>>>> new >> >>>>>>>> skin >> >>>>>>>> and the new demo application to the MyFaces community, in its >> >>>>>>>> current >> >>>>>>>> state, >> >>>>>>>> and continue there if you guys agree. >> >>>>>>>> Many thanks go to my collegue Adonis who has put a lot of effor= t >> >>>>>>>> into >> >>>>>>>> designing and implementing the new skin called 'Casablanca'. I'= m >> >>>>>>>> sure >> >>>>>>>> he >> >>>>>>>> can >> >>>>>>>> give you more details as needed about how the process went. >> >>>>>>>> >> >>>>>>>> A few words about the new demo: >> >>>>>>>> >> >>>>>>>> =A0first of all, many thanks to another collegue of mine, Cosmi= n, >> >>>>>>>> for >> >>>>>>>> his >> >>>>>>>> continuos efforts with this. >> >>>>>>>> the demo is working only with facelets (there is no jsp version= ) >> >>>>>>>> it uses the latest 1.2.13-SNAPSHOT version of Trinidad >> >>>>>>>> we tryied to build it so it can be searched online also, >> >>>>>>>> currently >> >>>>>>>> tryied >> >>>>>>>> with Google Custom Search, but this didn't work out so smoothly >> >>>>>>>> so >> >>>>>>>> far. >> >>>>>>>> In >> >>>>>>>> any case, that's the reason for the pretty urls used. (so, no >> >>>>>>>> point >> >>>>>>>> in >> >>>>>>>> trying the search currently as it doesn't work). >> >>>>>>>> in general, it replicates the examples available already for >> >>>>>>>> Trinidad >> >>>>>>>> in >> >>>>>>>> the >> >>>>>>>> existing demo, in someplaces slightly improved. >> >>>>>>>> it tryies to provide a platform on which to build much more dem= os >> >>>>>>>> as >> >>>>>>>> required as there can be always new ideas about demoing a >> >>>>>>>> meaningfull >> >>>>>>>> use >> >>>>>>>> case on Trinidad, or some component behaviour. >> >>>>>>>> >> >>>>>>>> I'm eager to get your reactions, I think these guys did a great >> >>>>>>>> job >> >>>>>>>> so >> >>>>>>>> far >> >>>>>>>> and this would bring Trinidad at least a few steps closer to a >> >>>>>>>> more >> >>>>>>>> appealing and user friendly component set. >> >>>>>>>> regards, >> >>>>>>>> Catalin >> >>>>>>>> [1] http://example.irian.at/trinidad-showcase-casablanca >> >>>>>>>> ------------ >> >>>>>>>> Codebeat >> >>>>>>>> www.codebeat.ro >> >>>>>>>> >> >>>>>>>> >> >>>>>>> >> >>>>>>> -- >> >>>>>>> Matthias Wessendorf >> >>>>>>> >> >>>>>>> blog: http://matthiaswessendorf.wordpress.com/ >> >>>>>>> sessions: http://www.slideshare.net/mwessendorf >> >>>>>>> twitter: http://twitter.com/mwessendorf >> >>>>>>> >> >>>>>>> >> >>>>>> >> >>>>>> -- >> >>>>>> ------------ >> >>>>>> Codebeat >> >>>>>> www.codebeat.ro >> >>>>>> >> >>>>>> >> >>>>> >> >>>>> -- >> >>>>> Matthias Wessendorf >> >>>>> >> >>>>> blog: http://matthiaswessendorf.wordpress.com/ >> >>>>> sessions: http://www.slideshare.net/mwessendorf >> >>>>> twitter: http://twitter.com/mwessendorf >> >>>>> >> >>>>> >> >>>> >> >>>> -- >> >>>> ------------ >> >>>> Codebeat >> >>>> www.codebeat.ro >> >>>> >> >>> >> >>> -- >> >>> ------------ >> >>> Codebeat >> >>> www.codebeat.ro >> >>> >> >>> >> >> >> >> >> >> >> >> >> -- >> ------------ >> Codebeat >> www.codebeat.ro > > --=20 Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf