I was thinking that since users will most likely begin modifying the source code for Librarian, there should be a broadcast of voted on Librarian software(or most used) that has been released by other users. I think doing so would allow users to have access to different features that may be accessible with other different versions of Librarian. I don’t know if this is currently being done or something else more efficient is being done, but it’s just an idea.
I’m not sure I follow. Do you mean broadcasting different versions of Librarian, possibly modified?
Yes, that is what I mean. I apologize for the confusion.
Im curious what level of modification would occur to the program that you would need to add seperate versions to it. Perhaps a certain amount of that could simply be done through apps that overhaul the layout or add in features and configuration files, though any significant modifications that were widely enough adopted already would probably be integrated into the existing program.
Librarian currently has some basic API for HTML/JavaScript apps that it recognizes as such and gives access to files. You can see a simple demo here:
http://librarian.outernet.is/en/apps/
This app simply reads a JSON file located here:
http://librarian.outernet.is/en/files/messages
My future plan for Librarian is to make an app for the entire content library instead of having it as a built-in feature. When that is complete, I see no reason to serve different versions of Librarian anymore.
So the app is intended as a way of accessing content for which other interfaces could be made?
Basically swap the current interface for managing content with an app that does the same thing. I still need to give apps their own databases and provide hooks for executing SQL statements, so it’s still a couple of months away, but yeah, that’s the plan.
1 Like
Sounds like a good plan.
That is actually a better idea.
1 Like