Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
I don't like the first graph either. It is to jagged so that one is easily lost in it.
But I think that losers (SL hit) are not that interesting in this case, since we are now concentrating on the money on the table... What about omitting the losers?
Just keep it simple... Two lines, one realized, one potential...
IDEA! ok i know were working on getting everything working for the normal features that we have outlined, but if i dont get this out it might get lost in the space that is my head!
i think an updater needs to be built into this importer.. so it will become and importer/updater app.. when new journal versions come out, all one will have to do is load up the old journal with all of the users trades, and then load up the new version of the journal, and it will import all the data safely so the end user doesnt have to worry about any mistakes complications! this would also help in diagnosing issues here because we could eliminate the end users error of 'mismigration'..
what you guys think?
this sounds pretty solid to me, but i also dont use all of the graphs as much either..
dont believe anything you hear and only half of what you see
Hmm, seems to me like an error in date.
Either there is a mismatch in the locale used to export the csv and the one selected in the importer or there is some malformed input.
Could you please send me a sample export file so that I am able to see how the dates are formatted?
hey @petrmac, im working on the text file for ya.. are you taking the description/name from NT? that way we can be consistent? also is this just for currencies?
dont believe anything you hear and only half of what you see
Cool, that helps.
I have there just two entries for testing... so the description doesn't matter. You can easily use the ones from NT.
As for the list... no not just currencies, it is needed for all instruments if you for some reason want to import file that is in currency format (i.e. not points).
So put there anything you like...
ok ill use the NT description as the standard naming scheme them.. i am going to include the currencies that i have currently added(the most popular and a few extras) and then ill add the rest of what we have built into the journal as default. does that sound good? and like the journal, users and add their own instruments to suit their needs as they like beyond the defaults?
dont believe anything you hear and only half of what you see
The issue pointed to is fixed.
I improved the error handling and thanks to @madLyfe there are already some instruments in the list. The importer can now read trades with them.
USAGE comment:
be careful when deciding the delimiter and the locale. Ninja will export the data based on the Windows regional settings and that can make a huge difference in the format of almost everything (decimal numbers - "." or ",", dates).
If there is a locale that is gravely needed, just drop me a line and I will add it. This is not a big change.