I just updated to 3.5. It's very fast. I like it a lot (^_^)
However, I'm getting *lots* of red Xs in ERExtensions and
ERDirectToWeb regarding unclosed <br> <hr> ... that sort of thing.
Now, for my stuff, I like that... but for the wonder frameworks,
some of those things are correct because they are still using HTML
doctype so it would be invalid to change them to <br/> etc. Is
there any way to quiet down eclipse with regard to these on a per
project/framework basis so I can keep them for my stuff, but disable
them for ERD2W and ERExt?
Look in your WOLips Development Preferences for your project and see
if "Require Well-formed Templates" is checked .. Uncheck it and clean
build if it is.
Also... I have been cheating with a //VALID notation that no longer
works. I have
CheckboxWrapper: WOGenericContainer {
// ** Because there's no elementName, this is an invisible
wrapper element.
elementID = wrapperElementID;
name = context.elementID;
formValues = selections;
}
Of course, this works fine, but it gives me a red X. The trick that
worked before was...
CheckboxWrapper //VALID
: WOGenericContainer {
That was a bit of overkill because it disabled validation on the
whole WOD, but it did work. Now, that's not working... sooooo, any
hints on how to make my red Xs go away?
i'm amazed that worked before :) i didn't intentionally disable this,
but then i never really intentionally ENABLED it. Valid should
definitely not have disabled for the entire WOD -- are you sure it did
that? what red 'x' are you getting btw? that elementName is a required
binding? if it isn't, then we should remove it from the API
validation rules for WOGenericContainer.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
