Has anyone come up with a method of continuously displaying information from a Baan database on any type of display? The goal is to have a running display of information available to a shop floor environment. The display can either be a stream type of display (e.g. a CNN type of running info display), or a frequently updated display of certain items of information (such as a frequently refreshed information box in a corner of a display).

Steve Ruger
sr@mylodestar.com

No, but a cool idea.

There are plenty of java applets out there that will handle displaying any text in basically any form you feed it.

Using that, all you need is to extract the desired data in text format through bdbpre, exchange or directly from the database on a regular basis.

Sounds doable?

Why not have a baan session that in the init.form that does an execute(cont.process). Then in the choice.cont.process you could call a subroutine that is in a continuous loop. Of course you would have to kill it from the shell.

Something like this:


form.1:
init.form:
execute(cont.process)

choice.cont.process:
on.choice:
testloop()

functions:
function testloop()
{
long i,j

i = 0
while(1)
pager.number = str$(i)
display.all()
i = i + 1
for j = 1 to 10000
endfor
endwhile
}


Did this in a test script, of course you would probably want to display something useful.:)
You could put in a select in the while loop and display everything in the set and it would just keep repeating.

Mark

It seems a good idea,... I would like to something like the ttgbfprocess, the process browser, which acts like a java applet, when it gets the focus it automatically refreshes and gets the latest processes on the current bshell.

We are on the BaaN-5.2 where the gbf is moved to the tools package "tt". In the earlier versions, the gbf is under the "tg" Orgware package, maybe some one can look into the code and make a prototype to start with...

In the past, I wrote a set of sessions that executed and "Monitored" the steps and status of activities in a data conversion WBS.

The two sessions below were used to control the "Monitor" process. Hope it helps you out ....


|*****************************************************************************
|* Some Parent Session with Start Monitor and Kill Monitor User Options
|****************************** declaration section **************************
declaration:
long mon.id | monitor process id
|****************************** program section ******************************
after.program:
|* Kill monitor if it's still running
if mon.id <> 0 then
kill(mon.id)
endif
|****************************** form section *********************************
form.1:
init.form:
mon.id = 0
|****************************** choice section *******************************
choice.user.0: |* Start Monitor
before.choice:
if mon.id = 0 then
mon.id = activate("tuddctk22m000")
else
message("Monitor is already running")
endif
choice.again()

choice.user.9: |* Kill Monitor
before.choice:
if mon.id = 0 then
message("Monitor is not running!")
else
kill(mon.id)
mon.id = 0
endif
refresh()
choice.again()

|******************************************************************************
|* Monitor Session
|****************************** declaration section ***************************
declaration:
long last.time
long curr.time

|****************************** program section ********************************
|****************************** form section **********************************
form.1:
before.form:
last.time = time.num()
while true
curr.time = time.num()
if curr.time >= last.time + 10 then
|* Refreshes ever 10 seconds
execute(first.set)
last.time = curr.time
endif
endwhile
|****************************** Table section ********************************
main.table.io:
after.read:
|* Control data displayed here if need be using skip.io
if --data.not.in.condition-- then
skip.io("")
endif

I haven't checked but wouldn't the option Refresh Interval (sec) in maintain user data template be usefull?

Han

Hans,

Here is more info about - "When will "Refresh rate" option be enabled?"