With HS 2 beta out there and kicking, I thought this would be a good time to give everyone a detailed progress update on WAPSeer 3. As most of you know, WAPSeer 3 is the next generation of WAPSeer, running as a compiled plug-in instead of script, and it'll be a free upgrade to all WS 2 owners. With that...
General Status
I'm spending several hours a day on WS 3, and it's coming along very nicely. I've managed to "borrow" more WS 2 code than I originally thought I'd be able to, which is helping things move more quickly. Everything related to events is working, location display is working and device on/off is working. The framework for a lot of other stuff (like device dim, Compose, script-based thermostats, QuickList, etc.) is in there, but not quite working yet. One thing I can say is that, being compiled, the new code is definitely several times faster than the old version. It's crisp, even on a local 802.11* network.
Big New Features
From the mobile device side, WS 3 looks and works like WS 2 did. I didn't want to tinker with something that worked. However, there will be a number of new features that have been requested or make sense:
Smaller (but still important) Stuff
WML Mode
This is something that I'm stuggling with, and I could use some community input here. Supporting WML mode is cumbersome, because it requires supporting an entirely seperate WAPSeer code base. I'm strongly considering dropping WML mode support. However, if a large number of users needs this functionality, I'll continue to support it. If you have an XHTML compliant phone, test with HS 2 and WAPSeer 2.1's XHTML mode (WAPSeer.ash). If that still doesn't work, but WAPSeerWML.ash does, please let me know in this thread.
Your Thoughts
If there's something you've been wanting to see in WAPSeer and it's not on the new features list, feel free to post here. I'll do my best to include it!
Thanks much for your business (and your patience),
Justin
General Status
I'm spending several hours a day on WS 3, and it's coming along very nicely. I've managed to "borrow" more WS 2 code than I originally thought I'd be able to, which is helping things move more quickly. Everything related to events is working, location display is working and device on/off is working. The framework for a lot of other stuff (like device dim, Compose, script-based thermostats, QuickList, etc.) is in there, but not quite working yet. One thing I can say is that, being compiled, the new code is definitely several times faster than the old version. It's crisp, even on a local 802.11* network.
Big New Features
From the mobile device side, WS 3 looks and works like WS 2 did. I didn't want to tinker with something that worked. However, there will be a number of new features that have been requested or make sense:
- HS-integrated configuration. WAPSeer 3 configures via a web interface looking and working like the rest of HS 2 (using the "Config" button in the Setup/Interfaces screen). You shouldn't have to touch your INI except for the most extreme customizations (per-device-type custom links are one situation where you'll still have to hand-edit the INI).
- Plug-In Thermostat support. All the HST plug-in thermostats will be supported, of course with multiple 'stats/interface if you're running that way. HST has provided a consistent interface across their 'stat plug-ins, making it so that I only have to write one set of code to support them all. Third party thermostat plug-ins will continue to require the use of events to work with, unless they conform to the HST thermostat plug-in API.
- Media Player Plug-In support. Long overdue.
- Global X10. I'll be providing the ability to enter an X10 code and send a command (On, Off, Dim, All Off, etc).
- HTML directory: zero footprint. WS 3 puts nothing in your HTML directory. Everything (even the CSS) is generated in real-time by the plug-in.
- Major compatibility enhancements. Being in a plug-in, I control my own HTTP headers now, which will reduce the situations where I have to ask HST to make a change to the HomeSeer code to make soemthing work. I've removed the old URL system, which was A=&D=&M=&X=, replacing it with a simpler CMDREFEXT.RND system. Removing special characters like & and = from the URL line will help a great deal with compatibility. I don't use X10 codes anywhere - every communication back to the app is expressed by the device or event's internal refid number. Couple all that with the genuine IIS web server in HS 2, and WS 3 should work on a lot more phones.
- Integrated troubleshooter. The new Device Setup wizard will help you get WAPSeer working, provide information provided by DEBUG.ASP on the WAPSeer website and much more.
Smaller (but still important) Stuff
- A new feature called RefreshGuard is now available. In WS2, if you execute a command, close your browser and re-open it, your phone may refresh the page and re-execute the command. With RefreshGuard activated (via an INI setting), WS 3 will bounce you back to the WS main menu when this happens. This does not affect repeat executions of the same command, only page refreshes.
- When viewing an event, instead of offering both Disable and Enable options, only the currently relevant option is displayed. For instance, if an event is enabled, only the Disable option appears, and visa versa.
- WS 3 will require that you be logged on to HS as Admin (or Admin + Local) to function.
WML Mode
This is something that I'm stuggling with, and I could use some community input here. Supporting WML mode is cumbersome, because it requires supporting an entirely seperate WAPSeer code base. I'm strongly considering dropping WML mode support. However, if a large number of users needs this functionality, I'll continue to support it. If you have an XHTML compliant phone, test with HS 2 and WAPSeer 2.1's XHTML mode (WAPSeer.ash). If that still doesn't work, but WAPSeerWML.ash does, please let me know in this thread.
Your Thoughts
If there's something you've been wanting to see in WAPSeer and it's not on the new features list, feel free to post here. I'll do my best to include it!
Thanks much for your business (and your patience),
Justin
Comment