Converting HTML5+CSS+JS project to Polymer (as PWA) [closed] - polymer

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I created a web application with HTML5/CSS/JS and using JavaScript template literals. I am in the process of converting HTML5 pages to use custom web components (rewriting the HTML pages) and make it PWA.
However,
Application is not a single page application
Application uses responsive Material template (css and js that should stay)
I need to convert to Progressive Web App (PWA) using workbox.
I am looking for advise, if Polymer or Lit-Element or HTMLElement would allow maximum code reuse.
Also, any web application (HTML5 with css, js) can be converted to PWA - right?
Having web components will provide better performance, but not a criteria for converting to PWA?

Don't use Polymer; I suggest you look into lit-element for components and lit-html for templates; they work very well together but you can use anything for templates, of course.
As far as I'm aware this is the official recommendation of people who were working on the Polymer project at Google. There is an active community on Slack you can go to for help, too.

Related

Is it possible to create a mobile navigation application with React Native? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
How to do navigation application using with google maps and react native? I want to do a navigation application but I am not sure if this is possible with react native.
What are your recommendations?
Of course it's possible, anything is possible as long as you have the patience to to it.
React is just a JavaScript Framework, if you can make a navigation website using HTML and JS, surely you can make one using React. If you want it to be a standalone (not a web application), you can try using Electron, but I suggest sticking with a web application.
Now, if by application, you mean a mobile application, you can run the website on a web view, so provided the website is mobile friendly, you can use React for that too.
A quick Google search led me to the following results:
https://github.com/react-community/react-native-maps
Which is a React Native Mapview component for iOS and Android.
There's an image from the repository:
Good luck!
You may use a library called react-native-google-maps-directions.
https://www.npmjs.com/package/react-native-google-maps-directions
you can easily set your source and destination then it will navigate using the geo coordinates provided.

When to use AngularJS? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I want to develop a website by my own. I want to make different web applications which need to interact with databases. I read about AngularJS, a JavaScript framework. The thing I do not understand is: When to use AngularJS? Do I first build my website in HTML & CSS and then add functionality to it with AngularJS? How do professional developers start with that?
Thanks.
When you want:
A single page app
A RESTFUL app
Flexibility of the front end and Ultimate separation of both front and back end
And you should stay away from it when:
you have low budget as you will need both front and backend engineers. Most times, backend engineers can bring up your site without worrying too much about various stuffs Javascript has to offer.
If mobile users are you main target developing HTML5 Mobile application. I prefer Backbone instead (Yes backbone)because Angular makes my phone extremely hot and drains battery like hell.
Angular js is a javascript frame work which will run at client side.
It will reduce no. of http calls to the server.
Lot of server side executions can be done at the client side itself.
Page loading is faster.
Mainly used for single page applications.
Used to write modular and re-usable code.
If you want to create some kind of social interaction site which have likes, comments, posts etc in that scenario Angular js is best choice.
You can use Angular js along with lot of server side languages like Php, Asp .net etc.

Does it matter which ASP.NET Project type I use for a super-simple site? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I'm going to create a super-simple, one-page, site. It will have text and images and links on it, that's all.
No code, either C# or jQuery or anything else - just some HTML (and minimal CSS).
I created mockups of the site (page) using VS 2013 by selecting New > Project > Web Site > ASP.NET and then each of the following, in turn:
Empty Page
SPA
Web Forms
For the first two, I added an HTML page and copied my HTML and CSS and ran it. It works fine.
For the last option (Web Forms), the difference was that there was already a page (Default.aspx). I replaced the existing HTML in there with mine (and my CSS). It also works fine.
I plan on publishing it to/with/as an Azure web site. I assume I can do this with any of these project types.
The Web Forms adds a bunch of stuff I don't need or use, so I imagine one of the other two would be my best bet. Is there any reason why I would select one project type over the others for a simple page like this?
If it's a static site and you know what HTML/CSS you want to use, your best bet with Visual Studio is to use the Empty Page template.

Make a web app in Go? [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
How can I make a web app in Go?
Is there a way I can interchangeably use Go code and HTML like with PHP and HTML?
More specifically, what I want to know is how to get my PrintLn output to show in a web browser and how to accept input from HTML form fields?
You can't embed Go & HTML (for many, many reasons) but you can use Go's html/template package (http://golang.org/pkg/html/template/) to generate a HTML page from your HTTP handlers.
I'd suggest reading http://golang.org/doc/articles/wiki/ and using http://www.gorillatoolkit.org/ (routes, cookies, etc) for the web server side
You need to setup a web server in go and process http request/response as input/output. There is already an answer about go web frameworks which would be helpful. link
If you don't want your ui to show in a browser window, you will have to bind your own html engine. For that purpose you can look at ui frameworks like walk which has ie based webview builtin or engine bindings like go-webkit which builds a custom webview.

Custom html page in Confluence [closed]

Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 years ago.
Improve this question
I have some client they always asked me how to add custom HTML page in Confluence Page that work or function similar to master page in ASP.NET.
The equivalent to a 'master page' in Confluence is a Theme. You can read more about themes here: https://confluence.atlassian.com/display/DOC/Working+with+Themes
Custom themes can be written by developing a custom Confluence plugin. The underlying technology used is Apache Velocity templates rendered using SiteMesh.
If you want to learn how to create a new theme plugin, here's some places where you can get started:
Creating a Theme (User documentation)
Writing a Confluence Theme (Developer documentation)
Creating a Theme (Developer documentation)
Creating a Stylesheet Theme (Developer documentation)
Confluence Theming 101 (Slides from a technical presentation)
Overall I would say that the technical complexity of developing a Confluence theme is significantly higher than customising an ASP.NET master page. In ASP.NET, you are just working with the bare framework and the rendering engine, but in Confluence you have to contend with two different open source technologies, plus Confluence's own idiosyncratic plugin system. You should expect to have to invest some time in overcoming the learning curve before feeling competent at building them.