Viktor Szakáts wrote: > >> project.hbi and project.hbp are two different entities. >> It is difficult to post hbIDE specific commands in .hbp. >> .hbp is a non-visual creation and .hbi is a visual one. >> .hbi will supply all needed info to .hbp, and this had been >> the goal since begining. I strongly over-rule this idea. >> >> Just like .ppo is generated, .hrb can be initiated, no issues. > > It's a huge issue. Since it ties the whole project to > HBIDE, which means the project cannot be built without > HBIDE. Some ppl prefer command line tools for some tasks > and for some automated tasks this is actually a basic > requirement, since there is no other way to do it than > invoke hbmk2 directly. > > Plus if both "visual" and non-visual information would > be in the same interchangeable file, it would be > _very_ elegant to just supply a .hbp for every project > (many of them already have one) and simply use that > with HBIDE _as is_. No need to reconfigure everything, > no need to ever _sync_ anything, and users can simply > switch between GUI env and cmdline env without worrying > about any additional problems. > > This is real flexibility and such a solution would > make HBIDE more superior in this regard to even MSVS. > > 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. Pritpal Bedi -- View this message in context: http://old.nabble.com/hbIDE---Requested-Thought-of-Features-Tracking-tp27313368p27315798.html Sent from the Harbour - Dev mailing list archive at Nabble.com. _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
