DonationCoder.com Software > N.A.N.Y. 2011

NANY 2011 Release: NetLaunch

(1/8) > >>

kamahl:
NANY 2011 Entry Information
Application Name NetLaunch Version 1.0 Short Description Netlaunch is a program to launch applications based on Network status.   It functions in both Agent (GUI) and command-line form. Supported OSes Windows (XP+) Web Page None yet Download Link NetLaunch 1.0.1.zip (461.49 kB - downloaded 2355 times.)System Requirements
* .NET Framework 4
* Windows XP or higher
* A network interface (preferably not always connected)Version History
* 16 July 2010 - PreAlpha: 0.0.0.zip (41.51 kB - downloaded 1590 times.)
* 2 August 2010 - PreAlpha: 0.0.1.zip (42.96 kB - downloaded 1488 times.)
* 6 August 2010  - Alpha: 0.1.0.zip (11.86 kB - downloaded 1508 times.)
* 1st January - 1.0 Release! NetLaunch 1.0.zip (50.7 kB - downloaded 1605 times.)Author Kamahl

Description
NetLauncher is designed for use on a computer (probably a netbook), which is often going in and out of wireless access.

The idea is that NetLaunch will sit as a background agent, and check network status.  On status change, the program will launch/quit programs depending on user-defined rules.

Sample ConfigurationNetwork activated:

* Launch Pidgin
* Launch Windows Live SyncNetwork deactivated:

* Kill Windows Live Sync process
* Gracefully close pidgin
* Prompt user whether to close Firefox

While this app will not be useful while sitting in a flaky wireless area, it is perfect for people who travel between areas with wi-fi, and those without wi-fi (or just none that you have access to :P).

Features

* Command-line arguments for once-off launch checking.
* Agent mode
Planned Features
Per-interface rules (possible, not yet sure whether it's worth it.)

Screenshots
NANY 2011 Release: NetLaunch

Usage
Installation
Extract zip into a folder.  Not much of an install process yet.

Using the Application
Using the Command-line Interface is best done with a shortcut, or FARR item.
NetLaunch.exe -u "C:\Program Files\pidgin\pidgin.exe" -u "C:\Program Files\Windows Live\SyncUX\wlsync.exe" -d pskill.exe [pidgin.exe] -d pskill [wlsync.exe]

Uninstallation
Delete Files.

Known Issues

* Can't launch apps with command line arguments, as NetLaunch eats them.
* Still no GUI.
* Cannot edit or delete tasks.
* Adaptor Blacklist may be wrong in places.  If someone finds an adaptor that is incorrectly allowed/blocked, please tell me.

Original PostNetLauncher is a piece of software I'm designing for use on a computer (probably a netbook), which is often going in and out of wireless access.

The idea is that NetLauncher will sit as a background agent, and check network status.  On status change, the program will launch/quit programs depending on user-defined rules.

Sample configuration (my netbook):
Network activated:

* Launch Pidgin
* Launch Windows Live SyncNetwork deactivated:

* Kill Windows Live Sync process
* Gracefully close pidgin
* Prompt user whether to close Firefox
While this app will not be useful while sitting in a flakey wireless area, it is perfect for people who travel between areas with wifi, and those without.

It will also have a command line interface, to allow users to run actions without the use of an agent.
IE: NetLaunch.exe -u "C:\Program Files\Pidgin\Pidgin.exe"
or: NetLaunch.exe -d "pskill.exe Pidgin.exe"

It will be a Windows-only application.

Perry Mowbray:
Welcome! This looks like a nifty idea  :Thmbsup:

-- which reminds me... I must get a netbook...  ;)

lanux128:
nice, this will come in handy for those on the move..

sgtevmckay:
Greetings kamahl   :D
Welcome to DonationCoder.com

This is truly a concept who's time is well past due.
I see the potential in such a piece of software that could potentially grow into something huge.

Look forward to your builds.

Have fun  ;)

Regards
The Sarge

kamahl:
Hey guys, I've got a question for you.

I've set up two different methods for identifying an 'active' network, both with pros and cons, and I'm wondering which should be default

Method 1: Adapter Status
Check the status of the computer's network interfaces.
Pros

* Instantaneous
* Uses no bandwidthCons

* Fooled by VMware-like adapters (will create a adapter blacklist to combat this bug)
* Fooled by down-the-line failuresMethod 2: Ping
Send a ping to an online server
Pros

* Not fooled by VMware or dead connections (see above)Cons

* Uses bandwidth (bad if on a 3G connection)
* Fooled by honeypots (but then, so is the other method)
* Relies on target server being alive (I'd go for something like the Google public DNS, as it has near-perfect uptime)
* Will have minor (~10ms) latency
I plan on implementing both (Method 2 is done, and method 1 is 90% complete), however I would like your opinion on which to implement as the default method.
Once I get method 1 completed, I plan on releasing a command-line only build for public testing - This should be in a week or so.

Navigation

[0] Message Index

[#] Next page