Can anyone outline the steps I should take to create upload-a-scorm-zip-file and make it available as a course to users on laravel 8/9 with laravel scorm handler?
Related
I would like to develop a web application with Spring Boot, Spring Web MVC and Thymeleaf. I recently stumbled upon Web Components and Polymer which might be a good addition to Thymeleaf in order to use cool components. As I'm a frontend noob, I ask myself why I need this npm and bower stuff in order to use Polymer.
If I got it right, Web Components and Polymer are just js libraries. Why can't I just include them (maybe by using a cdn) in my html page? I like Thymeleaf as it's possible to view the pages without the need to have a webserver. If I could just include polymer as js library that would still work. I am quite sure that I misunderstand some major concepts, but I can't grab it. Can anyone help me?
Thanks!
First, thanks for the opportunity,
I noticed that the latest template using ABP 3.0 and aspnetcore 2.0 doesn't come with social logins implementations. Also I cannot register user in UI anymore. I would like to know why they were gone.
Will these features come back in future versions? I'm afraid to use the codes from previous versions and crash with the new aspnetcore 2.0.
Thanks in advance
User Registration is available. There is a register link in the login page: https://github.com/aspnetboilerplate/module-zero-core-template#login-page
However you should switch to a tenant for that. Host side does not has register functionality by design.
We removed social logins since the implementation had some problems and we didn't want to provide support for it and wanted to keep startup template simple. It's pretty standard, you can implement yourself by following Microsoft's documents.
I have a Spring MVC application that connect with Alfresco using CMIS libraries, actually I can upload documents and download it but I need integrate Alfresco's WebPreviewer to preview documents in my app.
I found some code here but I don't know how to do it
It's hard to say for certain because of the limited amount of information that you've provided, but I think that the problem that you're going to be faced with when trying to use any of the existing previewer code is one of authentication. If you're using only using CMIS then you won't be able to use any of the WebScript based REST APIs that the Alfresco widgets will be using.
There are two possible previewer widgets that you can use - the older YUI2 based previewer (that you'd currently find in the document details page and the Document Library film strip view, and the newer Aikau component that you'd find in the faceted search previewer (from version 5.0 onwards).
I suspect that you won't be able to re-use either of these components without either authenticating against Alfresco in a way that allows you to access the WebScript based REST APIs or extending and customizing those widgets.
You've said that you have your own Spring MVC application, but you haven't said whether or not that is using the Surf extension - if it is, and you're using the authentication capabilities provided by Surf then you will be authenticated to use those REST APIs - as the Surf authentication provides access across all APIs (including CMIS) via a single authentication.
If you are able to access those APIs then you should be able to follow the steps outlined in both the form post and the blog posts in your own question and the previous answer, however - based on your question I suspect that you can't do that.
If you've not come across it, you might be interested in the Aikau archetype that builds a ready-made Alfresco client using Surf (see this link) and that tutorial also shows how to use the Aikau previewer (see here).
Because this is providing you with a Spring MVC client that is preconfigured to authenticate against Alfresco, you might be able to port your application to use it.
Otherwise, as I said earlier - chances are you'll need to extend the existing widgets to use the CMIS APIs to render the previewers. Again, Aikau is easier to extend that the old YUI2 widgets - but is reliant on Surf.
I want to develop a pretty standard webproject with all basic functionalities such as landingpage, user registration, login and so on.
Since I'm familiar with Java and Spring, I set up the a project with Spring Roo including DBRE from an MySql database, MVC and Spring security.
Right now I'm wondering how to go on with the UI. I would like integrate a template from twitter-bootstrap and I already downloaded a working example project (no apache tiles structure). I'm not very familiar with Apache tiles and frontend design in general so my question is, what would be the best way to integrate it and bypass the standard CRUD design?
Is it only necessary to design a new default-layout and reuse existing .jspx files? Also is it possible to take the existing bootstrap.jsp template which uses sitemesh from the bootstrap-example as a new template and reuse existing .jspx files?
Reuse is important since there are still entities which will change in future.
Appreciate any help!
I haven't personally used twitter-bootstrap, but I am fairly familiar with the Spring Roo structure.
My first bit of advice would be to just simply not use their UI stuff. Nothing says you have to generated your Controllers with scafolding, which takes the scafolded classes and auto-generates the CRUD methods and UI peices for you. In fact, in my last 4 projects, I did all the UI coding myself (I still used Tiles w/JSPs, and let Roo make all the relavent tiles configs and resource bundles). You can ALWAYS generate a plan Controller and use Roo for everything except the View pieces.
I don't see why you couldn't use the bootstrap.jsp you speak of. The Tiles implementation is done using the TilesViewResolver, I believe, which should be configured in the application_context.xml (or whatever Roo calls the context XML file). Just replace the TileViewResolver setup with something else. I would suggest reading up on Chapter 17.5 Resolving Views in the Spring Reference guide. I think for JSPs you want to use InternalResourceViewResolver.
Of course this can be done using an iframe, but i'm looking for a solution where the application is injected in the dom on load, using all of the stylesheets and scripts that are already available on the page.
This is useful for websites that need a component with rather difficult requirements (like live push updates), that are available out of the box when using meteor.
I don't want to embed a meteor application inside of an iframe, because of the need of duplicating stylesheets of scripts on the main page.
Because Meteor is a full-stack application framework, this won't be possible. Meteor isn't like a typical client-side javascript framework where you can just hook it into some other platform, it's a platform itself. So I would ask: what are you trying to do, and why do you think inserting Meteor into the page will help solve your problem?