Posted by Robert G Laurin on December 24, 2008 at 06:55:02:
I am getting very frustrated ! I am also getting old and I forget more and more.
Somethings that I do not forget is stuff I didn't learn yet. After years of writing a gazillion lines of Comet code I find myself unable to compile it.
It is no secret that I am a CED die hard. Well I do try, I've been toying with UltraEdit for two years now. And recently I wrote a complete project on it (Yes! I used the project option - which is not perfect yet and requires user tweaking). But to this day, I do not know how to write an ! //IB// command line.
Oh Yes, I can copy an //IB// command line, but I cannot write a new one. I checked the IB documentation and it shows only the legacy (aka CED) command line options. And I do not remember ever seeing the complete documentation with real-life example other than compile "This.IBS" into "That.Obj" with all default options.
So for most of the last two years, most of my non-default compiles have been done through a compile script in CED. Somehow I feel that this beats the purpose...
So..
This aging dinosaur would like to move to the 21st century before it is over. Can someone at Signature put meaningful Documentation in the Documentation? (By the way, where's the "Documentation" on Signature.net nowadays?)
I am afraid, very afraid, that I will be pointed into an old software announcement somewhere (same software announcement that cannot be successfully searched on Signature.net).
In the meanwhile, I need a compile listing of my .IBS source... (I guess I'll "R CED")
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.