Community
Participate
Working Groups
It isn't possible to specify a source folder/location in the Package Wizard, which leads to a problem specifically when no source folder is selected prior to opening the wizard: "Source folder name is empty". The user has no option to select a source folder, so they must exit the wizard, click on a location and open it again.
This is a result of our reuse of the package wizard from JDT. I've been thinking a lot (probably too much) about this and am of the mind that the package wizard isn't all that necessary. We can specify a new package in the class wizard. Isn't that enough. In fact, I can't remember the last time I used the JDT package wizard...
Hmm I see. That may be true, but from the point of view of someone learning to program in Java, I'm not sure that the logical sequence of steps would be the same. If I were just being introduced to packages and how they relate to the rest of the project hierarchically, I would be inclined to make my project, put my package inside it, and then put a class in the package. It wouldn't make as much sense to use the Java Class Wizard to make a new package at the same time. On top of that, it isn't immediately obvious that in the Class Wizard, typing in your own package name will create a new package. The dropdown menu format implies that you must select an already existing one from the list. Perhaps it wouldn't take much to discover that you can type in the package field, but I don't think we should rely on the user knowing to do this, particularly when they are new to using Eclipse and programming in Java.
So what's the solution? Should we put some hover help on the CCombobox?
I'm still of the mind that if we're going to allow new packages to be created, we should keep the package wizard. If we put a tooltip on the CCombobox, I would like to see it done in addition to keeping the package wizard. If they're making a class, they can find out there's a faster way to make a package. But until then, the ability to make a package should be made clear right from the start, next to the New Project and New Class options. That's just my opinion anyway. Does anyone else have thoughts?
I agree with you Brenda. I think it should be dead obvious, so next to the New Project and New Class options is a good idea.
If we're going to keep the new package wizard, then it's going to have to be rebuilt along the same lines as what we did with the new class and new project wizards. I believe that this problem is caused by hacking the JDT wizard.
I believe this bug can be closed because Bug 306651 deals with the issue of a package constructor, which in turn fixes the problem stated in this bug.
