www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.learn - Descent project file organization

reply "Bill Baxter" <wbaxter gmail.com> writes:
I think I figured out the answer to my last question about installing Descent.
It seems I can just copy the plugins and features directories from the
Descent .zip over top the ones in in the Eclipse folder.

The next question is about file organization.

I'm thinking it might be nice to Descent as an alternate way to edit
and look at my D source code.
But I don't want descent to "own" the files.
So basically I would just like to tell Descent which files are part of
the project, but leave the files where they are.
The first thing I tried for adding a file to a project made a separate
copy of the file in my Workspace directory.  Not what I want.
The second thing I tried was the "Link source" option under the Build
Path menu.  But that added *everything* in the directory into the
project, not just the relevant D stuff.  Plus the same dir contains 3
different files with a 'main'.

Is there some way to just add a soft reference to specific files to a project?

With Visual Studio I just say "add existing file" and it puts a link
to that source file into the project.  It doesn't move or copy
anything, it just makes a link to that one specific file.  That's the
kind of behavior I'm after.

--bb
Nov 20 2008
next sibling parent reply Ary Borenszweig <ary esperanto.org.ar> writes:
If you don't want to move your files and keep them where they are, 
create a new D project and in the first page of the wizard select "from 
existing source" and type or select the folder where your files are. 
That will two files in that directory: .project and .classpath. But 
that's it. I hope those don't bother you. :-)

The "Link source" option efectively links everything under the selected 
folder, you can't just link a particular file, sorry.

Bill Baxter escribió:
 I think I figured out the answer to my last question about installing Descent.
 It seems I can just copy the plugins and features directories from the
 Descent .zip over top the ones in in the Eclipse folder.
 
 The next question is about file organization.
 
 I'm thinking it might be nice to Descent as an alternate way to edit
 and look at my D source code.
 But I don't want descent to "own" the files.
 So basically I would just like to tell Descent which files are part of
 the project, but leave the files where they are.
 The first thing I tried for adding a file to a project made a separate
 copy of the file in my Workspace directory.  Not what I want.
 The second thing I tried was the "Link source" option under the Build
 Path menu.  But that added *everything* in the directory into the
 project, not just the relevant D stuff.  Plus the same dir contains 3
 different files with a 'main'.
 
 Is there some way to just add a soft reference to specific files to a project?
 
 With Visual Studio I just say "add existing file" and it puts a link
 to that source file into the project.  It doesn't move or copy
 anything, it just makes a link to that one specific file.  That's the
 kind of behavior I'm after.
 
 --bb

Nov 20 2008
next sibling parent Ary Borenszweig <ary esperanto.org.ar> writes:
Ary Borenszweig escribió:
 If you don't want to move your files and keep them where they are, 
 create a new D project and in the first page of the wizard select "from 
 existing source" and type or select the folder where your files are. 
 That will 

~ add ~ two files in that directory: .project and .classpath. But
 that's it. I hope those don't bother you. :-)
 
 The "Link source" option efectively links everything under the selected 
 folder, you can't just link a particular file, sorry.
 
 Bill Baxter escribió:
 I think I figured out the answer to my last question about installing 
 Descent.
 It seems I can just copy the plugins and features directories from the
 Descent .zip over top the ones in in the Eclipse folder.

 The next question is about file organization.

 I'm thinking it might be nice to Descent as an alternate way to edit
 and look at my D source code.
 But I don't want descent to "own" the files.
 So basically I would just like to tell Descent which files are part of
 the project, but leave the files where they are.
 The first thing I tried for adding a file to a project made a separate
 copy of the file in my Workspace directory.  Not what I want.
 The second thing I tried was the "Link source" option under the Build
 Path menu.  But that added *everything* in the directory into the
 project, not just the relevant D stuff.  Plus the same dir contains 3
 different files with a 'main'.

 Is there some way to just add a soft reference to specific files to a 
 project?

 With Visual Studio I just say "add existing file" and it puts a link
 to that source file into the project.  It doesn't move or copy
 anything, it just makes a link to that one specific file.  That's the
 kind of behavior I'm after.

 --bb


Nov 20 2008
prev sibling parent Ary Borenszweig <ary esperanto.org.ar> writes:
Bill Baxter escribió:
 On Fri, Nov 21, 2008 at 10:59 AM, Ary Borenszweig <ary esperanto.org.ar> wrote:
 If you don't want to move your files and keep them where they are, create a
 new D project and in the first page of the wizard select "from existing
 source" and type or select the folder where your files are. That will two
 files in that directory: .project and .classpath. But that's it. I hope
 those don't bother you. :-)

 The "Link source" option efectively links everything under the selected
 folder, you can't just link a particular file, sorry.

Ok. Yeh that seems to be the same as what I got from using the Build Path --> Link Source option after the fact. It does at least collect all the .d files in one place at least. But it's annoying that it puts all the junk files (the .exe, .map files etc) at the top level. At least if the linked files were in a sub-folder of their own in the IDE I could collaspe that and not have to look at them. Thanks for the response. --bb

In the Project Explorer view there's a little white arrow at the top-right corner. Click it and select "Filters...". There, check "Dll files", "Map files" and "Obj files". In that way (probably) only the exe files will stay visibles, and I think that's the important stuff: d files for editing, exe files for launching. If there are other file extensions which are very common and you wouldn't like to see them, let me know so I add filters for them. (I think you can't write customizable filters in Eclipse...)
Nov 21 2008
prev sibling parent "Bill Baxter" <wbaxter gmail.com> writes:
On Fri, Nov 21, 2008 at 10:59 AM, Ary Borenszweig <ary esperanto.org.ar> wrote:
 If you don't want to move your files and keep them where they are, create a
 new D project and in the first page of the wizard select "from existing
 source" and type or select the folder where your files are. That will two
 files in that directory: .project and .classpath. But that's it. I hope
 those don't bother you. :-)

 The "Link source" option efectively links everything under the selected
 folder, you can't just link a particular file, sorry.

Ok. Yeh that seems to be the same as what I got from using the Build Path --> Link Source option after the fact. It does at least collect all the .d files in one place at least. But it's annoying that it puts all the junk files (the .exe, .map files etc) at the top level. At least if the linked files were in a sub-folder of their own in the IDE I could collaspe that and not have to look at them. Thanks for the response. --bb
Nov 20 2008