ChimneySweep Release-X Features Discussion

We are currently evaluating features for a possible "ChimneySweep Release-X"
that would follow the current Release 5.1 which has now been on the market
for nearly 3 years.  During that time, enormous changes have taken place
not only in the Windows operating-system but, as we all know, with Paradox
itself.  After such lengthy delays in the release cycle (most of them
caused by external events not of interest here)... the question is, what
should the forthcoming release contain.

Based on the in-progress (and in most cases nearly-complete) code base that
we have for this product, this "Release-X" ... which would undoubtedly be
the final one ... might contain the following.  Your comments are welcome.

(1) 16-BIT SUPPORT IS GONE:  No question about that.  Holding on to 16-bit
and 32-bit parallel compatibility proved to be a serious error as we held
on to it as a keystone product point long after its market usefulness had
ceased.  Support for 16-bit software is virtually gone already in Windows,
and it has quite clearly long outlived its usefulness.

(2) THE SCHEDULER IS GONE:  Windows Vista put a stake of holly through the
heart of the scheduler revision code, which was to be a Windows system
service, by eliminating the ability of a system service to interact
directly with the GUI.  However, Vista already provides an excellent
scheduler of its own.  We don't need two.

(3) JOB AND JOB-OUTPUT MANAGEMENT:  The plan is to store job information and
an output-catalog in two XML-formatted repositories.  Job output also would
initially be an XML, not flat-text file, which would then be transformed
into an HTML-based output.  A third schedule-repository originally
contemplated is gone.  Jobs and output would be filed by GUIDs.

(4) FURTHER SIMPLIFICATION OF THE JOB CREATION PROCESS:  "Just tell me where
the tables are.  Or, let me figure them out from the alias-list.  Give me
passwords if I determine that I need them.  All the other options can be
default."


----
ChimneySweep(R): Fast(!) table repair at a click of the mouse!
http://www.sundialservices.com

> During that time, enormous changes have taken place not only in the
> Windows operating-system but, as we all know, with Paradox itself.

sorry, but I gotta ask.. the last version of Paradox tables was released in
1997, and the last real "new" version of Paradox software hit the streets in
2000.. what, pray tell, has happened in the last three years that
constitutes an "enormous change" ??


--
Steven Green - Myrtle Beach, South Carolina USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards
"Sundial Services" wrote in message

> We are currently evaluating features for a possible "ChimneySweep
> Release-X"
> that would follow the current Release 5.1 which has now been on the market
> for nearly 3 years. During that time, enormous changes have taken place
> not only in the Windows operating-system but, as we all know, with Paradox
> itself. After such lengthy delays in the release cycle (most of them
> caused by external events not of interest here)... the question is, what
> should the forthcoming release contain.
>
> Based on the in-progress (and in most cases nearly-complete) code base
> that
> we have for this product, this "Release-X" ... which would undoubtedly be
> the final one ... might contain the following. Your comments are welcome.
>
> (1) 16-BIT SUPPORT IS GONE: No question about that. Holding on to 16-bit
> and 32-bit parallel compatibility proved to be a serious error as we held
> on to it as a keystone product point long after its market usefulness had
> ceased. Support for 16-bit software is virtually gone already in Windows,
> and it has quite clearly long outlived its usefulness.
>
> (2) THE SCHEDULER IS GONE: Windows Vista put a stake of holly through the
> heart of the scheduler revision code, which was to be a Windows system
> service, by eliminating the ability of a system service to interact
> directly with the GUI. However, Vista already provides an excellent
> scheduler of its own. We don't need two.
>
> (3) JOB AND JOB-OUTPUT MANAGEMENT: The plan is to store job information
> and
> an output-catalog in two XML-formatted repositories. Job output also would
> initially be an XML, not flat-text file, which would then be transformed
> into an HTML-based output. A third schedule-repository originally
> contemplated is gone. Jobs and output would be filed by GUIDs.
>
> (4) FURTHER SIMPLIFICATION OF THE JOB CREATION PROCESS: "Just tell me
> where
> the tables are. Or, let me figure them out from the alias-list. Give me
> passwords if I determine that I need them. All the other options can be
> default."
>
>
> ----
> ChimneySweep(R): Fast(!) table repair at a click of the mouse!
> http://www.sundialservices.com