I have enjoyed using Bazaar. Its flexibility is tremendous. I've always used whatever SCM system I was using from the command-line and avoided turning on integration in the IDE since it seemed to cause more problems for very little benefit.
However, after watching some of the Xcode 4.0 WWDC videos, I've realized the writing is on the wall. Xcode integration of svn and git will now provide useful benefits. I also realize that as the third most popular DVCS, Bazaar is unlikely to ever see support in Xcode.
So, with that in mind, I've decided to switch from Bazaar to Git (unless something goes horribly wrong).
The positive news is that so far, the conversion has been about as painless as it could possibly be. Certainly far more painless than the conversion from CVS to Bazaar.
To convert from Bazaar to Git involved the following steps:
1) Install the Bazaar fastimport module
2) Install git
3) Create a git repository into which to convert
git init git.repo - (use --bare if it's going to be on a central server)
cd git.repo
4) Run a command to export the bazaar repository, piping the result to a command to import into git
In this example:
~/bzr_repo - the bazaar repository to convert
~/git.repo - the new git repository
(command is being run from the git.repo directory)
bzr fast-export --export-marks=../marks.bzr ../bzr_repo/ | git fast-import --export-marks=../marks.git
That's it. You're now done. You can now clone that repository and go to work.
Thursday, July 22, 2010
Tuesday, July 6, 2010
Doctors' payments
Does anyone else hate trying to pay their doctor as much as I do?
First, you can never figure out how much you owe them. Typically, a huge bill comes first. But you know you don't owe that much, since insurance is going to cover the majority.
So you wait for your next statement to see what you really owe. But now you're past-due. And woe be to you if you visit the doctor more than once in 30-days; you'll be lost in an impossible maze of charges and insurance reimbursements.
Ok, fine. My doctor sent me a "please pay now" notice, so I'm pretty sure this is what I actually owe. No problem. While I'm sitting here paying bills online, I'll just quickly go to their website and pay online.
Except that they don't accept online payment. Are you freaking kidding me? An industry that has massive trouble collecting payments does not provide a way for patients to pay online? Yep, that's right. Ninety-nine percent of doctors have no way for you to pay online.
I could pay with my regular online bill payment service. However, it seems like I have about 12 different accounts associated with the doctors we see. So it's awfully inconvenient to have 12 different payees in my payment service.
Fine. I'll call them. Oh wait - it's 11 pm and an industry which has trouble collecting payments only has its billing office open from 9-5 on weekdays.
Fine. I wait until tomorrow. I call the business office during their advertised hours and listen on hold for 20 minutes while the voice response system tells me my call is important. After 20 minutes, it routes me to a voice mail box. I leave a voice mail. Four hours later, after receiving no call back, I call again. 20 minutes later I leave another voice mail. Four hours later after no call back, I call again. Twenty minutes of repeated "your call is important to us" later, the system tries to transfer me to an operator, but it hangs up instead.
The business office is now closed for the day. To make a long story a little shorter, after two more attempts the next day, I finally get through and pay my bill over the phone with a debit card.
In short, absolutely unacceptable.
Yes, I realize I could just write a check, get a stamp, put it in the envelope and mail it. However, that's not the point. The point is, I want to pay my bill NOW. Online. And you're not letting me do it.
No wonder you have problems getting paid.
First, you can never figure out how much you owe them. Typically, a huge bill comes first. But you know you don't owe that much, since insurance is going to cover the majority.
So you wait for your next statement to see what you really owe. But now you're past-due. And woe be to you if you visit the doctor more than once in 30-days; you'll be lost in an impossible maze of charges and insurance reimbursements.
Ok, fine. My doctor sent me a "please pay now" notice, so I'm pretty sure this is what I actually owe. No problem. While I'm sitting here paying bills online, I'll just quickly go to their website and pay online.
Except that they don't accept online payment. Are you freaking kidding me? An industry that has massive trouble collecting payments does not provide a way for patients to pay online? Yep, that's right. Ninety-nine percent of doctors have no way for you to pay online.
I could pay with my regular online bill payment service. However, it seems like I have about 12 different accounts associated with the doctors we see. So it's awfully inconvenient to have 12 different payees in my payment service.
Fine. I'll call them. Oh wait - it's 11 pm and an industry which has trouble collecting payments only has its billing office open from 9-5 on weekdays.
Fine. I wait until tomorrow. I call the business office during their advertised hours and listen on hold for 20 minutes while the voice response system tells me my call is important. After 20 minutes, it routes me to a voice mail box. I leave a voice mail. Four hours later, after receiving no call back, I call again. 20 minutes later I leave another voice mail. Four hours later after no call back, I call again. Twenty minutes of repeated "your call is important to us" later, the system tries to transfer me to an operator, but it hangs up instead.
The business office is now closed for the day. To make a long story a little shorter, after two more attempts the next day, I finally get through and pay my bill over the phone with a debit card.
In short, absolutely unacceptable.
Yes, I realize I could just write a check, get a stamp, put it in the envelope and mail it. However, that's not the point. The point is, I want to pay my bill NOW. Online. And you're not letting me do it.
No wonder you have problems getting paid.
Friday, June 25, 2010
Status of the Mac client
As some of you may have guessed by my lack of posts, the Mac client has basically been stalled. My real-world job has been absolutely crazy, summer means all sorts of kids' activities and I've picked up additional responsibilities at VATSIM.
I have no intentions of abandoning the project though. In fact, I'm considering adding some additional team members to help speed things up. Things I'd likely farm out would be the things that can be easily compartmentalized like alias and POF file handling, flight strips, etc.
I haven't made a final decision yet, but if you know Objective-C and want to help, let me know.
I have no intentions of abandoning the project though. In fact, I'm considering adding some additional team members to help speed things up. Things I'd likely farm out would be the things that can be easily compartmentalized like alias and POF file handling, flight strips, etc.
I haven't made a final decision yet, but if you know Objective-C and want to help, let me know.
Sunday, February 14, 2010
Some network goodness
More & more pieces are coming into place in the Mac client. This week I wrote an Objective-C wrapper around the VVL network code. Good chance by the end of next week I'll be able to login and start testing sending and receiving text messages on the network.
Additionally, it won't be difficult to wrap the voice code either, so it may not be too much of a stretch to get voice working before much longer as well. The Mac voice code all needs to be rewritten as it's still VERY old SoundManager code (yech) which frankly I'm surprised still works. However, it does work, so I'll probably start off with just using it as is at first, so we can get something out the door without having to wait on me to rewrite the code with CoreAudio.
Additionally, it won't be difficult to wrap the voice code either, so it may not be too much of a stretch to get voice working before much longer as well. The Mac voice code all needs to be rewritten as it's still VERY old SoundManager code (yech) which frankly I'm surprised still works. However, it does work, so I'll probably start off with just using it as is at first, so we can get something out the door without having to wait on me to rewrite the code with CoreAudio.
Saturday, January 30, 2010
Things are looking up
With the heavy snow (well heavy by our standards) snow in Nashville, the family hasn't been able to get out of the house, so I've had a little more time to sit and program rather than running all over creation.
I've gotten a not completely insignificant portion of the interface wired up with Interface Builder and have moved on to start working on the text windows. This part is going to be a bit challenging since I'm trying to integrate traditional Cocoa controls on top of an OpenGL view. It can be done, but not having attempted it before, it's going to take some playing with.
I've gotten a not completely insignificant portion of the interface wired up with Interface Builder and have moved on to start working on the text windows. This part is going to be a bit challenging since I'm trying to integrate traditional Cocoa controls on top of an OpenGL view. It can be done, but not having attempted it before, it's going to take some playing with.
Subscribe to:
Posts (Atom)
