The document discusses new features and improvements in Plone 3.3 including improved linking, resource registration, navigation, internationalization, and locking. It then outlines plans for Plone 4 which include a redesigned page composition system using blocks, increased performance, use of Dexterity for content types instead of Archetypes, upgrading to Python 2.6 and WSGI, and simplifying the Plone core.

2. 3.3 (Release candidate 2) (Apr 07, 2009) 11 Feature Enhancements (PLIPs)‏

3. PLIP || PL one I mprovement P roposal

4. 1

5. #126: Link type should automatically redirect when accessed directly

7. Redirect Immediately to link target

8. 2

9. #232: Resource Registries Improvements

10. Conditional Comments (IE Only)‏ IE Conditional Comment Field with value 'IE'

12. External Resources http://quintagroup.com/default.css

13. 3

14. #234: Standardizing use of INavigationRoot

15. Portal Tabs

16. Breadcrumbs

17. Sitemap

18. Navigation Portlet

19. New : Fixed Search

20. 4

21. #237: Minor i18n upgrades

22. PlacelessTranslationService 1.4.13 PloneLanguageTool 2.0

25. 5

26. #238: Disable inline editing by default

27. Before

28. Now

29. 6

30. #239: Adapterise the Extensible Indexable Object Wrapper

31. Before

32. from Products.CMFPlone.CatalogTool import registerIndexableAttribute def customIndex(obj, portal, **kwargs): “”” some code goes here “”” registerIndexableAttribute('customIndex', customIndex)

33. Now

34. indexers.py: from interfaces import IPage from plone.indexer import indexer @indexer(IPage) def customIndex(object): “”” some code goes here “”” configure.zcml: <adapter name=&quot;customIndex&quot; factory=&quot;.indexers.customIndex&quot; />

35. 7

36. #240: Improve locking configurability

38. lock_on_ttw_edit

40. 8

41. #241: Clean up auto-sort, auto-order code

43. 9

44. #243: Replace workflow history viewlet with content history viewlet

45. Before

46. Now

47. 10

48. #246: View for rendering events as an iCalendar file

49. Before

52. 11

53. #247: Automate ZCML Loading for Plone Plug-ins

55. Now z3c.autoinclude

56. Now setup(... entry_points=&quot;&quot;&quot; ... [z3c.autoinclude.plugin] target = plone ... “”” ...)‏

57. BONUS !!!

58. New favicon.ico that is in line with the new branding

59. Improved products installation story

60. Before Reinstall

61. Now Upgrade

62. A lot of bugs fixed due to regular Plone tune-up events http://plone-tuneup.ning.com

63. 4 (Unreleased) (after early 2010)‏

64. Smaller. Faster. Easier.

65. Plone 4 will be primarily a feature based release, not time-based

66. Better page composition story (Plone Deco Proposal)‏

67. Proposal snapshot

69. Prototype snapshot http://www.fourdigits.nl/plone4uidemo/v16

74. Noticeably increase performance

75. Hanno Schlichting: “The slogan today is: Plone is getting twice as fast with every release.”

77. The possibility to easily use a non-Archetypes based content types (e.g. Dexterity)‏

78. Dexterity is considered as an alternative (to Archetypes) way for creating Plone content types

80. Improve technical base (Python 2.6 and WSGI)‏

81. plone-coredev buildout already requires Python 2.6 http://dev.plone.org/plone/changeset/26393

82. Plone versus Python 3 Possible Scenario :-) http://blog.hannosch.eu/2008/12/plone-versus-python-3.html

83. Plone is ...

84. Plone trunk is already running as WSGI application by means of repoze.zope2

85. Right now there are 22 Plone 4 PLIPs in plone trac project http://dev.plone.org/plone/report/24

86. Which mostly aim to simplify Plone base

89. To be continued ...