-
Notifications
You must be signed in to change notification settings - Fork 1
Current Issues
The usual practice for 3rd party js libs appears to be to just point to the appropriate lib location on the web. (such as the google api, etc). However, this app should be running locally, so it might make more sense to include all necessary (js) libs in the www directory. The argument against this is essentially the fear of code bloat. So what is the best practice for this situation? Should we do both? i.e.
<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"></script>
<script>!window.jQuery && document.write('<script src="jquery-1.4.2.min.js"><\/script>')</script>
Sometimes when editing points, it would be nice be able to toggle off any rendering of shapes. In some cases, this will simplify seeing what is going on
Debugging can be painful. To fix this I need to extend the shinyACE editor and a lot of customization for pointR and may also need to provide hooks in svgR.
Should there be a naming convention for file extensions of compounds?
How to make an easy deployable version of pointR?
-
As a package we can insure dependencies such as svgR, stringr, ... are installed. But this places a barrier for anyone that just wants to try it.
-
As a zip file: user simply invokes
library(shiny);
runUrl( "weblink to pointR zip")
The problem with this is the libraries would need to be installed. Options for this are
- directly use r-shiny-electron to bundle and deploy with docker inside
- Install automatically to R libs (behind the users back?)
`
if(!require(somepackage)){
install.packages("somepackage")
library(somepackage)
}
`
- Check, if not install prompt user to install?
`
if(!require(somepackage)){
continue<-someMessageWindow()
if(continue){
install.packages("somepackage")
library(somepackage)
} else {
exit()
} #exit with predjudice
}
`
make help available
- Should the svgR user guide (and help above) be in seperate browsers, or should they be contained inside an iframe in pointR?
- Should add bookmark capabilities to the editor
- Should allow stepping through code.
- Should have multiple edit windows available (and commit for an svgR window, run for non-svgR windows, implied here is that we have a console output (maybe the current error log would due). We might also want just a console.
- Currently we support basic Rmds, but some improvements under consideration:
- Would be great if pointR could open rmd files and insert the svgR code directly.
- Or at a minimal, single command for copy all and add the results='asis' to the clipboard for pasting.
- The current drippet editor needs to be improved