I am working on one pet project to get the better understanding of the SAPIUI5 framework. About me, I am a very experienced front-end developer and enjoy working in VS Code IDE. I started SAPUI5 development in SAP Web IDE and then exported the project to eclipse to run it locally, but in eclipse, I was missing a lot of new features like es6 and es7 and some plugins, so I moved my project to VS Code. In VS code, I introduced grunt to run a small static web server to run my SAPUI5 application, so far it is working fine, and I have no issues, but I am worried about the hidden scenarios that I can't see right now in regards to SAP UI5 deployment and deployment environment. With no experience in the deployment environment and production environment requirements for SAPUI5 client-side application. Can you guys please tell me of any potential issues if there are any in this sort of approach and development of SAPUI5 with VS CODE?
Potential issues:
ES6 and ES7 is not supported across all browsers, so you might want to add Babel to your grunt chain.
Deployment:
The grunt plugin grunt-openui5 lets you minify the code into a single Component-preload.js.
The grunt plugin grunt-nwabap-ui5uploader lets you deploy your code directly to SAP NetWeaver.
Here is a sample by SAP which shows their Gruntfile: https://github.com/SAP/openui5-sample-app
Related
We have on-Premise apps deployed through Eclipse to our ABAP repository, with the component-preload file generated using gulp.
Now that we've moved to SAP WEB IDE, which using grunt as opposed to gulp. Can apps be deployed directly to ABAP without eclipse or will it cause conflicts?
we have a similar environment:
WebIDE Full Stack
Gulp
I manually deployed an application to our ABAP Repo. The app works but is not minified.
If you are dropping Eclipse completely and only use the WebIDE you probably won't need gulp and can replace it with the default grunt stuff generated by the WebIDE.
We are planning to automate testing of my eclipse application GUI using window tester. Version of eclipse is oxygen.
Please inform me how to integrate window tester with eclipse application. I do not see any window tester plugin in eclipse market place. If not, Which GUI testing framework can i use to test my eclipse application.
Thanks in Advance.
I have personally used first two types of the frameworks:
SWTBot
RCPTT
Jubula
RedDeer
RCPTT is focused on creating and running UI/System test for RCP/SWT applications. It is an alternative or addition to the open source projects SWTBot or Jubula. All of them have their specific advantages and disadvantages, RCPTT uses a very different approach than that of SWTBot or Jubula.
SWTBot is a Java API to consume while writing tests (can be JUnit,
TestNG...), which makes it very easy to use for Java developers.
Jubula has its own XML-based languages to write tests. Аlso
uses an embedded database and thus differs internally most from the others.
RCPTT using Eclipse Command Language to write tests.
Thanks to #howlger for help.
Jubula test can be written either with a UI, which can be used without any programming experience or with an API for Java.
I would have written this in the comments for #MBaev but i was not able due to low reputation
I have been engaged in developing IBM MobileFirst + Ionic applications for the last few months, but I still couldn't figure out a way to use SASS. How I managed till date is, I will have a static Ionic project with SASS setup and I re-use/copy-paste the HTML and CSS from this static www folder to actual MobileFirst project common folder.
Is there a better way around, like to have a node + gulp setup on the MobileFirst project?
NB: I'm using IBM MobileFirst 7.0.0
Cheers!
In Hybrid apps in v7.0, you use Eclipse. This makes things more complicated. In Eclipse you can use Ant scripts to alter the generated folder with anything you may need. Perhaps the Ant script could execute whatever it is that you need.
You can see an Ant script integration example in Studio, here: https://mobilefirstplatform.ibmcloud.com/blog/2015/08/03/integrating-3rd-party-cordova-plug-ins/
This will be easier for you in v7.1, where you can create "pure Cordova" apps using the command line, thus your integration points with other tools such as Node.js and gulp is much more natural, and more feasible.
Is it possible to use Eclipse (with AppEngine SDK plugin) and Google "push-to-deploy" together? I have managed to install "gcloud"-tools and initialize a project fine! But now I can't figure out how to combine Eclipse project structure and the structure generated by "gcloud init". I mean I would like to do this:
1) Use Eclipse to edit the application and test it locally in Development server as before
2) But also utilize Google "Push-to-deploy" GIT repository (instead of GitHub)
Is this possible or feasible and is there any instructions how to do this kind of project setup correctly.
Thanks for any tips!
After some more experiments with gcloud (Google Cloud SDK) I would recommend creating the project with Maven and use Maven for building & running the development server. Still you can import the Maven project in Eclipse and use that as Java editor + remote debugger. Here's the instruction to get started:
https://developers.google.com/appengine/docs/java/tools/maven
Also Google Endpoints is quite nice tool for building REST APIs (though it still has some weaknesses, like limited support for HttpServletRequest data and poor authorization support in Development server)
https://developers.google.com/appengine/docs/java/endpoints/
I'm trying to learn how to develop a j2ee web application but is currently figuring out what's the advantage of using seam-gen vs eclipse seam web project or vice versa.
Why would I use one over the other?
Thanks,
czetsuya
Command line seam-gen stuffs the whole application into a single project and included some files that we didn't need (6 versions of the messages file, for example, each in a differnet language).
The eclipse jboss tools seam-gen produces a bit more modular, streamlined app. It generates 3 separate projects (4 if you want a test project). It took some time to get used to it, but once I got it down, I prefer it. Additionally, when you create he project in eclipse you can leverage more easily the benefits of using those integrated tools.
You can do this with a seam-gen commandline-generated project as well by creating an eclipse project using your seam-gen project as source , but it takes some fiddling around in eclipse to get the settings just right.
My recommendation is to go with eclipse/jboss tools. If you come from a command-line centric background (as I did), the learnign curve may be a bit steeper, but in the end it will be worth it. Use the jboss tools forum for questions you have about this project.
Good luck. Once you get going with eclipse/jboss you'll find it's a great environment to work in.