Carl Karsten wrote: > I am gong to overhaul some of the setup docs. I don't like any of the > suggested > names for the dabo home dir (dabo and projects.) > > dabo makes sense, but then the classes end up in dabo/dabo, which can lead to > confusion when someone says "the dabo dir." I considered renaming it dac > (dabo > abstract classes) and making the docs show how to link/path it into site > packages such that the "import dabo" command would still work, but decided > that > was worse than dabo/dabo. > > > [EMAIL PROTECTED]:~$ find ./ -name dabo -type d > ./src/projects/dabo > > ~/dev/apps/ is where my apps go > > > [EMAIL PROTECTED]:~$ find ./ -name dabo -type d > ./dev/dabo > ./dabo > ./dabo/carl/dabo > ./dabo/carl/dabo/dabo > ./dabo/carl/dabo.foo/dabo > ./dabo/carl/dabo.bar/dabo > ./dabo/trunk/dabo > ./dabo/trunk/dabo/dabo > > ./dev/dabo is where my apps go. > > I am wondering if anyone has come up with something better?
Where each top-level directory is irrelevant, and it is up to the person. If people need that much handholding, just telling them to put everything in the home directory should be sufficient. I did away with my top-level projects dir with my last computer switch a couple months ago, and I like it (having everything directly underneath my home directory). Here's an example: -> /home/pmcnett/dabo top level dabo directory, the one with AUTHORS and README and (most importantly) the one with the dabo subdirectory (the top-level of the importable dabo stuff). -> /home/pmcnett/daboide top level daboide directory, the one with ClassDesigner.py, ReportDesigner.py, and friends. -> /home/pmcnett/ss top level directory for the dabo app I'm currently developing for a client. That's the short version. The long version involves how I set up my symlinks and helper scripts, but the key is getting dabo placed somewhere and importable from Python. It matters not where individuals choose to place their directories, and I'd argue that part of the process of initiation into something like Dabo would be for people to come up with their own best practices themselves. It isn't rocket science. -- pkm ~ http://paulmcnett.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
