Re: Re: Template Manager

Thanks J, I can see how the dynamic component can become more confusing, the
one implemented within eclipse although adequately provides this support is
quite hard to use. I could be thinking of the code format support in
eclipse, i haven't used it in a long time.

Could we vote on this please
http://www.netbeans.org/issues/show_bug.cgi?id=103851

-Brett

On 5/11/07, Jesse Glick <[email protected]> wrote:
>
> Brett Ryan wrote:
> > include an inline editor to allow the user to simply
> > edit/save/revert-default a template.
>
> I think it's a good idea. I'm not positive offhand, but I think it would
> be straightforward to embed an editor like you describe. File an RFE
> against core/favorites please.
>
> > When creating templates I find that a lot of the components that
> > build up templates are replicated, for example a java exception
> > template should inherit the template from a java class; only adding
> > to the body of the class.
>
> This is certainly possible. I would be concerned however that making
> common templates too "smart" would be more confusing than helpful to
> people trying to edit them. It's easier to paste the same couple of
> lines of boilerplate into a handful of separate templates than to figure
> out a new templating macro language.
>
> > I'm seeing what looks to be great support in 6.0 M9 for more flexible
> > templates and am hoping templates might become a little more dynamic.
>
> Yes, new versions of NB use Freemarker.
>
> > Once I install a new version one of the first things I do is go
> > through all the templates and alter them, adding a __LICENCE__ tag at
> > the top of each file and a string table entry to match it.
>
> This should no longer be necessary with the new system.
>
> -J.
>
> --
> [email protected]  netbeans.org   ant.apache.org  hudson.dev.java.net
>             http://google.com/search?q=e%5E%28pi*i%29%2B1
>