RAD Pattern project, Your opinion please.

Hi folks,
I would like to here your opinion regarding RAD pattern projects.
Do you like it ?
Is it difficult to use ?
Is it flexible enough ?
Why you don't use it ?

and so on...

Many thanks, Björn

Icebreaker

I think the Rad pattern is a very useful weapon in our developer arsenal. Nevertheless a few things are not very clear to me. For instance :
According to the on line help

RAD pattern generation :
Tip: We recommend that you only offer the windows or pages that relate to the RADFileB and RADFileD files.

So, why ?

RAD Table and Form
If needed add link buttons
If needed add Vision plus buttons.

When ? Or in other words, what is the indication to use a link, respective a vision plus button ?

Further :
I wonder how the window template stuff fits into the RAD pattern mechanic ?

Why the OOP RAD is called depreciated. ? I would like to reuse them.

What da ya think ?
Björn

Hi:
I created my own RAD pattern and it's great! But in my case they are useful
just to automatically generate de basic View/Insert/Modify/Delete/Print of
the tables. After this, you need to manually create each of the rest of the
program's windows (processes, reports, etc).
In my case, I created the windows and buttons exactly as I wanted throught a
Windows Template, and then I applied this tempate to the RAD so now, all
windows have my own look and feel. Besides, I added popup menu in the table
to call the form, and other interesting things (like highlight the field
that has the focus in the form..) which are nice to include in my
application.
I also defined an specific window aspect (I created my own skin) and a style
for the tables. Both are inserted in the RAD. So once I generate using this
RAD in a new project, everything (skin, table styles, etc) is available for
subsequent windows (even, if they are created manually).

Respect why to only offer windows for RADFileB (and not RADFileA and C) it's
because they are basically the same..I mean, all those windows are used when
you create a full-RAD, so if you have an Orders table, which has a Details
child and a Customer ancestor (the Orders will have a lookup for Customer
table), then those different windows are used for each different tables. But
when you will generate a Windows based on RAD, it will not generate all the
other windows, so it would be almost the same to use the RADFileA or
RADFileB. That's why they recommend to offer RADFileB only.
In my case, I only included Vision buttons wich allow you to create lookup
fields in the form. For ex, in Orders form you can open the Vision table for
Customers and select (or even create a new one) the desired customer for the
order.
I did not include Links buttons because these are to create a link to the
details od the child table. Let's say you have an Order form, you would have
a link (button) which opens the Details table window. In my case, I don't
want to have all windows with such a Link buttons because it's a mess. Only
some specific windows would have access for the child's detail window. May
be, in such a case, the detail table would be in the same window...
In order to create the RAD pattern you need to create many windows, so if
you create a window template with the common things (including the skin) you
will have all RAD windows with the same common look and feel.

Regards;
Gus



"BLS" <guest@news.pcsoft.fr> wrote in message
news:65092009041710500451.25667@news.pcsoft.fr...
>
> Icebreaker
> I think the Rad pattern is a very useful weapon in our developer arsenal.
> Nevertheless a few things are not very clear to me. For instance :
> According to the on line help
> RAD pattern generation :
> Tip: We recommend that you only offer the windows or pages that relate to
> the RADFileB and RADFileD files.
> So, why ?
> RAD Table and Form
> If needed add link buttons
> If needed add Vision plus buttons.
> When ? Or in other words, what is the indication to use a link,
> respective a vision plus button ?
> Further :
> I wonder how the window template stuff fits into the RAD pattern mechanic
> ?
> Why the OOP RAD is called depreciated. ? I would like to reuse them.
> What da ya think ?
> Björn
>


Message forwarded from pcsoft.us.windev

Many thanks for the inside view Gus.
A few remaining questions :

1 ) Do you start with window templates ?
- Where did you enter the code for let's say an OK Button . Within the Form pattern or within the adequate window template ?

2 ) Do you encounter any problems with MDI child windows in your RAD pattern
- I f.i. would like to have a RAD Table Pattern as MDI child window.

3 ) Is it possible to create a RAD Table with Table pattern, or a Form Table pattern using WD12's new RAD. In other words, takes the new RAD care about relationships.

In other words can I replicate all the WD 11 RAD stuff.

Many thanks in advance !, Björn

Hello Bjorn:

To answer your questions:
1 ) Do you start with window templates ?
- Where did you enter the code for let's say an OK Button . Within the Form pattern or within the adequate window template ?

I just use the Window Template in order to have all windows with the same visual appearance...In my case, I created a customized window (using my own background image...). Then, I applied this template to all my windows in the RAD. You can add all controls and/or code you want to have in every windows in the RAD. But if this code will reference a file, it should be added to the windows RAD (these windows are used when generated the code, and replace the filenames with the file selected from the analysis).
Another option is to use generic code in the template using Indirection. But I didn't use it in my RAD.

2 ) Do you encounter any problems with MDI child windows in your RAD pattern
- I f.i. would like to have a RAD Table Pattern as MDI child window.

In my RAD I'm using Free windows, not MDI windows. In the menu, I'm using OpenChild() to open the RAD generated windows.

3 ) Is it possible to create a RAD Table with Table pattern, or a Form Table pattern using WD12's new RAD. In other words, takes the new RAD care about relationships.
In other words can I replicate all the WD 11 RAD stuff.
Yes, I think it's quite possible, althought I didn't try it yet. But be aware that there is a bug when you generate the RAD...Please refer to this:
[forum.pcsoft.fr]

I can also send you my RAD if you want...The tedious part is to generate the required analysis, which is common to all the different RADs you may want to create.

egards;
Gus

WOW, that is very generous. ! Yep, I would like to study your RAD pattern.

nanali at (wanado) dot fr

THANKS! Björn

Gus !
I will also be interested to see your RAD and maybe get idea about main and if you have no any restriction to me maybe use yours
Sorry, I forgot : exelent@bih.net.ba



Edited 1 time(s). Last edit at 04/19/2009 10:02PM by ICI.

Hi Bjorn:

I wasn't able to reach you via the provided email.
Please, send me an email to gus at yahoo dot com and I will reply your message.

Regards;

Gus

Hi Gus,

I've posted several threads on the subject of the WD RAD - It looks great in theory, but I've had trouble getting it to work in the way I wanted it to. I had to give up in the end and resort to several window templates to achieve my requirements.

This said - would it be possible for me to take a look at your RAD to see if I can understand it better?

My email is darren_farmer at hotmail dot com...

Many thanks in advance...

Hi Gus , send you an email.

Beside, did you file a bug report to PC Soft ?

Björn nanali at orange dot fr