google scripts using jquery datepicker extermely slow - google-app-engine

There are 2 topics which have asked the same thing, they are several years old so I wanted to create a new one.
jQuery + datepicker extreme slowness in Google Apps Script
JQuery UI in Google Apps Script HTML Service very slow
Is using jquery with google scripts just a bad idea or have we had any success on speeding it up?
Are there any suggestions on what I can use as a date picker using the HtmlService (reading that the gui will probably eventually be phased out)
Currently my google script app has only 2 fields and loading jquery and jquery ui, with the css takes over 10 seconds to just load, while in dev mode. I have not tested in a published state, but I guess more importantly should I be looking at a different solution?

If most of your users use a Google Chrome or any webkit-based browser, you might use
<input type="date">
But styles vary differ. Doesn't worked in ie and firefox (use js).
Helpful links:
w3.org/input.dat
Try it in different browsers
Is there any way to change input type=“date” format?

Related

Is Mobile Angular UI a framework I can use for a mobile html application?

Our current web application for mobile is build with jquery mobile
https://www.bit2c.co.il/mobile
I would like to upgrade it with better ui, plus I believe that jquery mobile js and ui are not working smooth over IPhone 4. (the nav bars, header and footer, are refusing to stay fixed ).
So I did some research and found that mobile angular UI is working pretty well over different smart phones including IPhone 4.
My question is:
1.Is this framework well supported and will continue to grow ?
2.Is it working inside phonegap hybrid application ?
3.If using it means there is no need for jquery? and by that how all the functionality done with jquery is done with angular instead?
Please keep in mind I have little angular knowledge and I've seen there will be great change in angularJS 2.0. which leads me to concern in using this version.
Thanks !
If anything, Angular 2.0 is more mobile-aware than 1.3. My team has built a mobile-only application with Angular 1.3 and it works quite well. We've also wrapped it in Cordova to build native mobile apps, although there were more issues there due to third-party JavaScript. The main problem with starting a new app with Angular 1.3 today is that eventually Google will only push security fixes, and no new features will come to the framework. If you build a one-off app, that's fine, but if you're building a new product that will keep on evolving over the next 2 years, 1.3 is not the right choice anymore.
The main challenge I would say we have is that it takes a while to load upon the first page-load. We're a content site with little user "functionality" and while Angular has been good, I don't think it's the best solution for a plain content site; Angular is really meant for applications where you want users to interact with things on the screen without creating new pageloads for every click.

Is there a way to live update app while writing angularjs?

I want to create an angularjs app but each time it requires to press the refresh button in the browser to get the update. thus it bring to this question:
Is there any way to get live update while writing angularjs app? So I don't need to press the refresh button each time I make changes in my angularjs app.
Yes, you can use grunt which is a task runner written in node, grunt has a plugin called grunt-contrib-livereload that reloads the page whenever there are changes in the files/directories that you want to watch. Alternatively, there's a scaffolding tool for client side web applications in AngularJS called yeoman, that has a generator called generator-angular - this generator has an opinionated structure towards AngularJS application development and it comes with a basic setup that you can use for livereloading code changes from any files that you have configured to watch.
Start using yeoman. It has grunt that will solve yr problem plus lots of more exciting stuff.
Check this quick start guide : http://yeoman.io/learning/
I use the open source editor Brackets.io by Adobe. Just click the lightning icon button to the right of the editor to run your web page and will auto refresh for every save.
You can do this in many ways. Many of the options are already mentioned in this post. All of them are workable. In my experience the most simplistic way to do this by the following way.No configuration , No setting , No need to code anything.
Just add this line in your <head> </head> tag of the html file
<script src="http://livejs.com/live.js"></script>

What are the drawbacks when using Ionic Framework or OnsenUI only as hosted webapp

We plan to create a hosted web app with AngularJS. As UI Framework we found Ionic and Onsen to work well with AngularJS. Both of this frameworks promote that they are made particularly for Hybrid Apps. But us I understand correctly, both frameworks are based on web technologies. So what are the drawbacks when using the suggested UI frameworks for non Hybrid Apps? Is it mainly the Browser support?
Thanks
Well, both Ionic and Onsen are made particularly for Hybrid Mobile Apps. You just won't be able to use it even for tablet apps without customization (If I am wrong, please correct me) just because they target the limited viewport and incorporate phone UX patterns.
Also, they are made with PhoneGap in mind (the apps will be hosted in the WebView component), and addresses some common WebView problems, e.g GPU acceleration for better performance.
If you need just some UI framework for a simple Web App you'd better have a look at Twitter Boostrap or Zurb Foundation. For a complex case you may even consider Sencha instead of Angular.
There is a part of Ionic that expects the Cordova/PhoneGap Device plugin to be installed. It helps with displaying on Android and iOS appropriately, as well as increasing the size of header bars for iOS 7. That wont be an issue for web though, since you'll have the browser's "chrome" taking up that space.
You may loose some of the buttery smoothness in things like page transitions because the template files need to travel over a (often cellular) connection to the internet, but your app will most certainly work if built with Ionic or Onses over the web.
Things changed considerably over last few months.
Both frameworks now support splitview so they can be used for tablet devices. Subjectively Onsen UI has a better support (it is much more configurable), but Ionic is also not bad. This can translate to smaller desktop browsers screens.
You should also consider that Onsen UI has a dedicated desktop browsers support (all web-kit browsers). Ionic framework will also work on desktop browsers, but it was not fully tested or optimized for such environment.
Biggest problem here is that both frameworks were never meant to be used on larger screens. They look oversized and bloated. If you ever worked with jQuery Mobile (on desktop browsers) you will understand this problem.
There is nothing stopping you from doing that - it might even be a smart approach for a mobile first design approach. The advantage is that you could rapidly iterate an idea an then invest in a native or platform specific app depending on user feedback/metrics.
The main drawback would be the user expectations for your UI and application logic which are different for a web page and a native app. For example the back button will be duplicated in the browser and in your header. You could use some platform specific CSS or configurations to hide it. Then there is your application state and user data - will you save it in local storage, session or database? This depends on your app and best judgement.
There will be some browser issues which may not be addressed in the core of Ionic and Onsen because they are not targeted to work with IE6/7 (see angular browser support), for example, but you can resolve those by having a graded browser support policy.

es5-shim or chrome frame for making angular apps work in IE

I am developing rich frontend apps which will be used by users running IE 8 and above. I am using angular.js as my frontend framework.
I currently see two choices using es5shim or google chrome frame. What I am not able to discern are the differences between both.
As I understand that es5-shim monkey patches the js engine, and is much more lighter as it doesnt require the user to download and install.
What does chrome frame provide over es5-shim, and which is recommended?
Google Chrome Frame is a application, and need user to install it, es5-shim is JavaScript code, you just need to include it.
If you want to use AngularJS in in IE, you should read this: http://docs.angularjs.org/guide/ie. Long in short, include es5-shim(optional but really useful) and JSON polyfill.

Make a website mobile ready

I have a website and i want this to be mobile ready. I found Kurogo very helpful for static website. But this is not useful when i have a website where there are many forms and all. which is the best way to convert a website mobile ready where it has many forms, add, edit , update forms and all. I use php/mysql for my application.
you can always try to use bootstrap or zurb foundation and then load the css using a media query

Resources