Hi team;
Before I ask my question, let me explain what my original plan was before deciding to use "File Explorer" and why I had that original plan. Then I'll ask my question and how I can still get the benefit of my original plan and be able to use the FileExplorer.
I started creating a Database table with hierarchical structure (Parent_ID, Child_ID) to create a complete directory structure in the database. Although these directories never would be created on the server side, but in the end user's mind they would think these are the actual directories on server (sort of virtual directories). Each record of the directory had a few properties (like if upload is allowed, If the directory is private or shared, Max number of files allowed and etc.). The reason I created this table is to have these properties that I could make decision at runtime if everyone can upload files or if the directory is private. Or who owns the directory and etc. But in reality there wasn't any directory.
Then I had another database table for files. that were connected to directory table as a child table and file record had it's properties that gave me controls of the files. Although, all the files would be stored in one physical directory. Just the two database tables will create a virtual directory to users.
But I had to write all the codes for uploading, adding new files, deleting, renaming, displaying images and etc.
Then I saw the FileExplorer which blew me away, because I had to create an exact control that works with my Directory and files tables. The big difference is that, your File Explorer works directly with OS directory and file system. But using your control, I loose all those properties that I had described that I could use at runtime to make decisions on. Here, with your File Explorer, I loose the control that I need to have for my app.
My question: Now that I have explained my problem, my question is, how can I use your control and still be able to have the features that I was planning to have in my original plan?
I was thinking of using your File explorer and I would still create the Directory and file tables side by side. The File Explorer would serve the actual work and my tables would serve as decision making metadata.
But, to do so, I need a series of "Post" action events to store the info in my tables, like the directory name (that was created or renamed or deleted), file name and etc. I only see Events that are "Before" the actions are taken place.
So, what direction would you suggest?
Or if I go with my idea, I'm missing those Post Events to sore the data.
Looking forward to your help!
Thanks!
..Ben
Before I ask my question, let me explain what my original plan was before deciding to use "File Explorer" and why I had that original plan. Then I'll ask my question and how I can still get the benefit of my original plan and be able to use the FileExplorer.
I started creating a Database table with hierarchical structure (Parent_ID, Child_ID) to create a complete directory structure in the database. Although these directories never would be created on the server side, but in the end user's mind they would think these are the actual directories on server (sort of virtual directories). Each record of the directory had a few properties (like if upload is allowed, If the directory is private or shared, Max number of files allowed and etc.). The reason I created this table is to have these properties that I could make decision at runtime if everyone can upload files or if the directory is private. Or who owns the directory and etc. But in reality there wasn't any directory.
Then I had another database table for files. that were connected to directory table as a child table and file record had it's properties that gave me controls of the files. Although, all the files would be stored in one physical directory. Just the two database tables will create a virtual directory to users.
But I had to write all the codes for uploading, adding new files, deleting, renaming, displaying images and etc.
Then I saw the FileExplorer which blew me away, because I had to create an exact control that works with my Directory and files tables. The big difference is that, your File Explorer works directly with OS directory and file system. But using your control, I loose all those properties that I had described that I could use at runtime to make decisions on. Here, with your File Explorer, I loose the control that I need to have for my app.
My question: Now that I have explained my problem, my question is, how can I use your control and still be able to have the features that I was planning to have in my original plan?
I was thinking of using your File explorer and I would still create the Directory and file tables side by side. The File Explorer would serve the actual work and my tables would serve as decision making metadata.
But, to do so, I need a series of "Post" action events to store the info in my tables, like the directory name (that was created or renamed or deleted), file name and etc. I only see Events that are "Before" the actions are taken place.
So, what direction would you suggest?
Or if I go with my idea, I'm missing those Post Events to sore the data.
Looking forward to your help!
Thanks!
..Ben