From: Brian @ A. <br...@aj...> - 2006-03-22 09:26:56
|
=20 > a) I wanted to know in terms of posting requests and stuff ... is it better=20 > to post in this forum or use the mailing list? You get better control over formatting in the forum pages. You can have = your code snippets displayed as such and when you use the forum you can = easily search for items (more easily than in the mailing list archive in my opinion) and you can also have the forum s/w just show you new posts = since you last login. I know that Jason has said he's not likely to use the forum, preferring = the lists, but the forums seem to have plenty of other proficient Anthem = users and developers to answer any questions. > b) In terms of making changes to Anthem code who is in charge of it = like how=20 > do u stop 2 people making the same changes etc for example one guy = wanted to=20 > make the ID's AJAX_ while someone else wanted them as ANTHEM_ so who decides=20 > which one to go with and how do u stop people overriding changes? Jason has granted selected developers access to the sourceforge CVS to = check in changes. Limiting the number to a few, and maintaining proper = comments on each check-in means that it's unlikely for any change to be overridden = or undone accidentally. > c) Does jason do the final release? Where is he?heehe Jason is the final arbiter. He decides what's a release and when to do = it, but you can get the latest snapshot on demand. You'll always get the = latest checked in files, regardless of the status of the 'release' version. Jason is apparently "busy on other projects". That's why he's happy to = have others involved in developing Anthem. =20 Brian Lowe, AJP Interactive br...@aj... =20 -----Original Message----- From: ant...@li... [mailto:ant...@li...] On Behalf Of Roberto Sent: 22 March 2006 00:18 To: ant...@li... Subject: Re: [Anthem.NET-users] Anthem generated code and HTML Tidy Thanks for all that guys... it's good to get anthem to a validation standard... I have a couple of questions: a) I wanted to know in terms of posting requests and stuff ... is it = better to post in this forum or use the mailing list? b) In terms of making changes to Anthem code who is in charge of it like = how do u stop 2 people making the same changes etc for example one guy = wanted to make the ID's AJAX_ while someone else wanted them as ANTHEM_ so who = decides which one to go with and how do u stop people overriding changes? c) Does jason do the final release? Where is he?heehe Regards DotNetshadow ----- Original Message ----- From: "Brian @ AJP" <br...@aj...> To: "'John Murphy'" <jm...@ge...> Cc: <ant...@li...> Sent: Wednesday, March 22, 2006 5:02 AM Subject: RE: [Anthem.NET-users] Anthem generated code and HTML Tidy > 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... -----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. 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. 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. 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 :-/ Per my original suggestion, I propose replacing the invalid "__*" with a valid "AJAX_*" 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. 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? 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." So, unless anyone objects loudly (and quickly), I'm going to recommend changing the invalid "__" to a valid "AJAX_". Code will follow. Brian Lowe, AJP Interactive w: www.ajpi.co.uk <http://www.ajpi.co.uk/> e: br...@aj... f: 07075 167630 _____ 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 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... Could you do this for me? Manu. On 3/21/06, Manu Temmerman-Uyttenbroeck <man...@gm...> wrote: Ok Brian. If I'll find the change I'll check in the change tonight. I hope it won't break any code though... 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. Manu. On 3/21/06, Brian @ AJP <br...@aj...> wrote: 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.) 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. 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. What does the team think? Brian Lowe, AJP Interactive w: www.ajpi.co.uk <http://www.ajpi.co.uk/> e: br...@aj... f: 07075 167630 _____ 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 Brian Lowe asked the same question 11th of February. This was my answer then: 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 page contains following html elements: <input type=3D"hidden" name=3D"__EVENTTARGET" id=3D"__EVENTTARGET" value=3D"" /> <input type=3D"hidden" name=3D"__EVENTARGUMENT" id=3D"__EVENTARGUMENT" value=3D"" /> 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 comment on this? So I have the same question again. The 2 hidden fields generated by asp are also seen as invalid? Manu. On 3/21/06, Roberto <ro...@lt...> wrote: Hi Guys 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. 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;" 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;" alt=3D"Progress Icon" />Please wait while retrieving information...</span> line 36 column 9 - Warning: <span> ID "__Button1__" uses XML ID synta 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 ------------------------------------------------------- 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 ------------------------------------------------------- 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 --=20 No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.2.6/287 - Release Date: = 21/03/2006 --=20 No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.2.6/287 - Release Date: = 21/03/2006 ------------------------------------------------------- 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=3Dlnk&kid=3D110944&bid=3D241720&dat=3D= 121642 _______________________________________________ anthem-dot-net-users mailing list ant...@li... https://lists.sourceforge.net/lists/listinfo/anthem-dot-net-users |