Home
>
WinDev Forum
>
Topic
WD23 and groupware
Posted by Jan de Bruin
|
Jan de Bruin
WD23 and groupware September 03, 2018 10:27AM |
|
Re: WD23 and groupware September 03, 2018 01:00PM |
Admin Registered: 54 years ago Posts: 280 |
|
Re: WD23 and groupware September 05, 2018 11:34AM |
Registered: 5 years ago Posts: 13 |
|
Re: WD23 and groupware September 05, 2018 01:04PM |
Admin Registered: 54 years ago Posts: 280 |
Hi aelfassi,
we wrote our own groupwares, a different one for each project, depending on necessities. They're tightly interwoven with our licensing scheme plus the ability to seamlessly switch between HFSQL Classic and HFSQL C/S. It would take many days to cut out and make a working & "neutral" groupware without the licensing and a few other "features". I'm sorry, currently there is no time & manpower for that.
we wrote our own groupwares, a different one for each project, depending on necessities. They're tightly interwoven with our licensing scheme plus the ability to seamlessly switch between HFSQL Classic and HFSQL C/S. It would take many days to cut out and make a working & "neutral" groupware without the licensing and a few other "features". I'm sorry, currently there is no time & manpower for that.
|
Re: WD23 and groupware September 05, 2018 03:26PM |
Registered: 5 years ago Posts: 74 |
|
Re: WD23 and groupware September 05, 2018 11:22PM |
Registered: 5 years ago Posts: 13 |
|
Re: WD23 and groupware September 06, 2018 10:17AM |
Registered: 5 years ago Posts: 192 |
Aelfassi,
start using the option to include the groupware in your project ("custom user groupware"). Together with the option to start it manually at runtime (a call to gpwOpen() )
From that point you are able to dig into it and see how it is done. Basicly a user/group has access to ALL controls until defined otherwise. So whenever you make a certain control invisible.inactive/disabled for a user/group, that will be stored in the groupware-database.If you get a peek into the tables you will see how things are organized. Quite simple if you ask me/
Then on window/page opening these records are loaded and the corresponding controls are set to the desired state. This is done by the WD/WB framework and works bug free if you ask me. But you can write and extend one yourself if you want.
Until a few years ago (can't remember the exact version) the built-in windows (talking about WD..) were looking really awful. Therefore I built my own one, still using the groupware database (but added some extra fields) and also letting the framework do the work when opening a window (as described above).
So you can use the grouwpare as-is.
You can use the groupware partially and extend/change where needed.
You can build one yourself from scratch,
Arie
start using the option to include the groupware in your project ("custom user groupware"). Together with the option to start it manually at runtime (a call to gpwOpen() )
From that point you are able to dig into it and see how it is done. Basicly a user/group has access to ALL controls until defined otherwise. So whenever you make a certain control invisible.inactive/disabled for a user/group, that will be stored in the groupware-database.If you get a peek into the tables you will see how things are organized. Quite simple if you ask me/
Then on window/page opening these records are loaded and the corresponding controls are set to the desired state. This is done by the WD/WB framework and works bug free if you ask me. But you can write and extend one yourself if you want.
Until a few years ago (can't remember the exact version) the built-in windows (talking about WD..) were looking really awful. Therefore I built my own one, still using the groupware database (but added some extra fields) and also letting the framework do the work when opening a window (as described above).
So you can use the grouwpare as-is.
You can use the groupware partially and extend/change where needed.
You can build one yourself from scratch,
Arie