Closed
Bug 190408
Opened 22 years ago
Closed 8 years ago
Tracking bug for obstacles to learning revealed by ISBN 0131423436
Categories
(Core Graveyard :: Tracking, defect)
Core Graveyard
Tracking
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: nrm, Assigned: nrm)
References
Details
(Keywords: meta)
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130 NRM tracking bug for defects revealed by book work Reproducible: Always Steps to Reproduce:
Assignee | ||
Comment 3•22 years ago
|
||
Could you please assign to nrm@kingtide.com.au? I have a set of bugs that span the whole Mozilla platform and need a tracking bug to manage them. If there is a better Product/Component combination for such a bug, please advise. I'm working on Mozilla documentation but have both doc. and tech. issues to work on (see bug 190406 deps).
Comment 4•22 years ago
|
||
Over to tracking and to Nigel
Assignee: asa → nrm
Status: UNCONFIRMED → NEW
Component: Browser-General → Tracking
Ever confirmed: true
Updated•21 years ago
|
QA Contact: asa
Assignee | ||
Comment 5•21 years ago
|
||
This bug is for reader feedback due to the book "Rapid Application Development with Mozilla". This bug is designed to collect remarks about Mozilla that will help make future Mozilla versions easier to learn. If you find the book accurate and useable, but also find that Mozilla is challenging to work with, then put your specific concerns here. Better still, log your own bug and make it "block" this one. If you find that the book itself has problems, see instead bug 190407
Summary: Tracking bug for platform issues revealed by Mozilla book → Tracking bug for obstacles to learning revealed by ISBN 0131423436
I have found troubles testing the code for templates. In particular, I haven't been able to make your Listing 14.1 work. Here are some issues/suggestions: 1. It would be nice if this listing and the corresponding test RDF file were available on line for us to run. 2. For debugging, it's very hard for me to tell what's gone wrong when I see no instances of the template. I have looked at the DOM inspector and the template is there, but the data hasn't gotten into it to make instances. There's no obvious way to find out WHY/HOW this is failing. Does Mozilla print any diagnostic information if it's unable to find the datasource file? What about if it's unable to find the root object in the ref attribute? 3. It's not obvious how the datasources attribute works. In the example, this is just a naked basename, and I couldn't determine how this basename was going to be interpreted. Presumably there's some default directory name, but what would that be. When I attempted to supply a full file URL, it didn't seem to help. 4. It's also not obvious how the datasources might interact with the Mozilla security model. Must all file-reading templates be installed in chrome in order to open files?
Assignee | ||
Comment 7•20 years ago
|
||
thanks for your feedback on the Mozilla book. Did you see the current errata at www.nigelmcfarlane.com? It points out an error in Listing 14.2 and the code is now available for download. I'd love to hear how that gose for you. Note: I'm going to update the errata in more detail soon. I'm working on your general concerns, but some answers are: 2. "no and no". 3. the default directory is the same as the directory the chrome file is in, but also see the Errata again. 4. No. They can be on a remote website. But that's not covered until later. more as it arrives. - N.
Comment 8•20 years ago
|
||
For me as a beginning XPCOM developer, it was very annoying not to find the ominous netscape.security.PrivilegeManager.enablePrivilege("UniversalXPConnect") at a prominent place in the book. Luckily this question is often asked on the usenet, so it was not that hard to find - but still, I feel it should be mentioned where it's easy to find.
Assignee | ||
Comment 9•20 years ago
|
||
Now on the list of things to do ...
Comment 10•8 years ago
|
||
Marking all tracking bugs which haven't been updated since 2014 as INCOMPLETE. If this bug is still relevant, please reopen it and move it into a bugzilla component related to the work being tracked. The Core: Tracking component will no longer be used.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•