Hi Norman,
Please try new version with a proper symbols support.
Let me know how this works for you.
https://github.com/anjlab/eclipse-tapestry5-plugin#support-for-tapestry-symbols
On Wed, Feb 4, 2015 at 10:47 PM, Norman Franke wrote:
> Ignoring paths containing symbols works fine with me.
Hi Martin,
Try latest release (2.9.6), all three assets should be resolved now.
See notes here:
https://github.com/anjlab/eclipse-tapestry5-plugin#support-for-tapestry-symbols
On Wed, Feb 4, 2015 at 7:15 AM, Martin Papy wrote:
> Hi Dmitry,
>
> My code was slightly different, but I updated it
Ignoring paths containing symbols works fine with me. I’d otherwise not have a
problem with a project-based configuration file. Maybe it should live under
WEB-INF or even META-INF.
Norman Franke
Answering Service for Directors, Inc.
www.myasd.com
On Feb 4, 2015, at 11:46 AM, Dmitry Gusev wro
Hey Norman,
I'll come with some solution in the next release. Probably will just ignore
validation for paths containing symbols.
Regarding static analysis of tapestry's symbols - it won't be easy to do,
because the values for them calculated at runtime using method invocations
and string manipula
Speaking of which, any chance the plugin could not warn about @Import using
"${tapestry.scriptaculous}/“ paths? Or is there a better way to include things
like effects.js and builder.js?
Norman Franke
Answering Service for Directors, Inc.
www.myasd.com
On Feb 4, 2015, at 2:15 AM, Dmitry Gusev
Hi Geoff,
Yes, this is a known "bug".
I know that CMD+R (Ctrl+R) sometimes stops working in the Debug
Perspective, and keeps broken after returning from Debug to the Java
Perspective.
This happens after you set a breakpoint in the Java code and debugger hits
that.
It becomes broken because Debu
Hi Dmitry,
I find this tool utterly invaluable, even though I keep related java, tml, and
properties in the same folder. There is one problem, though - the keyboard
shortcuts get corrupted as the day goes on - probably by clashes with other
editors (javascript editor in particular? I'm not sure
Hi Martin,
I'm sorry I was unclear, the symbol expansion support is not yet in the
plugin.
I was just saying that it shouldn't be hard to add the support for simple
symbol contributions :)
I'll try to add it in the next release.
On Wed, Feb 4, 2015 at 7:15 AM, Martin Papy wrote:
> Hi Dmitry,
>
Hi Dmitry,
My code was slightly different, but I updated it to see if there was any
difference. So now I have this :
public static void
contributeApplicationDefaults(MappedConfiguration
configuration) {
configuration.add("layout.assets", "META-INF/assets");
configuration.add("
Hi Martin,
My current goal is to avoid configuration files at this stage if possible,
but try to get all the data via static code analysis.
In this sense capabilities of the plugin are somewhat limited, for example,
this may be implemented with a little effort if you define your symbols via
Symbo
That is indeed a GREAT work :) Awesome :)
If I have 1 quick idea, it would be to be able to configure a symbol list
so that we can open properly assets from the Import Annotation :). Here
bellow I would like to defined what ${layout.scripts} points to.
@Import(library={
"${layout.scripts}
Awesome work, Dmitry! It just gets better and better...
On Mon, Feb 2, 2015 at 1:51 AM, Dmitry Gusev wrote:
> Hey Tapestry Users,
>
> I haven't updated release notes for the plugin for almost a year, lots of
> minor features & improvements were released since then.
>
> Release 2.8.0 is different,
Hey Tapestry Users,
I haven't updated release notes for the plugin for almost a year, lots of
minor features & improvements were released since then.
Release 2.8.0 is different, because it introduces basic support for
Tapestry 5.4.
Some major changes:
- Tapestry Context View
- Now show
13 matches
Mail list logo
