Revision history for WishListFor117
Revision [23385]
Last edited on 2016-05-20 07:38:47 by ScouBidou [Replaces old-style internal links with new pipe-split links.]Additions:
Recently, DarTar posted to the [[http://mail.wikkawiki.org/mailman/listinfo | community mailing list]] the following query:
- **[[http://wush.net/trac/wikka/ticket/546 | OpenID]]** To login to an OpenID-enabled website (even one you've never been to before), just type your OpenID URI. The website will then redirect you to your OpenID Provider to login using whatever credentials it requires. Once authenticated, your OpenID provider will send you back to the website with the necessary credentials to log you in. By using Strong Authentication where needed, the OpenID Framework can be used for all types of transactions, both extending the use of pure single-sign-on as well as the sensitivity of data shared.
These would be ideal candidates for modules using the new [[http://docs.wikkawiki.org/UserRegistrationValidationFramework | User Registration (UR) Validation framework]].
- **[[http://wush.net/trac/wikka/ticket/515 | Microformats]]** Microformats are a way of adding simple markup to human-readable data items such as events, contact details or locations, on web pages, so that the information in them can be extracted by software and indexed, searched for, saved, cross-referenced or combined. More technically, they are items of semantic markup, using just standard (X)HTML with a set of common class-names. They are open and available, freely, for anyone to use.
- **[[http://www.w3.org/WAI/intro/wcag.php | WCAG Compliance]]** From the WCAG page: //The Web Content Accessibility Guidelines (WCAG) documents explain how to make Web content accessible to people with disabilities. Web "content" generally refers to the information in a Web page or Web application, including text, images, forms, sounds, and such.//
- **[[WikkaAsARapidDevelopmentFramework | Rapid Development Framework]]** Wikka is an ideal platform for creating standalone applications using a framework such as CakePHP. Wikka provides the "container" (i.e., look-and-feel, authentication, security, etc.), freeing the developer to focus on providing core functionality.
- **[[WikkaFolksonomy | Enhanced Folksonomy]]** Create a tagging framework for Wikka.
- **Charting Functionality** Build a module to provide support for online charting and diagramming, such as is provided by vendors like [[http://www.gliffy.com | Gliffy]]. Other networking schemes, such as those used by sociologists to describe social networks, could be supported as well given a well-designed extensible framework.
- **""WikkaFramework""** What if WikkaWiki was refactored in such a way that all of the base functionality (security, authentication, session management, module management, skinning, etc.) was offered as a basic framework upon which to quickly build and prototype other applications? WikkaWiki could then be offered as a ready-to-deploy set of modules on top of the ""WikkaFramework"". Given the glut of wikis that are out there, and the relative dearth of easy-to-use, robust frameworks (for instance, although robust, I don't consider [[http://www.cakephp.org | CakePHP]] "easy to use"), this might be something to consider for the future direction of WikkaWiki. (One important question needs to be answered: Is it possible to release ""WikkaFramework"" under the GPL and still permit the development of proprietary modules [such as what might be found on an Internet appliance]? Or would the LGPL be more appropriate for such a framework? And if so, would it even be possible to relicense from GPL to LGPL without a complete rewrite?)
- **Multilingual Wiki** Possibility of writing the same page in different languages, like with [[http://www.anwiki.com | Anwiki]].
- **WYSIWYG** Possibility to switch between Wiki editor and a true WYSIWYG editor like in Google Documents. See [[http://wikkawiki.org/WysiWyg | WysiWyg]].
- **[[http://wush.net/trac/wikka/ticket/546 | OpenID]]** To login to an OpenID-enabled website (even one you've never been to before), just type your OpenID URI. The website will then redirect you to your OpenID Provider to login using whatever credentials it requires. Once authenticated, your OpenID provider will send you back to the website with the necessary credentials to log you in. By using Strong Authentication where needed, the OpenID Framework can be used for all types of transactions, both extending the use of pure single-sign-on as well as the sensitivity of data shared.
These would be ideal candidates for modules using the new [[http://docs.wikkawiki.org/UserRegistrationValidationFramework | User Registration (UR) Validation framework]].
- **[[http://wush.net/trac/wikka/ticket/515 | Microformats]]** Microformats are a way of adding simple markup to human-readable data items such as events, contact details or locations, on web pages, so that the information in them can be extracted by software and indexed, searched for, saved, cross-referenced or combined. More technically, they are items of semantic markup, using just standard (X)HTML with a set of common class-names. They are open and available, freely, for anyone to use.
- **[[http://www.w3.org/WAI/intro/wcag.php | WCAG Compliance]]** From the WCAG page: //The Web Content Accessibility Guidelines (WCAG) documents explain how to make Web content accessible to people with disabilities. Web "content" generally refers to the information in a Web page or Web application, including text, images, forms, sounds, and such.//
- **[[WikkaAsARapidDevelopmentFramework | Rapid Development Framework]]** Wikka is an ideal platform for creating standalone applications using a framework such as CakePHP. Wikka provides the "container" (i.e., look-and-feel, authentication, security, etc.), freeing the developer to focus on providing core functionality.
- **[[WikkaFolksonomy | Enhanced Folksonomy]]** Create a tagging framework for Wikka.
- **Charting Functionality** Build a module to provide support for online charting and diagramming, such as is provided by vendors like [[http://www.gliffy.com | Gliffy]]. Other networking schemes, such as those used by sociologists to describe social networks, could be supported as well given a well-designed extensible framework.
- **""WikkaFramework""** What if WikkaWiki was refactored in such a way that all of the base functionality (security, authentication, session management, module management, skinning, etc.) was offered as a basic framework upon which to quickly build and prototype other applications? WikkaWiki could then be offered as a ready-to-deploy set of modules on top of the ""WikkaFramework"". Given the glut of wikis that are out there, and the relative dearth of easy-to-use, robust frameworks (for instance, although robust, I don't consider [[http://www.cakephp.org | CakePHP]] "easy to use"), this might be something to consider for the future direction of WikkaWiki. (One important question needs to be answered: Is it possible to release ""WikkaFramework"" under the GPL and still permit the development of proprietary modules [such as what might be found on an Internet appliance]? Or would the LGPL be more appropriate for such a framework? And if so, would it even be possible to relicense from GPL to LGPL without a complete rewrite?)
- **Multilingual Wiki** Possibility of writing the same page in different languages, like with [[http://www.anwiki.com | Anwiki]].
- **WYSIWYG** Possibility to switch between Wiki editor and a true WYSIWYG editor like in Google Documents. See [[http://wikkawiki.org/WysiWyg | WysiWyg]].
Deletions:
- **[[http://wush.net/trac/wikka/ticket/546 OpenID]]** To login to an OpenID-enabled website (even one you've never been to before), just type your OpenID URI. The website will then redirect you to your OpenID Provider to login using whatever credentials it requires. Once authenticated, your OpenID provider will send you back to the website with the necessary credentials to log you in. By using Strong Authentication where needed, the OpenID Framework can be used for all types of transactions, both extending the use of pure single-sign-on as well as the sensitivity of data shared.
These would be ideal candidates for modules using the new [[http://docs.wikkawiki.org/UserRegistrationValidationFramework User Registration (UR) Validation framework]].
- **[[http://wush.net/trac/wikka/ticket/515 Microformats]]** Microformats are a way of adding simple markup to human-readable data items such as events, contact details or locations, on web pages, so that the information in them can be extracted by software and indexed, searched for, saved, cross-referenced or combined. More technically, they are items of semantic markup, using just standard (X)HTML with a set of common class-names. They are open and available, freely, for anyone to use.
- **[[http://www.w3.org/WAI/intro/wcag.php WCAG Compliance]]** From the WCAG page: //The Web Content Accessibility Guidelines (WCAG) documents explain how to make Web content accessible to people with disabilities. Web "content" generally refers to the information in a Web page or Web application, including text, images, forms, sounds, and such.//
- **[[WikkaAsARapidDevelopmentFramework Rapid Development Framework]]** Wikka is an ideal platform for creating standalone applications using a framework such as CakePHP. Wikka provides the "container" (i.e., look-and-feel, authentication, security, etc.), freeing the developer to focus on providing core functionality.
- **[[WikkaFolksonomy Enhanced Folksonomy]]** Create a tagging framework for Wikka.
- **Charting Functionality** Build a module to provide support for online charting and diagramming, such as is provided by vendors like [[http://www.gliffy.com Gliffy]]. Other networking schemes, such as those used by sociologists to describe social networks, could be supported as well given a well-designed extensible framework.
- **""WikkaFramework""** What if WikkaWiki was refactored in such a way that all of the base functionality (security, authentication, session management, module management, skinning, etc.) was offered as a basic framework upon which to quickly build and prototype other applications? WikkaWiki could then be offered as a ready-to-deploy set of modules on top of the ""WikkaFramework"". Given the glut of wikis that are out there, and the relative dearth of easy-to-use, robust frameworks (for instance, although robust, I don't consider [[http://www.cakephp.org CakePHP]] "easy to use"), this might be something to consider for the future direction of WikkaWiki. (One important question needs to be answered: Is it possible to release ""WikkaFramework"" under the GPL and still permit the development of proprietary modules [such as what might be found on an Internet appliance]? Or would the LGPL be more appropriate for such a framework? And if so, would it even be possible to relicense from GPL to LGPL without a complete rewrite?)
- **Multilingual Wiki** Possibility of writing the same page in different languages, like with [[http://www.anwiki.com Anwiki]].
- **WYSIWYG** Possibility to switch between Wiki editor and a true WYSIWYG editor like in Google Documents. See [[http://wikkawiki.org/WysiWyg WysiWyg]].
Revision [20310]
Edited on 2008-11-14 04:58:25 by ScouBidou [Replaces old-style internal links with new pipe-split links.]Additions:
- **WYSIWYG** Possibility to switch between Wiki editor and a true WYSIWYG editor like in Google Documents. See [[http://wikkawiki.org/WysiWyg WysiWyg]].
Revision [20309]
Edited on 2008-11-14 04:56:00 by ScouBidou [Replaces old-style internal links with new pipe-split links.]Additions:
- **Multilingual Wiki** Possibility of writing the same page in different languages, like with [[http://www.anwiki.com Anwiki]].
Additions:
- **""WikkaFramework""** What if WikkaWiki was refactored in such a way that all of the base functionality (security, authentication, session management, module management, skinning, etc.) was offered as a basic framework upon which to quickly build and prototype other applications? WikkaWiki could then be offered as a ready-to-deploy set of modules on top of the ""WikkaFramework"". Given the glut of wikis that are out there, and the relative dearth of easy-to-use, robust frameworks (for instance, although robust, I don't consider [[http://www.cakephp.org CakePHP]] "easy to use"), this might be something to consider for the future direction of WikkaWiki. (One important question needs to be answered: Is it possible to release ""WikkaFramework"" under the GPL and still permit the development of proprietary modules [such as what might be found on an Internet appliance]? Or would the LGPL be more appropriate for such a framework? And if so, would it even be possible to relicense from GPL to LGPL without a complete rewrite?)
Deletions:
Additions:
- **""WikkaFramework""** What if WikkaWiki was refactored in such a way that all of the base functionality (security, authentication, session management, module management, skinning, etc.) was offered as a basic framework upon which to quickly build and prototype other applications? WikkaWiki could then be offered as a ready-to-deploy set of modules on top of the ""WikkaFramework"". Given the glut of wikis that are out there, and the relative dearth of easy-to-use, robust frameworks (for instance, I don't consider CakePHP "easy to use"), this might be something to consider for the future direction of WikkaWiki. (One important question needs to be answered: Is it possible to release ""WikkaFramework"" under the GPL and still permit the development of proprietary modules [such as what might be found on an Internet appliance]? Or would the LGPL be more appropriate for such a framework? And if so, would it even be possible to relicense from GPL to LGPL without a complete rewrite?)
Deletions:
Additions:
- **WikkaFramework** What if WikkaWiki was refactored in such a way that all of the base functionality (security, authentication, session management, module management, skinning, etc.) was offered as a basic framework upon which to quickly build and prototype other applications? WikkaWiki could then be offered as a ready-to-deploy set of modules on top of the WikkaFramework. Given the glut of wikis that are out there, and the relative dearth of easy-to-use, robust frameworks, this might be something to consider for the future direction of WikkaWiki. (One important question needs to be answered: Is it possible to release WikkaFramework under the GPL and still permit the development of proprietary modules [such as what might be found on an Internet appliance]? Or would the LGPL be more appropriate for such a framework? And if so, would it even be possible to relicense from GPL to LGPL without a complete rewrite?)
Additions:
These would be ideal candidates for modules using the new [[http://docs.wikkawiki.org/UserRegistrationValidationFramework User Registration (UR) Validation framework]].
- **Category Link Description** would provide for a short description of the page being categorized. On the page: Category(some category) //desc="A page for users to list wishes."// This would translate to the category page as "WishListFor117 //A page for users to list wishes.//"
- **Category Link Description** would provide for a short description of the page being categorized. On the page: Category(some category) //desc="A page for users to list wishes."// This would translate to the category page as "WishListFor117 //A page for users to list wishes.//"
Deletions:
Additions:
- **Moderated and/or Email Validated Registration** Administrative option of reviewing new registrations prior to new users posting, further option of new users being emailed a link which must be followed to activate registration.
Deletions:
Additions:
- These would be ideal candidates for modules using the new [[http://docs.wikkawiki.org/UserRegistrationValidationFramework User Registration (UR) Validation framework]].
Deletions:
Additions:
- **Moderated and/or Email Validated Registration** Adminitrative option of revieing new registrations prior to new users posting, further option of new users being emailed a link which must be followed to activate registration.
Additions:
====Wish List for 1.1.7====
