I am still really bothered by this warning.
It’s like having MySQL throwing a warning every time I perform a query where 3 or more tables are joined for a single query.
I truly understand what David explained. But he also understands the need for developing application/solutions with more than three portals/tab panels in a form. But to explain my concern, I need to re-post these two points that David raised:
david wrote:You can use many tab panels as layout managers in smart client without running into quirky layout issues. In web client, piling on layout managers can have unintended side effects.
With all this said, the attached screen shot has uses 12 tab panels and it runs great up to 50-60ms ping time. We could easily create a view with three tab panels that would be dog slow.
I really think that Servoy shouldn’t have this warning as part of the warnings that will trigger from Servoy Developer when you are working on a standard/configuration/installation of Servoy Developer. Especially because there is a way to develop your application with “12 tab panels” and still runs it with a “great 50-60ms ping time.”
But, if Servoy really thinks that this warning is
very important, Servoy should offer alternatives and best practices in this regard. For instance, should the CRUD buttons be placed in every form rather than in a single form which can be placed then as a tab panel all other forms? And if so, shouldn’t those CRUD buttons be part of the CSS file? Am I correct? Don't know. I am really new too all of these goodies of the new Servoy architecture.
But what about when you really need to show data from many tables, what should we do? Should then use HTML forms and stop using some of the wonderful goodies that Servoy offers?
As I said, I really like Servoy 6.1. It is quite amazing development platform application. I am just asking for new how-to-do guides on how to develop with
"no more than 3 portals/tab panels" (as recommended in the warning) when you really need to show and edit data from many tables. The Docs are not enough. I think we need a guide, examples and a list of best practices in this regard.
Honestly, if I were as good of a developer as some of the stars in this forum, I’ll write this how-to-do guide myself.*
Best, Carlos
* "Stars in this forum," please do not take this message as if were indirectly asking you to do this. I think Servoy should. If I knew, however, I'll do just to give back to this community. You've already done a lot.