collection browser not mobile accessible
Currently the collection browser can't be used in mobile devices. My new collection browser widget solves this: https://github.com/wshager/xcollectionbrowser
I'll create a pull request ASAP
There are some issues to solve before the collection browser can be integrated in eXide:
- It uses Dojo, and Ace doesn't play nice with that. There's a noconflict build for Ace which might help here, but is the current version compatible with the latest Ace?
- I replaced the most vital jQuery functionality with a Dojo $ shim as to minimize code. I believe jQuery is mostly used for the current browser, so that could be replaced, unless there are objections.
hmmm I think the consensus is to ditch DOJO in exist in general
The current collection browser doesn't work, I have one that does. But perhaps I should ditch eXide?
I'm a bit confused because I thought you were going to replace the collection browser in the dashboard? The one in eXide is the one which works fine for me, whereas the one in the dashboard does not.
I also think ace fails on most android devices with virtual keyboards, which is why I made no attempt to make the collection browser mobile friendly.
To answer your question: the version of ace in eXide is not the latest one (see the submodule). It can be updated, but then all the editor functionality needs to be tested. Besides jquery, eXide also needs jquery-ui and d3s.
The same problem I have with the collection browser in dashboard I have in eXide as well: half of the time collection doesn't show its contents. This is a major nuisance. The problem lies with the grid widget and cannot be solved easily. AFAICT slickgrid is not actively maintained anymore.
The problems with ACE on Android are reported and will be solved for sure one day... Perhaps this issue should be renamed: I created it hastily while on a train to Belgium...
Like I said, jQuery can be replaced to prevent overlapping functionality: https://github.com/wshager/dexist/blob/master/util/%24.js
@wshager What is the status of your plan to submit a PR to address this issue? If you're not working on it, we'll close.
It's not up to me. I spend time to create a working replacement, but I'm told it won't be used because it's based on Dojo. I find that shortsighted because a) it's just javascript b) Dojo never got replaced in betterform c) jquery is the suckiest tool ever. I'm using the collection browser myself and it's quite good, but since I got absolutely zero reaction I'm not pushing this anymore.