Hi All,

I downloaded two new indicators this morning from the download area.

When I attempted to import them I was notified that I already had indicators with those names.

If the latest posting update is by the original auther? I understand using the same name.

If another member posts their version of an existing indicator, Please assign it a unique name!!!

Although "volumestop_v3" and "SMI2 no repaint" are titled differently, the indicator names are the same.

I was forced to rename the existing indicators before importing the new ones to prevent deletion of the original indicators.

Thanks for listening,

RJay

RJay 

Hi All, I downloaded two new indicators this morning from the download area. When I attempted to import them I was notified that I already had indicators with those names. If the latest posting update is by the original auther? I understand using the same name. If another member posts their version of an existing indicator, Please assign it a unique name!!! Although "volumestop_v3" and "SMI2 no repaint" are titled differently, the indicator names are the same. I was forced to rename the existing indicators before importing the new ones to prevent deletion of the original indicators. Thanks for listening, RJay

Thanks, RJay... you got me off my butt to post coding standards... posted as a Sticky in Programmers' Paradise... comments and suggestions welcomed!

I'll get some pictures together to make it clearer to understand... and I imagine there will be some modifications as I hear from others.

I did think about that and my rational is most users just want the new indicator to overwrite the old one since they are not programmer. A select few( say a hardcore programmer) will want to preserve the old version for the safekeeping purpose. Balancing between the two I will rename the indicator if there is a significant change otherwise it stays the same.

if you update an indicator you should give it a diff. name (means to give the version number not only in the .zip but also as real indie-name via "save as .... VolStop_V3_3 iE) - i think its really important!
We had this game with our DMAs + also sharky knows storys about this.
if i integrate indies in charts +/or strategys and mess that up with importing + overwriting - that brings really trouble.
if you have diff. versions everyone can decide if he deletes the old ones. that hurts no one.
if the stuff gets overwritten this can cause a pretty chaos.

cory, it is still a good idea to include the version numers so that anyone using it knows which they currently are using... of course if it is just for yourself... no one else cares... but if you are sharing it, and you post a chart... and someone else has the same chart, same TF but it doesn't look like yours, it is easy and quick to resolve by checking the version number... v1_3 where 3 is changed from 2 on minor changes, etc.

I posted suggested coding standards in the Programmers Paradise forum. I wrote these after the nightmare of the flurry of coding activity in June... a sharky indicator... no one knew what they had and it was very confusing and very frustrating for everyone involved.

max-td 

if you update an indicator you should give it a diff. name (means to give the version number not only in the .zip but also as real indie-name via "save as .... VolStop_V3_3 iE) - i think its really important! We had this game with our DMAs + also sharky knows storys about this. if i integrate indies in charts +/or strategys and mess that up with importing + overwriting - that brings really trouble. if you have diff. versions everyone can decide if he deletes the old ones. that hurts no one. if the stuff gets overwritten this can cause a pretty chaos.

max... RJay.. and others... when you have time... please have a look at the coding standards and give your thoughts

Coding Standards - DRAFT 2009 09 30 Here is my first cut at suggested coding standards for NexusFi (formerly BMT). I welcome comments and suggestions... following these simple guidelines will save us all a frustrating experience such as RJay posted today. 1. If you are modifying someone …

Saroj 

max... RJay.. and others... when you have time... please have a look at the coding standards and give your thoughts Coding Standards - DRAFT 2009 09 30 Here is my first cut at suggested coding standards for NexusFi (formerly BMT). I welcome comments and suggestions... following these simple guidelines will save us all a frustrating experience such as RJay posted today. 1. If you are modifying someone …

Saroj,

Lately, I have been tagging anything I work on with my ID. (RJay).

EX. (jtRealstats_RJay, BetterVolume_RJay.)

If versions are involved, It look like this (jtRealstats_RJay2, BetterVolume_RJay2.)

RJay

I prefer a group-wide standard because everyone will recognize it and understand it.. well.. at least you are indicating something...

I'll add in the idea of including a mneumonic to the indicator and file name.. great idea.