![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Improved DXL editor Topic Summary: Created On: 10-Nov-2003 16:58 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I'm still an "Amish" programmer and think "Crimson Editor" is GREAT. But that's just me. So the following is a crude set of desired features:
[] Ability to open a file in read-only mode, to allow looking at your library without fear of accidentally modifying it. This is different from a file-system "R" attribute on the file: your editor won't let you change it even if the file system will. [] Comment block /* ... */ should all be one color; specifically do no key-word color changing on words inside such a block. (I notice Crimson only defines a comment until the end-of-line). [] Multi-line strings should likewise disable key-word searches for words inside the string. [] Ability to locate the declaration statement for any variable or function. Good luck with the graphical DB builder. You know how to encrypt DXL? PLEASE let me know how. - Louie |
|
![]() |
|
![]() |
|
Hi Roger,
Sounds like a nice idea - my suggestions below are bit of an elaboration on some of the features you have already listed as well as some new ones. DXL Projects:- There needs to be a concept of a DXL project which manages a bundle of DXL files that interact to provide a function. Integrated DXL Help:- It's already possible to search the PDF DXL Reference Guide, what would really make the editor useful is to be able to select a DXL function in the code and launch context sensitive help on the selected function. DXL Encryption:- This is a must, Telelogic have been a bit coy about this one in the past, I think that most DXL coders are happy to make the odd bit of code publicly available, but when it comes to large DXL programs where a lot of IP and costly effort has been expended, it would be nice to protect that IP and investment. DXL Source Code Version Control:- Would be nice if the editor could interwork with popular existing version control products rather than re-inventing the wheel, eg: CVS, RCS, CM Synergy, ClearCase, SourceSafe, PVCS etc. Whatever is used, it must have the ability to branch, re-base, merge, recurse labels, embed version history information into the code file and present a graphical representation of the version tree. Debugger Trace:- Would be nice if the debugging functions included an ability to trace and record executed code lines to a configurable depth w.r.t. before, after or centred around a nominated breakpoint. Differance Viewer:- Ability to view the marked up differance between two selected DXL files (A must for any merge or re-base type operations). Keyboard Short-cuts:- The secret of improved performance in editing source code is in the use of keyboard short-cuts for all major/common code editing functions, just ask any user of the range of Vi editors that are available. ------------------------- Paul Miller Specification Practices Specialist, EuroCyber, Melbourne, Australia. Mobile: +61 (0)418 135 103 Web Site: http://www.eurocyber.biz E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz |
|
![]() |
|
![]() |
|
I currently define "Crimson Editor" as the "default" program for *.dxl and *.inc files; thus when I double click on MyScript.dxl I go straight to Crimson. I would thus prefer Crimson to have a toggle read-only feature.
Having "Open" and "Open Read Only" File menu options, as WELL as the toggle option would be nice. - Louie |
|
![]() |
|
![]() |
|
Two editors come to mind:
1. Codewright (Previously by Premia, Now by Borland) 2. Homesight (Macromedia) They are both very good and very powerful editors both with macro languages and cool things like "Chromacoding" (color coding key words/sections) Most of the other features that I would list have already been touched upon with the exception of a "Watch Window" the ability to place variables in a separate window and the debugger will display the value of those variables upon hitting a breakpoint. Good luck and I will volunteer to beta test anything you come up with. |
|
![]() |
|
![]() |
|
Metrowerks CodeWarrior is my IDE of choice. You might want to check it out at the following website: http://www.metrowerks.com ~Michelle
|
|
![]() |
|
![]() |
|
Hi,
What about the public domain GVIM code editor Roger (GVIM Web site)? Version 6.2 has some OLE functionality associated with it so that it can interwork with tools like Visual Studio, can this be any use? ------------------------- Paul Miller Specification Practices Specialist, EuroCyber, Melbourne, Australia. Mobile: +61 (0)418 135 103 Web Site: http://www.eurocyber.biz E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz |
|
![]() |
|
![]() |
|
Roger,
Are you still working on this? Regards Ken McGuffie |
|
![]() |
|
![]() |
|
Do you by any chance plan on finishing it? I know I for one would be deeply in your debt if you did...
|
|
![]() |
|
![]() |
|
Hi Roger,
as I mentioned in this thread I use sometimes the editor eclipse for DXL-editing. He is very extensible and very stable and runs on various platforms. I'am not a real Java programmer, but I think programming extensions (scanner, parser, highlighhter, etc.) for eclipse/DXL are not very difficult, because there are many other implemented language extensions and many books that teaches the technique... ... and if I had some spare time ... no, I think this is a real project and is not coded in some weeks. Dirk. ------------------------- Dirk Plaschke |
|
![]() |
|
![]() |
|
The editor of our choice is UltraEdit v11.
Got most of what you're looking for and is customisable. www.ultraedit.com ------------------------- werner.kolze@baesystems.com |
|
![]() |
|
![]() |
|
I use UE, but haven't downloaded since version 7
![]() ------------------------- Graham Stradling, Alcatel-Lucent. |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Improved DXL editor
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.