Wingide is a beautiful application

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Sybren Stuvel

    #16
    Re: Wingide is a beautiful application

    Sybren Stuvel enlightened us with:[color=blue]
    > SPE is already annoying because of all the new windows it opens...
    > Not a good start. I remember using it before, to check out the
    > Blender integration. Unfortunately, that didn't work. I'll give it
    > another go.[/color]

    I downloaded it, tried to run it, then it stopped with a message that
    it needs a newer wxPython version than the one that comes with Ubuntu
    Linux. Since this release of Ubuntu is two months old and rather up to
    date with all things Python, IMO the SPE builders are pushing it a
    little too much by requiring even a newer version of wxPython.

    Sybren
    --
    The problem with the world is stupidity. Not saying there should be a
    capital punishment for stupidity, but why don't we just take the
    safety labels off of everything and let the problem solve itself?
    Frank Zappa

    Comment

    • bonono@gmail.com

      #17
      Re: Wingide is a beautiful application

      I have been using vi/vim for a very long time and love it(now using
      ion3 + vim, not even gvim on debian), but never found it blend well
      with the Windows GUI.

      Sybren Stuvel wrote:[color=blue]
      > Claudio Grondi enlightened us with:[color=green]
      > > The file I was editing was just 22 KByte large having 450 lines, so
      > > you try here to explain to me, that for speed reasons Vim has to cut
      > > it into pieces?[/color]
      >
      > Yep.
      >[color=green]
      > > Stani SPE based on Scintilla does it right, UltraEdit does it right,
      > > Wing does it right, so what, are we now on a 1 MHz computer with 128
      > > KByte of memory for all the system and program files what would make
      > > such approach necessary?[/color]
      >
      > I'm giving you the reason why syntax highlighting in VIM doesn't
      > always do what you expect. I never said it wasn't a silly reason.
      > Having said that, A quick Ctrl+L usually fixes this for me.
      >[color=green][color=darkred]
      > >> Wrong. I have used Vim for years, and only found a few minor
      > >> issues, nothing more.[/color]
      > > Let us know about them, so that we know it too.[/color]
      >
      > Syntax highlighting is awfully slow on files with very long lines.
      > That's the only thing I can think of now. And it's fixed in the
      > upcoming VIM 7.
      >[color=green]
      > > But this is what I have experienced. Are you on a *nix system?[/color]
      >
      > Yep.
      >[color=green]
      > > I speak here about Microsoft Windows XP SP 2 on a 3GByte RAM
      > > equipped Pentium 4 and Cream-Vim installed[/color]
      >
      > I use Vim and GVim, on a 1.25 GB RAM equipped AthlonXP, on Ubuntu
      > Linux.
      >[color=green]
      > > But is does not work out of the box for me with the download I have
      > > mentioned and I was not able to fix it as I tried.[/color]
      >
      > That's probably because when you install Vim in Windows, it changes
      > key settings to be more appropriate for Windows. Rip those
      > Win32-compatability crap out of your .vimrc (or is it called _vimrc
      > there?) so you can use all the keys everybody else can.
      >[color=green]
      > > Yes, I see your point, but with the increasing speed of the hardware
      > > and better software quality it is now possible to choose tools which
      > > are easy to use and don't have a steep learning curve.[/color]
      >
      > True. I find Vim very easy to use, and it didn't take me long to learn
      > it. It does help if you're on a platform which supplies 'vimtutor'
      > along with vim, and doesn't mangle the keybindings, though.
      >[color=green]
      > > I am used to Microsoft Windows way of designing user interfaces, so
      > > I expect software running on Windows to provide what I am used to.[/color]
      >
      > LOL don't get me started on the Microsoft way in combination with my
      > expectations...
      >[color=green]
      > > The times where the user had to adopt to the software are over.[/color]
      >
      > You're very wrong there. Users have to adopt to the software, unless
      > they write their own. You also have to adopt to all sort of things in
      > your life, so what's the big issue with software?
      >
      > To give you a few examples: I live in The Netherlands, so I buy cars
      > with the steering wheel on the left. I have to use that, no matter
      > what I want - unless I take the effort to import a car from abroad. I
      > have to screw to the right to get a screw inside a piece of wood. I
      > have to adopt to that. That's the way things work.
      >[color=green]
      > > Now there are all preconditions available making it possible to
      > > adopt the software to the user.[/color]
      >
      > And most users get afraid of all those options they can set and all
      > those things they can tweak to get the software to adopt to their
      > whishes.
      >[color=green]
      > > What other editing tools have you already evaluated? I tried as many
      > > as possible including Vim before I decided to spend money on
      > > purchasing UltraEdit and inspite of the fact, that there are so many
      > > new editors there, I still see no chance to replace UltraEdit with
      > > any other editing tool[/color]
      >
      > I've tried UltraEdit, didn't like it, went back to Vim. Same with
      > other editors. I don't like the way I get popups in UE when I want to
      > search or replace something. I haven't tested this, but I haven't seen
      > a way to re-wrap text like Vim can - even in this post it can rewrap
      > your text without messing up the '>' symbols in front of it. It can
      > even rewrap comments, strings etc. in source code without messing up
      > indentation or marker characters.
      >[color=green]
      > > Just evaluate yourself at least SPE and Wing and come back to tell
      > > here about your experience comparing them to Vim[/color]
      >
      > I'll see if I can get around to it. I'm very busy atm, but I'm busy
      > doing Python programming, so perhaps I can do some with the IDEs you
      > mentioned.
      >
      > Hmm... neither are bundled with Ubuntu.
      >
      > SPE is already annoying because of all the new windows it opens... Not
      > a good start. I remember using it before, to check out the Blender
      > integration. Unfortunately, that didn't work. I'll give it another go.
      >
      > WingIDE is commercial software, which I'm not going to use. I'm not
      > all against commercial software, but if there is a Free alternative,
      > I'd rather use that.
      >
      > Sybren
      > --
      > The problem with the world is stupidity. Not saying there should be a
      > capital punishment for stupidity, but why don't we just take the
      > safety labels off of everything and let the problem solve itself?
      > Frank Zappa[/color]

      Comment

      • BartlebyScrivener

        #18
        Re: Wingide is a beautiful application

        If you're on Windows XP why not try Xemacs? That's free and does syntax
        highlighting etc. Doesn't have a problem with large files and so on.

        rpd

        Comment

        • Claudio Grondi

          #19
          Re: Wingide is a beautiful application

          BartlebyScriven er wrote:[color=blue]
          > If you're on Windows XP why not try Xemacs? That's free and does syntax
          > highlighting etc. Doesn't have a problem with large files and so on.
          >
          > rpd
          >[/color]
          Installed:


          Requesting help file I have got a plain text window with following text:

          Copyright (c) 1985, 1996 Free Software Foundation, Inc. See end for
          conditions.

          You are looking at the Emacs tutorial.

          Emacs commands generally involve the CONTROL key (sometimes labelled
          CTRL or CTL) or the META key. On some keyboards, the META key is
          labelled ALT or EDIT or something else (for example, on Sun keyboards,
          the diamond key to the left of the spacebar is META). If you have no
          META key, you can use ESC instead. Rather than write out META or
          CONTROL each time we want you to prefix a character, we'll use the
          following abbreviations:

          C-<chr> means hold the CONTROL key while typing the character <chr>
          Thus, C-f would be: hold the CONTROL key and type f.
          M-<chr> means hold the META key down while typing <chr>. If there
          is no META key, type <ESC>, release it, then type the
          character <chr>.

          Important note: to end the Emacs session, type C-x C-c. (Two characters.)
          The characters ">>" at the left margin indicate directions for you to
          try using a command.

          ....

          Out of the box after installation of

          gives me an editor window, but
          - no syntax highlighting for edited Python file (no idea how to get it)
          - no line numbering (a menu item is there, but clicking on it doesn't
          change anything)
          - no ruler (a menu item is there, but clicking has no effect)
          - [CTRL]+MouseSelection results in some editing action I don't
          understand ...

          I know emacx from the ancient time of computer technology, but I have
          never made to learn how to control it.
          By the way: I was a keyboard fan years ago, but now I would be glad to
          have some basic typing capability on my mouse, because most of the time
          I am moving the mouse, not typing much text on a keyboard even editing
          scripts.

          Claudio

          Comment

          • BartlebyScrivener

            #20
            Re: Wingide is a beautiful application

            Go to Options. Near the bottom, it will say "Edit Init.File" Click on
            it.

            Make an entry on a separate line near the top as follows

            (require 'python-mode)

            Then save the init file.

            When you open files with a .py extension xemacs should automatically go
            into "python mode"

            If you read the init.el file it will teach you a little about how to
            configure it. If you don't care about that and only want a python
            editor, then just add the line above.

            rpd

            Comment

            • Claudio Grondi

              #21
              Re: Wingide is a beautiful application

              BartlebyScriven er wrote:[color=blue]
              > Go to Options. Near the bottom, it will say "Edit Init.File" Click on
              > it.[/color]
              Done. A completely new file was created.[color=blue]
              >
              > Make an entry on a separate line near the top as follows
              >
              > (require 'python-mode)
              >
              > Then save the init file.[/color]
              Have copy/pasted to it including braces

              (require 'python-mode)

              No effect on reopening emacs, except:
              "
              (1) (initialization/error) An error has occurred while loading
              c:\Dokumente und Einstellungen\A dmin\.xemacs\in it.el:

              Cannot open load file: python-mode

              To ensure normal operation, you should investigate the cause of the
              error in your initialization file and remove it. Use the `-debug-init'
              option to XEmacs to view a complete error backtrace.
              "

              =============== =============== ==============

              To summarize my evaluation of XEmacs here:
              - nothing valuable for Python script development out of the box or
              easy achievable in its Windows version.

              XEmacs is out from beeing considered an option for someone looking for
              an editor helping him doing his Python scripting.

              =============== =============== ==============

              My final conclusions (I am tired now of evaluating):

              The only worth to consider freeware option to Wingide on Windows seems
              to be SPE (or other Scintilla based free editors with the disadvantage
              of not having specific support for Python scripting).

              The best not free overall text editing tool on Windows is UltraEdit, but
              for someone interested in an editor for the limited purpose of editing
              Python scripts Wingide in its Personal Version is probably actual a much
              better choice (and multiplatform).

              As closing words I would like to encourage anyone to start using
              SPE ( http://pythonide.stani.be )
              and contribute to its development making it beside IDLE a further
              standard editor for Python scripting having the potential to become one
              day a serious competitor to Wing. Why? Just because I decided to start
              using it and am eager to see it improving.

              Claudio
              [color=blue]
              >
              > When you open files with a .py extension xemacs should automatically go
              > into "python mode"
              >
              > If you read the init.el file it will teach you a little about how to
              > configure it. If you don't care about that and only want a python
              > editor, then just add the line above.
              >
              > rpd
              >[/color]

              Comment

              • Tony Nelson

                #22
                Re: Wingide is a beautiful application

                In article <1134929375.728 971.141000@o13g 2000cwo.googleg roups.com>,
                "sjdevnull@yaho o.com" <sjdevnull@yaho o.com> wrote:
                ...[color=blue]
                > I get the feeling that a ot of people working with heavy IDEs don't
                > realize how capable vim/emacs are, so I'll give a brief rundown of what
                > my Vim environment does for me. (I do Python web development)--if you
                > don't like the Vi keybindings, the Cream package is Vim that behaves
                > like a regular modeless editor but with all of vim's power (and a nice
                > embedded Python interpreter for writing extensions):
                >
                > 1. Python syntax checking: as I'm typing along, if I input a syntax
                > error then the line is immediately highlighted in red. Useful for
                > catching brainos like:
                > if a=1:
                > (which will highlight in red when I hit enter, point out that I need ==
                > instead of =).[/color]

                What do you use to do this? Cream doesn't seem to do this oob.

                [color=blue]
                > 2. Normal tag-jump stuff: Ctrl-click on a function/method call (or
                > class or whatever) will jump to the function/method/class definition
                > (Ctrl-T works as well if you don't like clicking). It keeps a stack of
                > visited files so you can drill down through your call stack and then
                > pop back up to where you came from.[/color]

                Do you set up ctags for this? I get error messages "E433: No tags file"
                and "E426: tag not found: xxx" when I Ctrl-click on a method call.

                [color=blue]
                > 3. Python class browsing stuff: A Class menu shows the parent and child
                > classes of the one you're currently in, and all the methods of the
                > current class; selecting any of the above jumps to the appropriate file
                > and line.[/color]

                Is this the Tag List?

                [color=blue]
                > 4. Interactive documentation stuff: When I type an open-paren, it looks
                > to see what the prior keyword is and displays help for it in the status
                > line (preferring Python documentation, then docstrings, then comments
                > before the function/method/class definition). Even if there's no
                > help/comments, it'll show the arguments that the function takes. So
                > if, say, I type:
                >
                > cmp(
                >
                > then the status line displays:
                >
                > cmp(x, y) Compare the two objects X and Y and return an integer
                > according to ...
                >
                > If I hit F1 it'll show the full help text. Often the arguments are
                > enough, and I find the status-line display a lot less intrusive than
                > many on-the-fly help systems I've seen.[/color]

                This stuff doesn't happen either. How is it set up?

                [color=blue]
                > 5. A client menu selects which client I want to work in (so, say, I get
                > a bug report for Client A, I select them from the menu). The Class
                > menu and other functions respect this (if I'm in the generic Company
                > class, the Class menu will list Client A's Company subclass before the
                > subclasses of other companies; if I jump to the Company definition,
                > it'll go to Company A's client-specific version). It also restarts
                > development httpd servers on the current machine running with conf
                > files appropriate to that client.[/color]
                ...

                Where is this "client menu"? How is it set up?
                _______________ _______________ _______________ _______________ ____________
                TonyN.:' *firstname*nlsn ews@georgea*las tname*.com
                ' <http://www.georgeanels on.com/>

                Comment

                • sjdevnull@yahoo.com

                  #23
                  Re: Wingide is a beautiful application

                  Tony Nelson wrote:[color=blue][color=green]
                  > > 1. Python syntax checking: as I'm typing along, if I input a syntax
                  > > error then the line is immediately highlighted in red.[/color]
                  >
                  > What do you use to do this? Cream doesn't seem to do this oob.[/color]

                  Nope. I'll try to package up my vimrc and get it uploaded somewhere
                  next week (busy with holiday stuff). The meat of it is:

                  import vim
                  def cur_x():
                  return vim.current.win dow.cursor[1]
                  def cur_y():
                  return vim.current.win dow.cursor[0]
                  def find_current_bl ock():
                  block = [vim.current.lin e]
                  current = cur_y()-1
                  while len(block[0])==0 or block[0][0] in " \t#":
                  current = current - 1
                  if current < 0:
                  break
                  block = [vim.current.buf fer[current] ]+ block
                  return block
                  def check_current_b lock():
                  import code
                  vim.command("sy n clear Error")
                  block = find_current_bl ock()
                  length = len(block)
                  try:
                  code.compile_co mmand("\n".join (block))
                  print ""
                  return 0
                  except:
                  (type, value, tb) = sys.exc_info()
                  line_no = cur_y()-1+value.lineno-length
                  badline = vim.current.buf fer[line_no]
                  badline = badline.replace ('"', '\\"')
                  print "Error at line %d: " %(line_no+1), badline
                  return 1
                  [color=blue][color=green]
                  > > 2. Normal tag-jump stuff: Ctrl-click on a function/method call (or
                  > > class or whatever) will jump to the function/method/class definition
                  > > (Ctrl-T works as well if you don't like clicking). It keeps a stack of
                  > > visited files so you can drill down through your call stack and then
                  > > pop back up to where you came from.[/color]
                  >
                  > Do you set up ctags for this? I get error messages "E433: No tags file"
                  > and "E426: tag not found: xxx" when I Ctrl-click on a method call.[/color]

                  Umm, either click the "build tags in current directory" button on the
                  toolbar, or "find . -name '*.py' | ctags -L -" in the top directory of
                  your python file.
                  [color=blue][color=green]
                  > > 3. Python class browsing stuff: A Class menu shows the parent and child
                  > > classes of the one you're currently in, and all the methods of the
                  > > current class; selecting any of the above jumps to the appropriate file
                  > > and line.[/color]
                  >
                  > Is this the Tag List?[/color]

                  No, this is more complex, I'll post it w/ the rest of my stuff.
                  [color=blue][color=green]
                  > > 4. Interactive documentation stuff: When I type an open-paren, it looks[/color][/color]
                  [SNIP][color=blue]
                  > This stuff doesn't happen either. How is it set up?[/color]

                  Likewise, I'll post.
                  [color=blue][color=green]
                  > > 5. A client menu selects which client I want to work in (so, say, I get
                  > > a bug report for Client A, I select them from the menu). The Class
                  > > menu and other functions respect this (if I'm in the generic Company
                  > > class, the Class menu will list Client A's Company subclass before the
                  > > subclasses of other companies; if I jump to the Company definition,
                  > > it'll go to Company A's client-specific version). It also restarts
                  > > development httpd servers on the current machine running with conf
                  > > files appropriate to that client.[/color]
                  > ...
                  >
                  > Where is this "client menu"? How is it set up?[/color]

                  It's a listing of all the clients we work with. It's a more
                  project-specific thing, but illustrates that you can easily integrate
                  vim into whatever your development system looks like (indeed, when I
                  get a python error in a page on my dev server then it opens the file
                  where the exception occurred in my vim and jumps to the line, setting
                  up the stack appropriately).

                  That stuff I can't post.

                  Comment

                  • Tony Nelson

                    #24
                    Re: Wingide is a beautiful application

                    In article <1135122072.317 411.62530@z14g2 000cwz.googlegr oups.com>,
                    "sjdevnull@yaho o.com" <sjdevnull@yaho o.com> wrote:
                    [color=blue]
                    > Tony Nelson wrote:[color=green][color=darkred]
                    > > > 1. Python syntax checking: as I'm typing along, if I input a syntax
                    > > > error then the line is immediately highlighted in red.[/color]
                    > >
                    > > What do you use to do this? Cream doesn't seem to do this oob.[/color]
                    >
                    > Nope. I'll try to package up my vimrc and get it uploaded somewhere
                    > next week (busy with holiday stuff).[/color]

                    OK, thanks.
                    [color=blue]
                    > The meat of it is:
                    >
                    > import vim
                    > def cur_x():
                    > return vim.current.win dow.cursor[1]
                    > def cur_y():
                    > return vim.current.win dow.cursor[0]
                    > def find_current_bl ock():
                    > block = [vim.current.lin e]
                    > current = cur_y()-1
                    > while len(block[0])==0 or block[0][0] in " \t#":
                    > current = current - 1
                    > if current < 0:
                    > break
                    > block = [vim.current.buf fer[current] ]+ block
                    > return block
                    > def check_current_b lock():
                    > import code
                    > vim.command("sy n clear Error")
                    > block = find_current_bl ock()
                    > length = len(block)
                    > try:
                    > code.compile_co mmand("\n".join (block))
                    > print ""
                    > return 0
                    > except:
                    > (type, value, tb) = sys.exc_info()
                    > line_no = cur_y()-1+value.lineno-length
                    > badline = vim.current.buf fer[line_no]
                    > badline = badline.replace ('"', '\\"')
                    > print "Error at line %d: " %(line_no+1), badline
                    > return 1[/color]

                    OK, I can tell that this is Python code, not VI script stuff. I'll need
                    to see how your vimrc sets this up. It looks like learning to use VI
                    (even with Cream) would take a few weeks of hard work.

                    [color=blue][color=green][color=darkred]
                    > > > 2. Normal tag-jump stuff: Ctrl-click on a function/method call (or
                    > > > class or whatever) will jump to the function/method/class definition
                    > > > (Ctrl-T works as well if you don't like clicking). It keeps a stack of
                    > > > visited files so you can drill down through your call stack and then
                    > > > pop back up to where you came from.[/color]
                    > >
                    > > Do you set up ctags for this? I get error messages "E433: No tags file"
                    > > and "E426: tag not found: xxx" when I Ctrl-click on a method call.[/color]
                    >
                    > Umm, either click the "build tags in current directory" button on the
                    > toolbar, or "find . -name '*.py' | ctags -L -" in the top directory of
                    > your python file.[/color]

                    OK.

                    [color=blue][color=green][color=darkred]
                    > > > 3. Python class browsing stuff: A Class menu shows the parent and child
                    > > > classes of the one you're currently in, and all the methods of the
                    > > > current class; selecting any of the above jumps to the appropriate file
                    > > > and line.[/color]
                    > >
                    > > Is this the Tag List?[/color]
                    >
                    > No, this is more complex, I'll post it w/ the rest of my stuff.[/color]
                    ...

                    Thanks.
                    _______________ _______________ _______________ _______________ ____________
                    TonyN.:' *firstname*nlsn ews@georgea*las tname*.com
                    ' <http://www.georgeanels on.com/>

                    Comment

                    • sjdevnull@yahoo.com

                      #25
                      Re: Wingide is a beautiful application

                      Tony Nelson wrote:[color=blue]
                      > OK, I can tell that this is Python code, not VI script stuff. I'll need
                      > to see how your vimrc sets this up.[/color]

                      vim has a Python interpreter embedded in it (assuming it's a reasonably
                      complete build--it's possible to leave the interpreter, or even parts
                      of the vim scripting stuff, out). I just put .py files in my .vim
                      directory, import them, and then use ":py myfile.doStuff( )" or map keys
                      to such commands.

                      The "vim" Python module (included in vim, just "import vim" from your
                      Python scripts) lets you run vim commands, access
                      windows/buffers/variables/etc.

                      Extending vim in Python is far nicer than using vim script, I basically
                      do all the work in Python and then just :map those functions to
                      whatever keys I want to use.

                      Comment

                      • Tony Nelson

                        #26
                        Re: Wingide is a beautiful application

                        In article <1135206593.612 883.284400@f14g 2000cwb.googleg roups.com>,
                        "sjdevnull@yaho o.com" <sjdevnull@yaho o.com> wrote:
                        [color=blue]
                        > Tony Nelson wrote:[color=green]
                        > > OK, I can tell that this is Python code, not VI script stuff. I'll need
                        > > to see how your vimrc sets this up.[/color]
                        >
                        > vim has a Python interpreter embedded in it (assuming it's a reasonably
                        > complete build--it's possible to leave the interpreter, or even parts
                        > of the vim scripting stuff, out).[/color]

                        OK, mine has Python in it.

                        [color=blue]
                        > I just put .py files in my .vim
                        > directory, import them, and then use ":py myfile.doStuff( )" or map keys
                        > to such commands.[/color]

                        So, you bind check_current_b lock() to the Enter key?

                        [color=blue]
                        > The "vim" Python module (included in vim, just "import vim" from your
                        > Python scripts) lets you run vim commands, access
                        > windows/buffers/variables/etc.[/color]
                        ...

                        OK. I see Python in the help.
                        _______________ _______________ _______________ _______________ ____________
                        TonyN.:' *firstname*nlsn ews@georgea*las tname*.com
                        ' <http://www.georgeanels on.com/>

                        Comment

                        • sjdevnull@yahoo.com

                          #27
                          Re: Wingide is a beautiful application

                          Tony Nelson wrote:[color=blue]
                          > So, you bind check_current_b lock() to the Enter key?[/color]

                          Yeah. The binding's not quite just "<C-O>check_current _block()<CR>"
                          because you need a bit of magic to keep autoindent working. I'll post
                          it with my conf files next week, essentially use <C-R>= with an empty
                          vim function wrapper around the python function (instead of <C-O>) and
                          input a character before leaving insert mode that's deleted when you
                          return (to preserve indent).

                          My goal is to make my conf files into a decent drop-in so you just put
                          them in your .vim directory and go, and post them next week.

                          Comment

                          • Tony Nelson

                            #28
                            Re: Wingide is a beautiful application

                            In article <1135228720.709 870.103680@g49g 2000cwa.googleg roups.com>,
                            "sjdevnull@yaho o.com" <sjdevnull@yaho o.com> wrote:
                            [color=blue]
                            > Tony Nelson wrote:[color=green]
                            > > So, you bind check_current_b lock() to the Enter key?[/color]
                            >
                            > Yeah. The binding's not quite just "<C-O>check_current _block()<CR>"
                            > because you need a bit of magic to keep autoindent working. I'll post
                            > it with my conf files next week, essentially use <C-R>= with an empty
                            > vim function wrapper around the python function (instead of <C-O>) and
                            > input a character before leaving insert mode that's deleted when you
                            > return (to preserve indent).
                            >
                            > My goal is to make my conf files into a decent drop-in so you just put
                            > them in your .vim directory and go, and post them next week.[/color]

                            OK, thank you.
                            _______________ _______________ _______________ _______________ ____________
                            TonyN.:' *firstname*nlsn ews@georgea*las tname*.com
                            ' <http://www.georgeanels on.com/>

                            Comment

                            • jussij@zeusedit.com

                              #29
                              Re: Wingide is a beautiful application

                              > I don't like, that one of the latest UltraEdit releases[color=blue]
                              > was buggy causing 100%CPU load and 2MByte of harddisk
                              > data traffic beeing idle, so I am looking for an alternative
                              > for years, but instead of finding it I was forced lately
                              > to spend money again on renewing my license.[/color]

                              Have you tried the Zeus for Windows programmers editor:



                              Zeus is closed source, but it is also very stable, comes
                              with support for Python and you can even write Zeus
                              scripts using Python.

                              Like all software it also has bugs, but when a bug is
                              reported it is fixed ASAP and a free patch is then
                              offered for download.

                              Jussi Jumppanen
                              Author: Zeus for Windows

                              Comment

                              • jussij@zeusedit.com

                                #30
                                Re: Wingide is a beautiful application

                                > The best not free overall text editing tool on Windows[color=blue]
                                > is UltraEdit[/color]

                                As I mentioned before, you should give Zeus a test drive.

                                Many Zeus users think it is the best programming tool for
                                the Windows platform:

                                A powerful, feature packed, fully configurable IDE specifically designed for Windows developers....


                                Jussi Jumppanen
                                Author: Zeus for Windows

                                Comment

                                Working...