Achieving one code base with forms and windows

It sounds like you are on the correct path.

We dump as much as we can into object classes and we use it in thick client
windows and remote forms… one code base.

On the remote form we create an instance variable such as oDataAccess with
a subtype to the object class itself.

ie. we get a quote from many areas of our system so we have something like
the following on the remote form: Do
oDataAccess.$GetQuote(iv_QuoteRow,pv_QuoteID)

Andrew

On Wed, Feb 7, 2018 at 1:44 PM, Das Goravani <das@goravani.com> wrote:

>
> So to achieve one code base while having fat client windows and remote
> forms that replicate each others functionality, one would use Objects and
> Table Classes to hold the code so that it’s not replicated in the form and
> the window, correct?
>
> Tables are best for that code which addresses the row or list it is
> related to because one does not have to do extra work to address said row
> or list.
>
> Object classes are repositories for code
>
> Once you have put your code that would be in the window or form, into
> object and table classes, one has very little code left in the window and
> form, just the calls to the code in the object and table classes, the
> passing of parameters too
>
> I think all of the above is correct. Is that correct?
>
> My question then is, I have heard someone knowledgable say that they
> instantiate their object classes into the form and window. Would this be to
> make calling into the object easier since it’s then an instance variable of
> the window? (I’m really out of my knowledge base now, completely unsure
> what I’m saying)
>
> How do you get the code you wrote in an object into an instance variable,
> is it by subbing it to the object you put code in… I’m not sure what
> subtype really does when it’s an object with code in it
>
> I want to move windows I have created (fat client windows) into being
> forms for iPads
>
> I have the windows done and working great.
>
> Now do I move the code to Tables and Objects for their respective
> qualities, make sure it all works, have to add ref’s and such things…then
> create my form replicating my window say, and call the code from it as
> well, with very little code left therefore in the form just like very
> little left in the window.
>
> Is this the overall idea ? Am I onto the path here of “one code base
> multiple platforms” correctly?
>
> My only question revolves around an unknown for me and that is what is the
> way to make the coding easiest…is it by putting the object somehow into the
> form and window…see I don’t know what subtype does…or do you assign your
> real object to an instance object…again this is only to make the code
> easier, otherwise I know I can call tables and objects without them being
> embedded in the window (tables can’t, I get that)
>
> OK thank you in advance,
>
> Das Goravani
> _____________________________________________________________
> Manage your list subscriptions at lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en@lists.omnis-dev.com
>
_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com
Start a new message -> mailto:omnisdev-en@lists.omnis-dev.com