Create / Modularity

Widgetplus widgets are split in divisions and you decide what division (div) you wish to use.
The *trick* here is that even though you can call each div as a standalone app, they still share a common runtime, and can access eachother serverside while running.

In the previous installation, we looked at the data capablities, and it so happens that we use a dialogue, and that dialogue is another div in the source, and it directly manipulates the main div serverside, and we see that serverside update happen on the client too.
So, it's a synchronized client/server event - it happens simultainiously on the client and on the server.

Example app: Dialogue data settings

This app consists of two divs in the same app, so even though we open them as two windows, it's really one and the same app.

The first div

Here is the link that calls for this DIV.



The dialogue div

Here is the link that calls for the secondary dialogue DIV.




The full source file with both divs

And this is the result.

This means that you can create very sophisticated applications, which may appear as many applications, while still - in reality - being only a single application.

There's no upper limit to how many divs an application may have, and divs may contain divs in turn, and it's only a matter of what div ID you are calling.
All the divs share the same 'space' or 'runtime' on the server, and they are all infact a single unit, except from the clientside point of view.

Another example is here.

Split example

Close all

Please take note that this is all happening serverside, and that this could have been whatever serverside data.
The source file is here.