To help you understand how PPL 2.1 connects to your device and what technologies are being used, we have prepared a little diagram that explains the connection flows.

When you run a program on your computer instead of the device, the connection flow is almost the same. PPL IDE creates a local TCP/IP server, launches PPL 2 interpreter which in turn connects to the local server.

So I promised a new version of CleverUpdate and PPL 2 yesterday, I know. Sorry but I will delay it for another couple days but it will be for a good cause…

The Windows Mobile SDK is being fully tested and things are being made easier to setup. We have rewritten the debugger TCP/IP engine so that now the PIDE2 is the server and the client is the target application. This will make it a lot easier to setup Windows Mobile devices to connect to a server than act as a server.

I am still working very hard on the real-time profiler. It gives very important statistics about your program that is running. It gives the system and process memory used at the time each line is executed. It also gives you the CPU usage for the process. It also returns the number of hits and time spent on each line of code. You get nice charts and graphs for easily spotting the lines or functions that slows down your program.

Each memory allocated with PPL variables is logged and the amount of bytes used is as well. If you have memory leaks you will easily spot them.

I am still having difficulties with the CPU usage routine for the interpreter process, I hope it will be fixed tomorrow.

The TCP/IP debugger engine is performing quite well and is pretty solid so far.

I hope to post a screenshot of this wonderful tool very soon.

Another thing that will be added to PPL is the ability to take notes and assign them to lines of codes with deadlines and priorities. This proves to be a nice addition as you can have your to-do list tide to your code and objects directly in the project.