anthem-dot-net-users Mailing List for Anthem.NET (Page 4)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

=20
> Did I object quickly and loudly enough?

You have a valid point about potential conflicts with other AJAX =
libraries.
I was thinking AJAX would probably have meaning for more people viewing =
the
source of the page than Anthem, but Anthem is clear enough. It has the
advantage of avoiding potential conflicts and also crediting Jason's =
work.

Manu expressed a preference for Anthem and your earlier example also =
used
anthem, so I count that as an overwhelming majority (2 for anthem vs 0 =
for
anything else).

Anthem_ is what I provided in my code sample to Manu earlier this =
afternoon,
so hopefully it will get into the CVS controlled source and the snapshot
very soon.

Brian Lowe, AJP Interactive
br...@aj...
=20

-----Original Message-----
From: ant...@li...
[mailto:ant...@li...] On Behalf Of =
John
Murphy
Sent: 21 March 2006 17:37
Cc: ant...@li...
Subject: RE: [Anthem.NET-users] Anthem generated code and HTML Tidy

I think it should be Anthem_.  Anyone who uses multiple ajax libraries =
may
run into a collision with AJAX_*.  I don't think anyone will be confused =
by
the Anthem_* markup if they are already including anthem.dll and =
creating
pages with anthem: tags.

Did I object quickly and loudly enough?

-----Original Message-----
From: ant...@li...
[mailto:ant...@li...] On Behalf Of =
Brian
@ AJP
Sent: Tuesday, March 21, 2006 6:53 AM
To: 'Manu Temmerman-Uyttenbroeck'
Cc: ant...@li...
Subject: RE: [Anthem.NET-users] Anthem generated code and HTML Tidy

I began to mind when I'd spent many weeks in discussion and testing with =
my
Indian subcontractors to get a large web application to pass the W3C
validators so that that site could carry the "XHTML" and "CSS" and =
"WAI-AAA"
badges, only to find that as soon as I added Anthem controls to a simple
page I lost all my validation ticks.
=20
I found the solution and made the suggestion but when it was pointed out
that the integral ASP.Net hidden fields all use the same invalid =
identifiers
I decided to drop my campaign. I don't know why the W3C validators and =
Tidy
let the Microsoft "__*" identifiers through and object to others, but =
that's
another issue.
=20
Now on revisiting it, and having seen some press about Microsoft's =
stated
intention to make IE7 standards compliant, I'm thinking that they could
easily issue a patch to the framework to replace all their double
underscores and generate valid IDs for the __EVENTTARGET and =
__EVENTARGUMENT
and __VIEWSTATE hidden fields. If they do that, and Anthem continues to =
use
the invalid double underscores, then Anthem could get the blame for lots =
of
invalid HTML.
=20
I'll pick up the latest snapshot today, and locate the required changes =
and
email you the relevant lines to change, if you don't mind. I tried CVS =
and
couldn't get my head around it :-/
=20
Per my original suggestion, I propose replacing the invalid "__*" with a
valid "AJAX_*"
=20
That would clearly identify to any human reader trying to step through =
or
debug the code that this element is peculiar to an AJAX addition to the
page.
=20
I'm equally happy to make it Anthem_ to give Jason some recognition for =
his
fantastic development, but I wondered if that would be as clear to =
anyone
coming later to review the generated code. Would they necessarily know =
that
Anthem was an implementation of AJAX?
=20
I'm a firm believer also in Alzheimer's law of programming: "After 3 =
weeks
you forget why you used that identifier or construct, so your names and
comments need to be very, very clear."
=20
So, unless anyone objects loudly (and quickly), I'm going to recommend
changing the invalid "__" to a valid "AJAX_".
=20
Code will follow.
=20
=20
Brian Lowe, AJP Interactive
w: www.ajpi.co.uk <http://www.ajpi.co.uk/>  e: br...@aj... f: 07075
167630

=20

  _____ =20

	From: ant...@li...
[mailto:ant...@li...] On Behalf Of =
Manu
Temmerman-Uyttenbroeck
	Sent: 21 March 2006 09:24
	To: br...@aj...
	Cc: Roberto; ant...@li...
	Subject: Re: [Anthem.NET-users] Anthem generated code and HTML Tidy
=09
=09
	I personally don't really mind this invalid html. But if you really
do mind, I don't mind changing it :)
	Could you therefore maybe submit a patch on sourceforge? It will
save me time to do it.
	Or send me a mail with what I have to change where. Pls download
first the latest snapshot so we are using the same code...
	=20
	Could you do this for me?
	=20
	Manu.
=09
	=20
	On 3/21/06, Manu Temmerman-Uyttenbroeck
<man...@gm...> wrote:=20

		Ok Brian. If I'll find the change I'll check in the change
tonight. I hope it won't break any code though...=20
		Hmm on second thought... I won't check it in. Could you
maybe make some testing for this? If you can assure me that it won't =
break
anything, then I'll check it in.
	=09
		=20
		Manu.
	=09
		=20
	=09
		On 3/21/06, Brian @ AJP <br...@aj...> wrote:=20

			If you follow the W3C recommendation for HTML and
XHTML you will find that an identifier must begin with a letter, not a
number or underscore, so the ASP.Net 'standard' hidden fields do use =
invalid
HTML, and so you can expect all ASP.Net pages to fail this validation =
test.
(I don't know why Tidy doesn't highlight "__EVENTTARGET" and
"__EVENTARGUMENT" - maybe there's a switch in it that turns a blind eye =
to
it because it knows it's Microsoft.)=20
			=20
			I suggested a fix for the anthem-generated element
IDs by simply changing a couple of lines of code in manager.cs, but =
didn't
press it because fixing it seemed pointless in light of the major =
Microsoft
invalidations.=20
			=20
			Now I'm thinking it should be fixed while we know
about it and how to fix it. The alternative is to carry on with known
invalid generated IDs. If Microsoft (newly committed to 'compatibility' =
and
'standards') issues a patch to the ASP.Net framework that fixes their
invalid IDs, then Anthem would be left out in the cold and would be to =
blame
for invalidating otherwise valid mark-up.
			=20
			What does the team think?=20
			=20
			=20
			=20
			Brian Lowe, AJP Interactive
			w: www.ajpi.co.uk <http://www.ajpi.co.uk/>  e:
br...@aj... f: 07075 167630

			=20

  _____ =20

				From:
ant...@li...
[mailto:ant...@li...] On Behalf Of =
Manu
Temmerman-Uyttenbroeck
				Sent: 21 March 2006 06:32
				To: Roberto
				Cc:
ant...@li...
				Subject: Re: [Anthem.NET-users] Anthem
generated code and HTML Tidy
			=09
				=20

		=09
			Brian Lowe asked the same question 11th of February.
This was my answer then:
			=20
			Your pages are invalid because of id attributes that
start with "__",
			correct?
			If so, then I'm a little bit confused. In the url
you pasted is that the
			name and id attributes can only start with letters.
Every generated aspx=20
			page contains following html elements:
		=09
			<input type=3D"hidden" name=3D"__EVENTTARGET"
id=3D"__EVENTTARGET" value=3D"" />
			<input type=3D"hidden" name=3D"__EVENTARGUMENT"
id=3D"__EVENTARGUMENT" value=3D"" />=20
		=09
			Does this mean that every generated aspx page is
invalid? If so, then I
			would putting 'fixing' this in Anthem on the bottom
of the priority
			list. If I'm wrong, then sorry... Brian? Could you
pls let me know your=20
			comment on this?
		=09
			So I have the same question again. The 2 hidden
fields generated by asp are also seen as invalid?
			=20
			Manu.
		=09
			=20
			On 3/21/06, Roberto <ro...@lt...> wrote:=20

				Hi Guys
				=20
				I was using the latest builds of
Anthem.NET, but I suspect the error has been there for a while... It =
seems u
can't validate a page using HTML tidy with Anthem controls since the =
control
names generate ID's such as ID=3D"__Button1__" which I think is not =
allowed in
the spec. Below is an example of the like that gives me a warning in =
HTML
tidy even though it's not an error it would be cool if it could be =
fixed.=20
				=20
				Does anyone have a fix for this?
				<span id=3D"__Button1__"><input
type=3D"submit" name
				=3D"Button1" value=3D"Start Ajax"
onclick=3D"AnthemButton_Click(this,'Button1',true,'Getting
info',false,Button1_PreCallBack,Button1_PostCallBack,null,true,true);ret
urn false;"=20
				id=3D"Button1" /></span><span
id=3D"ProgressSection" style=3D"visibility:hidden;"
				><img src=3D"images/indicator.gif"
border=3D"0" style=3D"vertical-align:middle; padding-left:5px;
padding-right:2px;"=20
				alt=3D"Progress Icon" />Please wait while
retrieving information...</span>
				line 36 column 9 - Warning: <span> ID
"__Button1__" uses XML ID synta
				=20
				Regards Rob

				No virus found in this outgoing message.
				Checked by AVG Free Edition.
				Version: 7.1.385 / Virus Database:
268.2.6/286 - Release Date: 20/03/2006
			=09
			=09
			=09

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting =
language
that extends applications into web and mobile media. Attend the live =
webcast
and join the prime developer group breaking into this new coding =
territory!
http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=110944&bid$1720&dat=121642
_______________________________________________
anthem-dot-net-users mailing list
ant...@li...
https://lists.sourceforge.net/lists/listinfo/anthem-dot-net-users

2005	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov (33)	Dec (28)
2006	Jan (198)	Feb (323)	Mar (143)	Apr (20)	May (13)	Jun (5)	Jul	Aug (3)	Sep	Oct	Nov	Dec
2007	Jan	Feb	Mar (1)	Apr	May	Jun	Jul	Aug (2)	Sep	Oct	Nov (1)	Dec
2008	Jan (1)	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec

anthem-dot-net-users Mailing List for Anthem.NET (Page 4)

anthem-dot-net-users — List for Anthem users