Bug 82988 [Import/Export] Importing Existing Projects should support Archive Files
Importing from Archive File and from File System should include options for importing as projects (similar to CVS). I've constructed a patch to do so, I've completed the najor functionality for Archive File (File System isn't done yet but should be very easy since it should be almost identical) but I'm running into some difficulties regarding the UI, as you can see the radio button for selecting an existing folder is not next to the text field and button which specify the folder, this is because these components are in WizardResourceImportPage which I can't really alter. The only options I can think of are to make them protected instead of private (did that a few times already) and start pulling out some components so I can stuff my radio button in there too. I'll attach the patch I have so far, ignore the "File System" section as that's going to be redone when I figgure out the solution, "Archive File" is the part I've been working on. I'm looking for opinions anyone may have on the current functionality and how to fix this UI issue. thanks
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/wizards/datatransfer/ImportOperation.java
* Creates a new operation that imports specific file system objects.
     * In this usage context, the specified source file system object is used by the
     * operation solely to determine the destination container structure of the file system
     * objects being imported.
     * <p>
     * The <code>source</code> parameter represents the root file system object to 
     * import. Valid types for this parameter are determined by the supplied 
     * <code>IImportStructureProvider</code>. The contents of the source which
     * are to be imported are specified in the <code>filesToImport</code>
     * parameter.
     * </p>
     * <p>
     * The <code>provider</code> parameter allows this operation to deal with the
     * source object in an abstract way. This operation calls methods on the provider
     * and the provider in turn calls specific methods on the source object.
     * </p>
     * <p>
     * The <code>filesToImport</code> parameter specifies what contents of the root
     * file system object are to be imported.
     * </p>
     * <p>
     * The default import behavior is to recreate the complete container structure
     * for the file system objects in their destination. If <code>setCreateContainerStructure</code>
     * is set to <code>false</code>, then the container structure created for each of 
     * the file system objects is relative to the supplied root file system object.
     * </p>
     *
     * @param containerPath the full path of the destination container within the
     *   workspace
     * @param source the root file system object to import from