VRML Books

good book for html db beginner developers. many GUI and detail instructions you can follow to develop your own application. very easy to read and play on your own.

This is a great book, I know this becuase I've read it. I've also passed it along to other developers within my group, three, to be exact and they like it as well. I'm finding it to be much more useful then the online documentation.
=============================================
I would recommed this book to anyone who wants a great resource for Oracle HTMLDB.

The authors state that this book is for beginning and intermediate htmldb developers but my opinion is that it is a confused conglomerate of descriptions of very obvious details through to details that only an advanced user would consider.

For example, there is a long description of the SQL Workshop. In my opinion, anyone who knows enough about constraints, triggers, defaults, nulls (:)) to make sensible use of this facility will be able to work out the workshop without much trouble.

In one place the authors point to useful information on the web, mainly the oracle "htmldb" home page, saying that there is no need to repeat the details in the book. On the other hand, the appendices (and other places) contain details which are readily available in manuals. I would have documented the former and referred readers to the latter.

Steps are listed in detail to perform many, often basic, functions. "and follow the prompts" would have been more than sufficient in many/most places and would have allowed the authors more space to actually get around to providing useful information. On the subject of useful information, in my opinion the manuals describe what can be done but useful information is what should be done. I purchased the book expecting the latter, that the authors would elaborate on lessons learned from experience (how-to information) so that readers would not have to go through the same pain to get workable applications most easily. But not so. The Tips and Techniques & Best Practices chapters are only 20 pages total; and are categorized as Advanced Topics. Neither is there any indication of things that logically htmldb could do for you but doesn't - such as (not) setting the max length of fields and incorporating column comments.

Want to know about checkboxes? Radio buttons? Well, don't expect to find index entries for these. Not what I would expect from a handbook.

There is detail on replacing XL and MSAccess with htmldb. Maybe this should have been left to a book on XE. In any case, I would assume that the push for this comes from the IT crowd, or some enlightened end user/developer, in order to get data under some corporate control. It is surprising therefore that there is no mention of data backups. Excel and access files are more than likely on network drives and so would be backed up periodically. Bundling multiple htmldb workspaces together might provide different challenges with respect to backup and recovery regimes.

I was not enlightened by the chapters in the Website and Application Examples section. Certainly not why I bought the book. Besides, harking back to the beginner and intermediate target audience, these examples are too complex in design. Furthermore, I half expected the source to be available so that the code could at least be examined in order to see how the design details were actually implemented. Perhaps this is more marketing than substance; though not as direct marketing as in the section on PL/SQL Error Handling.

OK, maybe I should admit that my negativity may have something to do with the fact that I am a DBA and have been using htmldb for almost a month. And that I expected the book to tell me what I now know about how to approach htmldb developments and to fill in the gaps where I am still grasping for elegant/generic solutions. It doesn't do either.

There are some good sections in the book. The sections on templates for example; though changing templates requires a reasonable knowledge of html and css (and javascript) and so is probably more an advanced topic.

If you haven't started with htmldb, application express that is, then find a simple application and some time; install XE; create a schema owner; design the schema and include surrogate PKs populated by triggers as well as defaults, FKs etc; build the tables; create views for the LOVs you need and then create the LOVs; set PICK_DATE_FORMAT_MASK; setup UI Defaults; build an application using 1 level tabs and using "form on table with report" for all tables; well, you might want tabular forms for tables that resolve M-M relationships; read the Issue Tracking tutorial from the oracle website and try out on your new website anything that you find that looks appropriate, useful or interesting; research and fix anything else that needs fixing and add anything that needs adding; get some constructive feedback; determine what the design should have been; re-jig or re-start.

I bought Oracle HTML DB Handbook, because I needed to write an application in HTML DB and I didn't know the language. With this book and google I was able to create an application with forms, tables, collections, email with links, and the ability to upload and download files.

I asked the authors a question about one of the procedures and I received a response in less than 24 hours.

The book is well worth the money.

To compare APEX (formerly HTMLDB) to .NET is like comparing a ready-made-sandwich to a gourmet meal. One (APEX) is a web-page generator with extensions, the other (.NET) is a bona-fide development environment. To suggest otherwise is at best disingenuous. That said, HTMLDB has a niche. This is the first book available and it is essentially a rehash of the online documentation. It says a lot when the author posts his own review and gives it 5 stars... next..

This book is ok. I had to get it for a class. The writing is alittle hard to follow, but it is a good reference.

CD came damaged from xpresstext in which there is a large mark/scratch across the CD using priority shipping and after attempting to notify them and Amazon 4 times, no response until I contacted the BBB and Amazon will not help because I did complain to the BBB. Guess it is up to the BBB now.

Ok, my written english isn't good at all, but I'd just wanna say how much I love this book. I have been studying html and css for some time now, and I already knew something when I bought this book, and what I think great about it is that it's so detailed about how the things work in html, xhtml and css that it's like if I was learning everything from the beginning again, but this time knowing exactly what I was doing and why.

Well, that's it.. sorry for my english.

I purchased this book to use in a class I was taking. I had no prior knowledge of HTML, but this book does an excellent job of introducing the reader to designing web pages. I found the chapters very easy to follow and the exercises were kind of fun as you got to practice what you just read about. I highly recommend this to anyone wanting to learn HTML.

I've taught HTML and e-commerce at the university level for about a decade now. This book is the best I have found. I use it as my personal reference. I require it for my classes.

It covers the essentials. It gives clear examples. It is organized in a logical order that works. It can be used by someone who has never tried to build a web page, and also has enough 'meat' so that those who have been building pages for years can find useful information and tips throughout.

I just wish I could find books on some of my other subjects that are as well written and organized as this.

This book provides a great overview of XHTML, from its origins and relationship to HTML, to adjacent technologies designed to work in conjunction with it. You'll primarily learn (1) how to migrate legacy HTML markup and (2) how to write new XHTML from the ground up. This book does well to cite available software to help you with both the conversion as well as the creation of XHTML. Towards the end of the book, the authors go into application-specific XML vocabularies and technologies designed to transform or style XHTML.

Novices will do great with this approach, but experienced web developers already knowledgeable with XML technologies may find the coverage of XSLT, CSS, etc. redundant with their other readings and/or life experiences. I've been in web dev for 6 years, so I was able to stop reading after Chapter 5. Perhaps this book may be construed as too shallow for the experienced developer. Or, perhaps there really isn't much more to say about XHTML to justify a thicker book. I won't know personally until I read at least one other book on the subject.

If you are new to XHTML -- as well as XML technology in general -- this book is great way to learn about the related technologies quickly.

I got this as I felt that XHTML was going to help me in my job.

Now I'm hoping the knowledge I've found in this book will help me
GET a job.

It's a good way to help an HTML designer make the transition to XHTML, but a good XML reference may be in order!

You do need some knowledge of HTML(at least know how to do a CSS!)

This book has good explanations. If you are planning to migrate from HTML to XHTML this is a good choice. Other than migrating, this book offers great working examples in the provided CD. The book covers CSS with XHTML, Intoduction to XML technologies like XForms, Xlink, and XSL. So get this book to be ready for the future. Note : Some chapters are hard to understand. You might have to read again to understand it correctly.

What is XHTML? Is it just another trendy acronym for web developers to toss around? Is it the child of a marriage between Hypertext Markup Language (HTML) and Extensible Markup Language (XML)? Is it worth worrying about?

The authors of XHTML have chosen to answer in a variety of ways. This book takes several approaches to explaining XHTML. They range from a high-level view of "Where did XHTML come from?" to an attribute-by-attribute listing of valid XHTML syntax to an in-depth look at Cascading Style Sheets (CSS). There are also several chapters of "What's next?" topics, each touching on an aspect of internet development (multimedia, forms, graphics, and scripts).

So what is XHTML? It is the Extensible Hypertext Markup Language. It's brings order to chaotic world of HTML by forcing adherence to XML standards. It promises to separate presentation from information (data). It can force a web page to act like data, with the benefit that anything that can access data can use your web page (like text-to-speech devices, mobile devices, and more). It's a W3C standard that has progressed beyond the 1.0 specification referred to in this book (and this book was published in 2001!).

This book could have easily been called XHTML and CSS - because they devote many pages to the key role that CSS will play in the deployment of XHTML. CSS is the way that the presentation elements are extracted from the HTML document - leaving only the data behind.

The book mostly succeeds in bringing XHTML to a wide audience. It tries to be an introduction, migration guide, and language reference. I recommend it to anyone interested in taking their internet development to the next level.

Know your goals. If you expect to have mastered XHTML after this book, look elsewhere. As said by another reviewer all the details are not covered and one is referred to other sources, but it is a good place for beginners to start. You will have to visit online tutorials to complete this book and you'll still need to purchase a XHTML book that can be used as a reference.

The author's expertise provides one with an excellent historical section, but I personally found it to be more on the side of information overload.

XML related subjects are mentioned, but only seasoned HTML'ers will be able to comprehend the explanations, which I found too brief to really be enriching.

For those with some HTML experience there are better books out there and one should continue their search for another XHTML book. Beginners will be will served with this book.

I love this book, they are no longer printing this book, but if you can grab it, grab it! It's truly amazing. Love this book and it comes with a CD.

I suppose this book might be helpful as a reference, but to someone who is actually trying to figure out what to do with xslt and xpath, this book is a very poor primer. I found that, in addition to offering little explanation as to how xpath and xslt are needed in a larger context (is this supposed to supplant sql??, for example), the examples are so error-prone that I learned more by correcting the errors than I did reading the book. Here is a list of errors you will encounter (from the CD) for the first 3 chapters:

1.1 (string not quoted)
1.2 (only 1 top-level element allowed).
2.1 (invalid character)
2.4 (cannot locate resource)
2.5 (template.xml undeclared namespace)
2.7 (cannot locate resource)
3.2 (output.xml invalid at the top level)
3.3 ditto
3.4 worked -- hey, a working example!
3.5 (output.xml invalid at the top level)
3.6 misplaced period
3.7 invalid at top level
3.8 only 1 top level element allowed
3.9 invalid at the top level...

The rest of the chapter examples are similar to this one.
Without good examples, a programming book is almost worthless.

I've had this book on my shelf since publication. I had to dig it out last week to do some fairly complex XSLT programming. The book was a huge help and helped me get everything done quite quickly.

I use this book as a reference book, not a how-to. This book is great for things like "what is the function that does 'x' and what are its arguments?" It probably helps that I know XML pretty deeply, so I don't typically look at the examples. Of course, that might be because the docs on the functions in the book are so good that I find I don't need to look at the examples.

XSLT hasn't changed much since this book was published. If you deal with XSLT, and, by extension, XPATH, get this book for reference.

I would agree this is more of a reference for the seasoned XPath/XSLT programmer. I'm a intermediate java programmer with some decent background in xml. I haven't really been able to get that much from this book in the way of examples. It's very light on examples.

This feels like a book that had it's table of contents laid out, and then the content filled in as quickly as possible. Editing must have lasted about 3 days. With a more thorough editing process, and a bit more thought to the examples (the boulevard examples taumatized me so much, I nearly stopped driving), it may have been a very good book.

In some sections, the same paragraph is repeated verbatim 2 or even 3 times. Often in the chapter overview, and then on the next page in the first chapter section.

Possibly the book appeals to other learning styles better, but I've found it a tough slog. In fairness though, XSLT is a strange and difficult beast- I may be transferring some of my frustration on to the messenger!

However, in general, I find the examples are too repetive, causing them to blur together. And you find myself flipping back as many as 6 pages at times to find the xml code the description is talking about.

And there is a lack of technical illustrations to help with more difficult topics.

I would have appreciate larger examples from different domains to specific goals. The problem with a lot of the examples is the purposelessness of the examples.

XML in a Nutshell, and Michael Kay's XLST reference have provided me much more joy.

My last word of advice- follow the examples live. XSLT and XPath need practice, and lots of it.

You couldn't ask for better service and a product in better shape. Thanks for your service.

I started with a book called Java 2 from Scratch and did a lot of scratching of my head. I think it'll be a good book for me eventually, but not right now. I needed something better to get my feet wet. A co-worker lent me his copy of Coulthard and Farr's book and I spent an evening with it. Afterwards I went to Amazon and ordered it.

If you are an RPG programmer (I'm from the ILE RPG IV side) and want to begin learning JAVA, this is the book to start with. It does a good job contrasting RPG with JAVA to as to give a decent reference point. No other book does that and I found it to be most helpful. When I finished the book, I felt a lot better about the language but I need to go further with something else (Ivor Horton's book is probably going to be the something else).

I thought the chapter on the Java Onion was really well done and very informative. The chapter on Threads was completly over my head. I'll return to that topic at some future point. The OO chapter was good but I found Jennifer Hamilton's Object Orientation for the AS/400 Programmer does a better job explaining these concepts. Over all these guys did a real fine job.

By the way, I had the privelege of attending their Java seminar at the Fall Common conference in Baltimore and they really made the seminar enjoyable. You should catch one of there presentations some time. They're a good team and keep your attention. They do a good job.

The one beef I have is they left me hanging on page 418 with the MsgBox class. They say it would be simple to add the line of code to your program to use the class. Maybe I'm being stupid, but it wasn't simple for me. They should have at least shown you how to use it because I still haven't figured it out. Phil or George, are you reading this? Maybe someone can e-mail be and let me know. Aside from that irritation, I really liked the book and would recommmend it to any RPG programmer looking to start learning JAVA. A word of caution, it's not the end all. It's a start but you will defintely need to move to something meatier as a next step.

This is a pretty good book for RPGIV programmers wanting to migrate to Java. It compares all the functions of Java to RPGIV in a way that is very understanding to non-object-oriented programmers. It's a much better book than the past Java books i've read (which are intended for university students familiar with C++).

What this book does lack however are self-excercises. It's merely a good reference book to learning the basics of Java. The authors do a good job of explaining the necessary components. This book also lacks a lot of 'interactive programming' samples other books offer. There were hardly any 'GUI' programming to practice on your home PC...mostly command line tests they show you. It's not a bad book overall.

Many readers coming to this might like what is described about java. Very different from RPG. The biggest change is the intrinsic object oriented nature of java. If you use RPG 3, then this will certainly be the most distinctive part of the narrative. RPG 4 programmers will at least be familiar.

There are many neat features about java that you should note. Like the higher level data structures, Vector, HashSet, Hashtable etc. These have been thoroughly debugged, and can save you much time recoding. Another difference is a full widget system. RPG came of age when graphics meant character oriented tables. Speaking of characters, java comes with internationalisation. Whereas RPG shows its heritage from an ascii background.

Unsurprisingly, the book has an extensive section on connecting java to a database. Some readers will perk up at this. You can closely compare functionality with RPG. Here, the latter is probably still stronger. But the java designers at Sun have done a competent job with JDBC.

If you have RPG III or RPG/400 code or this same code that was converted to RPG IV, then this book gives you little to go on but an education in ILE programming techniques. I think that if you were a C or Java programmer trying to understand RPG IV, this book would probably be very helpful.

My impression is that RPG IV should have been called RPG-C. That would have been closer to what it seems it was intended for, RPG to attract C programmers. I think that if one had their applications designed and written in ILE RPG with service programs and proceedures, etc. then this book would be helpful in learning the java language.

If your programs are designed around RPG III, converted or not to RPG IV, plan on having to learn two languages as you attempt to understand Java.

This book 'talks' about VRML. However, it has very limited scope with regard to "real world" applications and it contains almost no code examples. Almost completely useless for programmers.

I have read parts of this book and from not knowing what VRML is all about, I now have a clear idea of what its uses will be and how it will help companies market their products on the internet. A very good read.

John Vacca's new edition of VRML Clearly Explained covers the full scope of VRML 2 and its applications in the realms of VR, Telemedicine, Combat training and simulation, Communication, Data visulization, Art and entertainment are all addresed. A well written book on an important topic.

A lot of money for a book on the back ground of VRML and 3D in general. Doesn't really cover programming in VRML, not even the basics. Only chapter I could find was on VRMLSCRIPT which looks okay but I use JavaScript. Most of the referances are outdated or not available anymore and the CDROM has very little content, mostly URL links to deleted sites. The only programming chapter uses a 3rd party front end language tool which can export to VRML, alas this isn't on the CDROM and is no longer available at the URL. About 60-80% of the book is about what you can use VRML and 3D on the web for, I have an imagination so I can figure most of that out. I guess it's back to the dozen or so downloaded refs that I already have, I really wanted a book I could site down with and get a better understanding of some of the concepts and programming techniques in VRML, this isn't it. (If I had been able to find it in a bookstore to look at first it would have been left there.)

We manufacture VR Systems and we must costantly keep ourselves abrest of what happens in all secors related to our field. All of our SW developers have avidly read the book and preize it as a valuable work tool. I must say that all books written by John Vacca are clear, straight to the point, well documented and can easily turn into reference material for professionals as well as non specialist that want to know about the subjects John Vacca decides to write about

Use this book once you have Pence's basic HTML book down. It will provide many new tools to spruce up your exist web programming.

It is a great hands on textbook. The author did a great job conveying concepts. Easy to understand especially talking about codes. However a lot of typing error and project data or instructional errors. Misspelled in a lot of places. Information inconsistency. Requires professional editing services. I think the author should continue to write these book. Pence is a good writer but need to make sure information, data or examples are consistent. It hinders the student when trying to do the projects.

This book teaches what it claims to teach. It teaches CSS 1 for everyday tasks you would perform. It also teaches you how to create entire layouts using CSS. I strongly recommend this book to those who have just learned HTML and want to go ahead. This book also gives overview of very basics of CSS 2.

The book is well structured and includes hints, tips and other similar helpful stuff along the way.

Of course reading a book does not really make you a master unless you think and work hard yourself as well. So if you know HTML then this shud be your next step.

This book covers basic CSS. It succeeds in offering a very gentle and fairly comprehensive overview of CSS1 features, with some CSS2. However, his constant warning about the lack of robust support for CSS in browsers is somewhat dated and tiring. The book is also full of annoying typos that at times prevent examples from working--a missing period here, a misplaced semi-colon there. Perhaps to make the chapters (called "Modules" here) independent, there is quite a bit of repetition of the same ideas in many chapters. The gradual introduction of CSS syntax and techniques also seems to incourage the author to use examples that mix CSS and traditional html in ways that are not good CSS practice, just apparantely oversimplified examples to make simple points about transitioning from HTML to specific CSS features. That distinction could be lost on a lot beginners who don't get a more solid understanding of how to use CSS to build more complete and consistent pages and websites. I therefore wish the author would have included more comprehensive examples, rather than lots of smaller out-of-context and disconnected ones. This book is not terrible. I just think you could probably do better now. I would give it 2 1/2 stars if I could.

I swear the author of this book goes out of his way to make its readers feel incompetent. While full of useful information, this book is also just as full of typos and inconsistancies.

Do you want to know how frustrating it is to try and re-create a page using the code given to you in a book, have the page come out looking nothing like the example in said book, then finding out the reason for the discrepency is because the author actually coded their example differently? Well there's plenty of opportunities in this book!

I now have to learn inline CSS which I believe might have been covered to some extent in this book. I can't remember. That's how badly I want to forget this book! I'm sticking with CSS for Dummies!

I'm an ASP developer with just over a year's experience. This is the first book I've read on XML, and if I have a question, it will be the first place I look.

This book has it all, except solid examples that tie it all together. I now understand how vast and capable XML is, but I haven't gained an ability to put it to any real practical use.

Items I don't agree with:
1. The book is not 500 pages ...Page 223 marks the start of Appendix A, the XML 1.0 specification. The index ends on page 345. 122 pages of reference (over 33%).
2. The book's cover states I will learn to build web applications fast. Huh? There are no sample applications, only examples of how to use the syntax being discussed.
3. The cover states that I will learn by doing, as I work on a fictional e-commerce site. Huh? There are no exercises, and there is no e-commerce site being built.
4. The cover refers to real-scenarios. Again, where are they?
5. A chapter titled, "Common Examples of XML", was really an introduction to SMIL, SVG, and WDDX. Good stuff, but not what I was expecting.

This book needs a companion to deliver all that's been promised. I still don't have a clear picture of the XML DOM, the difference between a node and an element, nor do I have an idea of where I should be using XML (instead of (or with) the technologies I'm already familiar with (i.e. ASP, ADO, and JavaScript)).

Considering how the other reviews have labeled this book #1, is there any hope? Can anyone recommend a book that's better at painting the big picture?

The book starts out nicely explaining everything and it gets you motivated. From chapter 3 onwards, 19 pages later, its all guess work. He gives pieces of information with no coherent example that shows how all these pieces fit together. Its left up to your imagination to guess how it all comes together. Once more, I had to go back to internet tutorials (which I have found to be way better than a lot of computer programming books). XML is not rocket science. If you can't write a descent book about it, you ought to think about quiting the writing profession (stick to writing code). This was a waste of my time and money; needless to say a waste of paper and ink too.

This book is a really good basic book to get started. I've enjoyed it.

Just skip all the others and buy this one. Really.

Could have been good or even great. It starts clear, correct, and well-structured. Then about a third of the way through the book (which is really half the content because the last third is an absolete printing of the XML spec) the writing gets lazy. Comprehending the material becomes an absolute chore as all structure is lost.

The first part is the best intro to XML that I've read, but it's just an intro.

For me the best part of this book was Appendix A, entitled "XML Language Basics". This should have been the first chapter in the book. But by the time I got to it, I was pretty fed up with reading about "emergent behavior" and other buzz phrases. I did get a bit of a sense of what various acronyms mean, such as SOAP, UDDI, WSDL, J2EE and so on, but the ratio of fluff to substance was too high for my taste.

There are about 230 pages of actual content that provide a high-level tour of what the author calls the "data revolution." There is a crisp and concise overview of the XML technology family, along with some examples of XML in use. There is broad yet concise description of SOAP and Web Services. Common implementations like .Net, J2EE and other vendor implementations are discussed along with some of the issues in the industry. XML Security is discussed in enough detail to give you a good grasp of the issues. The book wraps up with some ideas about where this technology could take us.

The best thing about this book is that it shows how XML and Web Services overcome many of the problems that plagued RPCs, DCOM, CORBA and RMI in a way understandable by anyone.

This book is a quick read, in the concise, bulleted, margin-annotated style of Object-oriented Technology: A Manager's Guide. There are lots of really excellent visuals. This book will not help you actually write code or implement Web Services -- it is good for a semi-technical reader, or a technical reader who wants a better grasp of the big picture. Highly recommended.

If one can't manage to complete a book in a week, then it is not a book. It is a reference that you occasionally use. XML, Web Services, and the Data Revolution by Frank P. Coyle definitely comes under my 'book' category. If one wants to learn what XML and Web Services are in a week, this is a book to read.

Lot of information yet concise presentation accomplished with self explanatory pictures depicting various XML technologies.

I bought this book based on the reviews and I made a mistake.
This book doesn't give the technical details I wanted.
If you are one of those bosses who doesn't get into details and just want to know the jargon so you can look technical when you are in meetings with more incompetent people, this is your book.

Mr. Coyle has done an excellent job in demystiying XML and Web Services. He describes the technical details in a fashion that makes it easy to understand, and comprehend on the first read. His visual examples help the reader see the network, and communication paths that takes place between XML, SOAP, and WSDL. I consider myself semi-technical, and I felt that I had a much better grasp of these concepts, and the possibilities of applying this technology after reading his book. Highly recommended.

The errors in this text annoyed me to the point of wanting to drop my course. I took this class online so it was difficult to get feedback from professor. The case studies were helpful, and despite it all I have learned a couple of things about web development.

Ive taken the online course of this class and while over all the book is very imformative, there are several HTML errors every now and then which for me really has no excuse as this is the 3rd edition. The author DOES correct these errors on a website she maintains, but as this is a text book for a subject that requires exacting work, it can be quite a hinder to the learning process when the students are forced to check the professors own work when the coding does not work for them even after following the example to the letter. I highly recomend this product none the less, but you may want to have a friend on hand to double check the text if you are experiencing a problem with no reason.

Web Development & Design Foundations With XHTML (3rd Edition)
I used this text for a college Web design class. The lessons were easy to follow and laid out in a logical sequence. The case studies that are built upon as new material is learned are useful. I appreciate the attention paid to accessibility issues. I do have two major complaints though. First: There are far too many errors for a third edition, as noted by others. A great deal of study time is wasted before a student realizes that the text is wrong. Coding solutions provided by the publisher in the "Student Data Files" don't always validate, for example, and there are several mistakes not yet updated in the "erata" sections on the publisher's web site. Second: the extensive "Hands On Exercises" at the end of each chapter are less than helpful at the college level without at least some sample solutions. College instructors don't usually waste time on going over this type of material, so it's often a waste of time doing them. Suggestions for the publisher: Fewer "Hands On" exercises, more solutions and please fix all those text errors you've been hearing so much about!

Great book! It was easy to learn to design web pages with XHTML and CSS using this book! There are lots of examples and practice exercises.

Comments from reviewers of this book:

"The layout of Felke-Morris's text is excellent. I have always
disliked texts with crowded pages, distracting sidebars, and many colors. Felke-Morris' text focuses the student on salient content and uses color, text boxes, and the like to enhance and emphasize, rather than distract. Felke-Morris' hands-on exercises are something my current text does not even have. I really like these exercises because they give students a chance to learn and practice small chunks of material before applying the knowledge to a larger project."

"Great coverage of web accessibility standards! Glad to see a tutorial on File Management. Many students coming into this course struggle with those
concepts."

"Great inclusion of ethical issues and accessibility tips (these are areas that I do find myself supplementing with our current text)."

"Superior aspects of Felke-Morris include:
--Inclusion of web site pages and/or addresses that have been referred
to in the text as either examples of techniques, or places to find more information, or used as a part of the end-of-chapter section on Web Research. These are a real strong point of the text.
--Use of the same four example sites through the text as end-of-chapter Cases. As each chapter is completed, each site is enhanced using the current chapter's skills and concepts.
--The inclusion of Hands-On Practice and Web Research sections."