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!
Related
I chanced on Piral Framework for implementing micro-frontends and I wanted to implement it in my project.
However, my application comes as a Blazor wasm project and my aim is to use this current project as my app shell.
Is there any example on how I could implement that?
I can't really find my way around the documentation too.
Kindly note that I am a beginner. Thanks in advance.
For the app shell you cannot use Blazor.WASM. You can, however, make your app shell really lightweight (i.e., don't put almost anything in there) and have all the necessary layout parts defined in Blazor.
The idea boils down to the sample given at:
https://github.com/piral-samples/piral-distributed-layout
Now instead of having pilet(s) in React / Angular / ... you use Blazor.
For Blazor pilets (and extensions using Blazor) you can check out the documentation at the README of Piral.Blazor:
https://github.com/smapiot/Piral.Blazor/
Make sure to follow the instructions closely and use the right branch (named after the version of Blazor you are targeting).
After searching around on how to actually implement the concept of micro-frontends using Blazor WASM as my app shell, I still didn't find any solution which helped me. So I came up with a custom solution which I wrote about in a blog.
Basically, the solution makes use of the JS interop of Blazor as a medium of communicating between the other JS frameworks or libraries.
Kindly have a read: https://dev.to/xanderselorm/introduction-to-micro-frontends-using-net-blazor-wasm-part-1-lc9
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?
I want to build a demo app using SpringMVC as a backend and Flex as a fronend.
Can anyone please help me in this work.
My Questions:
1) Which tool I should use, where I can write code for both SpringMVC and Flex?
2) How to integrate this two different components?
3) I just want to build a Registration/Login demo. Please help me?
Note: I want to use free tools, plugins etc only
You can use Eclipse for both - just download the Flashbuilder plugin to allow you to develop Flex. Have a look at something like BlazeDS, which will allow you to call the spring MVC classes from Flex.
You may use Powerflasher's FDT, it is Eclipse based, last time I checked it has a free edition. Like TrueDub says, BlazeDS is worth looking at, and there is also Spring BlazeDS integration you can take advantage too.
Which GUI framework/component should I use. I am using Spring MVC with Java and intend to create web applications
I was looking for something similar to primefaces. But it seems that primefaces only works with spring web flow. I believe only a certain category of applications can be created with spring web flow which could be a negative point for using primefaces with spring.
I could use jquery but the jquery is not as good as primefaces when it comes to quickly creating web pages...
Thanks for the help guys..
I suggest you to have look at Thymeleaf [ http://www.thymeleaf.org ] as a template engine, combined with either mere jQuery or (as you say you consider it a bit too simple) jQuery + backbone.js (which is a javascript MVC framework) [
http://documentcloud.github.com/backbone/ ]
The client side would be well covered with these two js libs, and thymeleaf's javascript inlining capabilities would ease integration a bit...
I currently develop with Django, but want to be ready when a future client inevitably requests a site done in ASP.NET MVC. While most of the structure and flow of ASP.NET MVC is more or less identical to Django and RoR, the one part I'm not sure about is the Apps methodology Django employs to make code reuse easier.
Is there an equivalent to Django apps in ASP.NET MVC? That is, can I create a feature, like tagging, comments, calendar of events, simple blog, etc. and bundle it up, making it portable to other projects with a minimum of glue code required to integrate it? Perhaps some kind of plugin or module system?
Django doesn't follow the traditional MVC pattern, since they advocate that in the Web world, their MTV is more suitable. In the overall, I prefer Django over Rails because of the django apps. You can do almost the same in RoR with the Rails vendor plugins, but it's not the same.
ASP.NET follows RoR structure, and therefor you don't have the reusable apps. If you check the folder structure in a MVC project, you don't even find the RoR's Plugin folder, so I bet you should do it VisualStudio-Like.
Create a reusable app, as a separated project, include references for that project in your main one, and in your Route file, just redirect to the other project's controllers.
This might be of interest as well: App Areas
we've tried to do something similar, albeit from a different angle. we use compositional controllers for increased reusability in bistro, and an ndjango as the templating language. what we start to see is controllers become more granular, and as a result less dependent on where they reside - more componentizable.