Igor:
This looks pretty good. Can we change it so that if we're
in RELEASE mode, the _DYNAMIC_LINK_GNUCLEUSPROTO_DLL is defined, but
if we're in DEBUG mode, then it builds with _DYNAMIC_LINK_GNU...
undefined. That'll prevent unneeded "Debug assertion" message boxes.
We can update the "Components" tab as well, now, so that
it includes Gnucleus as an element.
thanks,
Scott
On Mon, 2 Sep 2002, Igor Kotelevsky wrote:
> Hello Scott.
> You wrote:
> > Okay, we should fix that first. Kaboodle shouldn't require
> > GnucleusProto.dll to run. If it's not there, the user simply cannot
> > use the VPN capability.
> I implemented that. But there is a problem.
> There absent a short way for good such implementation.
> It is a particularity of MFC library:
> GnucleusProto.dll creates an object, which inherit from MFC class CWinApp.
> Kaboodle.exe also creates such object.
> It is a rule of MFC - only single object CWinApp.
> If we use *static* link of GnucleusProto.dll
> - then above rule can be break up.
> But if we use *dynamic* link of GnucleusProto.dll - then above rule live,
> and we have many MessageBoxs *debug assertion failed*.
>
> Please remove a commentary from the line
> / / #define _DYNAMIC_LINK_GNUCLEUSPROTO_DLL
> in the file stdafx.h and you'll get what you want.
> The application works, but there is 5 MessageBoxs *debug assertion failed*.
> There need a full rewriting of GnucleusProto.dll source code,
> if we want to get a correct work of the application
> without above MessageBoxs.
> Above alteration will require refusal of use the object CWinApp.
> Therefore we cannot use MFC library on all amounts.
>
> - Igor
>
> ----- Original Message -----
> From: "Scott C. Best" <[EMAIL PROTECTED]>
> To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> Cc: "Kaboodle-devel" <[EMAIL PROTECTED]>
> Sent: Sunday, September 01, 2002 8:54 PM
> Subject: Re: Components tab
>
>
> > Igor:
> > Sorry for the late reply about this. Some comments inline:
> >
> > > > What 'd like it to show is a list of the add-on binaries
> > > > that Kaboodle uses: Gnucleus, VNC, WinPCAP, ZeBeDee.
> > > There are members of two kind in above list:
> > > a) - Binaries, which are *obligatory* part of Kaboodle.
> > > Without them a user cannot to run Kaboodle.
> > > Please try to remove GnucleusProto.dll and start Kaboodle.
> > > You will see a MessageBox
> > > *The dynamic link library GnucleusProto.dll
> > > could not be found in the specified path...*
> > > and Kaboodle didn't runs.
> >
> > Okay, we should fix that first. Kaboodle shouldn't require
> > GnucleusProto.dll to run. If it's not there, the user simply cannot
> > use the VPN capability.
> >
> > > Also I know that Kaboodle always activate GnucleusProto.dll at
> > > start up. I guess that Kaboodle will activate ZeBeDee at start
> > > up also. (I didn't know that Kaboodle uses WinPCAP now.)
> >
> > See, if this feature was working, you'd know that Kaboodle
> > was trying to use WinPCAP. :)
> >
> >
> > > It seems to me that it is not interesting for user to see
> > > an information about such binaries.
> > > I suggest didn't include in "Components" list binaries,
> > > which are *obligatory* part of Kaboodle.
> > > Otherwise the status of them will be "active" always.
> > > There are many other system binaries,
> > > which are *obligatory* part of Kaboodle, for example:
> > > ws2_32.dll, Rpcrt4.dll, Crypt32.dll, netapi32.dll, mpr.dll, etc.
> > > You can open Kaboodle in "Dependency Walker"
> > > - Microsoft Visual Studio\Common\Tools\depends.exe
> > > and see list of all binaries, which used by Kaboodle.
> > > There are several tens of such binaries.
> > > Why we need show GnucleusProto and don't need show above tens?
> >
> > I don't want to show system binaries, but I do want to
> > list optional component binaries. My list right now is: Gnucleus,
> > VNC, WinPCAP, ZeBeDee. Each of them should have a status field
> > that says either "Active" or "Not Installed".
> >
> > > b) - Binaries, which are *optional* part of Kaboodle,
> > > but which allow to expand Kaboodle's functionality.
> > > For example, VNC is such binary.
> > > If a user will open "Components" tab and see that VNC didn't installed
> > > yet, then the user can click "Get Info" button and
> > > see how interesting VNC service is.
> > > After that the user may be decide to install VNC.
> > >
> > > So I suggest include in "Components" list binaries,
> > > which are of kind 1.b only.
> > > Please let me know what you think about that.
> >
> >
> > I think we pretty much agree. Gnucleus, VNC, WinPCAP,
> > and ZeBeDee are all optional parts of Kaboodle and should be
> > listed.
> >
> > > 2. Now I see only single component VNC,
> > > which can be implemented in above tab.
> > > I suggest divide that component into two parts:
> > > VNC server and VNC viewer and show both these parts independently.
> >
> > Actually, it's very unusual for a system to have one
> > and not the other. I'd rather it just have one line that says
> > either "Active" or "Not Installed".
> >
> > I'd also like to change the layout of the Components
> > tab so that it looks like the "Main" tab of the VNC Service
> > icon. That is, it has some explanation text on the left, and
> > then a scrollable list of Components in the middle, and then
> > then "Get Info" and "Homepage" buttons either on the right
> > or at the bottom. The explanation text can read "Kaboodle
> > makes use of a number of other standalone applications to
> > achieve its overall functionality (hence the name!). A list
> > of these components, and their installation status, is shown
> > here".
> >
> > Thanks!
> >
> > -Scott
> >
> >
> > > ----- Original Message -----
> > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > Cc: "Kaboodle-devel" <[EMAIL PROTECTED]>
> > > Sent: Thursday, August 29, 2002 10:56 AM
> > > Subject: Components tab
> > >
> > >
> > > > Igor:
> > > > Now that the "Web Config" is working, in addition to
> > > > the interface bug problem, here's what I was hoping you could
> > > > work on: the Component tab of a PC running Kaboodle is currently
> > > > empty. What 'd like it to show is a list of the add-on binaries
> > > > that Kaboodle uses: Gnucleus, VNC, WinPCAP, ZeBeDee. For each
> > > > of these components, I'd like there to be a column called
> > > > "status" which indicates whether the binary is installed and
> > > > active or not. Each one of these components should be select'able,
> > > > and the user can click a "Get Info" button, which will open
> > > > a messageBox that tells about the binary (have a look at
> > > > www.Kaboodele.org, click on "Components", for some sample text).
> > > > I'd also like there to be a "Homepage" button underneath the
> > > > "Get Info" button -- clicking on that while a components is
> > > > selected will open a browser to that app's homepage.
> > > >
> > > > You've seem to got a good feel about how I like the
> > > > PropertyTabs to be laid out, so feel free to design it as you
> > > > have been doing. Thanks!
> > > >
> > > > -Scott
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
>
>
>
>
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
