Comments on: Script#: C# to Javascript Converter http://michaelsync.net/2007/10/29/script-c-to-javascript-converter Sharing our knowledge Fri, 04 Jul 2008 19:59:56 +0000 http://wordpress.org/?v=2.5.1 By: Michael Sync » Script# - Is Script# right for you? http://michaelsync.net/2007/10/29/script-c-to-javascript-converter#comment-14035 Michael Sync » Script# - Is Script# right for you? Sun, 25 Nov 2007 17:22:10 +0000 http://michaelsync.net/2007/10/29/script-c-to-javascript-converter#comment-14035 [...] I wanna share you. ( If you have no idea about what Script# is then you can read this post “Script#: C# to Javascript converter[^] “. ) I know that Script# is a great framework but it might not be right for all ASP.NET [...] [...] I wanna share you. ( If you have no idea about what Script# is then you can read this post “Script#: C# to Javascript converter[^] “. ) I know that Script# is a great framework but it might not be right for all ASP.NET [...]

]]> By: Myo Kyaw Htun http://michaelsync.net/2007/10/29/script-c-to-javascript-converter#comment-7628 Myo Kyaw Htun Wed, 31 Oct 2007 06:06:58 +0000 http://michaelsync.net/2007/10/29/script-c-to-javascript-converter#comment-7628 Mike, I think you should reduce the posts in main page or use <!--more--> inside your post. I think that will load faster. Just a thought. Mike, I think you should reduce the posts in main page or use <!–more–> inside your post. I think that will load faster. Just a thought.

]]> By: Michael Sync http://michaelsync.net/2007/10/29/script-c-to-javascript-converter#comment-7354 Michael Sync Tue, 30 Oct 2007 02:53:21 +0000 http://michaelsync.net/2007/10/29/script-c-to-javascript-converter#comment-7354 Hello Nikhil, Thanks a lot of visiting my blog... :) >>I’d be curious about your disappointments as well. Is there something beyond the debugging requires debugging script limitation? Yeah. there are some.... For example, scriptlet editor keep on removing "}" from my code and saying that I need to add "}" in my code. As I'm learning in process, I don't want to post about that for now.. (I'm very news with that tool ). but I made a note and I'll post about that in my blog after I got more idea about Script#.. Yeah. I would like to discuss with you too. Thanks again. Nikhil... Hello Nikhil,

Thanks a lot of visiting my blog… :)

>>I’d be curious about your disappointments as well. Is there something beyond the debugging requires debugging script limitation?
Yeah. there are some…. For example, scriptlet editor keep on removing “}” from my code and saying that I need to add “}” in my code.

As I’m learning in process, I don’t want to post about that for now.. (I’m very news with that tool ). but I made a note and I’ll post about that in my blog after I got more idea about Script#.. Yeah. I would like to discuss with you too.

Thanks again. Nikhil…

]]> By: Michael Sync http://michaelsync.net/2007/10/29/script-c-to-javascript-converter#comment-7338 Michael Sync Tue, 30 Oct 2007 01:45:33 +0000 http://michaelsync.net/2007/10/29/script-c-to-javascript-converter#comment-7338 >>I hope that the included JS libraries are fixing what is visually broken in the generated code! Yeah. >>.attachEvent and .detachEvent are IE-only events… As I'm a Firefox user, I have tested the generated code in Firefox. It works just fine... >>The “name” of the elements in C# are *NOT* the “ids” of the elements! there is a BIG difference! Yes. I agreed with you.. I haven't tested the solution that you mentioned. I think that it should not be a problem since we are creating the HTML element in HTML itself.. NOT from C#. If you look at the example 2, you will see that the input "nameTextBox" and button "sayHiButton" are created in HTML only. Anyway, I will try about this today and will let you know.. >>I hope that the included JS libraries are fixing what is visually broken in the generated code!
Yeah.

>>.attachEvent and .detachEvent are IE-only events…

As I’m a Firefox user, I have tested the generated code in Firefox. It works just fine…

>>The “name” of the elements in C# are *NOT* the “ids” of the elements! there is a BIG difference!

Yes. I agreed with you.. I haven’t tested the solution that you mentioned. I think that it should not be a problem since we are creating the HTML element in HTML itself.. NOT from C#. If you look at the example 2, you will see that the input “nameTextBox” and button “sayHiButton” are created in HTML only. Anyway, I will try about this today and will let you know..

]]> By: Nikhil Kothari http://michaelsync.net/2007/10/29/script-c-to-javascript-converter#comment-7337 Nikhil Kothari Tue, 30 Oct 2007 01:36:16 +0000 http://michaelsync.net/2007/10/29/script-c-to-javascript-converter#comment-7337 Michael, cool post! I'd be curious about your disappointments as well. Is there something beyond the debugging requires debugging script limitation? Michael, cool post!

I’d be curious about your disappointments as well. Is there something beyond the debugging requires debugging script limitation?

]]> By: hopes and dreams http://michaelsync.net/2007/10/29/script-c-to-javascript-converter#comment-7210 hopes and dreams Mon, 29 Oct 2007 17:49:30 +0000 http://michaelsync.net/2007/10/29/script-c-to-javascript-converter#comment-7210 Hmm, I hope that the included JS libraries are fixing what is visually broken in the generated code! .attachEvent and .detachEvent are IE-only events... if there is code to make other browsers mimic these, then fine... although the tool should make IE mimic the W3C, *NOT* the other way around. Note 2.) The "name" of the elements in C# are *NOT* the "ids" of the elements! there is a BIG difference! If I create a button, it can have a name, and an id, and both can be different (using them interchangeably *WILL* cause you much pain down the road. (e.g. if I have 10 checkboxes, with the same name, and different ids, will the generated code call $(name) or $(id) ? Depending which is called, and worse yet, which browser is used (unless the $() function has a patch for IEs incorrect behavior) you will get some very odd results. Otherwise, always cool to see a tool interact better with the web. Hmm, I hope that the included JS libraries are fixing what is visually broken in the generated code!

.attachEvent and .detachEvent are IE-only events… if there is code to make other browsers mimic these, then fine… although the tool should make IE mimic the W3C, *NOT* the other way around.

Note 2.)

The “name” of the elements in C# are *NOT* the “ids” of the elements! there is a BIG difference!

If I create a button, it can have a name, and an id, and both can be different (using them interchangeably *WILL* cause you much pain down the road. (e.g. if I have 10 checkboxes, with the same name, and different ids, will the generated code call $(name) or $(id) ?

Depending which is called, and worse yet, which browser is used (unless the $() function has a patch for IEs incorrect behavior) you will get some very odd results.

Otherwise, always cool to see a tool interact better with the web.

]]>