On Sunday 07 January 2007 14:59, Christopher Williams wrote: > David, > Well I'm not sure specifically what you'd like to know, so here's a > little primer... > > SourceFolderRoot and SourceFolder map one-to-one to JDT's > PackageFragmentRoot and PackageFragment (though our name gives a better > idea of what they are). SourceFolderRoot is exactly that: the folder in the > project whose contents hold ruby scripts. By default this is the project's > folder, and this element is tied very closely to loadpaths. It's where RDT > should begin traversing the filesystem looking for scripts. Every child > folder is a SourceFolder element. Our restrictions on namespacing in Ruby > are much different from java's so there shouldn't be any enforcement about > type names and their position in the folder hierarchy. > An external library could be represented as a SourceFolderRoot linked to an > external folder structure (outside the actual project), and this should be > how we'd implement linking back to Ruby core/std libraries.(The JDT has > JarPackageFragmentRoots, we'd just have ExternalSourceFolderRoots). >
Well, the real question then, is can I change it so that the root of the project is NOT the a SourceFolder, but another folder is? That's something RDT has 'needed' for a long time... ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
