If I create a services directory in /usr/local/etc/init.d and put the service scripts there the service tool panel displays services as a service. I believe the services scripts belong in /usr/local/etc/init.d which is where I had them. Then they show up in the tool panel correctly. Can you see in the code the exact commands that are being used for start, stop and status. What does pressing the button do and what turns on the green light?
The source code for TC3 alpha 4 doesn't seem available, I only had the code from TC2.11 to base my earlier comments on. Presumably the services tool has received an update then. Assuming the code is similar enough between 2.11 and 3.0a4 for the services tool, the button is just a toggle button. The logic is similarly just a toggle.
Application starts - get contents of services folder (keep in mind I'm working with the 2.11 code, hence continuing to reference the services folder)
Application queries each file found in services folder using status as described earlier
Application sets toggle button on or off, and tracks service status
User clicks button:
If light off, turn light on, start service (/usr/local/etc/init.d/services/samba start), update internal status for that service.
If light on, turn light off, stop service, (/usr/local/etc/init.d/services/samba stop), update internal status for that service.
It would be nice if the source code for the FLTK apps in the alphas was included (Or at least the oens that have changed) for those of us curious enough to try and work out how the new things / changed things work...