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 }}
Repository navigation
RFE: Upload Library Script could have GH import and sync #95
It would be helpful to have the repository linkage for libraries to import and load scripts automatically.
Currently I have one here and just found out I can't sync it unless I convert it to a user.js which would put in in the incorrect category of the Scripts instead of the Toolbox for OUJS.
Please advise?
EDIT: There may be the possibility of using a symbolic link somehow if the GH API supports detection and possible dereferencing with some error trapping on failures.
EDIT: Maybe in both places on OUJS (Toolbox and Scripts) that way the site code can be kept simplified for repositories... e.g. have a user.js synced as it is more or less now then enter a url to the OUJS site itself in the add library page but dynamically change the served file extension to .js? This would cover standalone self running libraries along with exportables. (Just throwing out some ideas) :)
The problem is that library scripts might not have metadata (in fact, the shouldn't since they aren't user scripts) and even if they do we don't read it. This is why you have to enter in the name of the library (and a short description, which is something I need to add soon). I guess I could store the path on GH during import, and use this for syncing. I could also detect the move or rename of the library since the GH webhook call gives me this info. Would that be sufficient?
... I could store the path on GH during import, and use this for syncing. I could also detect the move or rename of the library since the GH webhook call gives me this info. Would that be sufficient?
That sounds great. I just threw out the other ideas just in case I might get a nibble or spark some other idea. Being able to sync between OUJS and GH is my number one goal right now for data archiving but I have some catching up to do before I can assist with RFEs myself. I am watching the changes to better understand how OUJS is designed. I'm also getting prepared to have a specific test machine for OUJS when/if @DoctorSnowman posts that localhost.localdomain OUJS guide... and my distro is presenting a challenge in some areas too. :)
Activity
sizzlemctwizzle commentedon May 13, 2014
The problem is that library scripts might not have metadata (in fact, the shouldn't since they aren't user scripts) and even if they do we don't read it. This is why you have to enter in the name of the library (and a short description, which is something I need to add soon). I guess I could store the path on GH during import, and use this for syncing. I could also detect the move or rename of the library since the GH webhook call gives me this info. Would that be sufficient?
Martii commentedon May 13, 2014
That sounds great. I just threw out the other ideas just in case I might get a nibble or spark some other idea. Being able to sync between OUJS and GH is my number one goal right now for data archiving but I have some catching up to do before I can assist with RFEs myself. I am watching the changes to better understand how OUJS is designed. I'm also getting prepared to have a specific test machine for OUJS when/if @DoctorSnowman posts that localhost.localdomain OUJS guide... and my distro is presenting a challenge in some areas too. :)
Martii commentedon Jun 11, 2014
Covered in #129 when deployed.
Martii commentedon Jun 11, 2014
Closing as deployed and checks out.