I think the biggest problem with tersus (minus the loading page popup and its long time, no back buttons, and google can't index tghe pages) is the huge learning curve.
I think it would be a great benefit for a simple hellow world application example in video that shows us how to create a tersus app and deploy it to your own tomcat. A simple hello world page.
Then how to customize the look and feel of that page - the html /css images etc... from the default tersus look of every page.
thirdly a dynamic example of the date is now: new Date()
Forth a dynamic user input example of amitaning user value state via a inpuit field of 'what is your name' for submit. from one url to another. scope if you will page vars. versus session versus application.
Lastly a short and simple beginning to end example of creating and deploying a custom looking simple to read and write blog pages. A user front end view and an admin user access login only create and edit view of pages and different urls, on my own tomcat server with my own look and feel from everthing to page design to buttons etc... Simply how to create a custom blog and deploy it with tersus quickly.
I think the ability to do simple variable if else should be simpler than it is in tersus and so should the ability to customize how things look. Also deployment to an agnostic java server via an export to war should be as easy as that.
export to war of any project tot he point i can simply import via the tomcat manager that war file and it will run on any java server.
It would be nice within the tersus IDE to be able to simply import any html page a designer makes with buttons and fields and automatically be able to add behavios to these existing fields and give them database state or a least persistence of the user's session or any of my choice.
Imagine being able to import any html into the ui with all sorts of forms and fields. that I can visually then link to a db column a session persistence e.g. the logged in user's name e.g. this form's fields should be saved to this db. what fields are required and what messages should appear and where and how they should look if the form failes to pass the validation data rules defined.
I just feel the lack of simplicity in a visual editor and intuitiveness is simply not there. I can be wrong since I an new to tersus
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign
