xml script spec: template

Showing posts with label template. Show all posts

Wednesday, March 28, 2012

Why no Atlas Web Site template?

Hello -

Just getting started with Atlas. Downloaded and installed ASP.NET AJAX 1.0 Beta 2 and ASP.NET 2.0 AJAX Futures November CTP, but when I go to open a new Web site in VS2005, "Atlas" Web Site does not appear under My Templates (as the tutorials indicat should be the case).

What does appear under Installed Templates is ASP.NET Ajax-Enabled Web Site and ASP.NET Ajax CTP-Enabled Web Site. I chose the latter; however, none of the controls with the Atlas prefix (such as <atlas:ScriptManager>) are available to me through type-ahead.

Any suggestions on this are appreciated.

Eric

I just posted the same issue 15 minutes ago, Can please pass along any information if you come up with a fix.

In beta 2 version, prefix 'atlas' is replaced by 'asp'.
In beta 2 version, prefix 'atlas' is replaced by 'asp'. I am not sure what this means... Details please.

The responder means:

<atlas:ScriptManager>)

is now

<asp:ScriptManager>)

Does this mean that we no longer need the Atlas Web Site Template? Is it replaced with the ASP.NET AJAX-Enabled Web Site?
That is correct forget you even heard the word Atlas (its all Ajax now)
Thanks for the help. I am new at this programming and I have a lot to learn in a little time.

Hi,

When you install AJAX Extensions Beta2, It will adds some controls to Visual Studio2005 ToolBox.

So, open one ASP.NET website and click the ToolBox, goto AJAX Extensions Tab, click that Tab, it will show all controls which are newly installed.

All controls[UpdatePanel,..] will starts with 'asp'.

in design mode, drag-and-drop one control into the design view and goto the source view, there you will see the AJAX controls syntax.

Pradeep

Why templating the content of the UpdatePanel?

Many ASP controls use template for their content (theGridView being a good example). TheUpdatePanel has aContentTemplate property that, as the name suggests, contains the content of the UpdatePanel.

Yet, since the UpdatePanel is not a repeater control, I do not grasp (as a consumer of the ATLAS library) the interest of templating the content of the UpdatePanel. Does some has an idea why a ContentTemplate is used instead of the regular control children?

Thanks in advance,
Joannès
http://www.peoplewords.com

hello.

i'd say that a template let's you have complete control over the content of the updatepanel. if you had a property of another type, you'd only be able to use elements of that type (or of a derived type)

ThePlaceHolder is not templated and but can include any element (as long as they inheritControl which is not a real constraint). My question can maybe be rephrased as "Why did the UpdatePanel not follow the PlaceHolder design pattern?".

Joannès

hum...how about designer integration? i'm not sure because i really don't use the designer, but can you drag-n-drop controls from the toolbox into a placeholder control?

Wednesday, March 21, 2012

XHTML 1.1 Firefox and Opera problem

I installed AJAX Beta2 and used the CTP template to create a new web site. Which creates default.aspx page, with the doc type of:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">

I have a table with images. I run the page in IE7 looks perfect. I ran in FF and Opera the cells height are 5 to 10 px to big. After pulling my hair for about 2 hours. I notice the doctype.

I set it to this: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

And the table is correct (works in IE as well).

Should an AJAX site doctype be XHTML 1.1? Does it matter? Why did this break firefox on something so simple as a table?

Thanks

Rick

AJAX should support site doctype XHTML 1.1 in the release version. I aslo find the similar issue to yours.The Ajax control size?is?somewhat?different?
in?different?browers?such?as?IE,FireFox,Opera,Safari.

Ajax, shorthand for Asynchronous JavaScript and XML, is a web development technique for creating interactive web applications. The intent is to make web pages feel more responsive by exchanging small amounts of data with the server behind the scenes, so that the entire web page does not have to be reloaded each time the user makes a change. This is meant to increase the web page's interactivity, speed, and usability.
The Ajax technique uses a combination of:
XHTML (or HTML) and CSS, for marking up and styling information.
The DOM accessed with a client-side scripting language, especially ECMAScript implementations such as JavaScript and JScript, to dynamically display and interact with the information presented.
The XMLHttpRequest object is used to exchange data asynchronously with the web server. In some Ajax frameworks and in certain situations, an IFrame object is used instead of the XMLHttpRequest object to exchange data with the web server, and in other implementations, dynamically added <script> tags may be used.
XML is sometimes used as the format for transferring data between the server and client, although any format will work, including preformatted HTML, plain text, JSON and even EBML. These files may be created dynamically by some form of server-side scripting.

Wednesday, March 28, 2012

Why no Atlas Web Site template?

Why templating the content of the UpdatePanel?

Wednesday, March 21, 2012

XHTML 1.1 Firefox and Opera problem

xml script spec

Blog Archive

About Me