webdev 21 groupware

Startbeitrag von Allard am 15.10.2016 10:00

AWP versus dynamic webdev.

Hi I was looking at the groupware of webdev and noticed something when experimenting with this:

It is availeble in awp and dynamic web:

I never really looked at awp but now I did and something Odd happend. It seems that if you use AWP you can have hundreds of users on a webdev site As long as they do not do a mutation at exactly the same moment. And if this is the case then the webdev application server will have no problem with 10 simultanius actions.

AWP sessions only exist when generating the site. Then session is gone so application server is free again. Hmm cool. You really can have hundreds of users and still have no problem with the 10 sessions limit!!

That said AWP has to many limitations for me. The ajax stuff etc doesnot work etc witch makes the standard table useless in an application. And I like the fact I can see who is on the server.
But if you are into making all this yourself of have a simple application hmm take a look at awp ans save yourself the application server costs.



Hi Allard,

I'm using awp all the time, and I'm using AJAX a LOT with it... so when you say that ajax doesn't work in awp, I have to disagree...

And I making quite complexes applications in awp too...

And NOT for save 300$ on the server, just so that my site can be correctely referenced by search engines

Best regards

von Fabrice Harari - am 15.10.2016 11:58
Hi Farbice
PC soft is stating limitations themself on their site . Tables are limited .

from their site :

Limitations regarding the content and the programming of the AWP pages

First page of a project: An AWP page cannot be the first dynamic page of a project. An AWP page can be the home page of a project.
WLanguage trace functions: Only the output into a file is available (trFile constant).
Dialog boxes: The dialog boxes displayed by Confirm, Error and Info are ignored if a page is displayed in the same process by PageDisplay.
Global elements used in the project: When modifying an element global to the project (global procedure, query, class, ...), the project must be recompiled in order to take these modifications into account in the relevant stand-alone AWP pages.
Pagers: The pagers generated by RAD cannot be used in the AWP pages. Indeed, these controls use the project context (that does not exist in the AWP pages). These controls must be replaced by a programmed pager. Each link of the pager must display a page with specific data (page based on a query with parameters for instance).
All the records can also be displayed in a cell with scrollbar.
The pager in AWP mode automatically manages the method for passing parameters, without any programming. This type of pager allows you to reference all the linked pages and it avoids having to use cookies to store the current search.
Table control: The Table controls are limited (the browsing tables with Link columns do not operate anymore for example). They can be replaced by a looper (the links being built dynamically by the URL property).
Image control: No generated image can be used in the AWP pages.
Element in memory (list box, combo box, looper): The content of these elements is volatile. The content of these elements should be systematically filled in the initialization code of the page.
The value of the read-only controls is lost and it must be recalculated whenever the page is displayed.
Size of AWP pages: With large projects (containing several classes, global procedures or queries), the size of the generated AWP pages will be quite important.
Global server variables: The global server variables of the project regain their default value whenever the page is accessed in case of stand-alone AWP pages. However, you have the ability to use DeclareAWPContext or hidden controls associated with the requested value.
WINDEV or WEBDEV components: The components handled by an AWP page are not found. They must be moved to the _WEB directory.
Location of data files: The location of the data files must be performed in the initialization code of the project, via the following code line for example:
HSubstDir("?", fDataDir())
Relative URL: The relative URLs created by programming in the home page of the project must not be used.

von Allard - am 15.10.2016 13:40
Zur Information:
MySnip.de hat keinen Einfluss auf die Inhalte der Beiträge. Bitte kontaktieren Sie den Administrator des Forums bei Problemen oder Löschforderungen über die Kontaktseite.
Falls die Kontaktaufnahme mit dem Administrator des Forums fehlschlägt, kontaktieren Sie uns bitte über die in unserem Impressum angegebenen Daten.