Редакторы HDL, альтернатива Опции

[zorromen]

Привет всем ... Тока скачал кваркус 6.0 ... запустил ... и чета ваще немогу понять ... в нем не очень удобно пиать ... в смысле если писать на верилоге ... то неудобна симуляция и ваще как я понял эта штука нужна уже в конце когда усе готово и тока осталось засунуть усе в микросхему ...
Так че? пишем в других прогах а потом уже в кваркус? ... Или я всетаки чтото проглядел и в кваркусе всетаки можно писать с нуля проэкт?

[Vadim]

Вопрос к тем, кто работает с сликом. Как перенести личные настройки с одного компьютера на другой?

[dxp]

Вопрос к тем, кто работает с сликом. Как перенести личные настройки с одного компьютера на другой?

Попробуйте так (это фрагмент из старой доки, в новой почему-то этот FAQ убрали):

Q: How do I transfer my configuration?

A:
Each user's configuration is automatically transferred to a newly installed version of Visual SlickEdit when they run the new version. Some configuration changes will not be transferred such as changes to our menus, and changes to our dialog boxes. Changes to our toolbars are preserved only if you are upgrading from 3.0b or after.

non-UNIX platforms: For single user configurations you need to install the new version of Visual SlickEdit on top of the previous version in order for your configuration to be transferred to the new version.

SINGLE USER NON-UNIX PLATFORMS:

To manually transfer your configuration changes from the previous version of Visual SlickEdit, perform these steps:


· If you are currently running the new version of Visual SlickEdit, close the editor now.

· If you have made color coding changes, copy your "vslick\user.vlx" file into the "vslick" directory of the new version.

· If you have recorded macros, copy your "vslick\macros\vusrmacs.e" into the "vslick\macros" directory of the new version.

· To tranfer other configuration changes, bring up the previous version of Visual SlickEdit. Activate the Visual SlickEdit command line at the bottom of the editor (ESC for most emulations) and type "list-source" and press ENTER. This will create the macro file "vusrdefs.e", and possible another macro file called "vusrobjs.e" in your "vslick\macros" directory. Copy "
vusrdefs.e" and (optionally) "vusrobjs.e", into the vslick\macros directory of the new version.

· Run the new version of Visual SlickEdit.

· If you ran the "list-source" command, type "vusrmods" and press ENTER on the Visual SlickEdit command line. This will switch emulations if necessary, and run "vusrdefs.e" and "
vusrobjs.e" (if present).

· If you copied your recorded macros file ("vslick\macros\vusrmacs.e"), load this macro now with the Load Module dialog box ("Macro...", "Load Module...").

MULTI-USER NON-UNIX PLATFORMS:

To manually transfer your configuration changes from the previous version of Visual SlickEdit, perform these steps:

· If you have made color coding changes, copy your "user.vlx" file located in the directory specified by your VSLICKCONFIG environment variable into the your VSLICKCONFIG directory of the new version.

· If you have recorded macros, copy your "vusrmacs.e" file located in the directory specified by your VSLICKCONFIG environment variable into the VSLICKCONFIG directory of the new version.

· To tranfer other configuration changes, bring up the previous version of Visual SlickEdit. Activate the Visual SlickEdit command line at the bottom of the editor (ESC for most emulations) and type "list-source" and press ENTER. This will create the macro file "vusrdefs.e", and possible another macro file called "vusrobjs.e" in the directory specified by your VSLICKCONFIG environment variable. Copy "vusrdefs.e" and (optionally) "vusrobjs.e", into the VSLICKCONFIG directory of the new version.

· Run the new version of Visual SlickEdit.

· If you ran the "list-source" command, type "vusrmods" and press ENTER on the Visual SlickEdit command line. This will switch emulations if necessary, and run "vusrdefs.e" and "
vusrobjs.e" (if present).

· If you copied your recorded macros file ("vusrmacs.e"), load this macro now with the Load Module dialog box ("Macro...", "Load Module...").

UNIX PLATFORMS:

To manually transfer your configuration changes from the previous version of Visual SlickEdit, perform these steps:

· If you have made color coding changes, copy your "user.vlx" file located in your $HOME/.vslick directory into the your $HOME/.vslick directory of the new version.

· If you have recorded macros, copy your "vusrmacs.e" file located in your $HOME/.vslick directory into the your $HOME/.vslick directory of the new version.

· To tranfer other configuration changes, bring up the previous version of Visual SlickEdit. Activate the Visual SlickEdit command line at the bottom of the editor (ESC for most emulations) and type "list-source" and press ENTER. This will create the macro file "vusrdefs.e", and possible another macro file called "vusrobjs.e" in your $HOME/.vslick directory. Copy "
vusrdefs.e" and (optionally) "vusrobjs.e", into the $HOME/.vslick directory of the new version.

· Run the new version of Visual SlickEdit.

· If you ran the "list-source" command, type "vusrmods" and press ENTER on the Visual SlickEdit command line. This will switch emulations if necessary, and run "vusrdefs.e" and "
vusrobjs.e" (if present).

· If you copied your recorded macros file ("vusrmacs.e"), load this macro now with the Load Module dialog box ("Macro...", "Load Module...").