Re: Re: [bitpim-cvs-checkins] bitpim/help screen-editingcalendarevent1.png,NONE,1.1 screen-editingcalendarevent2.png,NONE,1.1 screen-editingcalendarevent3.png,NONE,1.1 screen-editingcalendarevent4.png,NONE,1.1 screen-editingcalendarevent5.pn
"Roger Binns" <[email protected]>
| Newsgroups | gmane.comp.mobile.bitpim.devel |
|---|---|
| Message-ID | <009c01c50ece$ee6f4a90$3501a8c0@rogersqyvr14d3> |
>>All those files need to be updated for the help to work correctly when >>not running in a developer tree. > > I figure those files would be generated as part of the build and that's > why I didn't commit them. The wxh file is the master project file and others are generated from it in various ways. They all have to line up right. > btw, what's the process of generating new help sections (those that don't > yet have Help IDs?) I'm thinking specifically of the Calendar Import Dialogs. For new files you need to tell me where you want them in the hierarchy and what the names are. If you need a new id then also tell me what it is and what file it is associated with. I do the editing in Help Blocks which updates the project and associated files, and also run the help generator. Unfortunately HelpBlocks isn't very good as a collaborative tool, but it does the best job for the price. BTW there are two types of ids. The numerical ones are only used in the web version to link pages into the right place in the frame of the content structure. Those are automatically updated by the help build system. You can just put in 0 and it will be updated in the next help build. The string ids are used when you need to make a help button in the UI go to the corresponding page in the help. That involves updating page properties in the Help Blocks UI. Roger ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click