From: Andy T. <an...@ha...> - 2005-04-20 09:58:13
|
Schollnick, Benjamin wrote: >>>Very useful.... I would suggest that Kevin consider adding >> >>it to the >> >>>Resource editor and maybe even expanding on it.... >>> >>>Possibly noting any non-default values that have been >> >>configured for >> >>>the widgets... > > >>The danger with this approach is that the printer friendly version >>*could* get out of sync with the resource file. Especially if the >>resource file is edited outside the resourceEditor. > > > While that is a valid concern.... In my opinion the user is not suppose > to edit the file outside of the ResourceEditor.... > > So it is a moot point. > Sorry, but there you are wrong. The whole point of making the resource file a valid Python file is so that you aren't restricted to using the resourceEditor to amend it. This is an important point and if there is any misunderstanding or mis-communication I think we should address it. Is there anything in particular that led you to this conclusion? [snip] > > > Then you are making an automated task into a manual task that has to be > run after every change made on the file.... (i.e. Pydoc) > > If you are concerned about allowing the user to do a manual execution of > this.... Then we could make a stub so that the user can run it.... But > it should stay in the resourceeditor to make it automagically updated > when edited in the resourceeditor. See Kevin's point about scriptlets, this is a perfect use case for one. Regards, Andy -- -------------------------------------------------------------------------------- From the desk of Andrew J Todd esq - http://www.halfcooked.com/ |