|
1-2 of 2 messages
|
Page 1 of 1
|
|
Press Release: TR and Log Windows Begin Talks
|
Reply
|
|
Anonymous post on May 17, 2001
|
Mail this to a friend!
|
The task of re-writing all this in Windows is massive, and you have a long way to go before catching up to where WriteLog is now.
WriteLog is an excellent and adequate program, but it unfortunately copied the same basic ins/plus data entry methodology as CT and NA. In complex exchanges such as the SS, you still have to enter the number, precedent, call, check and section; all in separate fields. TR�s strongest and most advertised feature is its ability to parse this information out of a single string, giving the op the flexibility of entering it in any order. I�m sure this feature could be added to WriteLog much more quickly than a total Windows re-write of TR. If this were done, you would be toast (and you better pray your competitor never thinks of this).
Ideally, nobody�s existing user interface would be copied. The best features of all current contest programs would be integrated and enhanced into a new and distinctly different product that would be simple to configure, learn and use. Rather than have one field to enter the callsign and another for everything else, the entry can all be done in a single field. The horrid TRUE/FALSE configuration issues also need to come out, as well as the function keys that change their CW message depending on this, that and the other. In short, don�t copy the TR interface: simplify it.
|
| |
|
Press Release: TR and Log Windows Begin Talks
|
Reply
|
|
by W4PC on June 11, 2001
|
Mail this to a friend!
|
Emailed on the Log Windows and TR Log Reflector today:
Thanks to everyone who filled out the survey, here's the results and the
direction we are going to take.
This is the information is the results that was compiled after all the
abusive, condescending and childish remark comments from some of the surveys
were removed. Those survey's were not counted and that accounts for about
10% of the total number of survey's.
1. Is it technical feasible to do? This is an unequivocal yes. It is
possible to take technology from Log Windows and TRLog and move them into a
32 bit program, as well as doing a Ring 0 process based device driver to
handle all the LPT and DVK, etc., I/O based functionality.
2. What do the users really want. From the survey, many of you just want a
version of TRLog that will run correctly in a DOS Window under Windows
(mostly for CW or DVP keying) so you can multitask with TRLog and Windows
apps. Since the architecture of DOS and Windows doesn't allow this, it's not
possible, but it's what you want.
3. Many of you want every feature in TRLog into a TRLogwin on the first
release. Since Tree has been coding TRLog for a number of years, it would be
impossible to have everything TRLog DOS has in TRLogWin 1.0 in a reasonable
amount of time.
4. Tree made the comment, "I doubt many current TR users will really like the
windows version - at least at first". Since most software development looks
for 1/2 to 2/3rds of the initial purchases to be upgrades, it doesn't look
like the market is there. In fact, talking to many of you at Dayton, Atlanta
and Dallas hamfest, this is the case. Many of you don't want to upgrade or
have to pay for it.
Since it would take $100,000 - $150,000 to develop this product correctly and
the market seems to be saying they wouldn't embrace a Windows version of
TRLog, I've decided at this time not to begin the development of the product.
I will however, continue to watch the TRLog reflector for a time that may be
more 'ripe' for a Windows contesting program, that would be the best product
for it's market.
Rick - W4PC
|
| |
|
Email Subscription
You are not subscribed to this topic.
Subscribe!
My Subscriptions
Subscriptions Help
Check our help page for help using
Forums, or send questions, comments, or suggestions to the
Forums Manager.
|
