> ah, i thought the cache dir was application specific. It used to be for custom applications (not for the standard apps), but to change that was the whole point of the modification.
> if that's not the > case, why not put it back in the qooxdoo dir itself? Yes, that would a good alternative in my eyes. >>> 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. Ah, ok, of course. But how is this related to the location of the cache directory? Are you saying this is the only place where the developer can be sure of having write access (as opposed to, say, the qooxdoo installation directory)?! > i wouldn't prefer to have developer-specific code in config.json, nor a > specific config.json for each of the developers. No, but you could have application-specific code in a config.json, couldn't you?! If you want the old behaviour of an application-specific cache, just add CACHE="./cache" to your config.json. > 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. Ok, so I think we have two issues here: 1) having a system-wide cache directory 2) having it in /tmp Are you still struggling with 1)? I think 2) would be easier to remedy. > 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. Ah, ok, now I get it. Of course, we could add a CACHE macro to the skeleton apps that makes the default explicit. T. ------------------------------------------------------------------------------ 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
