There's not yet, but it's going to be coming ... I haven't decided
what rules I want to use for this, because it actually is possible to
mess things up if you're not careful (as much as it's not supposed to
matter in HTML).
Also, I probably will have to add a bunch of settings for this,
because i'm sure some people like:
<table>
<wo:..>
<tr>
and other people want it where the underlying visual html structure
is preserved other the wo tag structure:
<table>
<wo:...>
<tr>
ms
On May 2, 2007, at 1:52 PM, Kieran Kelleher wrote:
> Thanks Mike. The error checking is awesome.
>
> Is there a way to Format the html with the new editor (like right-
> click->Format) with the old one? If there is, I cannot seem to find
> it.
>
> Regards, Kieran
>
> On May 2, 2007, at 12:17 PM, Mike Schrag wrote:
>
>> Responding to the list, since it's generally useful ... There is a
>> setting in WOLips=>Wod Editor preferences to turn off errors for
>> keypath validations on classes that implement NSKeyValueCoding.
>> This will get rid of those particular errors. Also, in your wod
>> file, you can add a "// VALID" to the end of a line with an error
>> and override its error message if you want. I don't know if I
>> have a setting to turn those into warnings at the moment, but I
>> can add that also. The downside of turning off NSKVC errors is
>> that a lot of classes in WO implement that interface, so you will
>> potentially lose a lot of value from validation. Maybe I should
>> add explicit support for ignoring NSDictionary and NSArray (as a
>> separate line item in prefs), since those are actually probably
>> the most common cases of these.
>>
>> ms
>>
>> On May 2, 2007, at 12:11 PM, Kieran Kelleher wrote:
>>
>>> Mike, thanks for all your effort!
>>>
>>> Some feedback. Probably a Warning instead of an Error might be
>>> better for keypath validation (if that's an easy change) since it
>>> shows errors for dictionary based keypaths.
>>>
>>>
>>> <pastedGraphic.tiff>
>>>
>>>
>>> Regards, Kieran
>>>
>>> On Apr 30, 2007, at 7:22 AM, Mike Schrag wrote:
>>>
>>>> I just committed a new html editor to wolips. It's based on the
>>>> Amateras EclipseHTMLEditor plugin, which was a pretty decent
>>>> base, easy to extend, and the code was good. To that base, I
>>>> added a bunch of wo-specific features + css completion. The
>>>> previous version of wolips has become the new "stable" build
>>>> (since this will likely have some kinks to be worked out).
>>>>
>>>> The list of new features includes:
>>>>
>>>> * html editor understands webobject tags (no more funky warnings)
>>>> * html editor understands wo:inline tags
>>>> * html editor colorizes $bindings and ~ognl bindings
>>>> * html editor validates webobject names
>>>> * html editor validates wo:classNames
>>>> * html editor validates attributes (required, etc)
>>>> * html editor validates inline $bindings
>>>> * html editor validates crappy html (this is the biggest
>>>> potential for annoyance right now, but it's really useful and
>>>> revealed a bunch of problems in my html)
>>>> * html editor completion on webobject names in <webobject> tags
>>>> * html editor completion on wo:classNames
>>>> * html editor completion on wo: binding names
>>>> * html editor completion on wo: $bindings
>>>> * html editor supports custom wo:shortcuts for completion and
>>>> validation (see WOLips prefs)
>>>> * wod editor hyperlink support on element names (cmd-click on
>>>> element names to open java file)
>>>> * wod/html editor validates binding references in "~ognl
>>>> bindings" (no completion just yet)
>>>> * extra control to turn on/off wod/html binding errors on
>>>> missing bindings on a class that implements NSKeyValueCoding
>>>> (like if you do nsarray.something, which would be valid, but the
>>>> validator could never know)
>>>>
>>>> ms
>>>>
>>>
>>>
>>
>>
>
This archive was generated by hypermail 2.0.0 : Wed May 02 2007 - 13:59:41 EDT