I, too, just received my Tech. license. I did get one of the formentioned books from the ARRL which focused on the FCC licencing requirements needed. Somewhat disappointed in the text (it wasn't as in-depth as I would have liked, especially from a "how to operate" standpoint), but that can be made up from other sources like the aformentioned books and listening to people actuallying operating (ok... maybe not so much...)
I also found some good online websites (I've lost the references...) that will quiz you using the question pools available to see if you know your stuff. Resist the temptation to memorize the question pool unless you understand the "why" behind the questions asked.
Having said that, if you have a technical background (doesn't NEED to be electrical... this ChE passed easily), and can use some common sense (which helps remebering many of the simple FCC regulations), the test is a simple multiple choice exam. With the online study, and what you learn studying for Technician, you may even be able to pass the General exam as well (I came short by 3 questions...and I didn't even study for it!).
As for the Morse requirement, I am having a hard time with it. I can hear the differences, but the brain is not doing so well in tying the rhythm with a letter. So, I'm happy that I can progress without knowing it, but at some point I will force myself to pick it up. (Been trying to decode a beacon on 6M around here... I know what it should be saying, but I haven't been able to pick up anything past VVV)
Being one who did some of the early work on the replacement, I'll throw in my reasons.;)
One reason why gdk-pixbuf came to be was to easily stuff RGB data into a gdkrgb/libart framework. Imlib wasn't really the easy way to to do this. Also, imlib had a "wonderful" alpha channel hack (basically, one bit alpha using magenta). Since we wanted to support a real alpha channel, this wasn't a great idea.
Second was the whole cache issue. It leaked like a sieve. Which leads to reason #3...
...the imlib code is a frightening mess. Look at the XPM loader for starters (io-xpm.c is one function...and well over 60 lines long, and indented a few(!!) times). At first, I tried to do some maintence, but it quickly became next to impossible to do. So, I bit the bullet and started from scratch.
And I give "mad props" to the GIMP and gtk crew, through allowing me and the other gdk-pixbuf hackers to use some of the GIMP plugins and gdk code to write the loaders. I like this free software thing.
As for esound, it seems like the maintainer has slid off the face of the planet. So, if anyone has pointers to docs for the latest ALSA API, I'd appreciate it (haven't found anything on the ALSA webiste:( )
IIRC, the XFree 4.0 stuff does talk to the monitor if the card/monitor supports it to get monitor info. Also, if you're missing specific modelines, it will default to VESA standards. Of course, I haven't mucked around with the latest devel release, and my linux box isn't in front of me...
-- "... the deep things in science are not found because they are useful; they are found because it was possible to find them."
I'm the current maintainer, and I've gotten backloged in some more important things (moving, starting work towards my PhD, working on gdk-pixbuf), so I haven't paid attention to it much.
If it works for you, I suggest you drive down to Las Vegas and hit the blackjack tables, because, boy, you're lucky!:)
Seriously, though, as soon as I figure out the last ins and outs of the Xv extension and massage it into my gtk-tv widget, a working (and releasable) Gnomovision will be ready.
(and yes, Virginia, with the gtk-tv widget, you can have a tv-applet for you sick freaks who wanna watch "Three's Company" in a 64x64 square...)
-- "... the deep things in science are not found because they are useful; they are found because it was possible to find them."
Slashdot Mirror
I, too, just received my Tech. license. I did get one of the formentioned books from the ARRL which focused on the FCC licencing requirements needed. Somewhat disappointed in the text (it wasn't as in-depth as I would have liked, especially from a "how to operate" standpoint), but that can be made up from other sources like the aformentioned books and listening to people actuallying operating (ok... maybe not so much...)
I also found some good online websites (I've lost the references...) that will quiz you using the question pools available to see if you know your stuff. Resist the temptation to memorize the question pool unless you understand the "why" behind the questions asked.
Having said that, if you have a technical background (doesn't NEED to be electrical... this ChE passed easily), and can use some common sense (which helps remebering many of the simple FCC regulations), the test is a simple multiple choice exam. With the online study, and what you learn studying for Technician, you may even be able to pass the General exam as well (I came short by 3 questions...and I didn't even study for it!).
As for the Morse requirement, I am having a hard time with it. I can hear the differences, but the brain is not doing so well in tying the rhythm with a letter. So, I'm happy that I can progress without knowing it, but at some point I will force myself to pick it up. (Been trying to decode a beacon on 6M around here... I know what it should be saying, but I haven't been able to pick up anything past VVV)
Good luck!
KC2QLC
...and soft matter systems, or piles of sand, or pores through activated carbon...
(just finished my thesis, which did touch on fractal structure of soft matter systems. Very interesting stuff, in my biased opinion)
Being one who did some of the early work on the replacement, I'll throw in my reasons. ;)
:( )
One reason why gdk-pixbuf came to be was to easily stuff RGB data into a gdkrgb/libart framework. Imlib wasn't really the easy way to to do this. Also, imlib had a "wonderful" alpha channel hack (basically, one bit alpha using magenta). Since we wanted to support a real alpha channel, this wasn't a great idea.
Second was the whole cache issue. It leaked like a sieve. Which leads to reason #3...
...the imlib code is a frightening mess. Look at the XPM loader for starters (io-xpm.c is one function...and well over 60 lines long, and indented a few(!!) times). At first, I tried to do some maintence, but it quickly became next to impossible to do. So, I bit the bullet and started from scratch.
And I give "mad props" to the GIMP and gtk crew, through allowing me and the other gdk-pixbuf hackers to use some of the GIMP plugins and gdk code to write the loaders. I like this free software thing.
As for esound, it seems like the maintainer has slid off the face of the planet. So, if anyone has pointers to docs for the latest ALSA API, I'd appreciate it (haven't found anything on the ALSA webiste
IIRC, the XFree 4.0 stuff does talk to the monitor if the card/monitor supports it to get monitor info. Also, if you're missing specific modelines, it will default to VESA standards. Of course, I haven't mucked around with the latest devel release, and my linux box isn't in front of me...
--
"... the deep things in science are not found because they are useful; they are found because it was possible to find them."
dons nomex suit
d) Imlib is one frightening piece of code. I wouldn't want to be one to help maintain it
(that, and the use of X calls in the 'gdk_imlib' portion of Imlib also made my life miserable as I played with win32/other non-x ports...)
--
"... the deep things in science are not found because they are useful; they are found because it was possible to find them."
Ok, so how does this "automatic load balancing" work anyways? I'm curious about the underlying mechanisms behind it.
Disclaimer: I am a moron. I only play a computer geek on the Internet. I'm really a ChmE by training....(I play with explosives, not networks ;) )
--
"... the deep things in science are not found because they are useful; they are found because it was possible to find them."
And it's still completely borked!
I'm the current maintainer, and I've gotten backloged in some more important things (moving, starting work towards my PhD, working on gdk-pixbuf), so I haven't paid attention to it much.
If it works for you, I suggest you drive down to Las Vegas and hit the blackjack tables, because, boy, you're lucky! :)
Seriously, though, as soon as I figure out the last ins and outs of the Xv extension and massage it into my gtk-tv widget, a working (and releasable) Gnomovision will be ready.
(and yes, Virginia, with the gtk-tv widget, you can have a tv-applet for you sick freaks who wanna watch "Three's Company" in a 64x64 square...)
--
"... the deep things in science are not found because they are useful; they are found because it was possible to find them."