| Author |
|
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: December 05 2004 at 22:13 | IP Logged
|
|
|
The newest beta version 1.03.4.3 is now available for download. This version includes the much anticipated support for the PowerLinc USB as well as some minor bug fixes and enhancements.
The next development step is to add support for the Velleman K8000 parallel I/O controller (Didi you must be doing backflips  ). This support will also enhance the I/O functionalities of the CPU-XA/Ocelot as we'll be getting some Digital I/O screens and some digital triggers.
Let me know if there are any problems with the new version.
Dave.
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: December 09 2004 at 22:09 | IP Logged
|
|
|
Hey, Dave! How do I get the web based control center to use a style sheet?! 
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: December 10 2004 at 14:01 | IP Logged
|
|
|
Tony,
Im glad you asked that  since I havent had a chance to document the Web Control Center functionality yet.
The web CC will accept three parameters, ID, TYPE, and FLAGS.
The ID is the ID of the tab to display and does NOT have to be a tab that is displayed on the client CC.
The TYPE parameter determines how the CC is displayed. This parameter can be set to 0,1,2, or 3. First a little background info. When dealing with standard web pages and HTML, whenever a form is submitted (in this case a button is pushed), the request is sent to the webserver and the result returned and loaded as the new web page. In the case of the Control Center, you may not want the page constantly being repainted every time you press a button. So you basically have a couple of ways to work around this. You can have the new page opened up in a separate window. You can have the new page opened up in a separate frame. Or you can have the page refreshed. Depending upon your needs, you're able to select the method that best suits you. A TYPE of 0 will cause PowerHome to return a Frameset. This frameset consists of two rows with the top row containing the CC and the bottom row set to 0 height for the new pages. The top frame will then use a TYPE of 1 so that as buttons are pressed, the result is sent to the bottom frame.
A TYPE of 2 will cause PowerHome to open a new window and immediately hide it behind the main window. Whenever CC buttons are pressed, the result will be sent to this hidden window.
A TYPE of 3 will cause PowerHome to not use frames or hidden windows and will instead refresh the main window with the result set.
The last parameter is FLAGS. To set the FLAGS parameter properly, you'll add together the individual flags you wish to take advantage of. They are:
1 Determines whether or not the CC is refreshed when a button is pressed. This flag is ignored if the TYPE = 3 (a TYPE = 3 means to refresh the CC). Add 1 to the FLAGS parameter if you wish to have a the CC refreshed on TYPES 1 and 2.
2 Specifies whether or not a link to the PowerHome Web "Main" page is displayed or not. Add 2 to the FLAGS parameter to force the "Main" link to not be displayed.
4 Specifies whether or not links to the displayable tabs are displayed or not. Add 4 to the FLAGS parameter to force the CC tabs list to not be displayed.
8 Specifies whether or not the CC uses it's own internal style sheet (as determined by the CC settings in the explorer) or an external style sheet (phcc.css) so that you can override the internal settings. Add 8 to the FLAGS parameter to use an external style sheet.
The default menu option for the web CC is: /ph-cgi/controlcenter?
This results in all three parameters being blank which will cause PowerHome to interpret them as follows:
The TYPE will be a 0. This will return a frameset whose top frame will immediately post a request with a TYPE = 1.
The FLAGS will be 0. This will force the frame to not be refreshed as buttons are pressed and will display links for the "Main" page and the displayable CC tabs. It will also use it's own internal style sheet.
The ID will be blank so the initial tab will be the tab with the lowest tab order.
With these parameters, a wide range of control can be achieved. You could create a complete set of CC tabs designed for a Pocket PC that are never displayed in the client by setting the tab order to 0. You can also set the main and CC tabs links to never display and then include buttons for your own navigation using the ph_setwebnexturl function (even though it says it doesnt work with CCBUTTON commands, it does).
Dave.
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: December 11 2004 at 16:49 | IP Logged
|
|
|
In case someone is like me and couldn't figure it out, multiple param's are passed like this...
/ph-cgi/controlcenter?TYPE=0&FLAGS=8
It also looks like the buttons grow to fit the text now! Any way to get the real CC to do this?
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: December 11 2004 at 20:28 | IP Logged
|
|
|
The buttons don't grow in Firefox. 
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: December 13 2004 at 12:05 | IP Logged
|
|
|
Yeah, thats a bummer. Unfortunately, each browser is subject to interpret the HTML and CSS how it see's fit. Even though the CSS specifically states an exact size and location of the buttons, it looks like Microsoft will expand beyond the fixed size if the text doesnt fit. Netscape apparently chose not to. It's this type of behavior that makes it hard to do web programming with any measure of reliability. Not only do different browsers interpret different ways, but sometimes different versions of the same browser interpret differently as well.
Sorry I didnt mention how to pass the params. I had actually thought to do so but in my rather long-winded answers, I sometimes forget what I was trying to say .
In any event, how are your pocket PC pages turning out?
Dave.
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: December 13 2004 at 12:30 | IP Logged
|
|
|
Well, they have not changed since I linked the sample image. I am now torn between using PSP's and the web CC. I need to go through the old posts on the CC and see what I have forgotten. I think the CC may win due to less coding required.
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: January 25 2005 at 18:58 | IP Logged
|
|
|
I just discovered why the buttons in the web CC don't change the pointer to a hand when using Firefox; the "cursor:hand" should be "cursor:pointer" in the css. Making this change works in both IE & Firefox.
Tony
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 25 2005 at 22:05 | IP Logged
|
|
|
Tony,
I'll make the changes to PowerHome so it'll be in the next beta.
Great detective work !!
Dave.
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: Version 1.03.4.3
