Massimo >With hbp a component technology is born in harbour
This is not component technology. It is simple GUI technology which Harbour lacks, at least in the core compiler. >Have you more sample? What more samples? Whatever I develop I put in demowvg.prg. You can examine it whenever I declare a new part functional. More you can stucy Xbase++ examples. But be aware that stucy only those parts which are covered in GTWVG. >Is hbp multi platform? If someone takes pain it can be. I have kept PRG layer separate from API layer. One has to write the wrappers for API layer only. Class framework will remain the same and docuented. >Do you think to implement all xbasepart like XbpGET()? Sure. But remember I have a very limited knowledge of WinApi. >Will this hbp syntax be used for having a pluggable gui (switch at runtime or linktime)? Yes. If you link your application with GTWVG then you can access all its power alongwith your CUI applications. But you need to design your applications accordingly. >Why not made hbp (Harbour part) as stand alone library? I am not sure what you mean. It is aleady standalone and is in contribs. >Will this component library and GUI controls implemented in harbour using native API access ? Again I could not understand your point. Right now it is for Windows only. Future I cannot foresee. Regards Pritpal Bedi -- View this message in context: http://www.nabble.com/2008-11-23-13%3A27-UTC-0800-Pritpal-Bedi-%28pritpal%40vouchcac.com%29-tp20651756p20653568.html Sent from the Harbour - Dev mailing list archive at Nabble.com. _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
