On Tue, 2009-06-02 at 13:23 +0200, Fritz Zaucker wrote:
> On Tue, 2 Jun 2009, Derrell Lipman wrote:
>
> > On Tue, Jun 2, 2009 at 4:37 AM, thron7 <[email protected]>wrote:
> >
> >>
> >> But what I take away from this suggestion is changing the way
> >> "create-application.py" works. How does everybody feel about something
> >> like the following:
> >>
> >> - create-application receives another CL option to specify the cache,
> >> like --cache <path>.
> >> - if not supplied the cache path will default to "TMPDIR/cache", as it
> >> is now.
> >> - the cache direcotry will be made explicit in the config.json in the
> >> CACHE macro.
> >>
> >> Additionally, we could add an interactive mode to create-application:
> >> - if run interactively create-application might prompt for an answer
> >> whether the cache should be "local"/"global", "local" meaning the
> >> "./cache" directory from the application root.
> >> - if "global" is chosen, it will prompt for a path to the cache
> >> directory, maybe offering some suggestions that can be picked from,
> >> with again "TMPDIR/cache" as the default, "QOOXDOO_PATH/cache" as
> >> another one, and maybe "~/.qooxdoo/cache" as yet another one on *ix
> >> systems.
> >>
> >
> > I like this idea of interactive mode a LOT. Also, an option to place the
> > cache in ~/.qooxdoo/cache is consistent with many Linux applications (e.g.
> > the mozilla cache goes in ~/.mozilla/somegarbagestring/cache).
>
> But this is for per-user stuff, NOT for system-wide stuff.
>
> > I have one further request for create-application: have it read
> > ~/.qooxdoorc for default settings. The cache path could be provided in
> > there, as could options for "quiet" (the current -q) and "silent" (don't
> > ask the interactive questions described above; rather use defaults
> > provided here in .qooxdoorc, and if not found here, then in base.json).
>
> Yes, please!
>
> > There's some common place for the equivalent of "rc" (start-up
> > configuration) files on Windows too IIRC, but I don't remember where that
> > is. It'd be nice to have similar functionality on all platforms if possible.
>
> As long as it is not in the registry ...
>From my experience, there are really two ways to approach Windows
startup settings like the "rc" scripts in *nix. If you're just trying
to get some variable values, then the old *.ini text file approach might
be suitable (where windows stored settings before the registry
appeared), where you can set variable values as key=value pairs. But if
you need to actually take some action to modify the windows environment,
then a *.bat file would be required. Both of these methods aren't tied
to any particular OS folder, which is part of the reason why Windows has
had such a poor security track record.
I'm not familiar with any other Windows methods outside of the registry
for customizing the windows environment.
Since I'm not familiar with the Qooxdoo toolchain that runs in Python, I
don't know how you handle platform differences with the single code base
that runs in all of the environments. I'm assuming the Python script
can detect the underlying OS and can take different approaches based on
the platform.
HTH,
Gene
>
> Cheers,
> Fritz
>
------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
