You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 31, 2021. It is now read-only.
The build process then also could copy all the stuff in Webcontent folder of the ODP. Dealing with file resources in an NSF and renaming everything is quite a hassle...
The text was updated successfully, but these errors were encountered:
zeromancer1972
changed the title
What about suing Webcontent instead of file resources?
What about using Webcontent instead of file resources?
Mar 8, 2019
I have to admit that use of ODP and Webcontent is something I have not done at this stage. I was going to dig into it over the weekend, but it sounds like you have done it before. Can you share an example of the process or database, if the combination of ODP and Webcontent allows to remove some of the frictions and can work with GitHub I am all in. But could use some help in setting it up.
Sure, no prob. In this sample https://github.com/zeromancer1972/DataTables I use almost everything from inside the Webcontent folder (Javascript plugins, css). This means I reference it on the XPages but you could also reference it like you do with the React app because the paths are the same (reference to db.nsf/style/some.css is identical for file resources and Webcontent relative paths). This is what I meant: as your build script places the files already in folders you can just grab the whole folder and copy it to Webcontent - and the relative path from the NSF is still the same. ODP of course is something that I can't explain in this small comment section though. I took some notes a while ago: https://oliverbusse.notesx.net/hp.nsf/blogpost.xsp?documentId=CDA
The build process then also could copy all the stuff in Webcontent folder of the ODP. Dealing with file resources in an NSF and renaming everything is quite a hassle...
The text was updated successfully, but these errors were encountered: