Win a copy of Micro Frontends in Action this week in the Server-Side JavaScript and NodeJS forum!

Derek Henninger

Wavemaker Support
+ Follow
since May 04, 2009
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Derek Henninger

The SearchListDetail template uses a LiveForm. As you noticed, the LiveForm automatically includes the "New", "Update", and "Delete" buttons in the OperationPanel. By default the OperationPanel is locked, meaning you cannot access the contents (which in this case is the 3 buttons). To access the contents, select the OperationPanel and unselect the "lock" property (near the bottom of the property inspector). Once you unlock the OperationsPanel you can then access the individual buttons. (They also appear in the model tree.) You can now easily remove the "Delete" button; simply select the button and press the delete key.

Documentation describing how to create templates is available here: Composite and Template Documentation

Birla Murugesan wrote:"WaveMaker Visual Ajax Studio " :Is it's a IDE to develope client/server architecture Java application or javascript code optimizer only .



WaveMaker is an IDE that helps you build the whole app: Java server backend, JavaScript front-end.

How efficiently WaveMaker handles the Memory usage and performance side?



The resulting app created when you use WaveMaker Studio is a standard Java/JavaScript application. The backend is a Java container (Tomcat, WebSphere, WebLogic, JBoss, Glassfish, etc) running Spring. The frontend is JavaScript, leveraging Dojo. Performance and memory is comparable to apps built in that architecture.

Is there any special reason why WaveMaker uses browser as the base container?



Are you asking "Why does WaveMaker Studio run in a browser?" There are a number of reasons:

1. WaveMaker is built using WaveMaker.
Applications built with WaveMaker are deployed in a browser. Since WaveMaker Studio is build in WaveMaker, it's deployed in a browser. In other words, we eat our own dog food.

2. Shorten code, build, test cycle
The application that you build in WaveMaker will be presented in a browser. When you are building your application in WaveMaker you see what the app looks like in the browser. You don't need to go through a code-build-test cycle. It's all there in Studio. WaveMaker Studio has a LiveLayout feature that displays the information from your Java container services. If, for example, a widget gets information from a database then the Hibernate service is executed within Studio, allowing you to see the application data while you are developing. With LiveData in the development Studio you have a complete view of the visual (widgets and their interactions) and non-visual (backend service integration) behaviors of your application. All this is available within Studio.

3. Integration with other software products
WaveMaker is also embedded within other software products. These other products are build as web applications so the WaveMaker Studio architecture is a natural fit.

4. Software as a Service
Since WaveMaker Studio is a web application we are able to deliver the Studio as a SaaS solution. See WaveMaker Cloud Beta for more information.