paragui-users
[Top][All Lists]
Advanced
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[paragui-users] want to run my dll idea for pg past anyone who cares to

From: Keith Swyer
Subject: [paragui-users] want to run my dll idea for pg past anyone who cares to look
Date: Tue, 4 Jun 2002 15:31:32 -0300 
well, i have been asking a few questions about dlls and pg etc latley, so i
thought i'd run my idea by you...

- make changes to the loadlayout to incorporate a tag in the head for any
dlls you want to dynamically load
in your app at runtime. somthing like...

    <DLL name proxyname baseclass>

    name - the name of the dll
    proxyname - the name of the exported function that will instantiate your
new class
    baseclass - the baseclass that your new class uses (maybe not needed)

- in the loadlayout function all of the dlls will be loaded and instantiated
into a list held in the PG_Application class
         map <string, baseclass *, less<string> > _map;

    we can then load the dll and insert a new class:
        _map[name] = instantiate(proxyname)

 of coarse one limitation is easily seen.....you can only use one baseclass
type for ALL dlls used

- now, back in your main program you will be able to access the _map with
all of the classes and since they are
all derived from your baseclass, you don't need to know the names of them to
call functions. and with the map, you can get the name of the new class.

PG_Application will possibly need a few new members. ??

- personally, what i am trying to accomplish is the following.

the main app loads a layout which is the 'main menu' and given any dlls in
the <head> new buttons are added
to the menu. I am not worried about doing this dynamically, whenever new
dlls are added, you change this main
layout to add new buttons.  now with the new buttons attached to their dlls,
pressing a button will bring you to
a new 'area', hiding the main menu and showing all of the new 'area' by
calling a member such as ShowArea() in the dll. THe class in the dll in turn
holds a list of all of its widgets so that we can show/hide all of them
witout have to destroy then create them again by moving b/w 'areas'.

anyway, can anyone see any major flaws or see anything that should be
added.?

-Keith
reply via email to
[Prev in Thread] Current Thread [Next in Thread]