jimkell
commented
11 years ago I like your idea. We could put tabs on the current panel on the right and have one tab that says Optimize, and another tab for your tree. I don't know what you would label that tab. Or if there is too much to fit in the panel, we could tab the entire GUI and have a tab for the tree. Jim
--- On Thu, 11/15/12, Shay Maor notifications@github.com wrote:
From: Shay Maor notifications@github.com Subject: [MOST] Local and Remote File Access (#15) To: "dennisegen/MOST" MOST@noreply.github.com Date: Thursday, November 15, 2012, 6:25 PM
I was thinking, I had a conversation with Prof Egen quite awhile ago about the prospect of a communal repository of metabolic models. There was also a discussion as to how it would look. When Xiaowei spoke of the prospect of file matching, I had thought further about it. I got to thinking today and realized it could be an interesting to have a section on MOST to the right where you would have a tree like structure. There would be a Local start node and a Server start Node (which could eventually be called community, or any other appropriate title). The local node would underneath be populated by several nodes based on either file types, or perhaps specific organism categories. A LocalFiles class would be responsible for transversing the local directory of the MOST and creating an arraylist object which would contain the list of local files, such that: lFiles = new LocalFiles(current directory); lFiles.SBML.getAll() would generate a list of all SBML files in the current directory. In this fashion such a code would be able to populate the local node. From there, accessing any file would simply involve clicking on a file listed there, and then hitting a "Load" button. The server end could be gotten to later, but I've found some code for downloading files off of a remote server. The LocalFiles class would also support entering other directories. I've done java code where I've transversed directories before and created tree like GUI's, so I could likely manage something like this, although I've usually created gui's using the NetBeans interface. Next, with the settings class developed, it could likely keep track of any new directories added to local files, as well as any server addresses to be populated upon loading MOST. I could attempt to work on this as well during the break and get a standalone GUI for such a task. — Reply to this email directly or view it on GitHub.
mentatpsi
I was thinking, I had a conversation with Prof Egen quite awhile ago about the prospect of a communal repository of metabolic models. There was also a discussion as to how it would look.
When Xiaowei spoke of the prospect of file matching, I had thought further about it. I got to thinking today and realized it could be an interesting to have a section on MOST to the right where you would have a tree like structure. There would be a Local start node and a Server start Node (which could eventually be called community, or any other appropriate title). The local node would underneath be populated by several nodes based on either file types, or perhaps specific organism categories.
A LocalFiles class would be responsible for transversing the local directory of the MOST and creating an arraylist object which would contain the list of local files, such that: lFiles = new LocalFiles(current directory);
lFiles.SBML.getAll() would generate a list of all SBML files in the current directory. In this fashion such a code would be able to populate the local node. From there, accessing any file would simply involve clicking on a file listed there, and then hitting a "Load" button.
The server end could be gotten to later, but I've found some code for downloading files off of a remote server.
The LocalFiles class would also support entering other directories. I've done java code where I've transversed directories before and created tree like GUI's, so I could likely manage something like this, although I've usually created gui's using the NetBeans interface.
Next, with the settings class developed, it could likely keep track of any new directories added to local files, as well as any server addresses to be populated upon loading MOST.
I could attempt to work on this as well during the break and get a standalone GUI for such a task.