>From: "Danny Robinson" <[EMAIL PROTECTED]> >OK, despite my prior email, let's postpone any changes to context params until >1.0.3. That way we >can take a good look at them and decide if we want to >make lightweight dialogs the default, and also >document properly the various >settings we're thinking of making public.
+1 On 8/1/07, Adam Winer <[EMAIL PROTECTED]> wrote: Things should be trinidadinternal if we don't want to document or support them; but if we need to doc and support them, I totally agree - they've got to be in trinidad. -- Adam On 8/1/07, Simon Lessard < [EMAIL PROTECTED]> wrote: > Along the same lines, I think we should move the iframe popup's context > param to .trinidad rather than .trinidadinternal as well. Actually, I don't > think any context param should be namespaced in trinidadinternal. > > Regards, > > Simon > > > On 8/1/07, Martin Marinschek < [EMAIL PROTECTED]> wrote: > > Thanks a lot! > > > > regards, > > > > Martin > > > > On 8/1/07, Matthias Wessendorf < [EMAIL PROTECTED]> wrote: > > > given the fact that this is useful, > > > I'd not mind to make it *public* > > > > > > -M > > > > > > On 8/1/07, Danny Robinson < [EMAIL PROTECTED]> wrote: > > > > That also prompts a question. Should we change > > > > > > > > > org.apache.myfaces.trinidadinternal.DISABLE_CONTENT_COMPRESSION > > > > > > > > to > > > > > > > > > org.apache.myfaces.trinidad.DISABLE_CONTENT_COMPRESSION > > > > > > > > Given this is so critical to successful skinning, shouldn't we make it > a > > > > public setting? > > > > > > > > Danny > > > > > > > > > > > > On 8/1/07, Danny Robinson < [EMAIL PROTECTED]> wrote: > > > > > Here's the two settings I use, one for javascript and another for > css > > > > compression. > > > > > > > > > > <context-param> > > > > > > > > > > <param-name>org.apache.myfaces.trinidad.DEBUG_JAVASCRIPT</param-name> > > > > > <param-value>true</param-value> > > > > > </context-param> > > > > > > > > > > <context-param> > > > > > > > > > > <param-name>org.apache.myfaces.trinidadinternal.DISABLE_CONTENT_COMPRESSION > </param-name> > > > > > <param-value>true</param-value> > > > > > </context-param> > > > > > > > > > > Danny > > > > > > > > > > > > > > > > > > > > On 8/1/07, Martin Marinschek < [EMAIL PROTECTED] > wrote: > > > > > > Hi *, > > > > > > > > > > > > maybe someone of you has a short answer - is there a way to > disable > > > > > > the JavaScript obfuscator in Trinidad? For debugging, I'd rather > see > > > > > > the full JavaScript-code. I suspect it's a simple switch, but I > don't > > > > > > seem to find it... do I have to configure the > maven-javascript-plugin, > > > > > > or can I do this during runtime? > > > > > > > > > > > > regards, > > > > > > > > > > > > Martin > > > > > > > > > > > > -- > > > > > > > > > > > > http://www.irian.at > > > > > > > > > > > > Your JSF powerhouse - > > > > > > JSF Consulting, Development and > > > > > > Courses in English and German > > > > > > > > > > > > Professional Support for Apache MyFaces > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Chordiant Software Inc. > > > > > www.chordiant.com > > > > > > > > > > > > > > > > -- > > > > Chordiant Software Inc. > > > > www.chordiant.com > > > > > > > > > -- > > > Matthias Wessendorf > > > > > > further stuff: > > > blog: http://matthiaswessendorf.wordpress.com/ > > > mail: matzew-at-apache-dot-org > > > > > > > > > -- > > > > http://www.irian.at > > > > Your JSF powerhouse - > > JSF Consulting, Development and > > Courses in English and German > > > > Professional Support for Apache MyFaces > > > > -- Chordiant Software Inc. www.chordiant.com
