From: Schollnick, B. <Ben...@xe...> - 2005-04-20 12:44:15
|
> Back in the 90's my company made a commercial Motif=20 > GUI-Builder. From that experience I concur that being able to=20 > manually edit the resource file is a necessity, even though=20 > it may be seldom used. A slight clarification... I am not saying that you can't edit the resource file manually... I am suggesting that the Resourceeditor is the only guaranteed method to produce a resource file. The resource editor can't make typos, make white space errors, make syntax errors, or any of a 100s of human errors... While the manually edited file should be okay, it's a valid concern that someone might manually edit the file and goof something up. Then demand that Kevin "fix" the problem.... **** I have been in that situation before. **** I feel that it's important to at least acknowledge that manually editing the file may not always be possible, nor supported.... What if Kevin moves to a XML based format? Sure it's plain ascii, but I personally don't feel that manually editing the tag data is worth it... Or heaven forbid a binary format.... =20 - Ben >=20 > -----Original Message----- > From: Andy Todd [mailto:an...@ha...] > Sent: Tuesday, April 19, 2005 5:36 PM > To: Schollnick, Benjamin > Cc: pyt...@li... > Subject: Re: [Pythoncard-users] newbie, tool to print=20 > resource structure > Importance: Low >=20 >=20 > 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... > >=20 > >=20 > >>The danger with this approach is that the printer friendly version > >>*could* get out of sync with the resource file. Especially if the=20 > >>resource file is edited outside the resourceEditor. > >=20 > >=20 > > 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 >=20 > Sorry, but there you are wrong. The whole point of making the=20 > resource=20 > file a valid Python file is so that you aren't restricted to=20 > using the=20 > resourceEditor to amend it. >=20 > 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? >=20 >=20 > [snip] > >=20 > >=20 > > Then you are making an automated task into a manual task=20 > that has to=20 > > be run after every change made on the file.... (i.e. Pydoc) > >=20 > > If you are concerned about allowing the user to do a manual=20 > execution=20 > > of this.... Then we could make a stub so that the user can=20 > run it.... =20 > > 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. >=20 > Regards, > Andy > --=20 > -------------------------------------------------------------- > -------------- > ---- > From the desk of Andrew J Todd esq - http://www.halfcooked.com/ >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: New Crystal Reports XI.=20 > Version 11 adds new functionality designed to reduce time=20 > involved in creating, integrating, and deploying reporting=20 > solutions. Free runtime info, new features, or free trial,=20 > at: http://www.businessobjects.com/devxi/728 > _______________________________________________ > Pythoncard-users mailing list Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/pythoncard-users >=20 > -------------------------------------------------------------- > ------------- > The information contained in this message may be privileged=20 > and / or confidential and protected from disclosure. If the=20 > reader of this message is not the intended recipient, you are=20 > hereby notified that any dissemination, distribution or=20 > copying of this communication is strictly prohibited. If you=20 > have received this communication in error, please notify the=20 > sender immediately by replying to this message and deleting=20 > the material from any computer. > -------------------------------------------------------------- > ------------- >=20 |