parseInt(string[, radix])
A radix-et tehat el lehet hagyni csak nem erdemes, mert ha nem adjuk meg akkor a string alapjan probalja megallapitani es ha “0″-val kezdodik akkor 8-as alapunak veszi es peldaul a “011″-bol decimalis 9 lesz, a “08″-bol pedig 0, mert ugye 8 nincs okatlis szamrendszerben.
The following controls do not conform to the standard Click event behavior:
Note The event behavior detailed below happens whether the user clicks on an item or not (that is, a mouse click or double-click anywhere within the ListBox control raises these events).
Note The event behavior detailed below happens whether the user clicks on an item or not (that is, a mouse click or double click anywhere within the ListBox control raises these events)
Note The event behavior detailed below happens whether the user clicks on the edit field, the button, or on an item within the list.
Note The event behavior detailed below happens only when the user clicks on the items in the ListView control. No events are raised for clicks anywhere else on the control. In addition to those described below, there are the BeforeLabelEdit and AfterLabelEdit events, which may be of interest to developers wishing to use validation with the ListView control.
Note The event behavior detailed below happens only when the user clicks on the items themselves or to the right of the items in the TreeView control. No events are raised for clicks anywhere else on the control. In addition to those described below, there are the BeforeCheck, BeforeSelect, BeforeLabelEdit, AfterSelect, AfterCheck, and AfterLabelEdit events, which may be of interest to developers wishing to use validation with the TreeView control.
Sometimes, when writing SELECTs, we come across situations in which we we need to write a join containing a condition of some sort. You might think to do this with either a CASE expression or with some OR boolean logic in your JOIN expression. Often, you might encounter syntax errors, performance problems, or results not being returned the way you expect when trying this. There’s a much better way to approach the problem.
Instead of trying to alter a single INNER JOIN’s relation from row to row, instead use multiple LEFT OUTER JOINS in your SELECT, one for each table or condition that you need to consider.
ISNULL(Transact-SQL): Replaces NULL with the specified replacement value.
De a lenyeg:
If you want to know whether the browser that views your page supports certain objects you want to use in your code, you should never EVER use a browser detect.
Instead, we simply look if the browser supports the object (method, array or property) we want to use. Let’s continue with the mouseover example. This script relies on the document.images array, so first and foremost we’ll have to detect if the browser supports it. This is done by
if (document.images)
{
do something with the images array
}
Another common detect is for window.focus. This is a method (a command by which you tell JavaScript to do something for you). If we want to use the method, we’ll have to check first if the browser supports it.
Note the correct way of doing this: you ask for the method without brackets. This code
if (window.focus)
means: “If the focus method is supported”, while this code
if (window.focus())
means: “If you can put the focus on the window” and assumes that focus is supported. If it isn’t, this line of code creates errors. The brackets () actually execute the focus command, which is not what we want in this case. So we check it without the brackets (see if it exists) and only when the browser passes the check we actually execute the command by adding brackets:
if (window.focus) window.focus()
So the whole point is that if you want to use the array document.images, first check if it is supported. If you want to use the focus method of the window, first check if it is supported.
If you always use object detection, your scripts will never generate any error messages, although they might not work in certain browsers.
The premise for graceful degradation is to first build for the latest and greatest, then add handlers for less capable devices.
…
Another common occurrence in sites built from the graceful degradation point of view is the noscript element. You provide some feature based on JavaScript and add a more basic version for user agents that do not support JavaScript or have client-side scripting disabled.
…
There is one problem with noscript, though. I may use a browser that supports JavaScript and has it enabled, but there could be a company firewall that strips incoming JavaScript for security reasons. In this case the noscript element will not be rendered (because my browser supports scripting) but the JavaScript code that should create the menu won’t be applied either, because it gets stuck behind the firewall.
Progressive enhancement starts at the opposite end from graceful degradation: begin with the basic version, then add enhancements for those who can handle them.
…
The most common occurrence of progressive enhancement is probably the external CSS style sheet.
…
This is progressive enhancement: it works for everyone, but users with modern browsers will see a more usable version.
Persze kell egy Print fv. is, hogy ez mukodjon.
unobtrusive: diszkret, szereny, tartozkodo, nem tolakodo, nem feltuno
-Bidirectional
-Download-only to Subscriber, allow Subscriber changes
-Download-only to Subscriber, prohibit Subscriber changes
Azzal volt bajom, hogy barmelyiket is valasztottam az visszaallt Bidirectional-ra mindenfele figyelmeztetes nelkul. Aztan vegul itt talaltam meg, hogy mitol van ez:
“to take advantage of this property (@subscriber_upload_options) the subscription must be marked as a ‘Client’ subscription and not the default of ‘Server’ subscription (see below). If you leave the default ‘Server’ option, the subscriber will always be created as bidirectional.”
Linux, the operating system;
Apache, the Web server;
MySQL, the database management system (or database server);
Perl, PHP, Python, and/or Primate (mod mono), scripting/programming languages.
forras: wikipedia
Mi a 4-esbe futottunk bele, azaz: “If you are using IE 5.5 or IE 6.0, and your local server name has an underscore or other non-alphanumeric character (other than a dash) in the name, then cookies will not work correctly.”
…impersonation isn’t “on” during Application_Start… Application_Start is an odd event. It’s not really a request related event, but of course it won’t fire until the first event arrives. The ASP.NET runtime doesn’t start impersonation until it begins to process the request in earnest. This event fires just before impersonation begins, during a time when ASP.NET is laying out the cocktail napkins and setting up for the party.
This article demonstrates how to create such an image and employ it within an ASP.NET web form.
echolália: Kényszer a hallott szavak visszhangszerű utánzására.
Temak:
MSBuild maximum verbosity
Client Report Definition (rdcl) files
ReportViewer control;
What if you define the following methods in global.asax (yes, all of them):
Having these five event handlers, which one(s) will be called?
It turns out all of them, except the last one, will be called, and in the same order as listed!
<html>
<head>
<style type="text/css">
html {height: 100%}
body {
background-image: url(http://www.google.com/images/logo.gif);
background-position: bottom right;
background-repeat: no-repeat;
}
</style>
</head>
<body>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
<h1>Hello</h1>
</body>
</html>
