[DUG] Advice on the TUMONZ SDK please

[Phil Middlemiss]

Thats a good idea. Cheers.

John Bird wrote:
> Re using localhost on a non networked pc, I am pretty sure there is a way,
> for instance I bet Google desktop search can do it.  I came across something
> similar when I found there is a way to use NET USE commands for a local
> printer where you can install the Microsoft Loopback adapter  (Go Google for
> more)  (Windows XP)
>
>
> http://support.microsoft.com/kb/839013
>
> SUMMARY
> The Microsoft Loopback adapter is a testing tool for a virtual network
> environment where network access is not available. Also, you must use the
> Loopback adapter if there are conflicts with a network adapter or with a
> network adapter driver. You can bind network clients, protocols, and other
> network configuration items to the Loopback adapter, and you can install the
> network adapter driver or network adapter later while retaining the network
> configuration information. You can also install the Loopback adapter during
> the unattended installation process.
>
> John
>
> -----Original Message-----
> From: delphi-bounces at ns3.123.co.nz [mailto:delphi-bounces at ns3.123.co.nz] On
> Behalf Of Phil Middlemiss
> Sent: Friday, 26 May 2006 10:47 a.m.
> To: NZ Borland Developers Group - Delphi List
> Subject: [DUG] Advice on the TUMONZ SDK please
>
>
> I need some general advice about the best way to go for building the 
> TUMONZ SDK.
>
> The SDK has a couple of objectives:
> 1) Provide a simple mechanism for feeding data for display in TUMONZ. 
> For this I am planning on using TCP/IP.
> 2) Provide interaction for mouse clicks etc for apps that need it. For 
> this I am planning on using ActiveX.
>
> I am thinking, at this stage of having two Active-X controls - one that 
> just wraps up the TCP/IP comms into simple methods such as AddIcon or 
> AddPolygon then SendData, and the second ActiveX for handling messages 
> such as when a client icon is clicked, or if a client app needs to 
> swallow a mouse click for placing a new icon.
>
> I want to keep the TCP interface rather than just use ActiveX for 
> sending data because it means that the sending app can be on a remote 
> machine running a different operating system.
>
> I don't want to try and handle the mouse interactions with TCP cause 
> that's just writing a whole middleware layer which is too big for our 
> timeline (the synchronisation issues alone!) and I'm going to assume 
> that apps that want to interact with TUMONZ are going to be running on 
> the same machine. The interaction ActiveX control can start TUMONZ if it 
> isn't already running. Developing ActiveX components is pretty easy in 
> Delphi.
>
> So here are my questions:
>
> 1) Is there a better way here that I've missed - I don't want to get 
> into middleware layers that are complex or costly and require extra 
> stuff to be installed on the client machine. I'm currently using Delphi6 
> but I have BDS2006 Pro, so perhaps there's a new technology in there 
> that I should be using instead?
>
> 2)  Are you still able to load and use TCP/IP for localhost comms if you 
> don't have a network card installed? The GPS Manager from verison 2 is 
> going to become a stand-alone app that uses the SDK to talk to TUMONZ so 
> we can't really go doing that if that means people without network cards 
> can't use it. If not is there a workaround?
>
>
> Phil.
>
>
> __________ NOD32 1.1461 (20060329) Information __________
>
> This message was checked by NOD32 antivirus system. http://www.eset.com
>
>
>
> _______________________________________________
> Delphi mailing list
> Delphi at ns3.123.co.nz
> http://ns3.123.co.nz/mailman/listinfo/delphi
>
>
>
>   
-------------- next part --------------
A non-text attachment was scrubbed...
Name: phil.vcf
Type: text/x-vcard
Size: 250 bytes
Desc: not available
Url : http://ns3.123.co.nz/pipermail/delphi/attachments/20060526/c2f1e8e8/phil.vcf