my time is limited and not everything is still updated... nor the final link does exist, but here u can take a look @ current state. afte finishing it, we'll force update for 097 feature more often, so it is not such a big part to do it @ once...
after finishing update, we'll create a downloadable release too. and I'll update pathes so Pol095, Pol096 and Pol097 Doc resist @ same time.
here u can find the doc now (will get changed after updating): PolDoc 096 beta
Shinigami
p.s.: yes I know, Wiki... but there are a lot of people loving this init by Rac
PolDoc 096
-
Firedancer
- Grandmaster Poster
- Posts: 104
- Joined: Fri Feb 03, 2006 6:32 am
sure... if someone tells me how to combine the wget switches in the correct order... I can use it to get offline stuff, but it will not use uoem.php as name... it will use fulllist.php&name=uoem (or something like that)... Rac doesn't remember how he's created it and I'm to lazy to do it by hand
Shinigami
Shinigami
-
Marilla
Actually the method of creating the downloadable version is pretty much included in the online version; You can create the page per module, as is in the DL version, and then just modify the index page from the 095 docs. I already did that myself to create a local copy of the 096 docs that works just like the 095 ones did.
Shini,
In the ListMobilesNearLocationEx lookup need to include the LISTEX_FLAG_CONCEALED flag in the list.
In the ListMobilesNearLocationEx lookup need to include the LISTEX_FLAG_CONCEALED flag in the list.
Fixed.Yukiko wrote:In the ListMobilesNearLocationEx lookup need to include the LISTEX_FLAG_CONCEALED flag in the list.
-
Marilla
Yeah, what Itec said! I had to modify the docs on my system when I downloaded them due to this, since I use Firefox.
Basically, inside the href attribute of the anchor tag, the # is a special character that tells the browser that it needs to go to an element with the name that follows; In the href attribute, that first # is not actually part of the name.
That means, if you name the target element with a #, the standard behavior (which IE does not follow, as is far too frequent, unfortunately) is that this WOULD be considered part of the name.
So, the standard behavior (which all browsers but IE follow) is that if you have an element named, say, "#config", in order to link to it, you would need an href attribute with the value "##config"... since the first # would be taken as the special character telling the browser not to simply go to the URL "config", but instead, to go to the element named with what's ever after the first # sign.
That means, for an href attribute with the value "#config" to work, the target element must be named "config". IE improperly 'guesses' what you mean by having an element named "#config", but this could cause problems if you ever actually did have an element named with a # in front of it (which probably is not a good idea, but could happen in situations where element names were dynamically generated by a server-side script).
Finally, by improperly adding the # to the front of the target elements' names, only Internet Explorer can go to those links.
Erm... now that I've said far too much.. heh
Basically, inside the href attribute of the anchor tag, the # is a special character that tells the browser that it needs to go to an element with the name that follows; In the href attribute, that first # is not actually part of the name.
That means, if you name the target element with a #, the standard behavior (which IE does not follow, as is far too frequent, unfortunately) is that this WOULD be considered part of the name.
So, the standard behavior (which all browsers but IE follow) is that if you have an element named, say, "#config", in order to link to it, you would need an href attribute with the value "##config"... since the first # would be taken as the special character telling the browser not to simply go to the URL "config", but instead, to go to the element named with what's ever after the first # sign.
That means, for an href attribute with the value "#config" to work, the target element must be named "config". IE improperly 'guesses' what you mean by having an element named "#config", but this could cause problems if you ever actually did have an element named with a # in front of it (which probably is not a good idea, but could happen in situations where element names were dynamically generated by a server-side script).
Finally, by improperly adding the # to the front of the target elements' names, only Internet Explorer can go to those links.
Erm... now that I've said far too much.. heh
change your bookmarks to http://docs.polserver.com