| Continuing CCIT Posted by: Jordan in SQL, PHP, Joomla, AJAX on May 28, 2008 |
Most of the components discussed earlier in my Creating CCIT have been created and I'm now just working on the cosmetics. I'll list here what still needs to be done, as much for my reference as yours:
- Wiki BB code needs to be parsed in JavaScript. You can notice some of the odd characters above like ''' or [[ ]]. The ''' are bold while the [[ ]] is an internal Wiki link. I cannot parse these in the PHP file because HTML characters such as < and > break XML.
- Currently the "word" isn't being passed to the popup text. This makes it impossible for me to link to the word from the bottom link "Read More".
- I'm considering using an iFrame for the text and another external PHP processor to display the full wiki page in a slim, mobile like window.
- Add onMouseOut event that actually fades the pop-up out after so many seconds.
- Some words can't be added to our Wiki such as "C#" or "C++". The wiki doesn't like the "#" and "++" symbols. Instead the words are added as "CSharp" and "CPP". This causes problems when trying to add a popup link to C++ and C# words. I have to convert them in an array upon submission to the PHP script and then deconvert them once they have been received by the JavaScript. This makes the code messy and I am either going to fix the Wiki to allow these words or remove those words as pop-up text words.
- Remove all HTML tags and "< >" symbols before sending back to the JavaScript. This causes issues and currently an issue can be seen with the C++ word on the test site. These symbols prevent the JavaScript from working correctly.
- Fix the Wiki page itself. Currently it is being loaded by a component in Joomla! and placed inside of a wrapper. When a link is clicked the URL remains the same but the wrapper navigates to the new location. I intend on removing the wrapper and using static URLs for every content item. This will also help with SEO. This may also require a rewrite of the Joomla! component or making the Wiki a stand alone application using the current CodeCall theme.
- Content.... We have no content in the Wiki which makes it hard for CCIT to actually show any text links. John, v0id and I have been talking about parse wikipedia for all programming related terms and extracting their Wiki into ours. wikipedia is currently under the GNU license and provides XML dumps of all their data for this use.
- Testing the widget out on CodeCall. I believe I'll start using it in the blog section only and then slowly progress to the forum. Once most of the bugs are worked out I'll write a tutorial on how other webmasters can include the widget on their website.
Some of what I said above is a bit wordy but won't actually take that long to fix. The biggest problem I forsee is the content problem.
TrackBack URI for this entry
