-
-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
s5 aspect not working #93
Comments
Using a git checkout of olelo, plus |
Content preview: Yes it works in the checked out version. However the diascope Content analysis details: (-2.9 points, 5.0 required) pts rule name description 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. Yes it works in the checked out version. However the diascope See also the list of presentation frameworks at
What is your opinion about that?
|
The simple fix is at I don't have time to work on diascope, it would probably be better to modify olelo to work with some of the newer JS presentation frameworks like reveal.js. (pandoc supports five of them: s5, slidy, slideous, dzslides, reveal) |
No I want to modify olelo exactly in such a way to support the different backends. We could also use the pandoc backend more heavily. |
I have been trying to get the s5 aspect working in the 0.9.15 gem.
First thing was to symlink plugins/filters/s5/ui to a checkout of diascope
After this the s5 aspect is available, but it doesn't render properly. Looking at the logs, the page is asking for e.g.
/_/assets/filter/s5/ui/common/jquery.js
whereas it should be
/_/assets/filters/s5/ui/common/jquery.js
(note: filters not filter)So I tried making what I thought was the obvious fix:
However even after a server restart, I see requests for /assets/filter/s5. Something is cached somewhere. In fact, if I edit plugins/filters/s5/main.rb and put some debugging in, I don't think
S5#params
is being called at all.I'm a bit lost now as to where the problem is.
Also: at http://www.gitwiki.org/Tests/Slideshow I note the comment "Still some stuff to fix here" which suggests there is some underlying issue...
The text was updated successfully, but these errors were encountered: