Community
Participate
Working Groups
The following is from EC but has been raised by others. The general idea seems sound. This is a PR in the desktop since the desktop is in the right position to know when the platform is up and a refresh can be done. If the resources plugin were to do this, it could cause a build and then we could end up with UI plugins being activated before the UI is actually up and ready to go. Basically this is a check and refreshLocal before entering the read/eval loop in the UI. ----------------------- EC post For those of us using external CM tools please add a preference entry to refresh from local on startup. The CM system replaces/adds files to the file system and I wuld like to know that when I open WSW it is current not holding on to old metadata and as a result generating compile errors that are not in the real source files. Even better would be to notice when file modification times change from what you have in your metadata and prompt the user to allow a refresh at that time. I presume these was not done to improve boot time, but I would rather have boot take an extra 30-60 seconds and get the correct results. After all, machines keep getting faster and someone can always turn off the option. NOTES:
As a command line argument that Core would support for all applications? The UI part of this feature request is possible. We should consider carefully when this method should be called. An inconsistent view of the resources is a source of problems for the user interface.
A command-line option (-refresh) already exists. This causes a refreshLocal to be done on the WorkspaceRoot at startup.
Need to add preference.
Dup. Pref added in 20020515.
