You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should encourage people to use the plate-model-manager, as @michaelchin is doing for the notebooks, but we should also adapt the existing DataServer object to use plate-model-manager under the hood so that we don't upset existing GPlately users. We can always deprecate DataServer in the future if we need to.
@michaelchin - I'm not sure if this is already an option, but can plate-model-manager download files to the user's cache directory?
The text was updated successfully, but these errors were encountered:
We should encourage people to use the plate-model-manager, as @michaelchin is doing for the notebooks, but we should also adapt the existing DataServer object to use plate-model-manager under the hood so that we don't upset existing GPlately users. We can always deprecate DataServer in the future if we need to.
Yes, this is a good idea. Another option is to keep both for a while. The plate-model-manager is new and maybe have some bugs. If we keep DataServer as it is, users have the option to fall back to DataServer if the plate-model-manager does not work for them.
We should encourage people to use the
plate-model-manager
, as @michaelchin is doing for the notebooks, but we should also adapt the existingDataServer
object to useplate-model-manager
under the hood so that we don't upset existing GPlately users. We can always deprecateDataServer
in the future if we need to.@michaelchin - I'm not sure if this is already an option, but can
plate-model-manager
download files to the user's cache directory?The text was updated successfully, but these errors were encountered: