NetTalk Central

Author Topic: Multi-DLL Menus and Such  (Read 2797 times)

DonRidley

  • Don Ridley
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 729
  • donaldridley2011@gmail.com
    • View Profile
    • Email
Multi-DLL Menus and Such
« on: March 07, 2018, 02:09:20 PM »
Hello All,

I just split up a single EXE app into a multi-DLL app.  Currently it is very basic.  A data DLL, a DLL with my main/exported procedures (most of my old app), a WebServer DLL, and a Main EXE.

I want to further break down the procedures into smaller DLL's.

My question is this:

Where do I put my menus?  Currently in the PageHeaderTag.  I'm just curious how to place everything.  I would like to have a small DLL with the basic stuff like the IndexPage, Header (with menu) and Footer and have all my other procedures separated into various other DLL's.

How have you approached this?

Thanks,

Don
"Eliminate the impossible, whatever remains, however unlikely, must be the truth."

NetTalk 12.55
Clarion 11

bshields

  • Sr. Member
  • ****
  • Posts: 392
    • View Profile
    • Inhabit
    • Email
Re: Multi-DLL Menus and Such
« Reply #1 on: March 07, 2018, 08:44:40 PM »
Hi Don,

I'm currently breaking up the main web server of a system as we are exceeded the 64MB exe limit. We are getting the error "Error( 8 ) : cifm$lnew Not enough storage is available to process this command." (if anyone has a magic solution for this would love to know).

This is where we are at:

1. All supporting services and management systems go into other apps (we started this way, but a good reminder).
2. We have a general purpose Tools.DLL for all our non-database dependant general tools.
3. Data DLL with all low level business logic, no NetTalk Page code. But we push all our reports and other non-UI stuff down here. We hand write reports (except for FRB reports that are served via specialist NT Web Server), so no NetTalk interaction for them.
4. Server EXE which includes Tools and Data and contains bulk of the system particularly the UI.

Our Server EXE is still 64MB will all debugging off, so i now have to do something else.

Its a difficult choice next, as i need to try and keep things simple as there are heaps of cross procedure dependencies and its essential I don't do anything stupid that could cause GPFs or instabilities.

I'll let you know what I do, meanwhile I'm also interested in what others do.

Regards
Bill

DonRidley

  • Don Ridley
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 729
  • donaldridley2011@gmail.com
    • View Profile
    • Email
Re: Multi-DLL Menus and Such
« Reply #2 on: March 08, 2018, 02:44:19 AM »
Thanks Bill.

Your WebServer EXE is still over 64MB?  I know all your NetWeb procedures have to be declared under the WebServer as Externals but they takes up very little space. 

I'm running my WebServer as a DLL under a very small "Main" EXE.  I basically used Example 20 as a framework. 

I look forward to hear how it works out for you.

Don
"Eliminate the impossible, whatever remains, however unlikely, must be the truth."

NetTalk 12.55
Clarion 11

bshields

  • Sr. Member
  • ****
  • Posts: 392
    • View Profile
    • Inhabit
    • Email
Re: Multi-DLL Menus and Such
« Reply #3 on: March 08, 2018, 03:22:15 AM »
Hi Don,

Thanks, I'll take a look.

That is how we do our desktop systems. Basically small EXE with the menu and a big pile of DLLs for all the code.

I can create an EXE with externals to all my procs, but i'll still end up with a big central DLL with all the interdependent procedures.

But, it will probably help, so thanks for the reminder.

Regards
Bill