Pretty code program (for all developers)...

Kenneth Adam Miller kennethadammiller at
Wed Jan 13 23:02:52 GMT 2010

Recently, as I was asking for help on IRC I posted my code. Someone said it
looked ugly. Of course, there are many coding preferences and one of them is
spacing style. I was thinking about writing  a simple vim plugin that could
reformat source code to make it look according to a sample, and then I
thought, since I don't have much experience out there, and there are lots of
different languages that might handle this much much better than a
cumbersome and lengthy program in C to handle strings, I thought perhaps
that I might ask for some opinions and directions on this. C/C++ program or
vim plugin? Or what's more, it could be something that I haven't thought of

The program should perform code tidying up and would be well suited to run
before a make command.

I think that it should offer spacing and indenting options as well as some
comment formatting options. These should be able to be set by a gui that
offers an abstract and quick way to set it. Otherwise, the user would have
to learn even *more* commands and that's the last thing that I want. I want
an abstract gui that will be easy to set.

This will offer very regular code formatting. Say you have a lot of nested
calls and you don't want to use tabs with space 8 because if you do it will
keep on trailing off the screen. Also, frequently there are often commands
that we like to use, but they are long. like... cout << "very long text";
and we don't want to redo each of them individually, it would take forever.
or say someone else used an editor that it looked good in and now you use
yours and it looks like crap. whatever the reason, i want a tool that can be
run like a command but will offer a gui to format the code.

After thinking this over, I've come up with a lot of ideas about how this
could be managed to provide a set of features/options that I don't want to
describe here.

If you guys know of any other tools that do anything of the sort like what
i've described here, I'd like to know what they are so that I don't start
another project only to find that someone else has already created something
similar. Or if you have any suggestions, send them my way, or perhaps you
don't think that this project is worth a shot-whatever it is, speak out
about it.
-------------- next part --------------
An HTML attachment was scrubbed...

More information about the Ubuntu-us-tx mailing list