Chapter 5 Function Demonstration
5.5 Website Manager
Our framework supports a user guide of Web 2.0 Toolbar and a manage system for Website Developers. This user guide is a web page, which supports a download point of Web 2.0 Toolbar program and a using example to tech users how to use the Web 2.0 Toolbar, which shows as Figure 5-9. The manage system allows these Website Developers to manage the information which related to their websites.
Website Developers can add/modify/delete tags and comments for their web pages.
Figure 5-10 shows the manage web page of Website Manger.
Figure 5-9: Web 2.0 Toolbar User Guide
Figure 5-10: Website Manager for Website Developer
Chapter 6
corresponding to the web page and subscribing/publishing RSS feeds to original websites. All of the four services are the most common and useful ways to getshare and discuss information in Web 2.0. Second, the Toolbar framework displays a friendly interface which integrates original web content and the related information (tagscomments) and services (chat roomRSS) closely, So that the users will not feel disharmonious. Finally, the Toolbar framework provides a flexibility interface to expand more and more services of Web 2.0.Although our Toolbar framework presents well results, however, it still has some limitations and a big difficulty to conquer. For one thing, our system can work well on almost all the traditional Web 1.0 websites. Even though it can be used on the greater part of Web 2.0 websites, it will be liable to error (parts of Javascript code may conflict). But the existing Web 2.0 websites are not the goals which our system focuses on, and they are out of our consideration. Overall, the targets which are
Over and above, we should face a serious problem which is the bandwidth problem on the Web 2.0 Management in the future. Although the problem is very important and difficult to solve, there are much experience of other large-scale websites which we can refer to. [30], [31], [32]
6.2 Future Works
The thesis has already presented a feasibility framework to upgrade websites from Web 1.0 to Web 2.0. The further directions of this study will be separated to four parts. First, besides IE, there is still 24.74% usage market share on the other browsers.
Ex: Firefox has 17.28%Safari has 5.73%. They occupy almost one quarter usage market, so we can consider porting the Toolbar framework to them. Using the framework to make Web 2.0 Firefox Toolbar or Web 2.0 Safari Toolbar is possible and even to the other browsers. Second, we can enhance the four existent services.
For examples, there will support an AI or Data Mining [27], [28] mechanism to help users to automatic tagging. Supplying sounds or pictures in chat room or allowing users to make private chat room, and then users will feel more convenient. Support RSS auto-discovery or cooperate with Ponyfish [29]. Third, we can gather statistics of tags and comments. Count the numbers of tags/comments which a user made. We can make a chart to encourage users to make more tags/comments. Count the numbers of tags/comments related to a web page. We can conjecture that whether the information of a web page is worthy or not. Fourth direction is that we can use our system in special-purpose service. For examples, moviefood and education. Only allow the professionals to make tags and comments. This way will let the information more meaningful. Consequently, final direction is that we can find more and more practice Web 2.0 services and enrich the functions of the Toolbar framework. In the course of
time, all the needs of these Web 1.0 website developers can be satisfied with the Toolbar framework.
Chapter 7 Reference
[1] Tim O’Reilly, “What is Web 2.0”, Sept. 2005,
http://www.oreillynet.com/pub/a/oreilly/tim/news/2005/09/30/
what-is-web-20.html
[2] Anderson. Chris , The Long Tail: Why the Future of Business Is Selling Less of More, Hyperion, 2006.
[3] WIKIPEDIA, http://www.wikipedia.org/
[4] del.icio.us, http://del.icio.us/
[5] Market Share Survey BY NET APPLICATIONS,
http://marketshare.hitslink.com/report.aspx?qprid=0
[6] Odeo, http://odeo.com/
[7] YouTube, http://tw.youtube.com/
[8] Susanne Boll, MultiTube-Where Multimediaand Web 2.0 Could Meet, Multimedia IEEE, Vol.14, No.1, 2007, pp. 9-13.
[9] Banff, Alberta, Canada, The two cultures: mashing up web 2.0 and the semantic web, Proceedings of the 16th international conference on World Wide Web, SESSION: Semantic web and web 2.0, 2007, pp. 825-834.
[10] Becky Gibson, Enabling an Accessible Web 2.0, International Cross-Disciplinary Conference on Web Accessibility, 2007.
[11] Michael Cooper, Accessibility of Emerging Rich Web Technologies: Web 2.0 and the Semantic Web, International Cross-Disciplinary Conference on Web
Accessibility, 2007.
[12] Mary Zajicek, Web 2.0: Hype or Happiness?, International Cross-Disciplinary Conference on Web Accessibility, 2007.
[13] Jesse James Garrett, “Ajax: A New Approach to Web Applications,” Feb.
2005,
http://www.adaptivepath.com/publications/essays/archives/000385.php
[14] Anne van Kesteren, “The XMLHttpRequest Object”, April. 2007, http://www.w3.org/TR/XMLHttpRequest/
[15] Mark Pilgrim, “The Myth of RSS compatibility”, Feb 2004,
http://diveintomark.org/archives/2004/02/04/incompatible-rss
[16] Google Toolbar, http://toolbar.google.com/T4/index.html
[17] Yahoo Toolbar, http://uk.toolbar.yahoo.com/
[18] Chi-Yang Tsai, Shyan-Ming Yuan. “Web Page Tailoring Tool for Mobile”, master’s thesis, Dept. Computer Science and Eng., Chiao Tung Inst., 2006.
[19] Gabbly, http://gabbly.com/
[20] Ming-Chih Hsieh et al., Web 2.0 Proxy: A New Framework for Web 2.0 Web site Development, Proceedings of the 7th WSEAS international conference on Telecommunications and Informatics, 2008.
[21] Hypertext Transfer Protocol,
[23] MySQL, http://www.mysql.com/
[24] Apache Tomcat, http://tomcat.apache.org/
[25] DWR, http://getahead.org/dwr/
[26] ROME: An open source to process RSS and Atom, https://rome.dev.java.net/
[27] Steels. L, and Kaplan. F, Situated Grounded Word Semantics, Proceedings of the Sixteenth international Joint Conference on Artificial intelligence. T.
Dean, Ed. Morgan Kaufmann Publishers, San Francisco, CA, 862-867.
[28] Sheung-On Choy, Lui A.K, Web Information Retrieval in Collaborative Tagging Systems, Web Intelligence, 2006. WI 2006. IEEE/WIC/ACM International Conference, Dec. 2006 pp 352-355.
[29] Ponyfish, http://www.ponyfish.com/
[30] Williamlong, “ 0< / ”, Jan. 2005, http://www.williamlong.info/archives/776.html
[31] Tong Sau Loon and Vaduvur Bharghavan, Alleviating the Latency and Bandwidth problems in WWW Browsing, Proceedings of the USENIX Symposium on Internet Technologies and Systems, December 1997. pp 20-20.
[32] Herbert J. Carlin, A new Approach to gain-bandwidth problems, Proceedings of Circuits and System, IEEE Transactions, 2003. Vol. 24, pp 170-175.
Appendix
A.1 Toolbar Controller
In this section, we show the main source code of building an IE Toolbar with four buttons and calling the Web 2.0 viewer to execute the Javascript code.
The function onCreate displays how to build four buttons on IE toolbar.
LRESULT CMFToolbar::OnCreate(UINT uMsg, WPARAM wParam, LPARAM lParam, BOOL& bHandled)
{
// buttons with images and text
SendMessage(m_hWnd, TB_SETEXTENDEDSTYLE, 0, (LPARAM)TBSTYLE_EX_DRAWDDARROWS);
// Sets the size of the TBBUTTON structure.
SendMessage(m_hWnd, TB_BUTTONSTRUCTSIZE, sizeof(TBBUTTON), 0);
// Set the maximum number of text rows and bitmap size.
SendMessage(m_hWnd, TB_SETMAXTEXTROWS, 1, 0L);
// add our button's caption to the toolbar window TCHAR* pCaption = _T("");
int iIndex = ::SendMessage(m_hWnd, TB_ADDSTRING, 0,(LPARAM)pCaption);
// load our button's icon and create the image list to house it.
HICON hMotley = LoadIcon(_Module.GetResourceInstance(), MAKEINTRESOURCE(IDI_TAG));
m_hImageList = ImageList_Create(14,16, ILC_COLOR16, 2, 0);
int iImageIndex = ImageList_AddIcon(m_hImageList, hMotley);
DestroyIcon(hMotley);
// Set the toolbar's image
::SendMessage(m_hWnd, TB_SETIMAGELIST, 0, (LPARAM)m_hImageList);
// add the button for the toolbar to the window TBBUTTON Button;
ZeroMemory((void*)&Button, sizeof(TBBUTTON));
Button.idCommand = IDM_TAG;
Button.fsState = TBSTATE_ENABLED;
Button.fsStyle = TBSTYLE_BUTTON | TBSTYLE_AUTOSIZE;
Button.dwData = 0;
Button.iString = iIndex;
Button.iBitmap = 0;
TCHAR* pCaption_2 = _T("");
int iIndex_2 = ::SendMessage(m_hWnd, TB_ADDSTRING, 0,(LPARAM)pCaption_2);
HICON hMotley_2 = LoadIcon(_Module.GetResourceInstance(), MAKEINTRESOURCE(IDI_Comment));
int iImageIndex_2 = ImageList_AddIcon(m_hImageList, hMotley_2);
DestroyIcon(hMotley_2);
// Set the toolbar's image
::SendMessage(m_hWnd, TB_SETIMAGELIST, 0, (LPARAM)m_hImageList);
TBBUTTON Button_2;
ZeroMemory((void*)&Button_2, sizeof(TBBUTTON));
Button_2.idCommand = IDM_COMMENT;
Button_2.fsState = TBSTATE_ENABLED;
Button_2.fsStyle = TBSTYLE_BUTTON | TBSTYLE_AUTOSIZE;
Button_2.dwData = 0;
Button_2.iString = iIndex_2;
Button_2.iBitmap = 1;
::SendMessage(m_hWnd, TB_INSERTBUTTON, 1, (LPARAM)&Button_2);
TCHAR* pCaption_3 = _T("");
int iIndex_3 = ::SendMessage(m_hWnd, TB_ADDSTRING, 0,(LPARAM)pCaption_3);
HICON hMotley_3 = LoadIcon(_Module.GetResourceInstance(), MAKEINTRESOURCE(IDI_MOTLEY));
int iImageIndex_3 = ImageList_AddIcon(m_hImageList, hMotley_3);
DestroyIcon(hMotley_3);
// Set the toolbar's image
::SendMessage(m_hWnd, TB_SETIMAGELIST, 0, (LPARAM)m_hImageList);
TBBUTTON Button_3;
ZeroMemory((void*)&Button_3, sizeof(TBBUTTON));
Button_3.idCommand = IDM_CHAT;
Button_3.fsState = TBSTATE_ENABLED;
Button_3.fsStyle = TBSTYLE_BUTTON | TBSTYLE_AUTOSIZE;
Button_3.dwData = 0;
Button_3.iString = iIndex_3;
Button_3.iBitmap = 2;
::SendMessage(m_hWnd, TB_INSERTBUTTON, 2, (LPARAM)&Button_3);
TCHAR* pCaption_4 = _T("");
int iIndex_4 = ::SendMessage(m_hWnd, TB_ADDSTRING, 0,(LPARAM)pCaption_4);
HICON hMotley_4 = LoadIcon(_Module.GetResourceInstance(), MAKEINTRESOURCE(IDI_RSS));
int iImageIndex_4 = ImageList_AddIcon(m_hImageList, hMotley_4);
DestroyIcon(hMotley_4);
// Set the toolbar's image
::SendMessage(m_hWnd, TB_SETIMAGELIST, 0, (LPARAM)m_hImageList);
The function Comment displays how to execute some Javascript code in IE when clicking the comment button.
TBBUTTON Button_4;
ZeroMemory((void*)&Button_4, sizeof(TBBUTTON));
Button_4.idCommand = IDM_RSS;
Button_4.fsState = TBSTATE_ENABLED;
Button_4.fsStyle = TBSTYLE_BUTTON | TBSTYLE_AUTOSIZE;
Button_4.dwData = 0;
Button_4.iString = iIndex_4;
Button_4.iBitmap = 3;
::SendMessage(m_hWnd, TB_INSERTBUTTON, 3, (LPARAM)&Button_4);
//::SendMessage(m_hWnd, TB_INSERTBUTTON, 0, (LPARAM)&m_com_button);
A.2 Web 2.0 viewer
In this section, we show the main Javascript source code of how to append the JSP file into the web page which IE is processing.
Toolkit.prototype.initialize = function()
// flag used to check whether webpage configurations have changed or not
this.tk_modified = false;
// use Effect.Appear() to let it appear later this.tk_window.style.display = "none";
// append toolkit window to <body>
document.getElementsByTagName("body")[0].appendChild(this.tk_w indow);
this._stylize();
}