Re: Updated to 3.5 and now lots of html errors
On Sep 23, 2009, at 11:45 PM, Ramsey Lee Gurley wrote:
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... so,
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
Oh yes, I remember quite distinctly that it would nuke the
validation for the whole WOD (^_^) But that was ok, because I got
everything else right and never touched it again after I put the //
VALID on it.
And yeah, the red X is regarding the missing elementName binding. I
was surprised, but WOGenericContainer works without it. And in this
case, it is the only way I can produce valid XHTML with this
component. Those bindings are copied from Apple sample code,
comment and all, located at
/Developer/Examples/JavaWebObjects/Frameworks/WOComponentElements/wo-
resources/Resources/WXCheckBoxList.wo/WXCheckBoxList.wod
Ramsey
BTW, I looked for a WOGenericContainer.api in ERExtensions. Nothing
there, so I guess that's Apple binding validation? I can see why 99%
of the time, I would want that validation. Perhaps there is some
other way to mark this one instance //VALID?
Ramsey
smime.p7s
Description: S/MIME cryptographic signature
___
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
Re: Updated to 3.5 and now lots of html errors
i'm surprised you can't do CheckboxWrapper : WOGenericContainer { //
VALID
On Sep 24, 2009, at 7:48 AM, Ramsey Lee Gurley wrote:
On Sep 23, 2009, at 11:45 PM, Ramsey Lee Gurley wrote:
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... so,
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
Oh yes, I remember quite distinctly that it would nuke the
validation for the whole WOD (^_^) But that was ok, because I got
everything else right and never touched it again after I put the //
VALID on it.
And yeah, the red X is regarding the missing elementName binding.
I was surprised, but WOGenericContainer works without it. And in
this case, it is the only way I can produce valid XHTML with this
component. Those bindings are copied from Apple sample code,
comment and all, located at
/Developer/Examples/JavaWebObjects/Frameworks/WOComponentElements/
wo-resources/Resources/WXCheckBoxList.wo/WXCheckBoxList.wod
Ramsey
BTW, I looked for a WOGenericContainer.api in ERExtensions. Nothing
there, so I guess that's Apple binding validation? I can see why
99% of the time, I would want that validation. Perhaps there is
some other way to mark this one instance //VALID?
Ramsey
___
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
Re: Updated to 3.5 and now lots of html errors
I've tried in all of the following places (one at a time) with no luck,
//VALID
CheckboxWrapper //VALID
: //VALID
WOGenericContainer //VALID
{ //VALID
// ** Because there's no elementName, this is an invisible
wrapper element.
elementID = wrapperElementID;
name = context.elementID;
formValues = selections;
//VALID
} //VALID
I've also just discovered that bindings like
HTML: WOGenericContainer {
elementName = html;
xml:lang = languageCode;
xmlns = http://www.w3.org/1999/xhtml;;
}
No longer work in 3.5. They still parse fine in the WOD, but they're
throwing exceptions in the app. Fortunately, reverting back to this
still works for me
HTML: WOGenericContainer {
elementName = html;
xml:lang = languageCode;
xmlns = http://www.w3.org/1999/xhtml;;
}
On Sep 24, 2009, at 8:01 AM, Mike Schrag wrote:
i'm surprised you can't do CheckboxWrapper : WOGenericContainer { //
VALID
On Sep 24, 2009, at 7:48 AM, Ramsey Lee Gurley wrote:
On Sep 23, 2009, at 11:45 PM, Ramsey Lee Gurley wrote:
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... so,
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
Oh yes, I remember quite distinctly that it would nuke the
validation for the whole WOD (^_^) But that was ok, because I got
everything else right and never touched it again after I put the //
VALID on it.
And yeah, the red X is regarding the missing elementName binding.
I was surprised, but WOGenericContainer works without it. And in
this case, it is the only way I can produce valid XHTML with this
component. Those bindings are copied from Apple sample code,
comment and all, located at
/Developer/Examples/JavaWebObjects/Frameworks/WOComponentElements/
wo-resources/Resources/WXCheckBoxList.wo/WXCheckBoxList.wod
Ramsey
BTW, I looked for a WOGenericContainer.api in ERExtensions.
Nothing there, so I guess that's Apple binding validation? I can
see why 99% of the time, I would want that validation. Perhaps
there is some other way to mark this one instance //VALID?
Ramsey
___
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/rgurley
%40mac.com
This email sent to rgur...@mac.com
smime.p7s
Description: S/MIME cryptographic signature
___
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
Re: Updated to 3.5 and now lots of html errors
No longer work in 3.5. They still parse fine in the WOD, but
they're throwing exceptions in the app. Fortunately, reverting back
to this still works for me
HTML: WOGenericContainer {
elementName = html;
xml:lang = languageCode;
xmlns = http://www.w3.org/1999/xhtml;;
}
not sure how WOLips/Eclipse would impact this at all ... certainly
validating, yes, but runtime-wise, we don't have anything to do with
it. That syntax is sort of weird, though -- you're competing with
binding namespaces using real xml namespaces. It's expecting a
loc:name=locKey.
file jiras, if you would
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
Re: Updated to 3.5 and now lots of html errors
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... so, 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
Re: Updated to 3.5 and now lots of html errors
On Sep 23, 2009, at 11:16 PM, Mike Schrag wrote:
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.
Ok, that appears to be doing the trick. I knew it had to be in there
somewhere (^_^)
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... so, 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
Oh yes, I remember quite distinctly that it would nuke the validation
for the whole WOD (^_^) But that was ok, because I got everything
else right and never touched it again after I put the //VALID on it.
And yeah, the red X is regarding the missing elementName binding. I
was surprised, but WOGenericContainer works without it. And in this
case, it is the only way I can produce valid XHTML with this
component. Those bindings are copied from Apple sample code, comment
and all, located at
/Developer/Examples/JavaWebObjects/Frameworks/WOComponentElements/wo-
resources/Resources/WXCheckBoxList.wo/WXCheckBoxList.wod
Ramsey
smime.p7s
Description: S/MIME cryptographic signature
___
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
