While the old documentation was hard to navigate, because it couldn't decide if it was a demo or a tutorial or API documentation, and didn't have any kind of index, table of contents, it was vastly more usable than the current documentation.
The tutorial material in the old docs seems to have fallen between the cracks, and now there is nothing to tell us how to initially set-up a JQM project (save for very basic CSS/JS loading setup on the "download" page) nor anything that explains basic principles, such as the page navigation model.
As a practical matter, you will need to refer to the 1.2 documentation if you are just starting out:
In particular, the "Pages and Dialogs" section, which contains a great deal of tutorial/intro material seems missing.
Update: the tutorial material is there, but not very accessible. You will need to click around on links in the Introduction section of the new demos, and guess which ones might be important to read. Alas, there still is not a real separation between demo and documentation, except that there is now a separate API documentation. They've "improved" the tutorial material by burying it behind inline links, where at least before it was nicely organized in a menu.
Basic getting-started info (like what to put in <head> to link to CSS and JS) can be found by going to the Introduction, scroll down to "Pages & Dialogs", then click on the "page" link in the first paragraph of that section.
Not sure what has become of the "old format" docs for 1.3.
IMO, both of the new documents hurt my eyes. It's why I'm wearing sunglasses. ;)
(It's not quite so bad on a Retina device like iPad. On most desktop displays, the font is way too thin and hard to read.)
You are right!!! I went to look at my bookmark for documents and it isn't the page anymore. The new so called website it's unreadable at all. Just a big mess of info graphic styles and colour that eeven my 4 years old daughter never mixed together...If this is a framework visit card they lost a lot of visitors like I cannot visit again the dojokit website...When developers wanna be graphic designer, engineer and todo that's the result...
I don't want to sound ungrateful for the work that went into 1.3, redesigning docs & API site; but I must say that I cannot read the news docs site: gray font on light background ... I hardly see what's on the screen.
Another ISSUE! In no place is described if theme created with themeroller using the 1.3.0 RC1 are compatible with 1.3.0 or what? Such a pity! Why rush to declare something final when there's such a lack of information...
In no place is described if theme created with themeroller using the 1.3.0 RC1 are compatible with 1.3.0 or what?
It should be, assuming they are using standard industry practice and terminology.
A "release candidate" is just that - a candidate for release. If it passes some level of testing (determined by the developer) then that release candidate becomes the release. It should just be re-labelled, with no other changes.
If there were some changes since RC1, there should have been an RC2.
I've been in hermit-dev mode for the last 2 weeks or so with JQM 1.3.0-rc.1 to try and push out my social-math app, and am loving everything about JQM.
However, I hate to say this, especially considering all the hard work they've obviously been putting in, but the new docs are horrendous. I don't have very good vision, and the 1/4 pixel-thin font is very hard on my eyes, especially the smaller font.
In fact, it makes me want to vomit - and I don't mean that as an insult, it's a result of the amount of effort and combined focus I have to use to read the text. I already have binocular thick glasses lol The paragraph text is fine.
I do dig the widget reference and search feature though.
Leave a comment on omgcarlos's reply
Change topic type
Link this topic
Provide the permalink of a topic that is related to this topic