Re: [Trinidad] added browser version support in skinning TRINIDAD-799

Cristi Toth said the following On 4/19/2008 10:58 AM PT: :) yep, I forgot about the "and" is "or" valid in those CSS rules? No. That's what the comma is for. -- Blake Sullivan On Sat, Apr 19, 2008 at 6:44 PM, Blake Sullivan <[EMAIL PROTECTED] > wrote: Cristi

Re: [Trinidad] added browser version support in skinning TRINIDAD-799

:) yep, I forgot about the "and" is "or" valid in those CSS rules? On Sat, Apr 19, 2008 at 6:44 PM, Blake Sullivan <[EMAIL PROTECTED]> wrote: > Cristi Toth said the following On 4/19/2008 3:51 AM PT: > > or @agent ie and (version:6) and (version:8) > > This rule would never be true because it is

Re: [Trinidad] added browser version support in skinning TRINIDAD-799

Cristi Toth said the following On 4/19/2008 3:51 AM PT: or @agent ie and (version:6) and (version:8) This rule would never be true because it is asserting that the agent must match IE and the version must match both 6.* and 8.* -- Blake Sullivan On Sat, Apr 19, 2008 at 1:31 AM, Blake Sulliv

Re: [Trinidad] added browser version support in skinning TRINIDAD-799

or @agent ie and (version:6) and (version:8) On Sat, Apr 19, 2008 at 1:31 AM, Blake Sullivan <[EMAIL PROTECTED]> wrote: > Glauco P. Gomes said the following On 4/18/2008 4:28 PM PT: > > I think that I'm not expressed correctly, what I wanted to say was not > sequencial major versions. > Eg.: > @

Re: [Trinidad] added browser version support in skinning TRINIDAD-799

blake, can you create an issue for "updating version support format for skinning" assign it to me (only if you want), add this class as a an attachement and if you guys (from Oracle) decide that you can pre donate the regex for determining the agent version, please add those too I'll handle it in t

Re: Exporter comes finally to the scene :)

OK, I will apply this soon with Cagatay! On 4/19/08, Cagatay Civici <[EMAIL PROTECTED]> wrote: > > Agree with Matzew, action listener way looks better. > > It'll also help making it work with client side state saving. > > On Sat, Apr 19, 2008 at 11:11 AM, Matthias Wessendorf <[EMAIL PROTECTED]> >

Re: Exporter comes finally to the scene :)

Agree with Matzew, action listener way looks better. It'll also help making it work with client side state saving. On Sat, Apr 19, 2008 at 11:11 AM, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > On Sat, Apr 19, 2008 at 9:22 AM, Hazem Saleh <[EMAIL PROTECTED]> > wrote: > > Hi Matzew, > > I fol

Re: Exporter comes finally to the scene :)

Hello Hazem, I would prefer matthias suggestion. If the exporter is inside a command it should be easier to use the exporter in a different renderkit. Regards Bernd Hazem Saleh schrieb: > Hi Matzew, > I followed the previous pattern of the excelExport component. > So IMO, I think it is not odd

Re: Exporter comes finally to the scene :)

On Sat, Apr 19, 2008 at 9:22 AM, Hazem Saleh <[EMAIL PROTECTED]> wrote: > Hi Matzew, > I followed the previous pattern of the excelExport component. > So IMO, I think it is not odd for the component users. well, perhaps personal choice. Take this: http://myfaces.apache.org/trinidad/trinidad-api/t

[jira] Created: (TOBAGO-653) Create a own JsonResponseWriter for dojo ajax requests

Create a own JsonResponseWriter for dojo ajax requests -- Key: TOBAGO-653 URL: https://issues.apache.org/jira/browse/TOBAGO-653 Project: MyFaces Tobago Issue Type: Sub-task Compon

Re: Exporter comes finally to the scene :)

Hi Matzew, I followed the previous pattern of the excelExport component. So IMO, I think it is not odd for the component users. On Fri, Apr 18, 2008 at 7:41 PM, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > On Fri, Apr 18, 2008 at 7:02 PM, Hazem Saleh <[EMAIL PROTECTED]> > wrote: > > Hi Matzew