With the end of the development plugin, the fun has gone out of GWT development. Every small change triggers endless recompilation and then I'm still debugging half Java half Javascript in the browser.
I'm thinking about migrating to AngularJS. Any hints on how to approach this?
Should I first switch my RPC Servlets to webservices returning JSON?
I'm also using GXT grids. How to best replace these?
Are you using Super Dev mode? This makes development a lot better as you use the browser dev tools to debug and it makes use of source maps. In my opinion, it has made GWT relevant again.
Do your backend first by converting your RPC servlets to an equivalent REST interface. Then you can use any front-end MVC framework - Angular, native mobile, or whatever.
For GXT grids, AngularUI has a grid component. http://ui-grid.info/. You could also use ExtJS grids.
Related
We have huge enterprise application written in angularjs.
Now we have to migrate to angular, so we have ruled out an option of hybrid approach angular suggests using "ngUpgrade".
So now we are creating a new application in angular, which means we have 2 applications "angularjs(old)" and angular(new).
So to switch between these two applications can be done without refresh using angular-spa.
I was trying to find if there is another framework, where navigating between two apps happens without refreshing(without refreshing entire page by navigating to new html).
Possible solution:
Use a new Angular application as a wrapper, then just use iframe to show the application you want depends on the context - old or new. The issue you might face is changing the iframe, but I guess you can use postMessage to communicate between the apps.
A bit more sophisticated:
Use Angular Elements to create your hybrid app.
I really recommend you to watch Erin talks from the last Angular connect about how Google made the migration from js to Angular.
I've recently tried the micro-frontend architecture described here:
https://www.martinfowler.com/articles/micro-frontends.html
Each app on different code repository, runtime build and quite easy to implement. Take a look :)
Is it possible to use an entire Angular2 app as a plugin within HawtIO? Our reasoning for doing this is so that as we develop our OSGi applications, each having their own UI, we can use HawtIO as the overall container and can detect and display each UI webapp within.
From what I have investigated so far, it looks like the only possibility is either adding simple plugins which add static links to our individual web apps, or re-write the Angular2 app as a AngularJS one instead?
The hawtio-core component from hawtio 2.x supports bootstrapping a hybrid angular 1/2 app which is pretty much what you're looking for:
https://github.com/hawtio/hawtio-core
It's been awhile but I played around with it in this branch from the fabric8-console project, it may need some adjusting to be inline with new angular2 developments:
https://github.com/fabric8io/fabric8-console/tree/angular2/plugins/angular2/ts
This is not a programming question. If it is not appropriate to post it here, just advise me some place worth to share this.
What would be best to know in order to startup a project in Cordova. What i need to know is that in order to create a working web and android app what should i use?
So far
I use Cordova.
Ionic for GUI.
PHP and MySQL for back end
Angular JS for client side and controller for the app.
JSON
Do I have to use AJAX as well? if so, where would it fit?
"Do I have to use AJAX as well? if so, where would it fit?"
Yes, you should build a Single Page Application inside Cordova using any framework that you desire. Ionic/Angular is a valid choice here, other options include JQuery/Bootstrap, React JS, Framework7, OnsenUI and pretty much any combination of JS single page application framework and mobile focussed web front end framework that you like and can make work together.
For going beyond what the web view can do you'll use off the shelf plugins, or write your own which will need Java / Objective-C / C# or Swift skills depending on which platforms you're using.
As you want to be building a single page application you will need to make AJAX calls to get resources from servers, call APIs and the like. Do this using the mechanism built into your chosen framework, e.g. $http service with Angular, $.ajax for JQuery etc.
With angular you can use AngularJS $http
Link to Angular documentation: https://docs.angularjs.org/api/ng/service/$http
I want to create an application using Ionic and AngularJS and Grails?
Also, I want to use Grails Spring Security Core plugin for login or registrations procedure.
Although, Stack Overflow is not the correct site to ask this type of questions which simply needs suggestions and other's opinions.
Well, we are here to help. You can try other StackExchange sites like https://softwareengineering.stackexchange.com/.
Grails + Ionic + AngularJS is a perfect combination of frameworks to build a fully functional and elegant mobile application for all platform. We've build various mobile applications using these three technologies and they work awesome.
Since Grails fully support the concept of rest API for JSON and AJAX based calls, it is absolutely possible to use it along with AngularJS. AngularJS doesn't care about the server-side technology you are using as long as your server side code can communicate over JSON data.
Ionic is just a beautiful front-end SDK which works on the top of AngularJS and provides various utilities to develop a hybrid user-friendly mobile APP.
So you can easily use these 3 technologies and get your mobile app ready in a few weeks.
Ionic doesn't care about what you use as a server stack. As long as you create a service which has well defined interfaces (REST?), you should be fine.
I for example use PHP (yeah, I know, shocking, right?) Slim framework + Postgres database as my backend.
We are developing a standalone angularJS web application and need to make it work in the newest backbase portal.
We have no idea if this is even possible?!
Thanks in advance!
Backbase widgets work standalone and follow the W3C specifications. However, if you are writing a SPA as a whole, you are not getting the true benefits of widgets.
You should separate your application into widgets, in other words, mini angular applications.