-
-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop dependency on shared-resources #309
Conversation
…y dependency for gid
package.json
Outdated
@@ -1,6 +1,6 @@ | |||
{ | |||
"name": "exide", | |||
"version": "2.4.13", | |||
"version": "2.5.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think due to the removal of the app generator this might merit a 3.0.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tend to agree
@wolfgangmm The default width of the last modified column is wonderful, and the resizable columns are working great! I noticed one slight change: in the old file manager it was possible to rename a resource by clicking in the resource name field. I'm not able to trigger the rename mode. It was always a little fiddly, though; it was easy to accidentally trigger unintended behavior—either entering rename mode or opening the resource. Perhaps a dedicated Rename button with a modal dialog for renaming resources would be better? In any case, I just wanted to note this issue. |
@joewiz Yes, I dropped the rename feature because with the new component it is too easy to accidentally activate it. A toolbar button to click for activating the cell editor could indeed solve this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a massive improvement.
Well, when I try to build the project I get following error
Any pointers or ideas on the above? |
@line-o the submodule support/xqlint it should be at 36c142b12a642a5693c744afe2a0ac69c184fc9b. Maybe you still have an earlier version checked out? |
git submodule ... that's it |
I would suggest to remove the second filter for now (hoping that it is easy to accomplish) |
The rename feature was a nuisance often times. |
eXide.find.Modules.select(doc.syntax); | ||
} | ||
}); | ||
// commands.addCommand({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would remove dead code
eXide.find.Modules.addEventListener("import", null, function (module) { | ||
editor.exec("importModule", module.prefix, module.uri, module.at); | ||
}); | ||
// eXide.find.Modules.addEventListener("open", null, function (module) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same here - or do we need to fix it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We may want to re-implement the feature sometimes, so I'll rather leave it commented out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, then it is still in version control. It may never come back and would then stay there forever.
Would you be against me removing it?
The rename feature is back. You now need to click the 'rename' button in the toolbar first to switch into edit mode. This avoids any conflicts with mouse and keyboard navigation. |
OK, everything is green. The last thing that keeps me from merging it is the discussion about dead code removal. |
Oh and the version discussion ... I am in team 3.0.0 |
@wolfgangmm Thank you! The rename function works well. I just noticed one issue with it: if the user selects a cell from a field other than Name and then selects the Rename button, the contents of that cell become available for editing—instead of the contents of the Name field. Users might misunderstand that they can use this tool to change the permissions, user, group, or date of resources. Here's a screenshot showing the date field being editable: If a user changes the value of one of these non-Name fields and hits return to submit the rename request, a "Rename error" dialog is validly shown: "Cannot move resource to itself '/db/test2.xlsx'. XMLDB exception caught: Cannot move resource to itself '/db/test2.xlsx'." The accompanying request URL: http://localhost:8080/exist/apps/eXide/modules/collections.xql?target=test2.xlsx&rename=test2.xlsx&root=%2Fdb%2F. Screenshot: Ideally, when the Rename action is triggered, only the Name field would be made editable, regardless of which cell is selected in the row. Do you have a sense of whether this would be possible in this PR, or would you prefer to defer this to a future PR? I could open an issue, and we could list it as a known issue in the release. @line-o Thanks for your fixes allowing CI checks to work with this PR! |
@wolfgangmm thanks for the hard work. This looks very well rounded now. Will merge after tests have run. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've tested the merged PR and can confirm that the Rename button only has effect if you've selected a resource's Name field. Thank you for everything in this PR, @wolfgangmm!
This PR drops all dependencies on shared-resources. It also modernizes the build to facilitate future updates and replaces some (though not all) of the old components, which were depending on jquery/jquery-ui.
TODO: