Re: [basex-talk] GUI feature request "Add as import"

Hi Andy, > I never got round for thanking you for this, > I found it a great time saver , but it was a bit dodgy and now it seems it > has gone in the latest 8.4 :-). I should have told you about the recent removal… When having another look at the feature, it didn’t feel good indeed, because it

Re: [basex-talk] GUI feature request "Add as import"

Hi Christian, I never got round for thanking you for this, I found it a great time saver , but it was a bit dodgy and now it seems it has gone in the latest 8.4 :-). >It's probably the most flexible solution as long as we don't do real parsing. And now you do? What I really want, in the editor,

Re: [basex-talk] GUI feature request "Add as import"

Hi Andy, I have added your requested menu item "Add as Import" in BaseX [1]. The feature, as implemented right now, feels a bit dodgy, because it does many things in one place (parsing a file, extracting things, building a string, adding it to the editor), and I haven't checked all possible error

Re: [basex-talk] GUI feature request "Add as import"

Hi Andy, thanks for the useful feature request. As I need some more thoughts on how to implement this properly, I have added a new GitHub issue [1]. Currently (and I guess you do something similar), I usually open the module to be imported, I copy the module declaration, paste it to the importing

[basex-talk] GUI feature request "Add as import"

Hi, I often find myself adding module imports in the GUI and I wonder if the following suggestion might speed up that process. Add a new menu item to the filelist right click context menu "Add as import" when the file selection is a XQuery module. The action would be to add a line to the current