On Fri, Nov 12, 2010 at 15:27, thron7 <[email protected]> wrote:
> > On Fri, Nov 12, 2010 at 12:08, thron7 <[email protected]>
> > wrote:
> >
> >> also, iirc, this add-nocache-param is false in the build version, but
> >> true in the source version. if you're debugging your source version
> >> (which is likely), set it to false in the "source-script" job, not
> >> "build-script".
> >
> >
> > That sounds backwards. The purpose of the source version is for
> debugging,
> > so why would you want to prevent debuggers from being able to do their
> > job?
>
> It all depends which problem you are trying to solve. Not all debuggers
> lose their breakpoints on a fresh reload. And not all browsers reload
> application files when you tell them to (e.g. Safari). So if you want to
> make sure modified files get loaded from disk during development, you
> sometimes need this setting to be true.
>
Ah, ok.
> > In contrast, the build version should be cached as much as possible for
> > faster response. It sounds to me like the default should be true for
> > build,
> > false for source.
>
> You are probably mixing the semantics of this setting. Yes, you want as
> much caching as possible in the build version. Therefore,
> add-nocache-param is set to false, because adding this URL parameter
> defeats browser caching. Get it?
Yes, I did have that one backwards. I guess for Firebug users, false and
false would be the proper settings for the source version. Thanks.
Derrell
------------------------------------------------------------------------------
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
