We Do Gadgets! - DoGadgets.com

World stock gadget is available.

2009-11-26T19:24:34+09:00

We released new gadget for world stock. Now you can check at a glance world wide stock market in igoogle or your site. You can check KRW/USD, JPY/USD, WTI, Gold, DXI, SOX, BDI, Korea, Japan, China, Russia, Pilippines, India, Malaysia, Turkey, STI, HSI, HSCE, Vietnam, Austrailia, Dow, Nasdaq, Canada, Chile, Venezuela, Argentina, S&P500, Spain, Italy, Germany, France, England, Denmark and Israel. We hope this gadget could be helpful for your web life.
Thank you.

Adding WMarket

Easy ways to talk about sex

2009-11-04T07:38:45+09:00

One way to overcome lack of communication about sex is to read books together that describe sex and then discuss them. It is a lot easier to approach the subject of sex if your partner doesn't feel blamed for doing it wrong. When you hear something that feels good to you, responding to it with a little "ummm" or a bigger "ummm" gives your partner the hint or reminder he or she needs.
No matter how much we know about sex, understanding differences between men and women adds a whole new slant. We are much more motivated to give our partners what they need when we understand the differences.

Sometimes when I speak about sex, I ask my audience to clap when they really like what I am saying, to emphasize to their partners that the point I am making rings true for them. Men are surprised at the times when the women clap the hardest, and vice versa. A husband doesn't take it so personally when his wife claps because almost all the women are clapping, and besides, she is just clapping at what she likes, not complaining about him. She doesn't need to tell him directly what she needs because he can observer her reaction.

Through directly experiencing feedback in his nonthreatening way, many couples who had even stopped having sex suddenly started to enjoy great sex. By learning about their differences in this way, men and women more able to remember them and are thus more motivated to do what it takes to create great sex for themselves and their partners.

Mars And Venus In the Bedroom

John Gray, Ph.D.

7 habits of a higly successful trader!

2009-11-03T19:02:28+09:00

Take Complete Responsibility
Have a System That fits you
Plan a Trade and Trade a Plan
Work Hard at Learning How to Trade Properly and Keep Working
Positive Self-Belief
View Trading as a Score in Points and Not In Money:
Keep trading as Part of a Balanced life

Mark Crisp

http://stressfreetrading.com

Roland JV2080 Patch list for Sonar or Cakewalk

2009-11-03T01:36:13+09:00

The attached file contains patch list for Sonar or cakewalk. Also included for expansion board of Session, Vintage synth and House.

JV-2080 PATCH.INS

Like an Ocean

2009-10-28T18:49:58+09:00

The market is like an ocean - it moves up and down regardless of what you want. You may feel joy when you buy a stock and it explodes in a rally. You may feel drenched with fear when you go short but the market rises and your equitiy melts with every uptick. These feelings have nothing to do with the market - they exist only inside you.
The market does not know you exist. You can do nothing to influence it. You can only control your behavior.
The ocean does not care about your welfare, but it has no wish to hurt you either. You may feel joy on a sunny day, when a gentle wind pushes your sailboat where you want it to go. You may feel panic on a stormy day when the ocean pushes your boat toward the rocks. Your feelings about the ocean exist only in your mind. They threaten your survival when you let your feelings rather than intellect control your behavior.
A sailor cannot control the ocean, but he can control himself. He studies currents and weather patterns. He learns safe sailing techniques and gains experience. He knows when to sail and when to stay in the harbor. A successful sailor uses his intelligence.
An ocean can be useful - you can fish in it and use its surface to get the the other islands. An ocean can be dangerous - you can drown in it. The more rational your approach, the more likely you are to get what you want. When you act out your emotions, you cannot focus on the reality of the ocean.
A trader has to study trends and reversals in the market the way a sailor studies the ocean. He must trade on a small scale while learning to handle himself in the market. You can never control the market but you can learn to control yourself.
A beginner who has a string of profitable trades often feels he can walk on water. He starts taking wild risks and blows up his account. On the other hand, an amateur who takes several losses in a row often feels so demoralized the he cannot place an order even when his system gives him a strong signal to buy or sell. If trading makes you feel elated or frightened, you will make irrational trades and lose. When fear grips you, you'll miss profitable trades.
A professional trader uses his head and stay calm. Only amateurs become excited or depressed because of their trades. Emotional reactions are a luxury the you cannot afford in the markets.

from Trading for a living by Dr. Alexander Elder

How to Create MACD

2009-10-09T06:54:45+09:00

Moving Average Convergence-Divergence

1. Calculate a 12-day EMA of closing prices.
2. Calculate a 26-day EMA of closing prices.
3. Subtract the 26-day EMA from the 12-day EMA, and plot their difference as a solid line. This is the fast MACD line.
4. Calculate a 9-day EMA of the fast line, and plot the result as a dashed line. This is the slow Signal line.

MACD-Histogram = MACD line - Signal line

SyncML Status code

2009-08-24T15:38:18+09:00

Status Codes of SYNCML

Informational 1xx

101 In progress. The specified SyncML command is being carried out, but has not yet completed.

Successful 2xx

200 OK. The SyncML command completed successfully.
201 Item added. The requested item was added.
202 Accepted for processing. The request to either run a remote execution of an application or to alert a user or application was successfully performed.
203 Non-authoritative response. The request is being responded to by an entity other than the one targeted. The response is only to be returned when the request would have been resulted in a 200 response code from the authoritative target.
204 No content. The request was successfully completed but no data is being returned. The response code is also returned in response to a Get when the target has no content.
205 Reset content. The source should update their content. The originator of the request is being told that their content should be synchronized to get an up to date version.
206 Partial content. The response indicates that only part of the command was completed. If the remainder of the command can be completed later, then when completed another appropriate completion request status code SHOULD be created.
207 Conflict resolved with merge. The response indicates that the request created a conflict; which was resolved with a merge of the client and server instances of the data. The response includes both the Target and Source URLs in the Item of the Status. In addition, a Replace command is returned with the merged data.
208 Conflict resolved with client’s command "winning". The response indicates that there was an update conflict; which was resolved by the client command winning.
209 Conflict resolved with duplicate. The response indicates that the request created an update conflict; which was resolved with a duplication of the client’s data being created in the server database. The response includes both the target URI of the duplicate in the Item of the Status. In addition, in the case of a two-way synchronization, an Add command is returned with the duplicate data definition.
210 Delete without archive. The response indicates that the requested data was successfully deleted, but that it was not archived prior to deletion because this optional feature was not supported by the implementation.
211 Item not deleted. The requested item was not found. It may have been previously deleted.
212 Authentication accepted. No further authentication is needed for the remainder of the synchronization session. This response code can only be used in response to a request in which the credentials were provided. 213 Chunked item accepted and buffered.
214 Operation cancelled. The SyncML command completed successfully, but no more commands will be processed within the session.
215 Not executed. A command was not executed, as a result of user interaction and user chose not to accept the choice.
216 Atomic roll back OK. A command was inside Atomic element and Atomic failed. This command was rolled back successfully.

Redirection 3xx

300 Multiple choices. The requested target is one of a number of multiple alternatives requested target. The alternative SHOULD also be returned in the Item element type in the Status.
301 Moved permanently. The requested target has a new URI. The new URI SHOULD also be returned in the Item element type in the Status.
302 Found. The requested target has temporarily moved to a different URI. The original URI SHOULD continue to be used. The URI of the temporary location SHOULD also be returned in the Item element type in the Status. The requestor SHOULD confirm the identity and authority of the temporary URI to act on behalf of the original target URI.
303 See other. The requested target can be found at another URI. The other URI SHOULD be returned in the Item element type in the Status.
304 Not modified. The requested SyncML command was not executed on the target. This is an additional response that can be added to any of the other Redirection response codes.
305 Use proxy. The requested target MUST be accessed through the specified proxy URI. The proxy URI SHOULD also be returned in the Item element type in the Status.

Originator Exceptions 4xx

400 Bad request. The requested command could not be performed because of malformed syntax in the command. The malformed command MAY also be returned in the Item element type in the Status.
401 Invalid credentials. The requested command failed because the requestor MUST provide proper authentication. If the property type of authentication was presented in the original request, then the response code indicates that the requested command has been refused for those credentials.
402 Payment required. The requested command failed because proper payment is required. This version of SyncML does not standardize the payment mechanism.
403 Forbidden. The requested command failed, but the recipient understood the requested command. Authentication will not help and the request SHOULD NOT be repeated. If the recipient wishes to make public why the request was denied, then a description MAY be specified in the Item element type in the Status. If the recipient does not wish to make public why the request was denied then the response code 404 MAY be used instead.
404 Not found. The requested target was not found. No indication is given as to whether this is a temporary or permanent condition. The response code 410 SHOULD be used when the condition is permanent and the recipient wishes to make this fact public. This response code is also used when the recipient does not want to make public the reason for why a requested command is not allowed or when no other response code is appropriate.
405 Command not allowed. The requested command is not allowed on the target. The recipient SHOULD return the allowed command for the target in the Item element type in the Status.
406 Optional feature not supported. The requested command failed because an optional feature in the request was not supported. The unsupported feature SHOULD be specified by the Item element type in the Status.
407 Missing credentials. This response code is similar to 401 except that the response code indicates that the originator MUST first authenticate with the recipient. The recipient SHOULD also return the suitable challenge in the Chal element type in the Status.
408 Request timeout. An expected message was not received within the required period of time. The request can be repeated at another time. The RespURI can be used to specify the URI and optionally the date/time after which the originator can repeat the request. See RespURI for details.
409 Conflict. The requested failed because of an update conflict between the client and server versions of the data. Setting of the conflict resolution policy is outside the scope of this version of SyncML. However, identification of conflict resolution performed, if any, is within the scope.
410 Gone. The requested target is no longer on the recipient and no forwarding URI is known.
411 Size required. The requested command MUST be accompanied by byte size or length information in the Meta element type.
412 Incomplete command. The requested command failed on the recipient because it was incomplete or incorrectly formed. The recipient SHOULD specify the portion of the command that was incomplete or incorrect in the Item element type in the Status.
413 Request entity too large. The recipient is refusing to perform the requested command because the requested item is larger than the recipient is able or willing to process. If the condition is temporary, the recipient SHOULD also include a Status with the response code 418 and specify a RespURI with the response URI and optionally the date/time that the command SHOULD be repeated.
414 URI too long. The requested command failed because the target URI is too long for what the recipient is able or willing to process. This response code is seldom encountered, but is used when a recipient perceives that an intruder may be attempting to exploit security holes or other defects in order to threaten the recipient.
415 Unsupported media type or format. The unsupported content type or format SHOULD also be identified in the Item element type in the Status.
416 Requested size too big. The request failed because the specified byte size in the request was too big.
417 Retry later. The request failed at this time and the originator should retry the request later. The recipient SHOULD specify a RespURI with the response URI and the date/time that the command SHOULD be repeated. 418 Already exists. The requested Put or Add command failed because the target already exists.
419 Conflict resolved with server data. The response indicates that the client request created a conflict; which was resolved by the server command winning. The normal information in the Status should be sufficient for the client to "undo" the resolution, if it is desired.
420 Device full. The response indicates that the recipient has no more storage space for the remaining synchronization data. The response includes the remaining number of data that could not be returned to the originator in the Item of the Status.
421 Unknown search grammar. The requested command failed on the server because the specified search grammar was not known. The client SHOULD re-specify the search using a known search grammar.
422 Bad CGI Script. The requested command failed on the server because the CGI scripting in the LocURI was incorrectly formed. The client SHOULD re-specify the portion of the command that was incorrect in the Item element type in the Status.
423 Soft-delete conflict. The requested command failed because the "Soft Deleted" item was previously "Hard Deleted" on the server.
424 Size mismatch. The chunked object was received, but the size of the received object did not match the size declared within the first chunk.

Recipient Exception 5xx

500 Command failed. The recipient encountered an unexpected condition which prevented it from fulfilling the request
501 Command not implemented. The recipient does not support the command required to fulfill the request. This is the appropriate response when the recipient does not recognize the requested command and is not capable of supporting it for any resource.
502 Bad gateway. The recipient, while acting as a gateway or proxy, received an invalid response from the upstream recipient it accessed in attempting to fulfill the request.
503 Service unavailable. The recipient is currently unable to handle the request due to a temporary overloading or maintenance of the recipient. The implication is that this is a temporary condition; which will be alleviated after some delay. The recipient SHOULD specify the URI and date/time after which the originator should retry in the RespURI in the response.
504 Gateway timeout. The recipient, while acting as a gateway or proxy, did not receive a timely response from the upstream recipient specified by the URI (e.g. HTTP, FTP, LDAP) or some other auxiliary recipient (e.g. DNS) it needed to access in attempting to complete the request.
505 DTD Version not supported. The recipient does not support or refuses to support the specified version of SyncML DTD used in the request SyncML Message. The recipient MUST include the versions it does support in the Item element type in the Status.
506 Processing error. An application error occurred while processing the request. The originator should retry the request. The RespURI can contain the URI and date/time after which the originator can retry the request.
507 Atomic failed. The error caused all SyncML commands within an Atomic element type to fail.
508 Refresh required. An error occurred that necessitates a refresh of the current synchronization state of the client with the server. Client is requested to initiate a slow sync with the server.
509 Reserved for future use.
510 Data store failure. An error occurred while processing the request. The error is related to a failure in the recipient data store.
511 Server failure. A severe error occurred in the server while processing the request. The originator SHOULD NOT retry the request.
512 Synchronization failed. An application error occurred during the synchronization session. The originator should restart the synchronization session from the beginning.
513 Protocol Version not supported. The recipient does not support or refuses to support the specified version of the SyncML Synchronization Protocol used in the request SyncML Message. The recipient MUST include the versions it does support in the Item element type in the Status.
514 Operation cancelled. The SyncML command was not completed successfully, since the operation was already cancelled before processing the command. The originator
516 Atomic roll back failed. Command was inside Atomic element and Atomic failed. This command was not rolled back successfully. Server should take action to try to recover client back into original state. should repeat the command in the next session.

ubuntu 8.04 Dual monitor setting with ATI graphic card!

2009-07-17T10:33:09+09:00

In case of ATI graphic card, you can set dual monitor with below command. This will set automatically the /etc/X11/xorg.conf.

$ sudo aticonfig --initial=dual-head --screen-layout=right --dtop=horizontal --overlay-on=1

from http://jglee.egloos.com/1467400

iCurrency code list

2009-06-30T07:50:41+09:00

These are codes in iCurrency gadget.

Argentine Peso (ARS)

Australian Dollar (AUD)

Bahraini Dinar (BHD)

Bolivian Boliviano (BOB)

Botswana Pula (BWP)

Brazilian Real (BRL)

British Pound (GBP)

Brunei Dollar (BND)

Bulgarian Lev (BGN)

Canadian Dollar (CAD)

Chilean Peso (CLP)

Chinese Yuan (CNY)

Colombian Peso (COP)

Croatian Kuna (HRK)

Czech Koruna (CZK)

Danish Krone (DKK)

Egyptian Pound (EGP)

Estonian Kroon (EEK)

Euro (EUR)

Fijian Dollar (FJD)

Honduran Lempira (HNL)

Hong Kong Dollar (HKD)

Hungarian Forint (HUF)

Icelandic Krona (ISK)

Indian Rupee (INR)

Indonesian Rupiah (IDR)

Japanese Yen (JPY)

Kazakhstani Tenge (KZT)

Kuwaiti Dinar (KWD)

Lithuanian Litas (LTL)

Malaysian Ringgit (MYR)

Mauritian Rupee (MUR)

Mexican Peso (MXN)

Moroccan Dirham (MAD)

Nepalese Rupee (NPR)

Netherlands Antillean Gulden (ANG)

New Israeli Sheqel (ILS)

New Romanian Leu (RON)

New Taiwan Dollar (TWD)

New Turkish Lira (TRY)

New Zealand Dollar (NZD)

Norwegian Krone (NOK)

Omani Rial (OMR)

Pakistani Rupee (PKR)

Peruvian Nuevo Sol (PEN)

Philippine Peso (PHP)

Polish Złoty (PLN)

Qatari Riyal (QAR)

Russian Ruble (RUB)

Saudi Riyal (SAR)

Serbian Dinar (CSD)

Singapore Dollar (SGD)

Slovak Koruna (SKK)

Slovenian Tolar (SIT)

South African Rand (ZAR)

South Korean Won (KRW)

Sri Lankan Rupee (LKR)

Swedish Krona (SEK)

Swiss Franc (CHF)

Thai Baht (THB)

Trinidad and Tobago Dollar (TTD)

Ukrainian Hryvnia (UAH)

United Arab Emirates Dirham (AED)

United States Dollar (USD)

Venezuelan Bolivar (VEB)

iGoogle currency exchange rate gadgets, iCurrency was released!

2009-06-11T16:09:15+09:00

You can check currecy exchange rate with iCurrency now!

Adding iCurrency