Actually it is easier with AB. even though I run AB on 4 computers, and some have more than 1 instance running simultaneously. Yes, I dont have a need to edit two copies of these files simultaneously on more than 1 computers. And if you are a single person operating multi computers/instances of AB, you can like the majority do that pretty much without drama, especially when another poster has alerted us the availability of power folder. 1. I use mounting of network drives for all computers to access AFL files 2. I use importing/exporting of watchlists to synchronise between instances of AB who are running concurrently. 3. I file synchronise the AB information files, and the database files if I need to. 4. I get each computer to automatically download data. As far as I can see, I do everything that you talk about with no problem, What I dont do, is simultaneouly edit my charts over many computers because I can only be at one place at a time. Of course, one can add bells and whistles, but I rather see Tomasz spending his time focusing on his core development. And Auto file synchronsiation, as the subject name rightly suggests should belong to a 3rd party utilities domain.
_____ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of progster01 Sent: Sunday, 13 January 2008 3:38 AM To: [email protected] Subject: [amibroker] auto file synchronizers (was Re: Extremely tired of this.) --- In [EMAIL PROTECTED] <mailto:amibroker%40yahoogroups.com> ps.com, "paultsho" <[EMAIL PROTECTED]> wrote: >it is no different than using word. >unidirectional means you cant update 2 copies >of the same file separately. Good example. In Word, if you update two text documents separately, you are left to choose between them at the time when you resync. (And if you want, you can shove one of them out of the way somewhere and be able to display/edit it later without problems.) However, in Word, the document you choose to distribute at sync time does not affect the subsequent operation of the program or display of other documents on either system. With AB, in some circumstances, that is not the case. So, respectfully, it is different than using Word. Maybe you've never encountered this aspect of AB, or perhaps the procedures you've which you've gotten into the habit of following help you to successfully avoid it. It's my opinion that it would be a great advantage if all copies of AB were "equal" at all points in time, with out a need to consider the multi-machine set as "fragile" the from the moment a single machine departs from it until the time it is carefully resynced (without allowing changes on any of the other machines in the meantime). I think it is fair for you to say that you, personally, don't feel a need for improvement in this area. However, I don't think it would be factually accurate to say that AB acts "just like all other software" (my words here) in this respect. It does not.
