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.
| Summary: | New File Type Wizard Tutorial | ||
|---|---|---|---|
| Product: | usersguide | Reporter: | puce <puce> |
| Component: | Code | Assignee: | Geertjan Wielenga <geertjan> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | CC: | tomwheeler |
| Priority: | P3 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
|
Description
puce
2008-10-25 12:25:18 UTC
This tutorial describes how to create new files programmatically: http://platform.netbeans.org/tutorials/nbm-filetemplates.html Note that you don't need the wizard classes for this. However, the module attached to the above includes some samples that show how to do so anyway. This module also provides a sample that generates code from a file template, again without needing you to use the wizard classes: http://plugins.netbeans.org/PluginPortal/faces/PluginDetailPage.jsp?pluginid=14239 I know that you can use templates and don't need always to have a wizard to create new files, but I actually meant, that it would be great to have a tutorial for the cases when you need such a wizard to create your files. Sorry, if I didn't write it clearly. I hope that I didn't miss something in your posted links and that it is ok to reopen this issue. reassigning for Geertjan to evaluate If I turn this 5-part series into an official tutorial, would that be a full response to this issue?: http://blogs.sun.com/geertjan/entry/how_wizards_work Yes, I think that would be great. Especially if you could add the parts of your blog, which show - how to finish the wizard, when it is not called by a custom action (override instantiate()?) - how to use custom templates from within a wizard - using APIs to get a package chooser etc. I read through the tutorial briefly now and it seemed very nice. I plan to read it more thoroughly in the next few days. I did notice something unusual at the bottom -- not sure if it's intentional or not, so I figured I'd point it out. Usually "branding" implies customization while "internationalized" or "localization" implies translation into another language, although I understand they use the same underlying mechanism in NetBeans. Towards the bottom of the page there's a section called "Branding the Wizard" but it's actually translating the button labels to Dutch. I'd have expected to see a minor modification within the same language in a section called "Branding the Wizard"; for example, changing the "Next" button label to "Advance" or "Ahead" or something. Thanks. Fixed that problem in the tutorial. Feel free to add more comments about it. Every time I give a training I'm surprised at how widely used the Wizard APIs are & how broadly interested people are in them. This tutorial is therefore of central importance to the NetBeans Platform, more so than 95% of the others, even. |