Recent comments
- June 2010 (2)
- March 2010 (2)
- November 2009 (1)
- October 2009 (3)
- September 2009 (1)
- August 2009 (1)
- July 2009 (2)
- June 2009 (4)
- May 2009 (1)
- April 2009 (3)
- March 2009 (9)
- February 2009 (3)
- January 2009 (5)
- December 2008 (4)
- November 2008 (15)
- September 2008 (4)
- August 2008 (6)
- July 2008 (10)
- June 2008 (13)
- May 2008 (8)
- April 2008 (7)
- March 2008 (1)
- February 2008 (5)
illogic-al.Org
Now that I've let this sit a while, it's time to explain.
The analogy that I chose to use may have been misconstrued by certain folks.
HOT CHICK is the world. At first she seems, all pretty and, well ... hot and everything that you want.
HOMELY CHICK is the christian life.
Hot chick's layer-caked makeup symbolizes the fakeness that is rampant in the world today. People who smile in your face but then talk about you behind your back. Circumstances which are presented as ideal at first glance, but upon reflection you see were bad ideas. I.E. doing things just to "have some fun" (because "everyone's" doing it) but later regretting it. You start to feel the regret after action passes and consequence sets in. I'm sure I don't need to give examples you, you can amply fill in the blanks with examples from your own lives. And as consequence sets in you begin to see the cracks in the layers.
Some see through the façade of the worldly life and start looking for something else, something better. And that's where homely chick steps in. A life of following Christ steps into the void, and, while at first this life seems more uptight and restricted, you paradoxically begin to feel freer for it. You start to see the "homeliness" for the beauty within, and as the relationship becomes a more intimate one (no, no. not like that) you see what it's all about. You begin to understand God's purpose for your life and see that it's actually the better choice.
That's the "flippin' hot" part btw. The attraction in this case is to the freedom this life affords. Freedom from death (of the soul), freedom from worry (God's gotcher back!), and freedom from following all the crap "everyone" is doing.
Alrighty, I'm out. PEACE!
No bad post, write more
Its funny how we always remember God when we feel disappointed with our life, or when we need his help most. I first decided to read the bible after a strong breakdown because i broke up with my boyfriend. I didn't succeed to finish it then, it was very difficult for me to focus then, so i gave up reading it. My second attempt to read it was better, because i looked for an online bible study, which made it sound understandable. Anyway, i am proud i finished it in few months, and i wouldn't mind to do it again.
Were these letters of love written to me, or by me?
Good work man. I know the feeling about being scared, I've found it's rarely God's plan unless you feel a bit intimidated by it all. That means we're relying on his strength rather than our own.
Have a good week!
I meant maybe the portfile for amarok-devel would be updated so that it works. Since amarok got wiped from the face of kde's svn repo it wasn't working (or so implies a trac ticket). I finally got it working last night, submitted, then went to bed.
It does the build in the srcdir which is against some policy, but it works so I'm happy. Well, the program itself crashes for me... but that's another battle for another day.
Thanks for the update ;-)
I submitted the bulk of the patches for KDE 4.3.0 to macport and snc was kind enough to actually commit them :)
What did you mean by "Maybe one day [snip] Amarok itself will also be updated"?
Can do.
You got it to work?
You haven't actually listed a problem...
Dude, if you aren't going to blog it (which I think you should) then can you tell me on Google Talk?
Peace!
While trying to compile all packages needed for amarok I had a lot of Problems but I solved most of them. But I collapse at amarok itself. Here is my Problem do you have any idea?
best regards, mike
I'm out of the packaging game but tried setting up instructions here way back when.
http://techbase.kde.org/Projects/KDE_on_Mac_OS_X/Macbook_Manifesto has instructions. You can also search the archives here if you hits some problems maybe I've encountered them before and solved them.
in google you can do that by: "site:illogic-al.org searchterms" good luck. :-)
Hello
I tried the whole last day to compile amarok for Mac and it ends at a linking error of kdelibs4.
So no amarok for my mac. A dmg for OSx would be much easyer for mac users and save a lot of time, so if its help you are missing for the dmg here "I AM".
I would be much easier if there is a dmg for every stable release. Is it possible for you to make a tutorial or some notes how to create a dmg with the ports compiles?
So I'm trying to fix my problem....
I look forward to hear from you.
best regards
What is forgiveness? Forgiveness cannot be understood without understanding the nature of sin and it's effects. St. Matthew (22: 37-40) records the words of Jesus: "You shall love the Lord your God with all your heart, and with all your soul, and with all your mind. This is the great and first commandment. And a second is like it, You shall love your neighbor as yourself. On these two commandments depend all the law and the prophets." Sin is a breaking of God's Laws to love Him and to love our neighbor, despite and in the face of His infinite Love for us.
Edit: Dear medea, I agree. P.S. No porn links allowed
(yes, your account is banned now - post can stay though) :-D
I will neither confirm not deny any awesomeness on my part in the resolution of the problem at hand. That is all.
Just wanted to thank you for the updates. Did you do anything to make the amarok-devel port compile since you wrote this? I didn't have any issues compiling and I'm wondering what changed.
Thanks much!
You can report any more checksum errors here. If stuff doesn't compile file a ticket.
http://trac.macports.org/ticket/19959
I think this was a cut and paste error. Can you confirm?
Thanks
Imagine how I feel. It's my site and I have to do it too. :-(
It was the easiest way I knew of to fight the spammers. It was either that or block everybody in mainland China :-)
Having done 2.5 years of cross platform development with Qt, I agree.
It takes a lot of effort to make Qt applications look like Mac applications.
For example I had to override the mouse and paint events in the Last.fm client to move the arrows it draws on the left 7 pixels to the right so that it looked like all the other tree views on OS X. I had to do tonnes of custom layout to make widgets line up like they do in other Mac apps (QDialogButtonBox is just rubbish). We had to override the QStatusBar to make it look like other apps on OS X! QStatusBar! Shouldn't that at least look right?
Four consecutive versions of our app used 4% CPU when idle on Mac. Eventually Qt 4.3 came out and the bug stopped. This is good, they fixed it, but things like this are why I maintain little confidence regarding Qt on Mac.
But this is only part of it, you can make Qt apps look like Mac apps, but you just can't make Qt applications feel like Mac applications.
Some of this was addressed with Qt 4.5 if you compile with Cocoa; one thing that always made Qt apps stick out like a sore-thumb was mouse wheel behaviour in scroll views. Mac mice have a scroll-ball, scrolling it a little moves the scroll view 1 pixel. Qt apps always scrolled by 10 or so. More like Windows and Linux behaves. This is fixed with Cocoa-built 4.5.
But sadly, numerous other issues remain. Also sadly, I can't think of any right now. But you only have to google for Qt mac sucks to get a feel for what real Mac users think.
I agree with you illogical. I'm not sure why all the losers above my comment are defending Trolltech so firmly, or demanding you fix it. You? Wtf? Don't you do enough already? I bet none of them do anything to help any open source projects. Trolltech are great, but I will not develop with Qt on Mac again if I can help it. I don't think the situation can be fixed until Qt 6, and only then if they really think about how widgets layout more carefully. I appreciate it is hard to do. If anything it exposes the truth about cross platform development, ie. really the GUI layer has to be native. But sadly Qt isn't flexible enough to allow that. And I don't know if it should be. Qt is wonderful because you can develop amazingly polished apps quickly and bugglessly. I wouldn't want to compromise that.
Also there are plenty of excellent and unique widgets that Cocoa provides. With Qt, you can get them, but only with Cocoa Qt and then you need to do platform specific development anyway.
Qt is great on Windows, Microsoft provide nothing good for C++ developers on Windows. And if you use Win32 you have basically no powerful widgets that are native. Qt is great on Linux, (although I would have picked GTK for Chrome too TBH), I wouldn't use anything else on those platforms.
Needs work on Mac, kthxbai.
ps I had to register to comment?! I _almost_ didn't. I guess that is what you want, but still, I'm not happy about it :P
Hi -
I see that you just removed yourself as a maintainer of kdelibs4 on macports, so I may be too late:
http://trac.macports.org/changeset/52298
But I'd really appreciate a hand here.
Backstory: earlier versions of digiKam have been made to work, but SVN head doesn't and the project is in a drive to 1.0. It's be really great if 1.0 was released for Mac, as well as their existing Linux and Windows versions. There's been someone who has done a lot of work and got most of the way there. He's done enough to get one of the core digiKam devs interested and willing to do the last bits. I come in because I can provide remote access to a Mac to Gilles. To do this, I've set up a new box, installed Xcode and am trying to set up all of the dependencies so that the digiKam dev can focus on the digiKam issues and not have to fight with an unfamiliar environment. (He's a linux guy.)
I see that you added kdelibs 4.2.4 to macports last night, which is great, since 4.2.0 was gone.
Unfortunately, here's what I get when I try to install that port:
Error: Checksum (md5) mismatch for kdelibs-4.2.4.tar.bz2
Error: Target org.macports.checksum returned: Unable to verify file checksums
Error: The following dependencies failed to build: kdelibs4
Error: Status 1 encountered during processing.
I don't know enough about macports to know where, exactly, the issue is. Has some change just not yet propogated to a server? This box is a fresh install and I started with a macports install and self update at about 3pm Central Daylight Time this afternoon.
I can file a ticket at macports.org but I thought I'd try you here since perhaps this just was a simple oversight during the check-in process?
Thanks for any direction you can provide.
thomas -at- lunde -dot- net
I'll agree with the central question -- Chrome should have picked Qt instead of GTK+ if they wanted to use it on Linux and Mac (and Windows). Qt is a much better choice. I think you can write better code with Qt.
I think Qt gets you ~80% of a Mac port. Granted, that's the most important 80% of an app (especially in science). But I know from experience that there are a lot of little details that need to go into a "native" program on any platform. File associations, icons, look-and-feel... Now that there's a Qt/Cocoa port, there's finally a way to take the extra steps for that last 20% of a Mac port.
There's just an impedance mismatch between Qt and Mac. The Trolls do a lot, but handling menus is a pain. If I close a document on a Mac, I still have menus. I had to write a pile of code to attempt that in a Qt/Mac program (Avogadro). It still has bugs.
That's the point of the MacMainWindow. You don't get those Mac looks for free -- you have to replace the Qt widgets with native Cocoa ones. Yes, it's possible, but it's not like you just recompile the KDE Linux app.
Anyway, Google made the wrong choice on Linux. Heck, Google Earth on Mac and Linux use Qt, right?
Isn't the fact that a "MacMainWindow" example exists enough proof that Mac-looks aren't something every Qt app gets for free? Maybe I'm wrong, but I'm pretty sure thats illogic-al's entire thesis in this blogpost.