Re: [PEDA] Toolbar Menus
> Menu and other customizations are stored in the various .RCS files that you > will find in your Windows install directory. Things like > client99se.rcs. These are text files - open them and look at the format. > On the subject of RCS/INI files I think Protel should consider making these > profile friendly - that is moving them from the Window install folder and > into some other folder that can also hook into the Windows logon. The > registry is the intended place for this under old versions of Windows but > there is a move away from the registry in the programmers world due to the > with the large binary nature. I would *not* want the ini/rcs etc files > made binary and stored in other than simple files. But it would be nice if > they were not stored in the windows folder, even one set of settings for > all users but stored in a dedicated folder in the Design Explorer folder > would be heaps better. Any one with comments on this? > > Ian Wilson I strongly agree that configuration/customisation settings should be kept in ASCII format files (rather than in binary format and/or in the registry). (I am also very glad to hear that many programmers are avoiding using the registry to store customised settings.) I also agree that these files should not be stored in the Windows directory, but I wouldn't lose too much sleep, personally, if they remained there. That said, I still think there is something to be said for being able to customise settings to a greater extent than is the case at present. Because I have customised my resources to a large extent, I keep backup copies of the files in the Windows folder in a separate folder, just in case Protel crashes on me badly and the files in the Windows folder are subsequently corrupted. Amongst the files I keep in the backup directory is a default configuration file for the Power Print Server, as the set of colours that I want to use for printouts typically vary from project to project, so I use that file to restore a default set of colours (and I save a customised copy of that configuration file for each project in which I want a customised set of colours, to facilitate restoring that set of colours in the event that I go back to doing any work on that project). That is one example of how a greater ability to customise settings would avoid (or otherwise reduce) current requirements to "juggle" configuration files on a project-by-project basis. It is not devoid of merit for Protel to follow the example of other applications, in which customised settings are determined by the contents of one or more configuration files that are in the same folder (or DDB file in the case of Protel?) that the application is launched in, with the contents of configuration files in a default folder (either the Windows folder or the folder where the application's executable and library files are stored) being used instead if such files do not exist in the thus "local" folder (or DDB file). This issue could be a can of worms to some extent though. While it is not as user-friendly as it could be, sufficiently experienced users can currently customise their settings for each project as required, by saving copies of configuration files containing settings customised for the requirements of particular projects, and then "juggling" files between folders as required. To that extent, the status quo "ain't broken, so don't fix it", and there could be a danger that attempting to improve matters could result in a "broken" application, or otherwise in an application that is not as user-friendly as it could be. I am not suggesting that changes should not occur, but we should still be very careful about exactly what we are requesting... Regards, Geoff Harland. - E-Mail Disclaimer The Information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any opinions or advice contained in this e-mail are confidential and not for public display. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * To post a message: mailto:[EMAIL PROTECTED] * * To leave this list visit: * http://www.techservinc.com/protelusers/leave.html * * Contact the list manager: * mailto:[EMAIL PROTECTED] * * Forum Guidelines Rules: * http://www.techservinc.com/protelusers/forumrules.html * * Browse or Search previous postings: * http://www.mail-archive.com/proteledaforum@techservinc.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Re: [PEDA] Toolbar Menus
At 06:48 AM 10/27/01 +1000, Ian Wilson wrote: >I would *not* want the ini/rcs etc files made binary and stored in other >than simple files. But it would be nice if they were not stored in the >windows folder, even one set of settings for all users but stored in a >dedicated folder in the Design Explorer folder would be heaps better. Any >one with comments on this? Sure. (1) Yes, I agree that the initialization and resource files should not be kept in the Windows folder. For one thing, it makes uninstallation a tad more difficult, causing frequent questions to this list about why certain crashes repeat even after Protel is reinstalled. (2) The initialization files should be kept with the executables, as with most programs. (3) Tango DOS had a system where a copy of the .ini and .dfn files was kept in the [Tango] PCB executable folder (the former controlled stuff like current loaded file, and the latter controlled pad definitions, gerber definitions, and other stuff that might be design-specific). But if Tango was executed from a current directory other than the executable directory, PCB would look in the current directory for the initialization files. So, if you wanted to do so, you could use a separate .ini and .dfn file for each design simply by keeping each design in its own directory with its corresponding .ini and .dfn files. I'd suggest that a customization file be a part of the .ddb. Initializations that are shell-related would have to be in a separate file, as now. But customization that relates to a specific .ddb would have control file(s) within that .ddb. These files would automatically be created from the default files when the .ddb is created, or the first time that a related server is loaded. If the file is in the .ddb already, this would be the file used. The default file would not be edited when one customizes; instead, the specific .ddb file would be edited. To change the *default* file, one would edit the corresponding file from within the .ddb, either through the customization tools which already exist, or through the text editor, to what one wants and export it. Or a default file from somewhere else could simply be overwritten outside of Client. I am aware that there could be complications, but I think that they could be addressed and the problems solved. We should be able to customize the environment for each design database, if we wish. Frequently I send a file to a client who is not so familiar with Protel. We are talking about, say, a PCB, and we both have it up on the screen. Quite often, the client will refer to or ask about a primitive by its color. Of course, since the colors are not part of the .ddb, he may have (and usually has) different colors than mine. He should be able to see what I see, exactly. In Tango, to accomplish this, I would simply send the pcb.ini file to the client, tell him how to change the video driver -- because this was DOS and Tango had a different driver for each make of video card -- and the rest would work fine. Because this file would be kept separately from his regular default file, he would be back to what was familiar to him when he worked on a different design. And I always archived the .ini and .dfn files with a PCB file, so the gerber setups, for example, would be the same the next time gerber was generated. Protel accomplishes this latter task with its database and CAM control files. Tools for sharing customizations should exist. It should be easy, not complicated. [EMAIL PROTECTED] Abdulrahman Lomax Easthampton, Massachusetts USA * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * To post a message: mailto:[EMAIL PROTECTED] * * To leave this list visit: * http://www.techservinc.com/protelusers/leave.html * * Contact the list manager: * mailto:[EMAIL PROTECTED] * * Forum Guidelines Rules: * http://www.techservinc.com/protelusers/forumrules.html * * Browse or Search previous postings: * http://www.mail-archive.com/proteledaforum@techservinc.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Re: [PEDA] Toolbar Menus
Thank You Ian and Joel for you solutions to my menu delimma. Ian, I'll give you a call on Monday, and Joel I'm just about to seek out the .rcs files. I agree that it was at least nice for them to save these files in text format. Shawn - Original Message - From: "Ian Wilson" <[EMAIL PROTECTED]> To: "Protel EDA Forum" <[EMAIL PROTECTED]> Sent: Friday, October 26, 2001 2:48 PM Subject: Re: [PEDA] Toolbar Menus > On 10:39 AM 26/10/2001 -0600, SHAWN said: > >Hi All: > > > >Is there a way that I can share my custom tool bars, easily -- say a file > >that I can throw on a disk. Furthermore, if there is, would anyone have a > >unique custom bar that they would like to share. They really speed up the > >process. > > > >Thanks, Shawn > > > Shawn, > > Menu and other customizations are stored in the various .RCS files that you > will find in your Windows install directory. Things like > client99se.rcs. These are text files - open them and look at the format. > > They are not really shareable unless you want to send *all* your settings > for that particular server - unless the receiver is prepared to do some cut > and pasting. > > There is another method that looks interesting that allows extra menus and > other resources to be added using INS files to allow others to install your > special customizations much like they are installing a new server. > > Yuri Potapoff kindly alerted us to the technique and prepared a long > detailed article on this method in three messages with the subject lines > "Creating Menus - part 1", "Creating Menus - part 2", "Creating Menus - > part 3" - dated 17 Aug 2001. > > You ought to be able to find them in one of the archives - ask if you need > directions to the archives there are two (and a half) that I know of. We > are still waiting for Techserv's promised www-accessible archive. > > > On the subject of RCS/INI files I think Protel should consider making these > profile friendly - that is moving them from the Window install folder and > into some other folder that can also hook into the Windows logon. The > registry is the intended place for this under old versions of Windows but > there is a move away from the registry in the programmers world due to the > with the large binary nature. I would *not* want the ini/rcs etc files > made binary and stored in other than simple files. But it would be nice if > they were not stored in the windows folder, even one set of settings for > all users but stored in a dedicated folder in the Design Explorer folder > would be heaps better. Any one with comments on this? > > Hooroo, > Ian Wilson * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * To post a message: mailto:[EMAIL PROTECTED] * * To leave this list visit: * http://www.techservinc.com/protelusers/leave.html * * Contact the list manager: * mailto:[EMAIL PROTECTED] * * Forum Guidelines Rules: * http://www.techservinc.com/protelusers/forumrules.html * * Browse or Search previous postings: * http://www.mail-archive.com/proteledaforum@techservinc.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Re: [PEDA] Toolbar Menus
On 10:39 AM 26/10/2001 -0600, SHAWN said: >Hi All: > >Is there a way that I can share my custom tool bars, easily -- say a file >that I can throw on a disk. Furthermore, if there is, would anyone have a >unique custom bar that they would like to share. They really speed up the >process. > >Thanks, Shawn Shawn, Menu and other customizations are stored in the various .RCS files that you will find in your Windows install directory. Things like client99se.rcs. These are text files - open them and look at the format. They are not really shareable unless you want to send *all* your settings for that particular server - unless the receiver is prepared to do some cut and pasting. There is another method that looks interesting that allows extra menus and other resources to be added using INS files to allow others to install your special customizations much like they are installing a new server. Yuri Potapoff kindly alerted us to the technique and prepared a long detailed article on this method in three messages with the subject lines "Creating Menus - part 1", "Creating Menus - part 2", "Creating Menus - part 3" - dated 17 Aug 2001. You ought to be able to find them in one of the archives - ask if you need directions to the archives there are two (and a half) that I know of. We are still waiting for Techserv's promised www-accessible archive. On the subject of RCS/INI files I think Protel should consider making these profile friendly - that is moving them from the Window install folder and into some other folder that can also hook into the Windows logon. The registry is the intended place for this under old versions of Windows but there is a move away from the registry in the programmers world due to the with the large binary nature. I would *not* want the ini/rcs etc files made binary and stored in other than simple files. But it would be nice if they were not stored in the windows folder, even one set of settings for all users but stored in a dedicated folder in the Design Explorer folder would be heaps better. Any one with comments on this? Hooroo, Ian Wilson * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * To post a message: mailto:[EMAIL PROTECTED] * * To leave this list visit: * http://www.techservinc.com/protelusers/leave.html * * Contact the list manager: * mailto:[EMAIL PROTECTED] * * Forum Guidelines Rules: * http://www.techservinc.com/protelusers/forumrules.html * * Browse or Search previous postings: * http://www.mail-archive.com/proteledaforum@techservinc.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
