Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
New stuff gets included
Message
From
17/11/2004 06:39:20
 
General information
Forum:
Visual FoxPro
Category:
Project manager
Miscellaneous
Thread ID:
00960731
Message ID:
00962107
Views:
8
[snip]
>>My own method is:
>>
  • Each module (an app) has its own pjx in its own map.
    >>
  • All prg's, vcx's, etc. are 'owned' by a module and ideally reside in the specific map.
    >>
  • I switch to the map to change things.
    >>
  • There is a special program (b.prg) that builds an app based on the only pjx in the current map. This b.prg first manipulates SET PATH, since it must refer to no other maps at all.
    >>
  • BUILD comes with a messagebox. There I answer 'Ignore all'.
    >>The result is a pjx/app that has nothing else inside than what is in that map.
    >
    >You might think about storing this metadata in the User memo of the project, although it would be subject to loss on project corruption. So backups and/or using an external XML document might be appropriate.

    I know of the existence of the User field, but what kind of metadata are you thinking of, and how could it be used?

    >>You might wonder why I started this thread then. Well, I also bear responsibility for a legacy application. It is completely impossible to restructure that stuff. Both your and my solution are impossible to implement in that legacy app. Here's an anecdote: Just this morning betatesters were testing the new version of that application. Guess what, an error occurred exactly because a prg had sneakilly got included in an app where it should not have got included. The routine also resides in the exe and uses an included table. That table is not known to the sub-app, so it could not be found. Bang..
    >
    >And you are also going to be susceptible to bugs going the other direction. If you mismark something as exclude and that functionality really does get called along some execution thread you'll hit program not found errors at runtime.
    >
    >Supporting legacy code that wasn't designed with optimal packaging is problematic, but it's not fundamentally VFP's fault/problem. It is good that VFP is hookable enough to create workarounds to these sorts of problems.

    The vfpteam has never been heavilly accused by me of causing the problem, at least that was not my intention, as I think I have made clear earlier. And indeed they have built hook facilities that can probably be of help here, as I have said before. Hope this is one more statement that should make clear my standpoint. I think we don't even have to agree that we disagree. :)
    Groet,
    Peter de Valença

    Constructive frustration is the breeding ground of genius.
    If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
    Let's develop superb standards that will end the holy wars.
    "There are three types of people: Alphas and Betas", said the beta decisively.
    If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
  • Previous
    Next
    Reply
    Map
    View

    Click here to load this message in the networking platform