Microbits

From what I’ve seen of Python, I relegated it to CUI and backend type tasks, since C# and .NET offer a powerful GUI platform out of the box, and Python seemingly didn’t have anything similar.

After looking into the OpenERP/OpenObject project (which looks pretty neat), I realized their complex GUI was written in Python. After a little investigation, I figured out they were using PyGTK (Python bindings for the GTK widget toolkit) and Glade (a GUI builder).

Combining Python, PyGTK and Glade seems to lead to a workable solution for creating GUIs for Python applications. There’s a nice tutorial on how all these pieces fit together here.

You’ve picked out the alliance, know the JF pickup point, and have all the skills you need trained. What should you bring with?

One of the most important things about JFs is that space comes at a premium. Ships that aren’t packaged take up a lot of space, and a single unpackaged Battleship will NOT fit in a JF. Don’t rig or insure any of your ships until they’re in null sec, since you’ll probably need to repacakge them for transport.

Before you leave, pick up any skillbooks you need, stock up on ammo (what you normally carry), and contract everything to the JF pilot (make sure this is someone you trust, or you just gave them a ton of ISK, since most alliance JF pilots don’t use collateral).

Check with your alliance to find out the safest root to their space, and if someone is willing to escort you. Wait till right before downtime, hop in your SB, and fly there. As soon as you dock at your alliance’s station, install a jump clone.

You should also start an alternate character on the same account that sits in the JF’s pickup point. This alt will buy stuff and contract it to the JF pilot so you don’t ever have to fly your main up or JC to do so. You might want to train contracting to level 1 on the alt so it can have multiple contracts.

In large fleet ops, everyone has to maintain a basic level of professionalism. If people don’t, comms get chaotic, people can’t communicate, and the fleet loses coordination and efficiency.

What does it mean to behave professionally in EVE?

1. Proper communication
   1. If battle/fleet comms are in effect, only speak if it’s relevant to the operation
   2. Make intel reports clearly (no mumbling)
   3. The only thing you can say in local is good fight (gf for short). No smack talk, mocking, or otherwise disparaging remarks or comments (more on this later).
2. Listening to the fleet commander
   1. Do nothing unless directed to by the FC.
   2. Do whatever the FC tells you do without question (if you think they missed an intel report or something, that’s different).
   3. 1 and 2 are very, very, very, very, very, very important.
3. Fly your ships well
   1. Train for T2 fittings.
   2. Ask how other people fit their ships.
   3. Always fully insure your ship. It’s illegal to fly without insurance. Not really.

Besides those specifics, it’s more of an attitude. If you’re professional IRL, you will be able to carry that over to EVE.

Smack talk in local is a waste of everyone’s time, and shows a lack of professionalism. If you want to talk to someone about how they fitted their ship, comment on something they did that you liked, etc, private convo them. If you act respectful, they usually will. Other than that, keep it in alliance/corp/fleet chat. Your enemies will have more respect for you if you do.

Living in null sec is vastly different from high sec. You have to assume that whatever you undock, you may lose. CONCORD and the Empire police forces do not patrol null sec, and there are no gate guns. Alliances, their member corporations, and the corporation’s members are essentially responsible for their own security.

Because of this new responsibility, you will need to learn how to achieve a relative degree of safety to avoid losing ships while not engaged in PvP. Although we all enjoy PvP more than anything else (that’s why we live in null sec), there are always carebear tasks to attend to. Be it running anomalies, mining, POS maintenance, logistics, PI, research or manufacturing, it all has to be done.

In null sec, if another pilot hasn’t been labeled friendly, we generally assume they are out to kill us. Assuming anything else is ignorant and irrational. Friendly pilots in EVE are known as “blue”. This comes from the blue square that appears next to their name in local, in their portrait, and in your overview.

You might be wondering, what’s “local”? Local is one of the most valuable safety tools available to null sec pilots. It’s the chat window for people in your current system. The reason it’s so valuable is it lists everyone who’s in the current system. Using this list, you can quickly check a system to find out if it’s safe (if everyone is blue, it usually is for the time being).
Read more…

A what bear? A “carebear” is a term used to refer (usually negatively) to players who don’t participate in PvP. Some people PvP from the beginning, but I don’t think most do.

People who don’t plan to be carebears for life have several PvP options open to them. In my opinion, the most rewarding is to find a good null sec alliance and move out there.

Null sec is perhaps one of the most unforgiving environments in EVE, second only to W space. Logically, it’s also has some of the best sources of income. Better asteroids, huge rats, plenty of anomalies (if your alliance owns an upgraded system). PvP usually isn’t a source of income unless you fly solo most of the time, so I wouldn’t really call it a source of income unless your corp pays you (do any?).

Before you even think about null sec, you should know why you want to go, and what the risks are. You’ll also need some specialized skills, and plenty of ISK. There are certain ships that you probably ignored in high sec, because they’re build for PvP. Since you’ll be flying them, you should have most of them trained before you move.
Read more…

The longer DT to move Tranquility (the main EVE cluster) has run way over the allotted maintenance window.

Please remain calm. Your assets have all been deleted. The world of New Eden has ended.

Just kidding. Hopefully CCP gets the cluster back up soon.

I’ve been wanting to give OSX a try for a long time… I think it’s time to pick up a Mac mini…

This is going to be interesting…

A what drop? Hot drop is a term used for lighting a cyno (a ship launched beacon that jump drive equipped ships can jump to) near an enemy and jumping reinforcements almost on top of them.

There are only two types of ships equipped with jump drives (and are therefore able to “jump”): most capital, and all black ops ships.

Normal cynos show up on the overview of everyone in the system, and function as a massive “capital ships here” sign. Covert cynos do not, and are only usable by black ops or indirectly by covert ops.

You might be wondering, how does a covert ops ship use a cyno? That’s where black ops comes in. These pricey ships (almost as costly as a carrier), usually left to gather dust in the hanger, have the ability to create a jump bridge to a covert cyno, allowing covert ops ships to jump through.

This type of jump bridge is the basis for the stealth bomber hot drop. We turned a HAC into a wreck 25 seconds after jumping, and thanks to the tiny sig radius of SBs, and our sensor dampeners, we didn’t take a single hit (although our tackle may have).

Simply because cruisers use the same sized rigs as battlecruisers. For the x million ISK, I’d rather rig something more powerful. If you rig most cruisers, the rigs end up costing more than the hull.

There are special cases where you may need a cruiser sized ship, with the advantages of rigs. In those cases, you should really use a T2 variant.

Later today, I’ll be setting up a bubble camp. Please stop by

After a few PHP access violations, I’m pretty sure EAccelerator does not work properly with multiple IIS worker processes.

I should really move to lighttpd or nginx one of these days…