From: Schollnick, B. <Ben...@xe...> - 2005-04-20 12:37:17
|
> > While that is a valid concern.... In my opinion the user is not=20 > > suppose to edit the file outside of the ResourceEditor.... > >=20 > > So it is a moot point. >=20 > Sorry, but there you are wrong. The whole point of making the=20 > resource file a valid Python file is so that you aren't restricted > to using the resourceEditor to amend it. So Kevin is suppose to accept typo's, and or bad syntax or managled white space in the file? We have a application that is perfectly able to edit and manipulate the resource file... If you manually change the file, you need to take responsibility for altering the file. Once in a blue moon I may open the file to do a group find and replace, if I decide to radically change my naming strategy.... But that doesn't mean it's a supported method of changing the file. How can kevin guarantee that the resource file is valid if it is not maintained through the resourceeditor? > This is an important point and if there is any misunderstanding or=20 > mis-communication I think we should address it. Is there anything in=20 > particular that led you to this conclusion? Specifically, no. But I believe that there needs to be a clear seperation between what Kevin supports and doesn't. Asking Kevin to support people editing the resource file outside of the resourceeditor is asking for support headaches. It maybe a plain text format.... But that does not mean that you can guarantee a valid resourcefile / python file will be the final result... > > But it should stay in the resourceeditor to make it automagically=20 > > updated when edited in the resourceeditor. >=20 > See Kevin's point about scriptlets, this is a perfect use=20 > case for one. Fine.... But I do still suggest that it is a automatic feature in the resourceeditor... Or at least have a preference option for it to be automatic... I have found that feature to be very useful.... It prevents me from having to have the resourceeditor open all the time to simply look up the field names... - Benjamin |