Dynamic Widget Guide. Options

[CSM]

Dynamic Widget Guide
(for beginners)

Let me start by saying that I LOVE WordPerfect. (Word Sucks!)

I created a "small" guide on simple dynamic widget elements.
If I get feed back I can add, delete, change or update items in the guide.

The following zip file should contain contains 5 files:

• Dynamic Widgets.pdf (Created by WordPerfect, Has Links, Bookmarks)*
• Dynamic Widgets.wpd (Original Document, in WordPerfect format) [Maybe...]
• JSTemplate.kon (My template file done all dynamically)

All the files except the .kon file should be the same (minus conversion errors). I provide them for compatibility or preference.
The guide maybe/will be a bore for experienced users. It covers how to create dynamic objects and sometimes goes over items at their most basic level. The projects become more complicated as the guide progresses.
All the displayed code was tested, and should work. Post here if it is unclear or doesn't work.

Please do not edit this guide in any way. Post things you would like to see fixed/added/changed, here instead.
Download Here




* I love WordPerfect because it allowed me to set bookmarks, or hyperlinks with in the document.
I first tried to export it to Word. I lost all of my links, but their blue color remained (bad). Also, I lost font data.
Then I tried to export it with PDFCreator (a printer driver), and that also got rid of all my links, keeping their blue color. The resultant file was 10.8 MBs after about 30 seconds of conversion!
WordPerfect on the other hand, exported the file in less than 5 seconds! And it kept all of my links and bookmarks. The final kicker is that the file is only 692 KBs!

[CSM]

Accidentally "buried" my own post.

[CSM]

Any ideas?

Not even a "Very Poor Job"? or "It sucks!"?

(I wouldn't be surprised at either, I'm not the best programmer in the world. There are many on this forum who are more qualified than me to write this...)

[AndrewPlusPlus]

I haven't had a chance to go through the entire guide, but I can tell a good amount of work went into this.

For me, I already have a good programming background (in C++, but not Javascript).
The programming aspects aren't new at all, but I can see the guide will be quite useful for pairing up programming techniques with Y!WE's capabilities/functions.

I'll let you know if there are any typos (I worked for a newspaper for a while) or errors.

Good job!

[CSM]

g6auc beat you to finding the spelling errors and help improve the code. I will reissue it today with the updates.

It would be helpful if you looked at that copy. I had a lot of errors. Not as many with the code. Those updates were partly functionality and aesthetic as well.

Let me know if anything needs to be added.

[CSM]

• Oh yea, I fixed a few things that aren't as clear and plus a few things that I noticed were wrong, like grammar (and to think that English is my native language ) and a few inconsistent declaratory things with i. (if you see I versus i, let me know. Since I used Word Perfect, it wanted to capitalize i to I.)
• I also only have two versions now. The PDF and the original document. No Word files. If you open the .WPD in Word, it will convert it (if you have version 2003 and above, I think.)
• Also, if the font looks a little fuzzy, it is because to avoid a font imbedding error, I had all the text exported as curves. Sorry. It was that or not be able to open the document.
• If it would be easier, I can add the pictures used in the examples in the zip file. Any thoughts?

I just uploaded the newest version.

[bjbk]

assuming i got the newest version just now, you spelt angle wrong on page 22

[CSM]

Wow. You are correct. The spell checker was hanging up on the code, so I pressed skip a bunch of times.

If I could define "No Spellcheck/Grammar and No QuickCorrect" areas that would be great. The I could check the document without hanging up on the code.

I uploaded a "new" version, fixing that spelling error as well as fixing a line defining scope (on the same page) to be more clear.

[CSM]

No new version, I just wanted to bring it up to the top for new users to see again.

[CSM]

After <how many?> weeks, no one has anything that is missing or to add?
There has to be something. I'm not even the most qualified guy to write this guide.

Bummer.

[g6auc]

After <how many?> weeks, no one has anything that is missing or to add?

<how many?> = 1
no one = {AndrewPlusPlus, bjbk, g6auc}
More comment in time - have patience.

[CSM]

Ok,ok... I will. Sorry.

[Owen]

"That" is miss spelled P. 14. it is spelled "tat"

[CSM]

Dang.

[Owen]

haha no worries. If my life depended on spelling, I would have been dead before i was born.

[CSM]

Firefox, checks my spelling, and wow, you should see the amount errors before I fix them.

Anyways, I uploaded a new version*. I fixed "tat" in 2 places. If I spell it wrong once, I've done it elsewhere.

Thanks.

*Same link as above

[Owen]

Great thanks. i have the FF spell checker as well, it's a life saver!

for those of you who do not have it, pick it up here, you won't regret it.

https://addons.mozilla.org/firefox/3497/

[Galewind]

FF2 has spell check built in, you don't need to install anything else.

[Owen]

sweet! i'll have to update.

[SWS]

Thanks for putting this together. This type of information is certainly helpful - the YWE "manual" only goes so far and often assumes a lot of knowledge. Other non-YWE web sources also usually have enough different subtleties in syntax or implementation that they further confuse. That frickin DOM & XPath is a good example (tackle that next will ya). It is too bad the wiki type approach to documentation hasn't seemed to go anywhere. Sure would beat the PDF and allow for more examples, etc.