Changeset 8271


Ignore:
Timestamp:
07/22/10 02:52:31 (22 months ago)
Author:
SvenDowideit
Message:

Item8841: adding a few more things to the release note.

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/core/data/System/ReleaseNotes01x01.txt

    r8269 r8271  
    99---++ Foswiki - The Free and Open Source Wiki 
    1010 
    11 Foswiki is an enterprise collaboration and information sharing tool targeted for professional use in many types of organizations: from small businesses to multi-nationals, from one-product open source groups, to worldwide research networks. 
    12  
    13 Foswiki is a wiki: fundamentally, a website with editable web pages. It looks like a normal web site but it encourages contributions, edits, updates, questions, and answers from its users. It's a powerful way of enabling a community to communicate asynchronously using intranet and public internet websites. Foswiki is simple to learn and use. It aims to provide a transparent way for you to publish and exchange your ideas with others over the web and eliminates the one-webmaster syndrome of outdated intranet content. 
    14  
    15 Foswiki is a structured wiki with tools that enable users without programming skills to build powerful yet simple applications to process information and support workflows. Developers can extend the functionality of Foswiki with plugins. 
    16  
    17 Foswiki is the old TWiki project under a new name. Restrictions on the use of the TWiki brand resulted in many of its developers continuing the project under the new Foswiki name. Foswiki is backwards compatible with all content from older TWiki installations. Foswiki 1.1 ships with a !TWikiCompatibilityPlugin installed and activated by default, thus enabling most extensions made for TWiki to work under Foswiki. 
    18  
    19 Since the start of the Foswiki project there have been several releases of TWiki, However there have been very few functionality changes, and the useful changes have all been tracked in Foswiki, so topics and wiki applications supported by TWiki should also work with Foswiki. 
     11Foswiki is an enterprise collaboration and information sharing tool targeted  
     12for professional use in many types of organizations: from small businesses to  
     13multi-nationals, from one-product open source groups, to worldwide research networks. 
     14 
     15Foswiki is a wiki: fundamentally, a website with editable web pages. It looks  
     16like a normal web site but it encourages contributions, edits, updates, questions,  
     17and answers from its users. It's a powerful way of enabling a community to  
     18communicate asynchronously using intranet and public internet websites.  
     19Foswiki is simple to learn and use. It aims to provide a transparent way  
     20for you to publish and exchange your ideas with others over the web and  
     21eliminates the one-webmaster syndrome of outdated intranet content. 
     22 
     23Foswiki is a structured wiki with tools that enable users without programming  
     24skills to build powerful yet simple applications to process information and  
     25support workflows. Developers can extend the functionality of Foswiki with plugins. 
     26 
     27Foswiki is the old TWiki project under a new name. Restrictions on the use  
     28of the TWiki brand resulted in many of its developers continuing the project  
     29under the new Foswiki name. Foswiki is backwards compatible with all content  
     30from older TWiki installations. Foswiki 1.1 ships with a !TWikiCompatibilityPlugin  
     31installed and activated by default, thus enabling most extensions  
     32made for TWiki to work under Foswiki. 
     33 
     34Since the start of the Foswiki project there have been several releases of TWiki,  
     35However there have been very few functionality changes, and the useful changes  
     36have all been tracked in Foswiki, so topics and wiki applications  
     37supported by TWiki should also work with Foswiki. 
    2038 
    2139Foswiki is released under the GNU General Public License. 
    … …  
    4967---++ Important Changes since Foswiki 1.0.9 
    5068 
    51 Foswiki 1.1 comes with a lot of "under the hood" improvements to the core code, with the goal of making it easier to plug in work from other projects, such as jQuery, !KinoSearch, Solr and others. We have also worked to improve the definition of internal APIs to allow other not-yet-written modules, such as store implementations, to plug in. Most of these modifications should be invisible to the end user and the admin, but are important to position Foswiki for the next generation of improvements. 
     69Foswiki 1.1 comes with a lot of "under the hood" improvements to the core code,  
     70with the goal of making it easier to plug in work from other projects, such  
     71as jQuery, !KinoSearch, Solr and others. We have also worked to improve  
     72the definition of internal APIs to allow other not-yet-written modules,  
     73such as store implementations, to plug in. Most of these modifications  
     74should be invisible to the end user and the admin, but are important to  
     75position Foswiki for the next generation of improvements. 
    5276 
    5377---+++ Powerful new =QUERY= macro 
    54 A number of new features have been added with the goal of improving support for wiki applications. These include the powerful new =QUERY= macro, which supports formatted access to formfields and other meta-data in topics using the same syntax as is used in =IF= and =SEARCH= statements. 
    55  
    56 The existing =META= macro has been deprecated (it is still available, but use is discouraged and it will be removed at some point in the future), joining the already-deprecated =METASEARCH=. 
     78A number of new features have been added with the goal of improving support  
     79for wiki applications. These include the powerful new =QUERY= macro,  
     80which supports formatted access to formfields and other meta-data in  
     81topics using the same syntax as is used in =IF= and =SEARCH= statements. 
     82 
     83The existing =META= macro has been deprecated (it is still available,  
     84but use is discouraged and it will be removed at some point in the future),  
     85joining the already-deprecated =METASEARCH=. 
     86 
     87---+++ Re-architecting of the SEARCH macro 
     88To improve the speed, consistency and extendability of the most complex  
     89and important Macro, we've started to separate the generation of search results 
     90from the outputing of FormattedSearch. The most significant user facing  
     91improvements are speed and reliability changes - with many more unit tests written 
     92to ensure future compatibility. 
     93 
     94---+++ FOREACH macro 
     95The extraction of the FormattedSearch system has made it possible to provide a  
     96Macro that allows users to render a comma separated list into any =header=,  
     97=footer=, =format= style. 
    5798 
    5899---+++ Testing configuration variables in %IF 
    … …  
    69110---+++ Tailoring of user registration made easier. 
    70111 
    71 The topic System.UserRegistration has been enhanced so it now determines whether a custom user registration page exists in %USERSWEB%, and includes it if it does; otherwise it includes DefaultUserRegistration. 
    72  
    73 This means that your tailored version in %USERSWEB% web will not be overwritten by future upgrades. 
    74  
    75 You can create a custom version of the UserRegistration form by first copying the topic DefaultUserRegistration to !UserRegistration in %USERSWEB% web. This will ensure that your changes will remain intact next time you upgrade. 
    76  
    77 A couple of common fields are hidden from normal view to make the registration page as simple as possible. You can unhide those fields on the page by removing =EXCLUDED_= from the =INCLUDE= tags). 
     112The topic System.UserRegistration has been enhanced so it now determines  
     113whether a custom user registration page exists in %USERSWEB%, and  
     114includes it if it does; otherwise it includes DefaultUserRegistration. 
     115 
     116This means that your tailored version in %USERSWEB% web will not be  
     117overwritten by future upgrades. 
     118 
     119You can create a custom version of the UserRegistration form by first  
     120copying the topic DefaultUserRegistration to !UserRegistration in  
     121%USERSWEB% web. This will ensure that your changes will remain intact next time you upgrade. 
     122 
     123A couple of common fields are hidden from normal view to make the  
     124registration page as simple as possible. You can unhide those fields  
     125on the page by removing =EXCLUDED_= from the =INCLUDE= tags). 
    78126 
    79127---+++ Easy tailoring of reset/change password and change email forms 
    80128 
    81 The topics %SYSTEMWEB%.ResetPassword and %SYSTEMWEB%.ChangePassword now only show the change forms when Foswiki is managing the passwords (the =configure= setting ={PasswordManager}= set to a manager that handles setting of passwords). 
    82  
    83 If the {PasswordManager} does not support password changing, the ChangePassword and ResetPassword topics will show a simple message. This message is defined iby the preference =CHANGEPASSWORDDISABLEDMESSAGE= in %SYSTEMWEB%.DefaultPreferences. You can redefine this setting by copying it to %USERSWEB%.SitePreferences and change it to include a link to the password management website of your organisation. 
    84  
    85 ChangeEmailAddress will now guide the user to define the email address in the user topic when the PasswordManager does not handle hidden email addresses, so you should not need to tailor this topic any longer. 
     129The topics %SYSTEMWEB%.ResetPassword and %SYSTEMWEB%.ChangePassword now  
     130only show the change forms when Foswiki is managing the passwords  
     131(the =configure= setting ={PasswordManager}= set to a manager that handles setting of passwords). 
     132 
     133If the {PasswordManager} does not support password changing,  
     134the ChangePassword and ResetPassword topics will show a simple message.  
     135This message is defined iby the preference =CHANGEPASSWORDDISABLEDMESSAGE=  
     136in %SYSTEMWEB%.DefaultPreferences. You can redefine this setting by copying  
     137it to %USERSWEB%.SitePreferences and change it to include a link to the  
     138password management website of your organisation. 
     139 
     140ChangeEmailAddress will now guide the user to define the email address  
     141in the user topic when the PasswordManager does not handle hidden email addresses,  
     142so you should not need to tailor this topic any longer. 
    86143 
    87144---+++ Logging of access failures 
    … …  
    107164see excessive errors reported by configure.  You are recommended to correct the 
    108165file system permissions.  
     166 
     167---+++ Newer modern Icon set for DocumentGraphics. 
     168To celebrate our new look, project and momentum, Foswiki now has a new ICON set  
     169to update the one shipped for the last 10 years. Using the FamFamFam icon set,  
     170augmented with icons from other leading graphic artists. 
    109171 
    110172---+++ Notes for extension authors 
Note: See TracChangeset for help on using the changeset viewer.