Results 1 to 3 of 3
  1. #1
    Platinum Lounger
    Join Date
    Feb 2001
    Location
    Yilgarn region of Toronto, Ontario
    Posts
    5,453
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Creating a graphical representation (vb6 - all programming languages)

    How do you go about creating a graphical representation of a set of modules?

    I've inherited 63 VBP files - 63 module source files if you will, and have managed to compile each one of them, resetting missing references as I go.

    I've learned that WinDev, WinReg, WinMsg and WinError are basic modules, but that ExPos, for example, depends on WinReg, WinMsg and ExUtil.

    I wish I'd made painstaking notes as I went.


    I figure I need the dependency diagram so that I know to recompile W, X Y and Z if I ever recompile Q.


    I'm considering printing each VBP file name on a small chit, and re-arranging these (as I work my way through the set of VBP files again) on the office floor, after which I'd type them up into what I HOPE is going to be a tree-structure.

    I believe that there's always a better way than the first one I think of.

    What did you do last time you inherited a serial collection of modules and had to work out dependency?

  2. #2
    Super Moderator jscher2000's Avatar
    Join Date
    Feb 2001
    Location
    Silicon Valley, USA
    Posts
    23,112
    Thanks
    5
    Thanked 93 Times in 89 Posts

    Re: Creating a graphical representation (vb6 - all programming languages)

    This sounds like a wheel not to reinvent. You could always go shopping... <A target="_blank" HREF=http://www.vbxtras.com/Default.asp>http://www.vbxtras.com/Default.asp</A>

  3. #3
    Platinum Lounger
    Join Date
    Feb 2001
    Location
    Yilgarn region of Toronto, Ontario
    Posts
    5,453
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Creating a graphical representation (vb6 - all programming languages)

    >This sounds like a wheel not to reinvent. You could always go shopping... http://www.vbxtras.com/Default.asp

    Wheel-spoken (grin!) It is indeed a wheel not to reinvent. Thats the reason for my post.

    In general, there are very few source of succour for the "project"-like end of things - how to set about errecting a project out of rubble.

    I checked the site - very rich, thanks - and added it to my list, subscribed to the newsletter. I didn't see anything that shrieked at me "Build a tree structure diagram", so I'll continue to plod along, making slow progress.

    I did cannibalise an existing Word97/VBA project to privide a batch-compile-and-documentation-and-registration utility. If nothing else that will assist me in the process of isolating projects and make a start on the documentation process.

Posting Permissions

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