Tersus: Future Development

Future DevelopmentDate: Dec 17, 2008After the very insightfull discussion on http://www.tersus.com/#Id=1809 here some other thoughts about the future development. Maybe it's the wrong forum (please replace it to the correct one)1) I think this kind of discussions about future functionallity is very interesting, maybe it's possible to create a new forum (wishlist) where we can discussing this kind of stuff. Or is the "Platform Development"-forum for this kind of discussions?2) It would also be interesting to know what kind of applications are developed with Tersus.

I've developped a Helpdesk (integration with Nagios), CRM, small Administration (Projects, Costs, Invoicing, etc.), Timeline, Document generator and some snippets like a Helptext-module, Treelike menu

Can you place some of your applications in the Applications area, or must we create a Marketing-place where we can buy some of the applications build with Tersus.

3) As a followup from my previous point, what are the problems/difficulties someone has in developing an application. So someone doesn't have to reinvent the "wheel"

The discussion about the calendar from Pawel was such an example, is it working? Are the endusers happy? What kind of improvements are you thinking about?

I've several applications, which are used by the same endusers. But endusers are mostly very stupid/simple, so how can I integrate them? Making one big application, or creating a kind of dashboard and if so, how can I avoid relogin in every application. What's your idea?

The Look and Feel is very important for endusers, so what kind of options are you using in every screen, besides the default ones (Next/Previous/New/etc.). I've in almost every screen a Print and Help button, but I'm also thinking about

An Export/Import button;
I want to store/load all the defaults from every "Advanced Table Display"(From/Next/Sort/etc.) per user. What's the best way a table? a cookie? And more important, where to place the (menu)button.
Extjs (http://extjs.com/) and Google has many great ideas about the layout of a screen.

Upgrading Tersus in an operational environment, what kind of problems where found, how to avoid this kind of problems

Example: From version 1.1 the html.customNavigation is introduced, this means every application must be changed. What's the best way to migrate, temporarely 2 tersus-server environments (old/new), or replacing all in one time (with a fallback scenario)

Ofcourse there are other points, please mention them.

4) Documentation, there are many improvements in Tersus, and many of them can be found in the changelog or document section. But is it possible to get an email of this improvements, like the subscription of the forum.At last, this post is not only for the Tersus guys, I'm also very interested in the opinions from all others.JPSee Also:

Re: Future Development

To use the full functionality of this web site, JavaScript needs to be turned on.

For best results, use the Firefox browser..

Loading ...