[plt-scheme] "Projects"

I suggested following all requires, as long as they're in this
directory or a subdir.  Then you suggested all using string specs,
with no subdir restrictions.  Then I suggested a union of the two.


On Sep 27, Carl Eastlund wrote:
> I'm confused.  Isn't that what I said?
> 
> On 9/27/07, Eli Barzilay <eli at barzilay.org> wrote:
> > But that won't work for files that you refer to using `lib'.  Maybe
> > use file and string specs without the in-the-same-directory
> > restriction?
> >
> > On Sep 27, Carl Eastlund wrote:
> > > How about modules required by a "filename.ss" or (file
> > > "filename.ss") spec, rather than by directory hierarchy.  That way
> > > "../" prefixes will still count as "the same project".  I have
> > > plenty of code with parent-directory references.
> > >
> > > --Carl
> > >
> > > On 9/26/07, Eli Barzilay <eli at barzilay.org> wrote:
> > > > Maybe a good imitation of the "Project" feature is to open (in tabs)
> > > > all files that are both required (or included etc -- runtime-paths)
> > > > from the current file, and that are either in the current-file's
> > > > directory or a subdir.  This way you need only two operations (open
> > > > main file, open relatives) to open a "Project".
> > > >
> > > > Maybe even more -- an "Open Project" menu entry that does the above
> > > > two operations, or, if you select a directory, open all files in that
> > > > directory and subdirs.  Also, it could add a "<foo> Project" entry to
> > > > the recently-used menu, so it's easy to do the same in the future.
> > > > (And avoid adding all of the project's files to the recent list.)

-- 
          ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:
                  http://www.barzilay.org/                 Maze is Life!