I haven't looked in detail, but browsed the code and as it is a real HTML/CSS menu, it surely will be hosted in a webbrowser control, maybe in an unusual ribbon format. I think popup windows are able to drop down and bee seen outside of the web browser control container and thus this ActiveX control can live side by side with normal VFP controls on a form. It's an idea to do so, but goes into the direction of going webapp, if just with the menu. You leave the UX of Windows, but the normal sysmenu is a dying species anyway. Even not talking of Office Ribbon as extended toolbar, most browsers hide their text sysmenu and only show the address bar and favorites bar to maximize the canvas for the websites. I still think the menu is a helpful tool, because you really can define VFP code executed within and assign hotkeys to menu items. As Mike points out you don't have to stay with default font and coloring and you can add icons for menu items.
If you want something else than a menu, I wouldn't go for CSS/HTML but for VFP controls, you want a fancier toolbar, then take a VFP form and design your interface as you like, this gives the maximum freedom to style it as you like and let it have much more complex functionality than pickable menuu items or clickable toolbar buttons. The only difference such things have is being real forms, they take the focus away and inactivate a form, whereas a menu or toolbar let the focus stay on the active form and its active control. A cheap price, as you mostly can live with that effect, but it may cause problems due to valid events, rule checks and validations when leaving focus of controls.
Bye, Olaf.