This would be the best possible scenario I think. But just can't get it working. I am using 0.8.1 of the asdt plugin now (was hoping to get any improvements regarding this) and keep getting erros If I try any type of classpath setting like you suggest below.
Just for clarity, I go to the navigator, right click my project, and go to AS2 Classpath. In there I have tried multiple things like: ..\Flash Classpath ..\Flash Classpath\ ../Flash Classpath/ Etc. But when I try using the code assist with something eclipse should have found in the added classpath I get the error : "Content assis did not complete normally. Please see the log for more information. Reason: Path must include project and resource name: /Flash Classpath" -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Schnabel Sent: woensdag 31 augustus 2005 13:00 To: Open Source Flash Mailing List Subject: Re: [osflash] ASDT Code hinting..... Again *sigh* there is an other solution: add an eclipse project with your libraries and add it to the classpath (../libs/src) if the project is open you should have code hinting. best regards Martin Schnabel Scott Whittaker wrote: >Hi Ben, > >I am using VSS and the same method of linking my class libraries at >work and don't have my linked folders added to VSS (although I can add >them if I wish). When I link a project to VSS no files or folders are >actually added to the archive until I right-click on a file or folder >within the project and choose to add it to the archive (which works >recursively for sub-folders). Then I can check those items in and out >using the right-click menu on the project folder. > >Because I don't set the linked class libraries explicitly to be >included in the archive, they are not checked in and out with the rest >of the project. But I can add them if I want to, using the same method. > >How are you adding your projects to VSS? Do you have an older version >of the plugin? > >Regards, > >Scott > >On 8/8/05, Ben Smeets <[EMAIL PROTECTED]> wrote: > > >>Hi all, >> >>This question has been handled multiple times as I could see in the >>archives. But still I can't find the correct solution for it. >> >>I am usin geclipse + asdt which works like a charm. Except for one >>annoying thing. The code hinting.... >> >> >>I have a setup (workbench) similar to this: >> >>- project A >> - Assets >> - Classes >> - nl >> - com >> - org >> - etc... >> >>- classpath >> - nl >> - com >> - org >> - etc... >> >>You can probably guess the problem.. I want to be able to use code >>hinting of 'classpath' classes, while editing classes in project A. >> >>I already found the solution of adding a new linked directory. And >>after doing that the code hinting *does* work. Buttttt.... >> >>I also use the Visual Sourcesafe plugin. And that plugin will submit >>the linked directory to the sourcesafe database also. So whenever I >>link the classpath directory, I have a duplicate in my sourcesafe. Not >>an ideal situation. >> >>So the question is two sided. >> >>1. Is it possible to enable this type of code hinting without using >>the linked directory? >>2. Is it possible to link a directory without adding it to the actual >>project (and thereby preventing it to be added to the sourcesafe >>directory? >> >>Any other tips or tricks are more then welcome too :) >> >>Tx in advance, >> >>Ben >> >> _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
