This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Simple project is defined by the projects infrastructure. It provides similar functionality as 3.4 project (it is a collection of files with some project-wide settings). Simple project helps users in transition of their existing netbeans projects into 4.0, espacially with those projects that cannot be transformed into any known project type. Simple project can also be used by modules that do not have time or resources to implement a better projects support or for the modules which are satisfied with the Simple project's functionality. Simple project has the physical view just like other project types. In the logical view it has a component which behaves as a generic sources component. The user can add/remove folders and files and work with files. The user can create any types of Data Objects in folders in the Simple project similarly as in the filesystems tab. Simple project will only have settings at the level of the whole project, no settings groups. The concrete UI and actions have to be determined. Questions: - should we support settings for individual data objects in Simple project?
Dirk, I know that the uispec doesn't say that we should have Simple Project, but I would like to ask once again for your opinion. I think it might be useful to have it and actually it would be realy easy to implement (just to create the template for it). It would have just the codegeneric nature, that means no resources, no build targets, adding/removing files/folder in Sources Node. Only basic file templates and templates for generic build targets like for Ant, etc. What do you think? Please, either, close this task or reassign it back to projects/code if you think we should implement it. Thanks.
Vito, Well, the problem I've always had with the "simple project" is that I've never seen a clear, compelling use case for it. But let's dig in a bit and see. First off, from your description it sounds like the only files creatable in a simple project would be: Html Web Bookmark Text File XML XML Document DTD Entity XML Schema XSL Stylesheet Oasis XML Catalog XML Parsed Entity Cascading Style Sheet Correct? So far, this doesn't seem hugely useful. Would anyone really want to use NetBeans to create a website, or a bunch of XML files? The one way in which (I think) this kind of project might be useful would be as some sort of dummy project that integrated together the outputs of other projects. For example, you might have a couple of EXEs and some DLLs, all enclosed in their separate projects. You could trigger a build of the whole set by creating a dummy simple project. The simple project would list each of the separate projects' outputs as a resource, and then would have some sort of Ant build target to collect them up and dump them out onto the disk. (But note one minor problem here -- you said that the simple project wouldn't have resources or build targets.) We'd probably want to call this simple project something else, e.g., "Deployment Project" or something. In any event, this is just a guess at how a simple project might be useful. But please tell me what else you were envisioning for it. Oh yes, I was confused about one other part of your message. How would a template for a generic build target like Ant be used if a simple project doesn't have build targets? Thanks, Dirk
Well, I can't see any other 'features' or use-cases of simple project besides those you've already mentioned. As I said, technically the implementation of simple project should be easy and we can quickly add it later in the release cycle if some good reason for doing that will occure. I agree that if we don't have cleare idea about the use-cases the simple project should solve it's better to leave it out (this is our favorite approach when designing API). So, let's wait for users preferences.
Sounds good!
closing