Get a Freelance Job

I am looking for a serious, smart coder with experience in mt4.Someone whowould not waste either of us time, understands

the project and is neat and orderly in his coding.

I just want some modification done on my existing EA.Please use the attached diagram to help understand how the EA

works.Basically,when the EA is attached, it does the following;

1) Waits for the current bar to close

2)Opens a buy or sell position X pips from the close of the current bar.If a buy positon is opened another buy positon

can not be opened unitl a sell postions has been opened.also if a sell posions has been opened , another sell positions

can not be opend until a buy positons has been opened(Please see attached diagram).Each time a poition is opened , it is

incremental by an already set incremental value
3)All opened positions are closed using either one of the following rules;

I) If the opened postions reaches take profit at the close of the bar, we close all opened positions

II)If the m value is reached at the close of a bar, we close all opened positons.

If the above is not attained we continue to open position according to the specifications above.

4) when the parameters of the EA is changed while it is working, the change is noticed by the EA and its working is

updated to reflect this change.

The above is the way the EA works, however I want the following modificatio made on this EA

It should have all the current features(listed above) with the following additions.

1)A hidden stop loss( this should be optional with a true or false toggle at the input tab, I can use true if i want

to use stop loss or false if I dont want to use a stop loss .If the stop loss is triggered, EA waits for the current

candle to close then starts the process all over again

Please the M routine( which uses the M variable.this is a routine that restricts the EA to only close open positions

when they reached a stiPulated dollar value.This dollar value is given in the M variable which is in the input tap)

should only apply when we are considering the first conditions for closing(that is the condition of closing all opened

positions at the close of the candle when the sum in dollar of all opened positions is a positive.
The winner of this bid would be able to run the EA to see and understand how it works

2)The EA should remember the last trade that it opened no matter the interruption(even if it is;market closure, internet

failure,EA removed from chart, power failure,e.tc..any type of interrruption)Currently , this fucntion works but not 100%

of the time.I want it to be effective 100% of the time

2) In Continuation of the specification above, When the market closes on friday then opens on sunday or any day or when

ever there is any type of interuption(market closure, internet failure,EA removed from chart, power failure,e.tc..any

type of interrruption)(irrespective of the duration) the EA should continue operation immediately the interruption has

ended or as soon as the EA is re-aattached to the chart

If the last position that was opened was a buy and the current price is Ypips below the opened buy postion or if

the Last positions is a sell and the current price is Ypip above the opened sell postions, the EA should do the

followingis ;

1)Calculate the difference between the current market price and the price at which the last position was opened

2) It should then immediately open a new position opposite to the last opened positons and with lot size equal to;

(difference between the current price and the last opened price)divided by interval ( D) then the result multiplied by

the increment value X and then added to the last lotsize.After which it starts its normal function of adding subsequent

position using the incremental value.

If current price=P2
Last opened Position Price=P1
Interval=D
Incremental value=X
Last Lotsize=LLsize

New Lotsize=(((P2-P1)

I need help with the magento website farinfraredshop.com.
1) i need the white space under the main banner to be eliminated.
2) I need the store width to stay large. When the site is opened in internet explorer 7 it is all compressed (made smaller) and messed up. Also, if the site is opened in a small laptop browser, the site width gets compressed (smaller) and then the font gets blurry. I want the site to stay uncompressed and large (like when opened in a larger desktop monitor) no matter what browser someone is using.

What I need or require:
A Fully Customizable Expert Advisor (For MT4) based on my Trading Strategies.

I’ll need an EA which is capable to run up to ten instances of candlestick patterns.
Each candlesticks pattern should have their individual Entry and MM settings.
Each independent candle within a candlestick pattern should be fully customizable.

***Note: When I mention ‘OR’ in the following, it means that I’d like to have both options open for me. So, you’ll still need to code all of them into the EA.

Before we begin on the candlesticks settings, let’s start off with some of the General settings this EA should consist of:
- Trading Session: Start and End session in Hours, based on local Broker’s time.
eg, Start Session 10 and End Session 20, would mean Start trading at my MT4 broker’s 10AM and ends at 8PM

- Total Open Trades Allowed: eg, a ’3′ would mean the maximum total trades currently opened is 3, any other entries would not be opened at all.

- General Money Management:
- Position Size opened based on ‘A’% of Account Balance, OR
- Position Size opened based on SL

- Sound Alert whenever an entry condition is met

- Email Alert whenever an entry condition is met

- An option to disallow the EA to open any trades, but keep the “Entry Condition Met” Sound and Email Signals on. In a sense, it will act like an indicator rather than an EA.

The General Settings are done, so now we move on to what a Typical CandleSticks Pattern should consist of, and I’ll need 10 instances of these patterns all customizable:

Instance 1 CandleSticks Pattern:

Part 1
-No of candlesticks This Pattern should consist of:
– 3 (Candle A, B and C. Candle D and E will be turned off), OR
– 4 (Candle A, B, C and D. Candle E will be turned off), OR
– 5 (All candles in this pattern will be turned on).

Each candlesticks should consist of a Min 2 candles and Max 5 candles.

Part 2
The Candle Stick Pattern
Note: Candle A will be the most recent candle, B the second most recent, and so on.

Candle A
Ability to define how the candle looks like:
- Bull or Bear Candle

- Min and Max Length of Candle (High Low)
- Min and Max Length of Candle Body
- Min and Max Length of Upper Shadow
- Min and Max Length of Lower Shadow

- Opened lower to Candle B’s O/H/L/C: Yes/No/Doesn’t Matter
- Opened lower to Candle C’s O/H/L/C: Yes/No/Doesn’t Matter
- Opened lower to Candle D’s O/H/L/C: Yes/No/Doesn’t Matter
- Opened lower to Candle E’s O/H/L/C: Yes/No/Doesn’t Matter

- Opened higher to Candle B’s O/H/L/C: Yes/No/Doesn’t Matter
- Opened higher to Candle C’s O/H/L/C: Yes/No/Doesn’t Matter
- Opened higher to Candle D’s O/H/L/C: Yes/No/Doesn’t Matter
- Opened higher to Candle E’s O/H/L/C: Yes/No/Doesn’t Matter

- Closed lower to Candle B’s O/H/L/C: Yes/No/Doesn’t Matter
- Closed lower to Candle C’s O/H/L/C: Yes/No/Doesn’t Matter
- Closed lower to Candle D’s O/H/L/C: Yes/No/Doesn’t Matter
- Closed lower to Candle E’s O/H/L/C: Yes/No/Doesn’t Matter

- Closed higher to Candle B’s O/H/L/C: Yes/No/Doesn’t Matter
- Closed higher to Candle C’s O/H/L/C: Yes/No/Doesn’t Matter
- Closed higher to Candle D’s O/H/L/C: Yes/No/Doesn’t Matter
- Closed higher to Candle E’s O/H/L/C: Yes/No/Doesn’t Matter

Candle B
- Bull or Bear Candle

- Min and Max Length of Candle (High Low)
- Min and Max Length of Candle Body
- Min and Max Length of Upper Shadow
- Min and Max Length of Lower Shadow

- Opened lower to Candle C’s O/H/L/C: Yes/No/Doesn’t Matter
- Opened lower to Candle D’s O/H/L/C: Yes/No/Doesn’t Matter
- Opened lower to Candle E’s O/H/L/C: Yes/No/Doesn’t Matter

- Opened higher to Candle C’s O/H/L/C: Yes/No/Doesn’t Matter
- Opened higher to Candle D’s O/H/L/C: Yes/No/Doesn’t Matter
- Opened higher to Candle E’s O/H/L/C: Yes/No/Doesn’t Matter

- Closed lower to Candle C’s O/H/L/C: Yes/No/Doesn’t Matter
- Closed lower to Candle D’s O/H/L/C: Yes/No/Doesn’t Matter
- Closed lower to Candle E’s O/H/L/C: Yes/No/Doesn’t Matter

- Closed higher to Candle C’s O/H/L/C: Yes/No/Doesn’t Matter
- Closed higher to Candle D’s O/H/L/C: Yes/No/Doesn’t Matter
- Closed higher to Candle E’s O/H/L/C: Yes/No/Doesn’t Matter

Candle C
- Bull or Bear Candle

- Min and Max Length of Candle (High Low)
- Min and Max Length of Candle Body
- Min and Max Length of Upper Shadow
- Min and Max Length of Lower Shadow

- Opened lower to Candle D’s O/H/L/C: Yes/No/Doesn’t Matter
- Opened lower to Candle E’s O/H/L/C: Yes/No/Doesn’t Matter

- Opened higher to Candle D’s O/H/L/C: Yes/No/Doesn’t Matter
- Opened higher to Candle E’s O/H/L/C: Yes/No/Doesn’t Matter

- Closed lower to Candle D’s O/H/L/C: Yes/No/Doesn’t Matter
- Closed lower to Candle E’s O/H/L/C: Yes/No/Doesn’t Matter

- Closed higher to Candle D’s O/H/L/C: Yes/No/Doesn’t Matter
- Closed higher to Candle E’s O/H/L/C: Yes/No/Doesn’t Matter

Candle D
- Bull or Bear Candle

- Min and Max Length of Candle (High Low)
- Min and Max Length of Candle Body
- Min and Max Length of Upper Shadow
- Min and Max Length of Lower Shadow

- Opened lower to Candle E’s O/H/L/C: Yes/No/Doesn’t Matter

- Opened higher to Candle E’s O/H/L/C: Yes/No/Doesn’t Matter

- Closed lower to Candle E: Yes/No/Doesn’t Matter

- Closed higher to Candle E’s O/H/L/C: Yes/No/Doesn’t Matter

Candle E
- Bull or Bear Candle

- Min and Max Length of Candle (High Low)
- Min and Max Length of Candle Body
- Min and Max Length of Upper Shadow
- Min and Max Length of Lower Shadow

Part 3
Entry Condition
- When the Candle Pattern is completed upon the closed of Candle A (most recent candle), initiate one of the following options:
– Buy, OR
– Sell, OR
– Buy order placed on Candle ‘X’ High or Low, with the option of + or – ‘N’ Pips, OR
– Sell order placed on Candle ‘X’ High or Low, with the option of + or – ‘N’ Pips.
* Candle ‘X’ refers to the selection of Candle A, B, C, D or E
* ‘N’ Pips refers to the amount of Pips as a margin added or subtracted to Candle ‘X’ High/Low. For instance, if Candle ‘X’ has a high of 1.5000, and the predetermined ‘N’ is +5, then the Buy Order shall be placed as 1.5005.

Part 4
Money Management – Should be independent for each individual candlestick pattern.
The following should be placed the instant a trade has been placed/executed:

Stop Loss
- Stop Loss in Pips, eg. 50 pips, OR
- Stop Loss = Candle ‘X’ High or Low, with the option of + or – ‘N’ Pips, but up to a Maximum of ‘M’ Pips

Take Profit
- TP in Pips, eg. 50 pips, OR
- TP = Candle ‘X’ High or Low, with the option of + or – ‘N’ Pips, but up to a Maximum of ‘M’ Pips

Set SL to BE
- When position has a floating profit of ‘Y’ Pips, Set SL to BE +/- ‘Z’ Pips
* If ‘Y’ Pips is set to 20, that means when the position reaches 20 pip profit, “Set SL to BE will be executed”.
* ‘Z’ Pips: I’d love to have the option to set SL to BE with a bit of profit margin. For example, If BE point for a Buy position is 1.5000, and ‘Z’ is set at +5, when Set SL to BE is executed, the new SL will be set to 1.5005.

Specific expertise that I am seeking:
If you have read and understand what this EA is up to, and already have a concrete idea on how to get it done… Then I’m depending on you!

Timeframe for delivery:
Max 4 Weeks, but You are the expert. You tell me

Finally:
I am no EA Expert nor a decent Programmer. I tried to state ‘exactly’ what I wanted with the EA in what I thought is a logical sequence. Tell me what you can do, what you can’t and what is impossible even in the year 2011.

If you think you have something better to add to this, Great! Let us discuss about it.

Thank you!

This is a fairly simple project that I would like to have completed as soon as possible.

The program that I need some automation for is Full Tilt, available here: http://www.fulltiltpoker.com/download-poker

Once installed, make sure the lobby view is selected as “Standard” [go to "Lobby" -> "Lobby View" -> "Standard"]. You do not need to login, just press “Observe.” Then make sure the filters are set the same as I have shown in the attached screenshot ["Sit & Go," "Heads Up," etc].

Now, in the main screen there is a list of games that are registering and running. What I want is to have a program that will automate the following task:
1. Double click a game that says “Running” under status
2. In the new window that opens [called the lobby], press “Observe Table”
3. Close the lobby
4. After a set period of time, close the table that was opened

I would like this to be repeated until a set number of tables has been opened. When a table is closed, another one should be opened so that there is always the specified number of tables open.

There should also be a start and a stop button to begin and end the process.

I have made a video of what the process would look like and uploaded it here: http://rapidshare.de/files/48774886/TableOpener.avi.html

I would like this to be completed within a couple of days of your bid being accepted, so please do not place a bid if you cannot work within that timeframe

This project is for 100 social media accounts to be opened for social bookmarketing. Accounts will be opened as per video specs then recorded on a shared google doc. Basic information to open the accounts will be given including password.

Hello

We got a lancer script similar to elance and SL installed on our server. Its working fine and good..no bugs.

All i need is to change the look of the site. similar to elance.. meaning.. u have to move the login boxes and contents to different place and change the template of the site.. its a common task for a webdesigner.

and next is.. in elance you can see number of members shown on the main page.. i need you to add that to that new skin for our site

next is to do some IP stuffs so i can ban multi users… etc

and atlast , i give cash prizes to best users.. so need to add such option to that script..

All these should be done

PM me with your doubts even if u bid or dont bid.

Harish

THIS MUST BE COMPLETED BY 11:59PM EST ON MONDAY SEPTEMBER 7 – DO NOT BID IF YOU CANNOT MEET THIS DEADLINE!!
<br><br>
The purpose of this module is for users to be able to:
1. View tasks in order of importance and deadline date & time.
2. Provide updates to the user that opened the task in a ticket-like system, with the user that opened the
task also able to reply back or add additional information to task at any time.
3. Add notes for themselves relating to the task.
4. Provide estimated date & time for task completion.
5. Mark task as complete.
6. Re-assign the task to another user.
7. Add a one-off task for themselves or another user to complete with level of importance and optional
deadline date & time, for example 10:00 AM on November 1st 2009, so user receiving the task can
see it should be completed by this time.
8. Add a recurring task for themselves or another user to complete which will come back into the
system once it has been completed. When creating the task can set to repeat either on a daily, weekly,
monthly basis, or on 1 or more specific days of the week (for example every Monday & Thursday).
The user should also select a level of importance with optional deadline time, for example 10:00 AM,
so user receiving the task knows it should be completed every time by 10:00 AM.
<br><br>
The main page should show the logged in user an overview of their outstanding tasks in order of importance
and date & time of deadline. Should also show the estimated completion date & time if the user has set this.
There should be be a separate archive area that shows tasks they have previously marked as completed.
The main page should also show overview of tasks the logged in user has created for other users, again in
order of importance and date & time of deadline. Should also show the estimated completion date & time if
the user assigned to the task has set this.
The purpose of this module is for users to be able to:
1. View tasks in order of importance and deadline date & time.
2. Provide updates to the user that opened the task in a ticket-like system, with the user that opened the
task also able to reply back or add additional information to task at any time.
3. Add notes for themselves relating to the task.
4. Provide estimated date & time for task completion.
5. Mark task as complete.
6. Re-assign the task to another user.
7. Add a one-off task for themselves or another user to complete with level of importance and optional
deadline date & time, for example 10:00 AM on November 1st 2009, so user receiving the task can
see it should be completed by this time.
8. Add a recurring task for themselves or another user to complete which will come back into the
system once it has been completed. When creating the task can set to repeat either on a daily, weekly,
monthly basis, or on 1 or more specific days of the week (for example every Monday & Thursday).
The user should also select a level of importance with optional deadline time, for example 10:00 AM,
so user receiving the task knows it should be completed every time by 10:00 AM.
<br><br>
They should be able to click on a task to see full information on the task including a notes the user has added
for themselves along with a ticket-like view of communications between the logged in user & the user that
created the task. They should also be able to set estimated date & time for task completion, or change date &
time set previously. There should be a button to mark task as completed which will notify the user that
opened the task and move the task to the completed archive for both users. They should also have the option
to re-assign the task to another user within the system.
The purpose of this module is for users to be able to:
1. View tasks in order of importance and deadline date & time.
2. Provide updates to the user that opened the task in a ticket-like system, with the user that opened the
task also able to reply back or add additional information to task at any time.
3. Add notes for themselves relating to the task.
4. Provide estimated date & time for task completion.
5. Mark task as complete.
6. Re-assign the task to another user.
7. Add a one-off task for themselves or another user to complete with level of importance and optional
deadline date & time, for example 10:00 AM on November 1st 2009, so user receiving the task can
see it should be completed by this time.
8. Add a recurring task for themselves or another user to complete which will come back into the
system once it has been completed. When creating the task can set to repeat either on a daily, weekly,
monthly basis, or on 1 or more specific days of the week (for example every Monday & Thursday).
The user should also select a level of importance with optional deadline time, for example 10:00 AM,
so user receiving the task knows it should be completed every time by 10:00 AM.
<br><br>
Everything should have pagination so there are not too many tasks on a single page.
The purpose of this module is for users to be able to:
1. View tasks in order of importance and deadline date & time.
2. Provide updates to the user that opened the task in a ticket-like system, with the user that opened the
task also able to reply back or add additional information to task at any time.
3. Add notes for themselves relating to the task.
4. Provide estimated date & time for task completion.
5. Mark task as complete.
6. Re-assign the task to another user.
7. Add a one-off task for themselves or another user to complete with level of importance and optional
deadline date & time, for example 10:00 AM on November 1st 2009, so user receiving the task can
see it should be completed by this time.
8. Add a recurring task for themselves or another user to complete which will come back into the
system once it has been completed. When creating the task can set to repeat either on a daily, weekly,
monthly basis, or on 1 or more specific days of the week (for example every Monday & Thursday).
The user should also select a level of importance with optional deadline time, for example 10:00 AM,
so user receiving the task knows it should be completed every time by 10:00 AM.
<br><br>
All users should also be able to set a reminder for themselves for a specified date & time, either as a standalone
reminder from the main page (which should just simply be some text entered by the user), or a
reminder relating to a certain task on the task information page (which should be some text entered by the
user along with a link to the task information page).
The purpose of this module is for users to be able to:
1. View tasks in order of importance and deadline date & time.
2. Provide updates to the user that opened the task in a ticket-like system, with the user that opened the
task also able to reply back or add additional information to task at any time.
3. Add notes for themselves relating to the task.
4. Provide estimated date & time for task completion.
5. Mark task as complete.
6. Re-assign the task to another user.
7. Add a one-off task for themselves or another user to complete with level of importance and optional
deadline date & time, for example 10:00 AM on November 1st 2009, so user receiving the task can
see it should be completed by this time.
8. Add a recurring task for themselves or another user to complete which will come back into the
system once it has been completed. When creating the task can set to repeat either on a daily, weekly,
monthly basis, or on 1 or more specific days of the week (for example every Monday & Thursday).
The user should also select a level of importance with optional deadline time, for example 10:00 AM,
so user receiving the task knows it should be completed every time by 10:00 AM.
<br><br>
Reminders and notifications that task is completed should be sent via MSN Messenger using pre-built PHP
class. The MSN address of all users is stored within the users table.

We are looking for a programmer to develop the integration between MS Office/Open Office documents (word, excel, etc) and the application Enterprise Forms (http://www.longnhi.com/), which is a web based workflow engine written in C#. This integration should be done according to the following requirements:

1. In the application Enterprise Forms we have created the following 2 templates:

–> 1.1. Parameters, with the following mandatory fields, among others:

—-> 1.1.1. Document Type
—-> 1.1.2. Revision Number
—-> 1.1.3. Format for the content: Office/EF Form
—-> 1.1.4. MS Office/Open Office template (Word, Excel, …) with predefined fields
—-> 1.1.5. Users that can save the MS Office/Open Office document locally

–> 1.2. Document named “Test”, with the following fields, among others:

—-> 1.2.1. Document Type
—-> 1.2.2. Title
—-> 1.2.3. Control Number
—-> 1.2.4. Revision Number
—-> 1.2.5. Status
—-> 1.2.6. Date Created
—-> 1.2.7. Date Released
—-> 1.2.8. Author
—-> 1.2.9. Launch in Office (MS Office/Open Office template (Word, Excel, …))
—-> 1.2.10. Approvers

2. When creating ANY DOCUMENT in Enterprise Forms:

–> 2.1. The Enterprise Forms document must receive the Revision Number (point 1.1.2.) and the MS Office/Open Office template (point 1.1.4), both defined in the Parameters document correspondent to the document type being created (point 1.1.). And the status field must have the value “In Process”.

–> 2.2. The Enterprise Forms document must have a button named “Launch in Office” (that is shown only if the option defined in point 1.1.3. of the Parameters document correspondent to the document type of the EF document is Office) and when clicked must launch the MS Office/Open Office attachment mentioned in point 2.1. above. The MS Office/Open Office attachment must be launched in a new window with the corresponding application (word/excel, …) and the Enterprise Forms document from were it was launched must also stay open.

–> 2.3. The MS Office/Open Office attachment launched must inherit automatically and immediately all the values of the fields from the Enterprise Forms document. These inherited fields cannot be editable in the MS Office/Open Office document (cannot be changed by anyone).

–> 2.4. The author of the Enterprise Forms document completes the content of the MS Office/Open Office document and when he saves and closes the MS Office/Open Office document it must be stored/embedded in the field “Launch in Office” of the Enterprise Forms document from where it was created.

–> 2.5. The update of the fields must be done always from the Enterprise Forms document to the MS Office/Open Office document, never from the MS Office/Open Office document to the Enterprise Forms document.

–> 2.6. Users must not be able to close the Enterprise Forms document or the application if there is an MS Office/Open Office document open. If they try to do it they must receive a message saying “You must first close the corresponding Office document”

–> 2.7. After the MS Office/Open Office document is saved the first time, every time the “Launch in Office” button (that is shown only if the option defined in point 1.1.3. of the Parameters document correspondent to the document type of the EF document is “Office”) is clicked it must open the saved/ambedded MS Office/Open Office document and not the template from the parameters document anymore. The MS Office/Open Office document must always be opened in a new window with the corresponding application (word/excel, …) and the Enterprise Forms document from were it was launched must also stay opened.

–> 2.8. Every time there is a change/update in the fields of the Enterprise Forms document the correspondent fields in the MS Office/Open Office document embedded in it must also be automatically and immediately updated, so that the fields that are common between the Enterprise Forms document and the correspondent MS Office/Open Office document have always the same values.

–> 2.9. Every time the MS Office/Open Office document is saved and closed it must update/replace the MS Office/Open Office document previously stored/embedded on the Enterprise Forms document (in the field Launch in Office).

3. After completing both the MS Office/Open Office document and the Enterprise Forms document, the Enterprise Forms document will go through an approval cycle and when approved the status field will become “Released”.

4. On the Enterprise Forms documents with the status field with the value “Released” a “New Revision” button must be made available, which when clicked must make a copy of the complete Enterprise Forms document (including the MS Office/Open Office Document embedded), and this copy should become available for editing again with the status “In Process”. In this new copy the field Revision Number (point 1.2.4.) must be incremented by 1.

5. When an Enterprise Forms document with the status “Released”or a previous version of the same document with the status “Archived” are opened, if the option defined in point 1.1.3. of the Parameters document correspondent to the document type of the EF document is “Office”, the correspondent MS Office/Open Office Document should be automatically opened in read only mode (no one can change it or save it in the Enterprise Forms document nor locally) using a corresponding viewer, and the Enterprise Forms document from were it was launched must also stay opened.

–> 5.1. In this case, the “Launch in Office” button must also be available and if it is used it must open the MS Office/Open Office Document in read only mode (no one can change it or save it locally), using a corresponding viewer, and the Enterprise Forms document from were it was launched must also stay opened.

6. When an Enterprise Forms document with a status different then “Released” or “Archived” is opened, the MS Office/Open Office Document should not be opened automatically and the users can open it manually from the “Launch in Office” button if and when they want to.

–> 6.1. In this case, when clicking the “Launch in Office” button, if the Enterprise Forms document is new and the option “Format for the content” in the Parameters document is defined as “Office”(point 1.1.3.), the MS Office/Open Office attachment/template (point 1.1.4.) defined in the corresponding Parameters document is launched in a new window, using a corresponding viewer and the Enterprise Forms document from were it was launched must also stay opened. If the Enterprise Forms document is not new and the option “Format for the content” in the Parameters document is defined as “Office” (point 1.13.), the MS Office/Open Office document previously saved/embedded in the Enterprise Forms document is launched in a new window, using a corresponding viewer and the Enterprise Forms document from were it was launched must also stay opened.

–> 6.2. When opening the MS Office/Open Office document, if the user at that moment has permissions to edit the Enterprise Forms document, the MS Office/Open Office document must be opened in edit mode and the user can change it and save it in the Enterprise Forms document, but must not be able to save it locally (except if the user is defined in the field “Users/Roles that can save the MS Office/Open Office document locally” (point 1.1.5.) of the Parameters document correspondent to the Enterprise Forms document in question). If the user doesn’t have permission to edit the Enterprise Forms document, the MS Office/Open Office document must be opened in read only mode and the user cannot change it or save it on the Enterprise Forms document nor locally.

–> 6.3. In this case, the author of the Enterprise Forms document must have also the option to delete the MS Office/Open Office document that had been saved/embedded in the Enterprise Forms document or to replace the MS Office/Open Office document that had been saved/embedded in the Enterprise Forms document with the current MS Office/Open Office document attached in the correspondent Parameters document (point 1.1.4.).

–> 6.4. The “Launch in Office” button must be hidden if when opening the Enterprise Forms document, in the Parameters document (point 1.1.) corresponding to this document the option “Format for the content” is defined as “EF Form” (point 1.1.3.).

7. This integration between Enterprise Forms documents and MS Office/Open Office documents must be available for use with any Enterprise Forms document/template if in the option defined in point 1.1.3. of the Parameters document correspondent to the Enterprise Forms document/template the value selected is “Office”. If this integration is being used for a certain Enterprise Forms document/template and the user changes the Parameters Document not to use integration for this Enterprise Forms document/template any more, from that moment on, when creating Enterprise Forms documents of that type they must not have integration any more, but the Enterprise Forms documents of that type that were created before this change must continue having integration and continue having the MS Office/Open Office document that had been saved/embedded in the Enterprise Forms document.

Regards,
Filipa Sousa

The only section of MQL code that I am looking for is the following.
When conditions are true for a Buy..CLOSE all open sell orders if any that have magic number (external variable). Verify all have been closed.
The code should send a buy with current symbol and external variable for lots and external Magic number variable.
Then it should verify that order was opened. When/if order hits external variable Take profit the half of the buy order should be closed and the other half is left open. NO OTHER BUYS get opened, even if there are NO open orders.
When SELL conditions are true then CLOSE all open buy orders with same magic number as above(should only be 1 if any). Verify all orders have been closed.
Then send a Sell with current symbol and external variable for lots and external Magic number variable.
Then it should verify that order was opened. When/if order hits external variable Take profit the half of the sell order should be closed and the other half is left open. NO OTHER SELLS get opened, even if there are NO open orders.

and it continues in both directions. Simple enough.
Open, confirm, close half if TP…close all and repeat in opposite

We are in need of the following Java Script for our Questions &amp; Answers page. Please note the following information.

Our site is set up using CSS style sheets

Default Font

JavaScript programming for Adobe Acrobat 8.0+

We would need source codes and files for the application, so we could do some additional changes or adjustments. As stated in the description, it will be possible to change some values in the scrolling lists. They are so specific that some particular administration should not be developed. It would be easier if we can edit it ourselves in the source codes.

Criteria:
- Price
- Delivery time (by May 7th if possible, May 19th at the latest)
- References

Description:
——————————————————–

1. use active opened PDF file in Adobe Acrobat; if there is no opened document, use Open PDF dialog with browse

2. Input variables in form:
NR = Number (01-99) (default: empty)
TY = Type (Re;3K;1K;V1;V2;N1;N2) (default: empty)
CO = Country (CZ;SK) (default: empty)
PR = Proof version (1-9) (default: empty)
DIR = Directory for files (Internal=INT|External=OUT) (default:
internal)
Editable (Yes|No) (default: Yes)

3. Save every page from opened PDF as single page PDF
- if switch Editable is Yes, than every single page PDF should be “Enabled for Commenting and Analysis in Adobe Reader”
- if switch Editable is No, than every single page PDF should NOT be “Enabled for Commenting and Analysis in Adobe Reader”

4. New files should be saved into directory and filename on variables:
Directory path construction:
\servercustomerproof%DIR%%NR%-%TY%-%CO%Proof-%PR%
Examples:
NR=11; TY=Re; CO=CZ; PR=1; DIR=INT
\servercustomerproofINT11-Re-CZProof-1
NR=12; TY=3K; CO=SK; PR=2; DIR=OUT
\servercustomerproofOUT12-3K-SKProof-2

5. Final filename construction:
%NR%-%TY%-%CO%-P%pagenumber%
Examples:
NR=11; TY=Re; CO=CZ; PR=1; DIR=INT
11-Re-CZ-P01.pdf; 11-Re-CZ-P02.pdf; 11-Re-CZ-P03.pdf; 11-Re-CZ-P04.pdf …

NR=12; TY=3K; CO=SK; PR=2; DIR=OUT
12-3K-SK-P01.pdf; 12-3K-SK-P02.pdf; 12-3K-SK-P03.pdf; 12-3K-SK-P04.pdf …

6. Other remarks:
%pagenumber% = Page number in source multipage PDF document

Source multipage PDF document may contain non-continuous page numbering!
e.g.: pages in PDF: 2,3,6,7 > filenames: XXX-P02.pdf, XXX-P03.pdf, XXX-P06.pdf, XXX-P07.pdf

For pages 1-9 there should be used 0 for correct filename sorting.
There is not expected more pages than 99.

If there is already file with the same name in directory, it should be overwritten without asking.

Main part of directory path (\servercustomerproof) should be editable in JS source code by our admin.
Values: Type, Country and Directory should be editable in JS source code by our admin.
Value Number will be written by user, it should be checked for correct input (only number from 1 to 99)

Note: English is not my mother language.

I need a very simple application in c/c+.

The interface will have three boxes. In the firt box, there should be space for four lines and will be where I paste Name, address and zip-code. Sometimes three lines, sometimes four lines. The next text-box will be a single line where social security number will be pasted, i.e.: 140256-2289. The third text-box is like the first box with space for up to four lines. This is doctors name/address. The three boxes is called:
‘Borgers navn og Adresse:’ ‘Personnummer:’ ‘L