>> I think we should seriously consider this, and think >> about the best way to combine the file types. I can >> even create a hbmk2 option parser call which can be used >> by hbide as is. >> >> F.e. we can use option prefix to denote HBIDE specific >> information: --hbide:cat.option=value, or use >> comments: #hbide:cat.option=value >> > > I am convinced. > > So we can have one more file type as only file > file for the project - .hbp. > > This way we can reuse existing .hbp. > However we must consider how to include / remove > sources in .hbp. I have an idea how to achieve it, and > will implement this concept in toto.
If we want to avoid full and hbmk2 compatible .hbp parser in HBIDE, one solution is to use section markers: --- .hbp -hbdyn -inc -... -o #HBIDE.FILES_START test.prg #HBIDE.FILES_END --- You can add similar sections for every .hbp parts which are allowed to be controlled also by GUI means. If you stick with above method, you can use this method to store HBIDE-only settings inside .hbp file: #HBIDE.category.option1=valuex #HBIDE.category.option2=valuey Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
