One thing that keeps me from using most of the available IDE's for D is
the (seeming) lack of "directory project" support in them.
This is what I mean:
When I open something like Poseidon or Descent (Eclipse), I would love
to just jump into a project directory and treat that as a active
project. I don't want to have to go through the pain of creating a new
project and importing all the files into it (copying them in the
process). This would be handy for quickly moving into a already started
project using it's active structure (like dwt or the sample dwt projects).
So how about this? Is there a simple way just to start a project based
on directory alone (the IDE may create some sort of project file in that
directory if need be)? I really wish it was just that simple
considering all the projects available on dsource... very few of them
contain a ready made project file for any of the D ide's.
This seemingly minor lack has made me mostly disinterested in using
powerful ide's like eclipse/descent or poseidon. Or perhaps I just
don't know how to use them.
-JJR

At least in Descent, create a new project, select the option "Create
project from existing source" and enter the directory you wish to use.
No files will be copied and, as you said, a project file will be created
in that directory.
Is that what you want?
John Reimer escribió:

One thing that keeps me from using most of the available IDE's for D is
the (seeming) lack of "directory project" support in them.
This is what I mean:
When I open something like Poseidon or Descent (Eclipse), I would love
to just jump into a project directory and treat that as a active
project. I don't want to have to go through the pain of creating a new
project and importing all the files into it (copying them in the
process). This would be handy for quickly moving into a already started
project using it's active structure (like dwt or the sample dwt projects).
So how about this? Is there a simple way just to start a project based
on directory alone (the IDE may create some sort of project file in that
directory if need be)? I really wish it was just that simple
considering all the projects available on dsource... very few of them
contain a ready made project file for any of the D ide's.
This seemingly minor lack has made me mostly disinterested in using
powerful ide's like eclipse/descent or poseidon. Or perhaps I just
don't know how to use them.
-JJR

At least in Descent, create a new project, select the option "Create
project from existing source" and enter the directory you wish to use.
No files will be copied and, as you said, a project file will be created
in that directory.
Is that what you want?

Yep, that's it. Thanks for pointing it out. I wasn't sure how to do
that with descent. I will give that a try.
-JJR

One thing that keeps me from using most of the available IDE's for D is
the (seeming) lack of "directory project" support in them.
This is what I mean:
When I open something like Poseidon or Descent (Eclipse), I would love
to just jump into a project directory and treat that as a active
project. I don't want to have to go through the pain of creating a new
project and importing all the files into it (copying them in the
process). This would be handy for quickly moving into a already started
project using it's active structure (like dwt or the sample dwt projects).
So how about this? Is there a simple way just to start a project based
on directory alone (the IDE may create some sort of project file in that
directory if need be)? I really wish it was just that simple
considering all the projects available on dsource... very few of them
contain a ready made project file for any of the D ide's.
This seemingly minor lack has made me mostly disinterested in using
powerful ide's like eclipse/descent or poseidon. Or perhaps I just
don't know how to use them.
-JJR

At Shawn Liu's original design, poseidon was used "directory project", while
project open, it will load all source files under project directory, it also
fit D programming language packages design, however, sometimes we have some
files existed in project but we don't want to load, compile and link, some
files we don't want to copy many times in different projects, so I change the
project struct to record source files....etc informations and add a strange
tool --"import all files" to quick load all sources under project directory.
Maybe we can make good balance between them, but we need good
suggestion about this......

One thing that keeps me from using most of the available IDE's for D is
the (seeming) lack of "directory project" support in them.
This is what I mean:
When I open something like Poseidon or Descent (Eclipse), I would love
to just jump into a project directory and treat that as a active
project. I don't want to have to go through the pain of creating a new
project and importing all the files into it (copying them in the
process). This would be handy for quickly moving into a already started
project using it's active structure (like dwt or the sample dwt projects).
So how about this? Is there a simple way just to start a project based
on directory alone (the IDE may create some sort of project file in that
directory if need be)? I really wish it was just that simple
considering all the projects available on dsource... very few of them
contain a ready made project file for any of the D ide's.
This seemingly minor lack has made me mostly disinterested in using
powerful ide's like eclipse/descent or poseidon. Or perhaps I just
don't know how to use them.
-JJR

At Shawn Liu's original design, poseidon was used "directory project", while
project open, it will load all source files under project directory, it also
fit D programming language packages design, however, sometimes we have some
files existed in project but we don't want to load, compile and link, some
files we don't want to copy many times in different projects, so I change the
project struct to record source files....etc informations and add a strange
tool --"import all files" to quick load all sources under project directory.
Maybe we can make good balance between them, but we need good
suggestion about this......

Hmm... I will have to try this again to see how it works in poseidon.
-JJR

One thing that keeps me from using most of the available IDE's for D is
the (seeming) lack of "directory project" support in them.
This is what I mean:
When I open something like Poseidon or Descent (Eclipse), I would love
to just jump into a project directory and treat that as a active
project. I don't want to have to go through the pain of creating a new
project and importing all the files into it (copying them in the
process). This would be handy for quickly moving into a already started
project using it's active structure (like dwt or the sample dwt projects).
So how about this? Is there a simple way just to start a project based
on directory alone (the IDE may create some sort of project file in that
directory if need be)? I really wish it was just that simple
considering all the projects available on dsource... very few of them
contain a ready made project file for any of the D ide's.
This seemingly minor lack has made me mostly disinterested in using
powerful ide's like eclipse/descent or poseidon. Or perhaps I just
don't know how to use them.
-JJR

At Shawn Liu's original design, poseidon was used "directory project", while
project open, it will load all source files under project directory, it also
fit D programming language packages design, however, sometimes we have some
files existed in project but we don't want to load, compile and link, some
files we don't want to copy many times in different projects, so I change the
project struct to record source files....etc informations and add a strange
tool --"import all files" to quick load all sources under project directory.
Maybe we can make good balance between them, but we need good
suggestion about this......

Adding all files from a recursive scan of imports would be nice.
Then the user specifies just main.d, and the IDE adds all the files
imported in one way or another by main.d.
--bb

One thing that keeps me from using most of the available IDE's for D
is the (seeming) lack of "directory project" support in them.
This is what I mean:
When I open something like Poseidon or Descent (Eclipse), I would
love to just jump into a project directory and treat that as a active
project. I don't want to have to go through the pain of creating a
new project and importing all the files into it (copying them in the
process). This would be handy for quickly moving into a already
started project using it's active structure (like dwt or the sample
dwt projects).
So how about this? Is there a simple way just to start a project
based on directory alone (the IDE may create some sort of project
file in that directory if need be)? I really wish it was just that
simple considering all the projects available on dsource... very few
of them contain a ready made project file for any of the D ide's.
This seemingly minor lack has made me mostly disinterested in using
powerful ide's like eclipse/descent or poseidon. Or perhaps I just
don't know how to use them.
-JJR

At Shawn Liu's original design, poseidon was used "directory project",
while project open, it will load all source files under project
directory, it also fit D programming language packages design,
however, sometimes we have some files existed in project but we don't
want to load, compile and link, some files we don't want to copy many
times in different projects, so I change the project struct to record
source files....etc informations and add a strange tool --"import all
files" to quick load all sources under project directory.
Maybe we can make good balance between them, but we need good
suggestion about this......

Adding all files from a recursive scan of imports would be nice.
Then the user specifies just main.d, and the IDE adds all the files
imported in one way or another by main.d.
--bb

That's kind of app-specific, though. What about building libraries? What
if there's test/whatever code not currently being referenced anywhere
but still in use?

One thing that keeps me from using most of the available IDE's for D
is the (seeming) lack of "directory project" support in them.
This is what I mean:
When I open something like Poseidon or Descent (Eclipse), I would
love to just jump into a project directory and treat that as a
active project. I don't want to have to go through the pain of
creating a new project and importing all the files into it (copying
them in the process). This would be handy for quickly moving into a
already started project using it's active structure (like dwt or the
sample dwt projects).
So how about this? Is there a simple way just to start a project
based on directory alone (the IDE may create some sort of project
file in that directory if need be)? I really wish it was just that
simple considering all the projects available on dsource... very few
of them contain a ready made project file for any of the D ide's.
This seemingly minor lack has made me mostly disinterested in using
powerful ide's like eclipse/descent or poseidon. Or perhaps I just
don't know how to use them.
-JJR

At Shawn Liu's original design, poseidon was used "directory
project", while project open, it will load all source files under
project directory, it also fit D programming language packages
design, however, sometimes we have some files existed in project but
we don't want to load, compile and link, some files we don't want to
copy many times in different projects, so I change the project struct
to record source files....etc informations and add a strange tool
--"import all files" to quick load all sources under project directory.
Maybe we can make good balance between them, but we need good
suggestion about this......

Adding all files from a recursive scan of imports would be nice.
Then the user specifies just main.d, and the IDE adds all the files
imported in one way or another by main.d.
--bb

That's kind of app-specific, though. What about building libraries? What
if there's test/whatever code not currently being referenced anywhere
but still in use?

It's just another way to specify a list of files to the IDE. I'm not
saying it should be the only way to do it. But files in a library do
imports too. So you specify the files you think are in the lib, and
then have the recursive scanner round out the list with any imports you
missed. Also sometimes people make an "all.d" module for libs, too.
--bb