Skip to main content

Uniface 9: Declaration public web ; Make trigger public to web

  • November 19, 2018
  • 5 replies
  • 0 views
Jan Cees Boogaard

Declaration public web ; Make trigger public to web

Author: avner@one1.co.il (avner)

Hi all
For  Those of you that play with Uniface 9.4.cr

you must check and remember  to

Be aware that Declaration of   .....     Public web at the begging of  dsp detail trigger or as the first line in an Extended trigger is a must.
 

trigger onchange
public web   ; Make trigger public to web, else it will not be fire

  EDITBOX_ = EDITBOX
  return 0


end


;BTN_RETRIEVE DETAIL Trigger

public web 
retrieve/e "PERSON"
if ($status < 0)
  webmessage/error "Retrieve failed ($status = %%$status%%%)"
endif
return 0

 
 
 
Also the DSP does not behave/run on internet explorer 8 , you should use Firefox or etc' insted.

Also you can Easily see that there are differancees with the   get state , set state   triggers  if you  compare it  to the RIAWidgets project (widget1.dsp)

Does anybody Knows  Why there are differences ?
 


5 replies

Jan Cees Boogaard

Declaration public web ; Make trigger public to web

Author: avner@one1.co.il (avner)

Hi all
For  Those of you that play with Uniface 9.4.cr

you must check and remember  to

Be aware that Declaration of   .....     Public web at the begging of  dsp detail trigger or as the first line in an Extended trigger is a must.
 

trigger onchange
public web   ; Make trigger public to web, else it will not be fire

  EDITBOX_ = EDITBOX
  return 0


end


;BTN_RETRIEVE DETAIL Trigger

public web 
retrieve/e "PERSON"
if ($status < 0)
  webmessage/error "Retrieve failed ($status = %%$status%%%)"
endif
return 0

 
 
 
Also the DSP does not behave/run on internet explorer 8 , you should use Firefox or etc' insted.

Also you can Easily see that there are differancees with the   get state , set state   triggers  if you  compare it  to the RIAWidgets project (widget1.dsp)

Does anybody Knows  Why there are differences ?
 


Hi Avner,

looks like "the Lab" found a better implementation
concept during the betatest phase.

Better a change now than when a couple of us are using 9.4 productive.

AFAIK, Andreas Herzig has listed some changes between 94b3 and 94c1

Success, Uli


Author: ulrich-merkel (ulrichmerkel@web.de)
Jan Cees Boogaard

Declaration public web ; Make trigger public to web

Author: avner@one1.co.il (avner)

Hi all
For  Those of you that play with Uniface 9.4.cr

you must check and remember  to

Be aware that Declaration of   .....     Public web at the begging of  dsp detail trigger or as the first line in an Extended trigger is a must.
 

trigger onchange
public web   ; Make trigger public to web, else it will not be fire

  EDITBOX_ = EDITBOX
  return 0


end


;BTN_RETRIEVE DETAIL Trigger

public web 
retrieve/e "PERSON"
if ($status < 0)
  webmessage/error "Retrieve failed ($status = %%$status%%%)"
endif
return 0

 
 
 
Also the DSP does not behave/run on internet explorer 8 , you should use Firefox or etc' insted.

Also you can Easily see that there are differancees with the   get state , set state   triggers  if you  compare it  to the RIAWidgets project (widget1.dsp)

Does anybody Knows  Why there are differences ?
 


Hi Uli

I Think That it  should be  Reasonable demand to have the declaration "Public web"  inserted by default to the dsp triggers

Especially  those that are created using buttons(Detail)  or  the VLC  trigger
 

Avner


Author: avner (avner@one1.co.il)
Jan Cees Boogaard

Declaration public web ; Make trigger public to web

Author: avner@one1.co.il (avner)

Hi all
For  Those of you that play with Uniface 9.4.cr

you must check and remember  to

Be aware that Declaration of   .....     Public web at the begging of  dsp detail trigger or as the first line in an Extended trigger is a must.
 

trigger onchange
public web   ; Make trigger public to web, else it will not be fire

  EDITBOX_ = EDITBOX
  return 0


end


;BTN_RETRIEVE DETAIL Trigger

public web 
retrieve/e "PERSON"
if ($status < 0)
  webmessage/error "Retrieve failed ($status = %%$status%%%)"
endif
return 0

 
 
 
Also the DSP does not behave/run on internet explorer 8 , you should use Firefox or etc' insted.

Also you can Easily see that there are differancees with the   get state , set state   triggers  if you  compare it  to the RIAWidgets project (widget1.dsp)

Does anybody Knows  Why there are differences ?
 


Hi Avner,

I think "the lab" will modify for GA the defaults in the "U" model according to your suggestion
even without a wish or a bug entry if they read this Forum entry.

In the meantime, we can change the defaults on our own devices.

Still think it is a kind of usability we as the customers have a right to insist on.

SUccess, Uli

 


Author: ulrich-merkel (ulrichmerkel@web.de)
Jan Cees Boogaard

Declaration public web ; Make trigger public to web

Author: avner@one1.co.il (avner)

Hi all
For  Those of you that play with Uniface 9.4.cr

you must check and remember  to

Be aware that Declaration of   .....     Public web at the begging of  dsp detail trigger or as the first line in an Extended trigger is a must.
 

trigger onchange
public web   ; Make trigger public to web, else it will not be fire

  EDITBOX_ = EDITBOX
  return 0


end


;BTN_RETRIEVE DETAIL Trigger

public web 
retrieve/e "PERSON"
if ($status < 0)
  webmessage/error "Retrieve failed ($status = %%$status%%%)"
endif
return 0

 
 
 
Also the DSP does not behave/run on internet explorer 8 , you should use Firefox or etc' insted.

Also you can Easily see that there are differancees with the   get state , set state   triggers  if you  compare it  to the RIAWidgets project (widget1.dsp)

Does anybody Knows  Why there are differences ?
 


See we are reading this ;-)

The reason for this public web thing is security. By default triggers are not public to the web and therefor secure your data on the server; even with JavaScript hacking it is not possible to call triggers that are not defined as public to the web. We think that making a trigger public should be an explicit action and not the default. Of course you are free to change the defaults yourself.

Let us know what you think by replying on this message.

Gerton
Uniface Lab


Author: Gerton Leijdekker (gerton.leijdekker@uniface.com)
Jan Cees Boogaard

Declaration public web ; Make trigger public to web

Author: avner@one1.co.il (avner)

Hi all
For  Those of you that play with Uniface 9.4.cr

you must check and remember  to

Be aware that Declaration of   .....     Public web at the begging of  dsp detail trigger or as the first line in an Extended trigger is a must.
 

trigger onchange
public web   ; Make trigger public to web, else it will not be fire

  EDITBOX_ = EDITBOX
  return 0


end


;BTN_RETRIEVE DETAIL Trigger

public web 
retrieve/e "PERSON"
if ($status < 0)
  webmessage/error "Retrieve failed ($status = %%$status%%%)"
endif
return 0

 
 
 
Also the DSP does not behave/run on internet explorer 8 , you should use Firefox or etc' insted.

Also you can Easily see that there are differancees with the   get state , set state   triggers  if you  compare it  to the RIAWidgets project (widget1.dsp)

Does anybody Knows  Why there are differences ?
 


Hi Gerton,

The reading was about "modifying the defaults".

As I said in my previous message, I expect that I do not have to go
to each individual trigger to add some code to get a working web-page.

I think that in the context of the web (like DSP and USP), the defaults delivered with the Uniface Installation
should provide a no-stress default definition for mandatory triggers like VLC.

Let me recommend somel precompiler lines for the top of triggers for web-related components :

#ifdefinded PUBLIC_WEB_TRIGGERS
#for trig=(<PUBLIC_WEB_TRIGGERS>)
#if <trig> = <$triggerabbr>
   PUBLIC WEB
#endif
#endfor
#endif ; defined PUBLIC_WEB_TRIGGERS

And #define PUBLIC_WEB_TRIGGERS with a menaingful set of triggers.

Still gives me as a user the security option by modifying the #define,
but no need to modify each separate trigger.

Success, Uli


Author: ulrich-merkel (ulrichmerkel@web.de)

Recent badge winners

Explore all badges
Terms & ConditionsAccessibility statement