Open Kadijah18 opened 6 years ago
@Kadijah18 I think that you may misunderstand the purpose and function of the XML import. Currently, RaiderPlanner stores its user data and state information in a binary serialized file. It is possible to export this to XML, but there are currently no other export options. This means that the idea of importing different file types would mean adding support for importing file types which the application cannot currently create. I suspect that it might be reasonable to expect that a user could create a CSV file using a program or script (for example to transform data from some other format) that we could then import. However, for that to happen we would need to document the support import format. In addition to all of that, I would like to see us move from the current binary data file format to a JDBC-based database back end (issue #12). That will almost certainly have an impact on the file formats that we would be able to reasonably support. I recommend that we wait a bit on this particular issue.
The current Program imports xml files only. The program should have the capabilities to import various files types such as excel and access databases. The desired end goal should be to have a distinct list of file types supported but being able to import excel and/or access is a good start in making these changes.
Tasks that need to be completed: