ASP.NET Futures

Re: Ajax Roadmap published

bkg4211 — Thu, 04 Dec 2008 00:12:17 GMT

In the roadmap, I notice that you mention “navigation aids for large files”. The document goes on to discuss a tree like or class view type of implementation. While that might be helpful, in my opinion a great win for Javascript editing in VS2008 would be to get the code editor to a state where it has the two dropdowns at the top of the editor (Left one contains classes, etc, right one has members of the object that is selected in the left dropdown) window like VB and C# have. This would go a very long way in making javascript coding easier.

Re: Ajax Roadmap published

bleroy — Fri, 21 Nov 2008 18:33:57 GMT

Sure, the data comes from the server as JSON. JSON is JavaScript (JavaScript Object notation).

Re: Ajax Roadmap published

ksivasenthil — Fri, 21 Nov 2008 11:09:16 GMT

bleroy:

The client data source feature is 100% based on standard html and Javascript. There is no XML in the picture.

Has it got something to do with JSON? How is it possible to bring server side data to client without using XML or JSON?

Please forgive me if I am misunderstanding the Client Data Source concept. It will be really nice if some light is thrown on this.. !

Re: Ajax Roadmap published

mohansanjee — Tue, 18 Nov 2008 08:10:51 GMT

good...

Re: Ajax Roadmap published

marcinobel — Mon, 17 Nov 2008 18:04:18 GMT

Re: Ajax Roadmap published

bleroy — Wed, 12 Nov 2008 18:20:34 GMT

Yes, this has everything to do with jQuery: now that we're supporting jQuery, we are not doing the selector APIs.

The client data source feature is 100% based on standard html and Javascript. There is no XML in the picture.

I hope this helps.

Re: Ajax Roadmap published

ksivasenthil — Wed, 12 Nov 2008 13:08:23 GMT

I am bit late to rep on this thread but any way I will spill my thoughts on this.

Your DOM API manipulation looks similar to jQuery, so I was just thinking whether has it got something with what Scott Gutherie announced some time back on packing jQuery inside ASP.NET.

On the Client Data Source front, It reminded me of the XML Data Island in HTML pages which was ported to ASP.NET as an XML control in the server side comopnents. However, it suffered from the browser war. It worked only in IE and failed to work on Safari Opera and earlier version of Mozilla Firefox(I am not sure whether it is supported now in Mozilla Firefox).

So, will the new Client Data Source will also suffer some such issues?

How is it implemented inside? Is it like the XML Data Island?

Or I suspect that it might use the DOM functions and JS's XML capabilities to modify the DOM on the fly?

These are few things that I was wondering on while I read the document. Can somebody shed some light on it?

It will be great to know more about how you (ASP.NET Team) are planning about it!!

Re: Ajax Roadmap published

vishalsimon — Mon, 10 Nov 2008 14:12:58 GMT

mhildreth:
It's great to see that there's the plan moving forward is open for discussion. The Futures library has some great stuff, but there hasn't been much mention of when or how that functionality will be transitioned into the framework. Here are the things I'd love to see:

DOM API Improvements

Animations

Drag & Drop

High Level Controls - Async validator, upload, layout, and rich text box

Thanks for listening!

It's great to see that there's the plan moving forward is open for discussion. The Futures library has some great stuff, but there hasn't been much mention of when or how that functionality will be transitioned into the framework. Here are the things I'd love to see:

DOM API Improvements
Animations
Drag & Drop
High Level Controls - Async validator, upload, layout, and rich text box

Thanks for listening!

Re: Ajax Roadmap published

yaip — Mon, 13 Oct 2008 17:24:33 GMT

Just like there is LoginView (which is very intuitive), it would be very nice to have a “CookieView”. I could then drag an instance of the control from the toolbox and set its property (say “CookieID”). This will control what the user sees on a web page based upon the existence of the cookie specified in “CookieID”.

Re: Ajax Roadmap published

yaip — Mon, 13 Oct 2008 17:23:28 GMT

rdonahue:
I second the ability to have a "dynamic" default button that could be set based on the "DefaultButtonGroup". That would be a great advantage.

Thx.

I have one more suggestion.

Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;}

Re: Ajax Roadmap published

rdonahue — Mon, 13 Oct 2008 14:04:48 GMT

I second the ability to have a "dynamic" default button that could be set based on the "DefaultButtonGroup". That would be a great advantage.

yaip:
One of the controls that I've always missed is "DefaultButtonGroup". The DefaultButton only exists at page level. It would be very cool if there was more than one DefaultButton on a page. And the DefaultButton ould change depending on the TextBox that had gained focus.

I would drag a "DefaultButtonGroup" from my ToolBox while designing. It would have a collection called "fields in the group" in the properties window. I would add all the fields on the page that belong to this group. I would then set a property called "DefaultButtonID".

This way I could have multiple default buttons on a page. All I would have to do is to drag another instance of "DefaultButtonGroup" and set its properties.

Re: Ajax Roadmap published, JsonFx is here today

jsonfx — Sun, 05 Oct 2008 01:20:00 GMT

While waiting for ASP.NET 4.0, try out JsonFx.NET, the JSON-savvy Ajax Framework. It works on ASP.NET 2.0 & 3.5 and supports many of these features today. Plus, it is open source:

Some of the features:

- a true Ajax framework embracing JSON as core to all features
- JsonML+Browser-Side Templating (JBST) data-binding JSON in the client
- JSON-RPC 2.0 support with auto-generated JavaScript proxies
- build-time optimization of client libraries (compaction/Gzip/Deflate)
- build-time syntax checking of JavaScript & CSS
- supports UserAgent-specific CSS (no more browser hacks)
- dynamic behavior binding features
- client-side globalization support
- Ajax history (browser back button) support
- helps get a Grade A in YSlow

A full demo and downloadable project templates are available at:

http://starterkit.jsonfx.net

Re: Ajax Roadmap published

Adam.Kahtava — Sun, 28 Sep 2008 19:10:09 GMT

Exciting news:

"Microsoft is looking to make jQuery part of their official development platform ... jQuery will be distributed with Visual Studio" Read more.

Re: Ajax Roadmap published

MisterFantastic — Thu, 25 Sep 2008 04:17:23 GMT

Hi ,

I would appreciate something that would be helpful for development of DataBound controls.

Currently we don't have an efficient Grid control that fully supports the Ajax funcionality. For example an add row event . A fully client efficient grdi control is needed.

Re: Ajax Roadmap published

bleroy — Thu, 18 Sep 2008 16:18:11 GMT

I'd have to know your specific scenario, but I'm guessing you're writing the script file for the page or application, not for the control itself, right?

So in ASP.NET 4.0, you'll be able to set ClientId on your server controls, which will result in predictible IDs on the client.

In the meantime, what people usually do is that they emit a small piece of JavaScript code that initializes a small data structure with the ids of the controls they need to reference and then pass that into the script. Does this help?