작업 종료됨
![](https://c.mql5.com/i/avatar/avatar_na2.png)
명시
I'm looking for a MQL4 programmer for long-term cooperation. The first Test Job. This document describes the TEST JOB.
FIFO is to be adhered, so trading server does not kick out orders for FIFO error. For the planned Cluster to evolve, we embed hooks/pipes/common file paths - whatever is available/ preferred so that multiple accounts may interoperate through shared data/information.
It has three parts:
1. The first part is to code a few trading related function calls.
2. The second part is to write a Block of Codes for saving trades related data sets on to files for subsequent optimization and interoperability between accounts (owned by same owner and running under FIFO).
3. The third part is to write only a structural block of a Foundation EA with the standard Nine(9) Code Blocks for External Inputs; Declarations of Internal Variables; Init; DeInit; Stop/Exit EA; a Housekeeping Block(saving in disk files, the trading history, alerts, errors, logs etc. for future use); a Block to Look at Chosen/ Required variables at N-ticks;a Block to Decide on Trading Actions; a Block for the Trading Actions; a Do No Trading Action Block(here wait for next tick or finish any unfinished housekeeping tasks). Additionally, each code bock will have a timer to gather execution time for that blockand it will be printed while debug or may be turned off. The EA will have a Symbol or Instrument Rack, which means it will launch or work on N (2 to 7 symbols as inputted) symbols when launched. EA will launch from a dummy/proxy chart (other than any symbol on the Instrument Rack); close all other charts making sure there are no orders/positions in those symbols; and reopen the instrument rack’s symbol charts on M1 and attach the EA to all of them. EA will work on multiple time frame candles data internally (as inputted into EA - up to 5 – M1, M5, M15, M30, H1) irrespective of chart candle period being manually changed on the MT4 platform for looking at the screen. EA will open a dashboard/display window we call EA Information Tableshowing the Instrument Rack Summary Information Data on the launching dummy/proxy chart (illustration given below). EA will open on each active symbol chart a dashboard/display window (for that symbol) what we call Symbol Local Trades Table(illustration given below). The EA runs simultaneously on all the symbols using same logic but with different (symbol specific) input parameters and / or internal calculated variables.
Please put in copious amounts of commented (//) lines as notes and comments.
The above codes will be acceptedby visual review and error free compilation and ability to just launch and navigate/operate the Foundation EAproperly on a FIFO DEMO account on an MT4 platform without doing any real trading actions but showing that the EA is running and freewheeling and can do the housekeeping and there is stable flow through the various code blocks.
Budget, acceptance, funds release and project time/pace.
· I am Septuagenarian; decades ago, have programmed in few languages and did so very efficiently. Now, I am rusted with writer’s block, but I can read, understand, review and debug mq4 codes visually, logically and can provide constructive and useful feedback through my collaborative contribution into the project. Receiving ‘in-progress-mq4 files’ as often as MyFCC (my freelance cooperation coder) sends me but not to exceed a gap more than a calendar week is a requirement. Being Septuagenarian, I am slow and cautious. I must try not to propagate gaps / errors / blind spots / lack of understanding. Do little by little but do it correct. I hope to get this cluster done on a small budget by bootstrapping the 1 stEA to do the 2 ndEA so on so forth.
· My total long-term budget is 30 x $108 = $3240; of which $216 is allocated to this First TESTas initial commitment to get to know MyFCC personally, and then allocate 27 x $108 per EA = $2196 to the end and then a final closure bonus of $108.
· After First TEST, I shall commit $108 per EA and one EA at a time. Every subsequent EA will appear simpler and be completed easier or faster with more fun and more aha moments and joy, if we do the First TEST - FOUNDATION EA as the proper foundation.
· I keep my MQL4/5 community account at a level of $216 to release the payment per EA amounts on final acceptance of each EA. Progress payments, if any, they shall be no more than $54 each and must be linked to some progress marker.
· I like quality work; being patient, expecting steady progress in reasonable time windows. Example: 36 days for the First TEST-Function Code Blocks with FOUNDATION EA; then on the Cluster 1 stEA (to be named ARENA) 27 days, 2 ndEA (to be named BLINDMAN) 18 days, 3 rdEA (to be named CARINA) 24 days so on so forth reaching a limiting turnaround time of say 9 days per EA towards the end of the cluster.
If my description is not clear, or you have question or query, please ask and I shall try to expand and explain with examples or illustrations.