This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

uv3 -b without all the windows

This has been discussed before, but not recently....

Has there been any progess in making uv3 not open all its windows when using the -b command line option?

It is rather annoying when all you want to do is compile from within emacs and it insists on waisting all that time opening 10s if windows for no reason at all....

Parents
  • Matthias,
    Nice trick, thanks!

    Stefan,
    You don't need to defend Keil's IDE from me, I think it's fine. I use it maintain project build info and debugging. I don't use the editor simply because it doesn't have the features I'm used to like brief emulation, auto listing structure members, auto listing function parameters, context tag completion and differencing directories just to name a few.

    -Walt

Reply
  • Matthias,
    Nice trick, thanks!

    Stefan,
    You don't need to defend Keil's IDE from me, I think it's fine. I use it maintain project build info and debugging. I don't use the editor simply because it doesn't have the features I'm used to like brief emulation, auto listing structure members, auto listing function parameters, context tag completion and differencing directories just to name a few.

    -Walt

Children
  • re "defending the Keil IDE"

    As I read the thread, I see that all that do not use the Imbecile Developer Environment say "for applying a wrong concept, Keil has done a fair job" so there should be no reason to defend Keil in this respect.

    ANY IDE can only be developed by making assumptions about what the user wants and thus it must end up as an insult to thinking individuals that know what they want, since ANY IDE will support what the dveloper of the IDE think the user wants, not necessarily what the user actually wants.

    So, if I use an IDE i will have to change my wants to the wants the developer of the IDE thought I had.

    You know something, writing the above I just got it. Here is the skinny: if you have not been in a situation where you could develop your own wants, the assumed wants of yours will fit. Thus anyone that has not developed without the IDE will be happy with it.

    BTW the main reason I do not use the IDE is not any of the above, it is because it is incable of developing multiple flavors without separate directives. Also, I would never use an IDE where a non-replacable editor was less capable than CodeWright.

    Erik

  • "Thus anyone that has not developed without the IDE will be happy with it."

    Not necessarily.

    I have developed without IDEs, and with IDEs.

    Currently, I use the Keil IDE.
    Yes, it has limitations - and I frequently use other editors (particularly CodeWright) in favour of the built-in one (I have created an item on the uVIsion 'Tools' menu to do it). But I find that the advantages outweigh the limitations.

    "BTW the main reason I do not use the IDE is not any of the above, it is because it is incable of developing multiple flavors..."

    I agree that this is a particular weak point in uVision (i've commented on it here before).
    Currently, it's not a big deal for me - so I stick with uVision.
    But if I needed to do loadsa variants as you do, I think that probably would preclude uVision... :-(

    PS

    Have you looked at Eclipse: http://eclipse.org/

    Perhaps if Keil et al just concentrated on making their tools Eclipse-compatible, they could all stop re-inventing their own IDE wheel...?

  • Perhaps if Keil et al just concentrated on making their tools Eclipse-compatible, they could all stop re-inventing their own IDE wheel...?
    Not only their own IDE wheel, but how much effort have they wasted on making an inferior editor.

    Oh, if the toolmakers could agree on a common interface

    * Keil et al could free up resources to make the compilers even better
    * CodeWrights succesor et al could free up resources to make the editors even better
    * Eclispe et al could free up resources to make the IDE even better
    * SILabs et al could free up resources to make the debugger even better
    * the developers could have the same look and feel when cnanging platform

    Erik

    PS any rumors as to where the CodeWright developers went after Borland (those bastards) killed CodeWright.

  • "PS any rumors as to where the CodeWright developers went after Borland (those bastards) killed CodeWright."

    Presumably, Borland intended that they'd stay with Borland and put their skills to work on other Borland products - just like a certain well-known FPGA manufacturer did recently when they bought another company and immediately canned their product entire line...

  • Presumably, Borland intended
    Just like Borland intended when they killed "Brief", those guys escaped and made CodeWright and now got "caught" again. My guess is that once you have escaped, you will do it again.

    Erik