Discussions

Ah, thank you!

I will have to try this out.

I just installed Vista RTM, effectively ending my almost year-long Mac stint. I've been reinvigorated with new ideas and drawn back to programming (and subsequently C9). Hoorah!

After scouring the web, I came across the different methods of glass implementation, all of which suck on some level or another. Now, I'm really interested in how us .NETters are supposed to go about implementing the other awesome Vista UI controls: command bar things, menu buttons, the new tabs, toolbars, etc. etc.

Is there any way to use these new controls, or, like XP, do we have to wait around for .NET version X with a year left in the Vista lifecycle in order to catch up?

If we have to rely on third party controls for the next three years I just may have to march to Redmond and do nasty, horrible, unspeakable acts involving UNIX.

/loves me some Vista UI goodness
//hates me some third party controls
///I'm looking at you, divelements

My Mac: Allison, Taylor
PC: Kristi, preceeded by Kelsey

An old friend got me naming computers and such after girls. Kinda went with it, I like the nicer sounding names rather than things like Watermelon and MOX4562-5465NINERZERO.

No, it's never too late. New technologies will arrive and enable you to create something entirely new not possible before, or  drastically improve upon an older concept.

It's just a matter of having the imagination.

JohnAskew:

Good points, and no, I don't talk like that around my grandparents because although I believe the concept of "swear" words is ridiculous, they don't. That sort of language I typically reserve for friends anyways, but I really do find the whole concept ridiculous.

I swear, this tread was created specifically for me.

No word is ever offensive for a valid reason. Ever. (excepting racial slurs and the like)

Take, for example, a four-letter word that begins with F. When used in a context not relating to sexual intercourse, all it does is express frustration. There's no hidden meaning. It doesn't refer to any race, let alone derogatorily. If I were to say, "Why the f**k are there mashed potatoes in my computer?" I would merely be expressing anger and/or frustration, etc. Nothing offensive. I could just as easily replace the word with a more socially acceptable one, but the meaning remains the same. All you do is replace some letters.

Again, example: Some people take to saying "frick" (or "frigging/fricking" in the case of a present participle) instead of the well-known four-letter no-no. Why? What are you changing? Nothing. The meaning and intention are the same, all you've done is changed a couple letters.

Someone give me one good, solid reason why any words are EVER offensive. There aren't any, except for racial slurs and things of that nature. They're words, people. A lot of them have the same meaning but are still considered "rude" or "offensive" for no particular reason, other than that our parents told us they were offensive.

And getting to your question, no, the word "sucks" is not offensive. All it does is describe the horrible quality or whatever of the thing you're describing. It's absolutely no different than saying "is extremely horrible."

So many aspects of modern culture suck.

EDIT: And I'd thought I'd get this out of the way: one of the posters above pointed out that sucks was originally durogatory but now it isn't. That's fine. It was offensive, and I can see good reasons for it being so, but now it isn't.

W3bbo wrote:

Or just use Mono?

PPC. No Universal/Intel version as of yet.

EDIT: Just installed it anyways. Hopefully it works fine.

RETURN OF THE EDIT: Hrm. It seems to have just hidden on my system. Awesome.

THE EDIT STRIKES BACK: It's ugly, according to some screenshots in this tutorial. Looks like Windows 9x.

Ah, much, much appreciated, CyberGeek. Maybe I'll play around with it later this afternoon.

CyberGeek wrote:

I personally tolerate Xcode and love Cocoa (it's really weird and different, but a lot of what it does differently starts making sense after you spend enough time thinking about it and playing with it). That said, I'm also really interested to learn about what's going to happen with WPF and C# on OS X.

Xcode is not that bad, I just prefer the way Visual Studio is laid out.

Cocoa though.. Oh, man. It'd be one thing if it was just the obj-c, but it's the API. And why isn't the toolbar part of the control palette? That'd be so much simpler than writing fifty classes and such for each item. Ugh.

Where/how did you learn Cocoa? I can't find many tutorials that aren't condescending to Windows users or well-written.

So I'll still be able to write apps in it, but the Mac CLR will be lacking certain features, like, say, SQL DB connectivity or MSMQ? Or is it just enough of the CLR to support UI operations?

Sounds good enough for me, so long as I get to stay far, far away from Cocoa. Though, if I could use Cocoa and skip the whole Xcode/IB thing, maybe it'd be tolerable.

/farker -- ricodued
//slashie slash slash