Hi Thomas,
thron7 wrote:
i loved the 0.8.2 place of the cache dir, what was wrong with that? it's
easy to find and get rid of when needed, it's easy to say whether it's
there or not, zero clutter cost.
There was nothing "wrong" with it, but it had some drawbacks which we
wanted to remedy. Particularly, we wanted to support developers doing
multiple applications on their machines. Which is the case for most of the
core developers who easily work on 10+ applications at any one time. Cache
re-use was a major time-saver.
ah, i thought the cache dir was application specific. if that's not the
case, why not put it back in the qooxdoo dir itself? this was the case
for <0.8 right?
and i can't think of any use case
where it would make sense not to have write access to the development
dir either. (this doesn't mean there isn't any, of course)
Which "development dir" do you mean?
i mean the develeopment dir where i have the qooxdoo project, with
resources, js files etc. that i'm supposed to actively perform change /
add / delete operations.
those being said, i'm also against a system-wide cache dir because we
have multiple people working on one development machine (via x
forwarding) who might need to work with different versions of qooxdoo.
Which should be fine, since they they will have different cach objects.
But there *is* an issue with concurrent access, when two developers are
accessing the same cache object simulatneously. So this might mandate
separate caches for separate developers. But this is all easily set up
using the CACHE macro.
i wouldn't prefer to have developer-specific code in config.json, nor a
specific config.json for each of the developers.
however, if thomas is going to insist on getting the default cache dir
via gettempdir(), at least have the default config.json in the skeleton
"./cache" as cache dir by default.
Well, that would defeat the whole idea of "default", wouldn't it?!
well, you said it was a fallback mechanism. i think it makes sense to
fallback on /tmp when the developer didn't specify a cache dir. but in
reality /tmp is a bad choice because of the reasons cited by others in
this thread.
so if you're going to insist on keeping the cache in /tmp by default,
i'm saying that at least make the default explicit because i got the
impression that it's going to be the first thing most people here will
want to change.
this way at least, i'll instantly
know where to change the place of the cache dir if i ever want to.
I don't get it. Nothing has changed in this regard. The default is set in
base.json, and you can always override it in the app's config.json?!
yes, but as i don't see it in the app's config.json, i need to consult
documentation to know how to override it if i ever need to. this is not
"instantly" from my perspective.
best regards,
burak
------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
