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
I've emailed before about recovering all partitions and I understand that was not a great idea. Now I raise the question, If it is possible to recover the partitions that are listed as recoverable instead of having to individually filter through each one. I am confident that each partition contains important date because as I am looking for a variety of file types on this rescue image. If you could lead me to the solution or a better solutions that would also be appreciated. Thanks you in advance.
The text was updated successfully, but these errors were encountered:
I have not conducted a deep comparison on the toolkits yet. I guess probably it would be better to choose either Qt or wxWidgets to keep it cross-platform.
A web based interface seems a cool idea though, I'd need to investigate it further.
Just throwing the idea out here: a master server process running in the background, that can receive events from clients either CLI or GUI. You'd have jobs that can be suspended, and once finished you can extract stuff from it easily without having to keep your python process open. This would allow a good separation between the core and the interface. But that's probably out of scope for an open source project that was not designed like that from the start. Small incremental changes sounds better here.
I've emailed before about recovering all partitions and I understand that was not a great idea. Now I raise the question, If it is possible to recover the partitions that are listed as recoverable instead of having to individually filter through each one. I am confident that each partition contains important date because as I am looking for a variety of file types on this rescue image. If you could lead me to the solution or a better solutions that would also be appreciated. Thanks you in advance.
The text was updated successfully, but these errors were encountered: