How to use Column Editing in uVision3.*

Regarding column editing: I've used it in M, Brief, MSVC, Eclipse and Notepad++. When an IDE/editor doesn't support it I sorely miss it. Arguments along the lines of "maybe you're not structuring your code right" are not really acceptable.

Regarding Eclipse: it may not be the best IDE but to me it seems good enough that I wouldn't be too upset if all the embedded vendors standardized on it.

Regarding uVision integration: it would be nice to have a better way of plugging editors and other tools into uVision but I here's what I've been doing as a second-best solution:

- Set up a fake CDT project in Eclipse (trivial)
- Set up a custom build command file that calls uVision to build the project in the background and pipe the errors back to Eclipse (easy)
- Set up an error parser that makes errors and warnings show up in Eclipse's "problems" tab (moderately easy)

Eclipse's SVN and CVS integration is great, by the way. Makes source control so much easier to use.

Now I can do all my editing and building in Eclipse and when it's time to debug I switch over to uVision for debugging. Since the uVision debugger is pretty good I'm not too upset about not having debugging in Eclipse.

Andrew

Regarding column editing: I've used it in M, Brief, MSVC, Eclipse and Notepad++. When an IDE/editor doesn't support it I sorely miss it. Arguments along the lines of "maybe you're not structuring your code right" are not really acceptable.

Regarding Eclipse: it may not be the best IDE but to me it seems good enough that I wouldn't be too upset if all the embedded vendors standardized on it.

Regarding uVision integration: it would be nice to have a better way of plugging editors and other tools into uVision but I here's what I've been doing as a second-best solution:

- Set up a fake CDT project in Eclipse (trivial)
- Set up a custom build command file that calls uVision to build the project in the background and pipe the errors back to Eclipse (easy)
- Set up an error parser that makes errors and warnings show up in Eclipse's "problems" tab (moderately easy)

Eclipse's SVN and CVS integration is great, by the way. Makes source control so much easier to use.

Now I can do all my editing and building in Eclipse and when it's time to debug I switch over to uVision for debugging. Since the uVision debugger is pretty good I'm not too upset about not having debugging in Eclipse.

Andrew

Now I can do all my editing and building in Eclipse and when it's time to debug I switch over to uVision for debugging. Since the uVision debugger is pretty good I'm not too upset about not having debugging in Eclipse.

Now I can do all my compiling and linking in uVision and when it's time to edit I switch over to CodeWright for editing. I'm not too upset about not having editing in uVision.

Erik

but I here's what I've been doing as a second-best solution:

have you considered making that "open source"?, you might get a beneficial return

Erik

I do not want to use tools written in coffee, my time is too precious

"Regarding Eclipse: it may not be the best IDE but to me it seems good enough that I wouldn't be too upset if all the embedded vendors standardized on it."

is it possible that others think the Keil IDE, without the column editing feature, is good enough for them too?

maybe that's why they didn't include a column editing feature?

If you really miss it that much, maybe you can talk to Keil to write a special IDE for you. I am sure that as long as you put big enough of a figure in front of them, they will move in your direction.

Keil or I should say Keil ARM does use Eclipse for there DS-5 toolset. Maybe they will move that Eclipse version into the ARM MDK tools in the near future but I doubt that they will change the C51 tools. I don't know that. It's just a thought.
Bradford

have you considered making that "open source"?, you might get a beneficial return

Erik

I have, actually, but I have to find some time to recreate a project from scratch and document the steps so it's actually useful.

Andrew