- Posts: 47
- Joined: Sun Mar 27, 2016 6:12 pm
Sun Jun 10, 2018 5:52 pm
Resolve has a Collaboration Mode. Maybe make a subset of this function.
BMD sets up a Error_Logging_Server (which works as a silent editing partner).
One logs into this special server - then the User (or several) continues on, working on their project.
When a Resolve error or crash happens, the logging data is automatically captured.
BMD can setup air-raid sirens, or huge multi-colored flashing lights, or whatever alarm system that is suitable - to inform the programmers - that 'something' has happened...
This colloboration effort would save time for the User, in making a zip file, trying to find some place to store it and then posted an error notice on the BMD forum...
***
If no errors occur during a session, the logged data for that particular User - is simply flushed out.
This Error_Logging_Server - could at first, be set up to handle - say 10 Users - and scaled-up, if necessary.
With the Error_Logging_Server - BMD's programmers would have live, instant and a complete data trail - as to the cause of the 'error'.
***
Say at some point - there are 100 Users logged into the Error_Logging_Server. Everyone works on their projects, and there are NO warnings, flags, errors or crashes - then the Beta cycle is finished...
Time to release a STABLE version.
The Error_Logging_Server could also be used on a Stable version - by Users who might find, expose and experience a rare bug...
***
As mentioned - this is just a procedural idea. Whether this process is possible - people with more technical knowledge and insight - can argue its merits (if any)...
kc
BMD sets up a Error_Logging_Server (which works as a silent editing partner).
One logs into this special server - then the User (or several) continues on, working on their project.
When a Resolve error or crash happens, the logging data is automatically captured.
BMD can setup air-raid sirens, or huge multi-colored flashing lights, or whatever alarm system that is suitable - to inform the programmers - that 'something' has happened...
This colloboration effort would save time for the User, in making a zip file, trying to find some place to store it and then posted an error notice on the BMD forum...
***
If no errors occur during a session, the logged data for that particular User - is simply flushed out.
This Error_Logging_Server - could at first, be set up to handle - say 10 Users - and scaled-up, if necessary.
With the Error_Logging_Server - BMD's programmers would have live, instant and a complete data trail - as to the cause of the 'error'.
***
Say at some point - there are 100 Users logged into the Error_Logging_Server. Everyone works on their projects, and there are NO warnings, flags, errors or crashes - then the Beta cycle is finished...
Time to release a STABLE version.
The Error_Logging_Server could also be used on a Stable version - by Users who might find, expose and experience a rare bug...
***
As mentioned - this is just a procedural idea. Whether this process is possible - people with more technical knowledge and insight - can argue its merits (if any)...
kc