Results 1 to 2 of 2

Thread: VDF Studio Workspace Profiler

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Join Date
    Feb 2009
    Location
    Adelaide, South Australia, Down under
    Posts
    2,499

    Default VDF Studio Workspace Profiler

    Hi Data Access,

    I was thinking the other day, that if I was DAW, I would be really
    interested in how the VDF product is used.

    On the same side, I think that many developers are happy to tell you.

    So I thought of a VDF Studio Workspace Profiler. This could be a stand
    alone program, perhaps in the start menu, or in the menu of the studio
    that can be used by the developer but perhaps also by DAW support.

    It could collect things like:
    - VDF Version number Serial #
    - O/S
    - Other VDF versions installed on the machine
    - Workspaces per version of VDF
    - Per workspace, # tables in filelist per driver, # components per type,
    date of last compile
    - Usage of certain functions of the studio like macro's

    The program could present a report on the screen, for the user to look
    at, and then press 'Send to DAW' or perhaps Save as HTML.

    Anyway, just a thought, worth typing in...

    Cheers,
    Marco

  2. #2
    Join Date
    Feb 2009
    Location
    Dallas, TX USA
    Posts
    1,385

    Default Re: VDF Studio Workspace Profiler

    Marco:
    Really like the ideal. Additional info would be the version of any
    drivers being used - ie: pervasive.SQL connecitity Kit 5.0.0.39 License
    #xxxxxx.

    Mark

    Marco Kuipers wrote:
    > Hi Data Access,
    >
    > I was thinking the other day, that if I was DAW, I would be really
    > interested in how the VDF product is used.
    >
    > On the same side, I think that many developers are happy to tell you.
    >
    > So I thought of a VDF Studio Workspace Profiler. This could be a stand
    > alone program, perhaps in the start menu, or in the menu of the studio
    > that can be used by the developer but perhaps also by DAW support.
    >
    > It could collect things like:
    > - VDF Version number Serial #
    > - O/S
    > - Other VDF versions installed on the machine
    > - Workspaces per version of VDF
    > - Per workspace, # tables in filelist per driver, # components per type,
    > date of last compile
    > - Usage of certain functions of the studio like macro's
    >
    > The program could present a report on the screen, for the user to look
    > at, and then press 'Send to DAW' or perhaps Save as HTML.
    >
    > Anyway, just a thought, worth typing in...
    >
    > Cheers,
    > Marco


Similar Threads

  1. Replies: 7
    Last Post: 26-Aug-2009, 07:04 PM
  2. Studio workspace problem
    By Ditte in forum Windows Applications
    Replies: 4
    Last Post: 10-Sep-2008, 03:22 PM
  3. Studio doesn't load selected workspace
    By ReneJungmann in forum Windows Applications
    Replies: 2
    Last Post: 16-Jul-2008, 07:13 AM
  4. Importing VDF 8.3 workspace to VDF 11.0
    By Tod Brannen in forum Windows Applications
    Replies: 1
    Last Post: 15-Jun-2005, 01:24 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •