Ideas

[dmitrygusev]

Validation:

• markers when some @imports are missing
• markers when some properties are not localized (present in one file, but not in the others)

Tapestry Context:

• Try determining tapestry context from referenced @imports: JS/CSS files
• Support assets referenced by @Inject @Path("asset.js") private Asset js;
• Show context for service intf/impl, i.e. it's contributions, advisors, decorators

Creating files:

• Customizable templates
• Eclipse 'Quick fix' to create missing @imports
• Create complement file if absent or create new JS/CSS file for context
  Some naming convention may be required here, i.e.:
  • files should be in the same package and have the same name as the Java file
  • or be in lower case with dashes instead of Pascal-casing
• Support Tapestry 5.4 locations for assets
• 'Find references' in project for JS/CSS files
• Rename refactoring for Java/tml

[trsvax]

This plugin is great but might be even better if create feature was source folder aware. For example if I want to create a tml file for a Java class in src/test/java it should default to creating the tml file in src/test/resources.

Thanks

[dmitrygusev]

@trsvax please try version 2.13.4

[vjlamp]

Love the plugin, Dmitry, thank you. Here is another idea. In the tml editor, use the font style configured for comments also for the <t:remove> component and its body. Or use a different, unobstrusive font style. What do you say?