[Tony Herstell]

With MyElipse 4.1 and tapestry..

I get various errors when geting my code formatted for me using the Cleanup Document or Format tools:

1. in a <SPAN> tag (heavilly used for adding in tapestry contols) I OFTEN get a “)” added…
e.g. <SPAN jwcid=”@Conditional” condition=”ognl:organisationSimpleTreeModel != null”)>
[Note the odd “)” bracket added by the formatter]

2. The SPANs do confuse the formatter and marks various errors where it expects tags that are not there…

3. Consecutive <SPAN> are put on one line which makes it unreadable.

Note: 2. may be related to 1.
Note: Adding in the <SPAN> tags where I need to may even break the HTML rules.
Note: The Spindle plugin may be involved somewhere along the line.

I can send a typical html page is required.

[Riyad Kalla]

Please send us an example page that exhibits the problem to support@genuitec.com ATTN Riyad with a link to this post, I’ll verify it and file it ASAP.

[Tony Herstell]

This is why I pay for this product.
Great service guys.
Email on the way.

[Riyad Kalla]

Got it and replied (wasn’t able to reproduce it).

[glongman]

@balanceofpower wrote:

With MyElipse 4.1 and tapestry..

I get various errors when geting my code formatted for me using the Cleanup Document or Format tools:

1. in a <SPAN> tag (heavilly used for adding in tapestry contols) I OFTEN get a “)” added…
e.g. <SPAN jwcid=”@Conditional” condition=”ognl:organisationSimpleTreeModel != null”)>
[Note the odd “)” bracket added by the formatter]

2. The SPANs do confuse the formatter and marks various errors where it expects tags that are not there…

3. Consecutive <SPAN> are put on one line which makes it unreadable.

Note: 2. may be related to 1.
Note: Adding in the <SPAN> tags where I need to may even break the HTML rules.
Note: The Spindle plugin may be involved somewhere along the line.

I can send a typical html page is required.

Sounds like a cleanup/formt tool outside of Spindle. The Spindle formatter is not capable of ‘adding’ anything to the file.

Geoff

[Tony Herstell]

I seem to have lost the other problems since I rebooted (user error possibly)…

This error still perisists however.

3. Consecutive <SPAN> are put on one line which makes it unreadable.

Are you sure you cannot reproduce this?

[Riyad Kalla]

balanceofpower,
The spans on multiple lines is intentional, I can reproduce that, but not the mangling of the code.

The formatter is fairly simply right now, it tries to put each open tag on it’s own line. We have enhancement requests already to allow adjustment of these settings but at this time there isn’t any adjustments available.

[hdupre]

@support-rkalla wrote:

balanceofpower,
The spans on multiple lines is intentional, I can reproduce that, but not the mangling of the code.

The formatter is fairly simply right now, it tries to put each open tag on it’s own line. We have enhancement requests already to allow adjustment of these settings but at this time there isn’t any adjustments available.

Another issue with the formatter is that tapestry requires its tags to be closed…
for instance
<input jwcid=”@TextField” type=”text” name=”subject” size=”45″ maxlength=”60″ value=”” />

the formatter replaces the /> at the end with > so after formatting, the tag becomes invalid for tapestry.

Any chance to fix that?

Henri.

[Riyad Kalla]

Henri,
Can you post a small example file so I can test it with our internal dev build to make sure it isn’t doing this? It should NOT do that, the formatter should just format. If you are using the “Cleanup Document”, that might explain why it’s actually changing content.

[Author]

Posts