1.
How do I do this:
<code>
<application>
<load>
<invokeMethod target="dataSource" method="select"/>
</load>
</application>
</code>
using server controls?
2.
How can I add the Atlas server controls to my VS toolbox?
3.
Can everything that can be done with Atlas in a script block be done using the server controls or are the server controls limited in some way?
4.
To understand Atlas better, why were the existing ASP.NET 2.0 server controls not extended to include Atlas functionality instead of creating new controls that don't have some of the features built into the ObjectDataSource for example?
5.
Will Atlas controls utilize the design view control wizards like the GridView, DetailsView or SqlDataSource controls?
Thanks. Atlas looks very promising and I can see it being very useful for people like me that are JavaScript challenged. :)
Keegan
Re #1: Due to a known bug, this is currently not possible. It was supposed to be possible in the preview by using a .script "codebehind" file with static atlas code.
Re #2: Just like you add any other web controls library. Go to your toolbox, right click -> choose items and locate Microsoft.Web.Atlas.dll.
Re #3: I assume you mean the "Atlas script block" when you refer to "script block"? If so, I don't see why not.
Re #4: One of the reasons is probably that this makes it easier to add without having to worry about breaking existing controls. Another reason for now is probably simplicitly: Atlas controls' rendering for example is different, and the capabilities of Atlas
controls is currently different as well (think behaviors, bindings). My guess is that those are a few factors that played a role.
Re #5: In its current form, Atlas server-controls can provide the same design experience as any other non-Atlas control could provide.
Wilco, thanks for your reply! The Atlas community seems rather small right now. I hope it grows larger.
Regarding your answer to question #5, I'm specifically refering to the pop-up design view wizards in VS 2005 that appear when you click on the little arrow in the upper right corner of a control that supports it. Do you know if plans are in the works for Atlas
controls to have this feature?
Do you know of an online resource that lists available values for the property "property" in a binding element?
You can be sure that the full design-time experience will be exploited once Atlas matures, including smart-tags.
The available values for property "property" can be lookup up by looking at the source. I don't think there is any official or unofficial documentation that lists them all. To see the list of available properties, you can basically look at the component's getDescriptor
implementation (and do the same for its 'base class', recursively, to get the complete list). For example, if you want to know what properties a Label has, look in the source for "Web.UI.Label", then look at it's getDescriptor to see what properties it registers.
Then see from what type it derives (in this case it's Web.UI.Control), and do the same for that, etc.
Until there is more documentation available, this is probably the only way to find out what all the properties of an object are.
mullaney
Member
230 Points
47 Posts
DataSource select on app load using server controls?
Oct 20, 2005 12:15 AM|LINK
How do I do this:
<code>
<application>
<load>
<invokeMethod target="dataSource" method="select"/>
</load>
</application>
</code>
using server controls?
2.
How can I add the Atlas server controls to my VS toolbox?
3.
Can everything that can be done with Atlas in a script block be done using the server controls or are the server controls limited in some way?
4.
To understand Atlas better, why were the existing ASP.NET 2.0 server controls not extended to include Atlas functionality instead of creating new controls that don't have some of the features built into the ObjectDataSource for example?
5.
Will Atlas controls utilize the design view control wizards like the GridView, DetailsView or SqlDataSource controls?
Thanks. Atlas looks very promising and I can see it being very useful for people like me that are JavaScript challenged. :)
Keegan
WilcoB
Participant
1454 Points
290 Posts
Re: DataSource select on app load using server controls?
Oct 21, 2005 03:22 PM|LINK
Re #2: Just like you add any other web controls library. Go to your toolbox, right click -> choose items and locate Microsoft.Web.Atlas.dll.
Re #3: I assume you mean the "Atlas script block" when you refer to "script block"? If so, I don't see why not.
Re #4: One of the reasons is probably that this makes it easier to add without having to worry about breaking existing controls. Another reason for now is probably simplicitly: Atlas controls' rendering for example is different, and the capabilities of Atlas controls is currently different as well (think behaviors, bindings). My guess is that those are a few factors that played a role.
Re #5: In its current form, Atlas server-controls can provide the same design experience as any other non-Atlas control could provide.
mullaney
Member
230 Points
47 Posts
Re: DataSource select on app load using server controls?
Oct 21, 2005 10:58 PM|LINK
Regarding your answer to question #5, I'm specifically refering to the pop-up design view wizards in VS 2005 that appear when you click on the little arrow in the upper right corner of a control that supports it. Do you know if plans are in the works for Atlas controls to have this feature?
Do you know of an online resource that lists available values for the property "property" in a binding element?
Thanks again,
Keegan
WilcoB
Participant
1454 Points
290 Posts
Re: DataSource select on app load using server controls?
Oct 22, 2005 09:26 AM|LINK
The available values for property "property" can be lookup up by looking at the source. I don't think there is any official or unofficial documentation that lists them all. To see the list of available properties, you can basically look at the component's getDescriptor implementation (and do the same for its 'base class', recursively, to get the complete list). For example, if you want to know what properties a Label has, look in the source for "Web.UI.Label", then look at it's getDescriptor to see what properties it registers. Then see from what type it derives (in this case it's Web.UI.Control), and do the same for that, etc.
Until there is more documentation available, this is probably the only way to find out what all the properties of an object are.
Update: I have put together a little class browser which should make things a bit easier. See http://www.wilcob.com/Wilco/Default/164/showpost.aspx for more information.
williaml
Member
95 Points
19 Posts
Re: DataSource select on app load using server controls?
Oct 23, 2005 02:22 AM|LINK
Wilco, thanks for posting that.
It'll come in handy :)
mullaney
Member
230 Points
47 Posts
Re: DataSource select on app load using server controls?
Oct 24, 2005 06:50 AM|LINK
Keegan