Hello All,
I posted this message yesterday but it seems to have disappeared - perhaps because I was critical of Dojo documentation?
Anyway, I have been playing around with Dojo for a day or two. I like its minimalist philosophy and the way it does things though the documentation I find drives me nuts. Nevertheless I have persevered and with some help from the source code have got a good handle on things.
Not unnaturally, I started off by looking at ways to create a screen layout akin to a true executable app using dojo.layout components. To my surprise I found that I could only make things work - particularly in IE - if I did not provide any DOCTYPE declaration at all.
Does this mean that Dojo works by throwing all standards compliance notions out of the window? Does it not mean that at some date in the future one or more browsers will use different defaults in the absence of an explicit DOCTYPE that could cause the whole Dojo edifice to come crashing down on its ears?
It would be nice to have some views - and some idea as to why my original posting was removed. Touchy development team perhaps?
no.
With regard to "disapproved" messages, there is no such thing. Drupal occasionally whitescreen's when posting, in which case your post is lost forever, but that is far from intentional. This is an unmoderated forum outside of edits to provide proper brackets around code samples (so they are readable) and occasionally delete an automated spam post. Not touchy at all: Glad to help, though drupal makes it difficult on occasion.
With regard to doctypes: All of the layout tests in dijit have a 4.01 HTML Strict doctype, none should be without one. The themeTester has a quirks-mode and standard test, and all appear to work. There must be something else going on breaking the flow, as I continually create valid HTML pages using Dojo (sans dojoType, etc).
Regarding docs: it's a never ending battle. Anyone willing to assist with doc writing, tutorial making, or otherwise noting holes in the dojo docs should get in touch with someone in #dojo, or one of the DojoCampus.org folks and offer assistance. Writing accurate documentation is harder than writing good code, and while we've bettered Dojo's doc offerings immensely since 0.4, it is still admittedly lacking. Every bit helps, so if you'd like to contribute ...
Regards,
Peter Higgins
Only works with no DOCTYPE
Hi,
I've had the same experience: if I add a DOCTYPE like
than it appeared that nothing happened. I use a SplitContainer with width and height 100%. I fixed it using this css style:
html {
width:100%; height: 100%;
}
Cheers,
Daco
Thanks. I wonder if you
Thanks. I wonder if you could clarify the sans dojoType comment. Surely, without a dojoType attribute how would dojo know what to do with the div?
Docs - I really like dojo. There is a fair chance I am going to contribute to the doc writing effort. Just give me some more time to get my bearings.
The dojoType only helps the
The dojoType only helps the dojo.parser, which is an additive feature of Dojo. You can use dojo / dijit progressively, and with valid markup, though is not as easy or convenient.
So the parsed version of:
can be achieved by the combination of:
and in code:
new dijit.TitlePane({ title:"baz" }, "foobar");
});
The string "foobar" is an id lookup. If null, a div will be created and used. you can append that node wherever you want, if you don't already have dom to turn into the widget:
dojo.body().appendChild(d.domNode);
Hope this helps.
Thanks!
Thanks!
DOCTYPE Crashes IE 7.0
I'm getting an immediate javascript error (invalid argument) when using the default DOCTYPE provided in Visual Studio HTML pages:
DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"
(intentionally left out the opening bracket-bang and closing bracket)
IMO, this sort of thing should be front-and-center in the install guide because it really lowers one's confidence when a simple example crashes with no explanation. I'll give you another one: selecting a closeable tab in nihilo is totally malformed. That shakes your confidence in the claims the toolkit makes for cross-platform testing and drop-in themes.
OK, so now I'm over the hump and but still feeling a little queasy about betting the farm on this toolikit. Hopefull things go more smoothly going forward.
Bug reports are always welcome.
One thing to keep in mind is that the majority of our community does not develop with Visual Studio; most are very big on Open Source and because of that MS products can sometimes go by the wayside.
(Also, many of us "hard-core" contributors tend to use tools like VIM and emacs; some develop using an IDE but in general the tool of choice is Eclipse.)
That's not to say that we don't want to support it; on the contrary. But sometimes the tools used dictates the approach taken.
If you'd like to file a bug, use the same credentials you use to log in here and create a ticket at http://bugs.dojotoolkit.org . Mercy buckets!
I should mention...
...that reports without reproducible test cases tend to go by the wayside; so when you file it, make sure you detail the steps to reproduce--tools used, browser, a code sample, etc.