Skip to main content

Mac OS X software equivalents to some windows software

Equivalents
tortoiseCVS -> eclipse's built in CVS interface
winCVS -> Cyber Duck
SciTE -> smultron
bloodshed dev cpp -> eclipse
texniccentre -> texmaker

Other
jollysvnc -> a vnc client (From Jon)
omnidisksweeper -> a gui for du (From Jon)



UPDATE:

The post Nick mentions in the comments is here.

Comments

  1. with everything I seen you posting lately about the Mac and developing on a Mac, don't forget to take a look at either Fink and/or MacPorts. Almost anything Unix oriented can be found there.
    I've used both, currently using MacPorts, but just installed fink on a co-workers computer. They both work fine and I wouldn't recommend one over the other. There are reviews and comparisons all over the place, I posted some commentary on it in my blog about a month ago here.

    ReplyDelete
  2. Hey Nick,

    Thanks for the pointers. I ran into both Fink and MacPorts. I shied away from a random bad experience (with Fink, I think it was) but there are always hiccups. I should look into this more.

    -K

    ReplyDelete

Post a Comment

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or...

Store numpy arrays in sqlite

Use numpy.getbuffer (or sqlite3.Binary ) in combination with numpy.frombuffer to lug numpy data in and out of the sqlite3 database: import sqlite3, numpy r1d = numpy.random.randn(10) con = sqlite3.connect(':memory:') con.execute("CREATE TABLE eye(id INTEGER PRIMARY KEY, desc TEXT, data BLOB)") con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", sqlite3.Binary(r1d))) con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", numpy.getbuffer(r1d))) res = con.execute("SELECT * FROM eye").fetchall() con.close() #res -> #[(1, u'1d', <read-write buffer ptr 0x10371b220, size 80 at 0x10371b1e0>), # (2, u'1d', <read-write buffer ptr 0x10371b190, size 80 at 0x10371b150>)] print r1d - numpy.frombuffer(res[0][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] print r1d - numpy.frombuffer(res[1][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] Note that for work where data ty...