New book about customizing the WoW UI
Posted 31 May 2007 - 11:18 PM
The publisher's website has some excerpts, including the Table of Contents, the Index and a part of Chapter 1. http://www.wiley.com...0470110023.html.
Quick link to Amazon for those interested: http://www.amazon.co...80654222&sr=8-1
If you have any questions, please let me know, or contact me on the boards, or at [email protected]
Posted 31 May 2007 - 11:23 PM
Posted 31 May 2007 - 11:26 PM
Posted 31 May 2007 - 11:27 PM
I will change the post title to hopefully stop this from happening again.
Posted 31 May 2007 - 11:30 PM
Edit: And I'm well aware that "hacker" has a different connotation these days. That doesn't mean morons won't abuse the term on these forums.
Posted 31 May 2007 - 11:30 PM
(edit) Beaten to it by two others...
Posted 31 May 2007 - 11:32 PM
Posted 31 May 2007 - 11:36 PM
(take from the link)
"Hacks, hacks everywhere-hacks encompass such unique topics as combat, artwork and model, map, interface, loot, chat, raid, PvP, class specific, and more!"
However, I do understand that "hacking" also refers to the art of writing and redefining computer programs.
I guess I'm just biased from all the other books, or guides, involving World of Warcraft that end up being cheap scams that any real player would know at once (Leveling Guides for example.)
Anyway, the book does look interesting and informative.
Posted 31 May 2007 - 11:38 PM
Posted 31 May 2007 - 11:51 PM
Looks interesting though how much of it is aimed at people using the default UI and few mods vs. the (usually) highly organized and heavily modded UIs that tend to be posted here?
Posted 31 May 2007 - 11:55 PM
If you're a budding addon author, the two addons you write are non-trivial and actually do something useful in both cases. They don't just tell you what to type, they explain why you're typing it =).
Posted 01 June 2007 - 12:04 AM
I've been struggling with the name too for a long time, and I knew this kind of confusion would happen as soon as the book was made available. Unfortunately, the name wasn't up to me, rather it was Wiley's decision from the start. In the end, it was probably a good marketing choice for them, but certainly causes a fair share of confusion for many players.
Anyhow, Jim gave y'all the basic information. If you have any questions, feel free to ask (my email address is [email protected]). There'll most likely be some contests coming up where you can will a copy of the book (since I've got a whole box of em). At the very least they'll be at atlasmod.com, possibly some bigger sites elsewhere stay tuned
Posted 01 June 2007 - 02:44 AM
A Hacker is someone who, in general terms, makes software do what he or she wants it to, with the express purpose being generally ease of use, or implementation of features left out by the original designer.
A Cracker does the same things, just with malicious intent.
Customizing your UI fits under the first category, running a bot the second.
These days hacking carries a wide number of negative connotations, from Script Kiddie to Cyber-terrorism, but it's still the correct and accurate nomenclature to use in this case.
Posted 01 June 2007 - 03:17 AM
I was under the assumption this book is a guide for illegal activities pertaining to the coding of WoW. Thats what I think of when the word "hacking" comes up. I apologize if this is not the case but,"Hacking World of Warcraft" seems to be a leaning to the shady side of addons.
A "Hack Solution" is a quickly coded application or method/function that is just what you need for the moment, not necessarily fleshed out in any way.
Figured I'd pass that along as well.
Alpha is recruiting... go go.
Posted 01 June 2007 - 03:35 AM
Posted 01 June 2007 - 06:54 AM
The term "Hacking" is actually the correct one. If the book were about exploits in-game, it would more correctly be called "Cracking".
Yeah, unfortunately modern journalism never made the distinction. Hacker, some few years ago meant person able to analyze, understand, configurate and operate the complex computer systems. Nowadays, it's most likely portraying a guy who eats junkfood all day, lives in a cellar and does illegal stuff with computers.
Big difference. The war about proper use of words has been a lost cause for a long time now. Lots of people still call themselves hacker and most often that's meant in the old sense.
You really pick all the important stuff out by just doing this and you already start with the Ace-Libs, which do a lot of work you'd need to do manually otherwise.
As with everything programming, learning by doing is imho the best way, though a good book is always great if it can give you a better understanding or some inspiration alongside.
Posted 01 June 2007 - 07:02 AM
Posted 01 June 2007 - 07:45 AM
You're going to be far better off if you learn how to do everything yourself first rather then having to rely on libraries all the time, using the book and/or wowwiki you can get a pretty good idea on how to do the basics involving events and so on.
I used to have the same opinion, but I do no longer.
If you really really want to know exactly what's happening right down there, then yes. I still know people that in this day and age write C or Assembler and not this "modern crap" that abstracts and don't let people get their hands really dirty by allowing to manipulate every single bit.
If you want to know exactly what is happening, then yes, I agree with you, though I wouldn't really start out with looking deep into that.
Today, I've moved away from NIH-syndrome ("Not invented here"-Syndrome; no accusation to you, just as example) and just take a good lib when I find one instead of trying to do all myself. Guess working for years in Java tends to make you yearn for good "classlibs". I personally find that people need to work more on understanding and using abstractions correct in order to be good programmers rather than able to track down each and every last bit. Just because the latter more often than not is no longer really relevant, where you work with layers upon layers of abstractions. Of course, being able to do both is always great. But I really only go looking below the hood if something is repeatedly not working as it should or I expect it to.
In short (and a bit evil, for which I apologize), I much rather just write a self:RegisterEvent("foo") and concentrate on the event handler instead of finding out how events work, writing my own event manager and then go to the event handler which I need to do in any case. And that's just a simlpe case, I don't really want to localize spell names in all languages, I couldn't even do it outside german and english. Yet all I need to do now is to get Babble-Spell for example and I have a maintained, working and proven solution. I just don't need to invest time there. Divide and conquer, really. Concentrate on what you want to do new stuff, don't reinvent X for the umpteenth time. It's there, it works already, it's in use other places. If there is a bug, other people will very likely find it before you even know there is one and it will most likely be fixed before you ever get bitten by it.
If you *need* to do it all by yourself, which of course isn't bad at all, you can do it. I guess not many of you built the house they are living in from scratch by themselves but are doing some hosework and changes here and there. It's the same for all software project beyond trivial complexity. You can build everything from scratch (and it may make sense to do so), but if you do it, you are just more likely to make more errors and mistakes than if you take bits and pieces that are known to work and just put it together and then expand a bit here and there. Especially if you've never done it before. It can be a great learning experience, but most likely you don't want to live in that first built house of yours but instead build a better second one.
Sorry for the longish derail on software design. You can guess what my day job is now
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users