• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
New in Plone 3.3. What to expect from Plone 4
 

New in Plone 3.3. What to expect from Plone 4

on

  • 4,630 views

Plone Roadmap

Plone Roadmap
World Plone Day 2009 (WPD 2009)

Statistics

Views

Total Views
4,630
Views on SlideShare
4,573
Embed Views
57

Actions

Likes
4
Downloads
5
Comments
2

5 Embeds 57

http://www.plug.org.ua 26
http://www.slideshare.net 13
http://plug.org.ua 9
http://talk.quintagroup.com 8
http://ploneua.quintagroup.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

12 of 2 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • Yes, you are right. Perhaps I had to add some notes after 'Simplification' slides about appropriate replacements or at least some appointment where to look for explanation for each PLIP. Will be better the next time ;-) Thank you for correction.
    Are you sure you want to
    Your message goes here
    Processing…
  • Quite a few things being removed in name of 'simplification'. Hope to see in future iterations of plone4 story also what will replace them. We don't want to give the wrong impression that the platform will lose functionality do we? :)
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

New in Plone 3.3. What to expect from Plone 4 New in Plone 3.3. What to expect from Plone 4 Presentation Transcript

      • New in Plone 3.3
      • What to expect from Plone 4
    Vitaliy Podoba http://quintagroup.com
  • 3.3 (Release candidate 2) (Apr 07, 2009) 11 Feature Enhancements (PLIPs)‏
  • PLIP || PL one I mprovement P roposal
  • 1
  • #126: Link type should automatically redirect when accessed directly
  •  
  • Redirect Immediately to link target
  • 2
  • #232: Resource Registries Improvements
  • Conditional Comments (IE Only)‏ IE Conditional Comment Field with value 'IE'
      • <!--[if IE]>
      • <style type=&quot;text/css&quot; media=&quot;all&quot;>...
      • <![endif]-->
  • External Resources http://quintagroup.com/default.css
  • 3
  • #234: Standardizing use of INavigationRoot
  • Portal Tabs
  • Breadcrumbs
  • Sitemap
  • Navigation Portlet
  • New : Fixed Search
  • 4
  • #237: Minor i18n upgrades
  • PlacelessTranslationService 1.4.13 PloneLanguageTool 2.0
  • PlacelessTranslationService 1.5
    • Multiple message catalogs in the same domain
  • PloneLanguageTool 3.0
    • A new content language-based negotiator
    • A new sub-domain negotiator
    • Option to restrict cookie negotiation to authenticated users
    • Changed default for displaying flags
    • Changed ITranslatable location
  • 5
  • #238: Disable inline editing by default
  • Before
  • Now
  • 6
  • #239: Adapterise the Extensible Indexable Object Wrapper
  • Before
  • from Products.CMFPlone.CatalogTool import registerIndexableAttribute def customIndex(obj, portal, **kwargs): “”” some code goes here “”” registerIndexableAttribute('customIndex', customIndex)
  • Now
  • 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; />
  • 7
  • #240: Improve locking configurability
    • Possibility to switch off locking
    • Locking timeout = 10 minutes
    • KSS action extends the lock every 5 minutes
  • lock_on_ttw_edit
    • Possibility to switch off locking
    • Locking timeout = 10 minutes
    • KSS action extends the lock every 5 minutes
  • 8
  • #241: Clean up auto-sort, auto-order code
  • Removed not fully completed plone2.1 plip #3
    • Deleted: ATContentTypes/interface/autosort.py ATContentTypes/lib/autosort.py
    • Cleaned-up ATCT Folder type
  • 9
  • #243: Replace workflow history viewlet with content history viewlet
  • Before
  • Now
  • 10
  • #246: View for rendering events as an iCalendar file
  • Before
  • @@ics_view collects events and returns them as an iCalendar file for:
    • Plone root
    • Folder
    • Large Folder
    • Topic
  •  
  • 11
  • #247: Automate ZCML Loading for Plone Plug-ins
  • Before
      • <include package=”some.package” />
  • Now z3c.autoinclude
  • Now setup(... entry_points=&quot;&quot;&quot; ... [z3c.autoinclude.plugin] target = plone ... “”” ...)‏
  • BONUS !!!
  • New favicon.ico that is in line with the new branding
  • Improved products installation story
  • Before Reinstall
  • Now Upgrade
  • A lot of bugs fixed due to regular Plone tune-up events http://plone-tuneup.ning.com
  • 4 (Unreleased) (after early 2010)‏
  • Smaller. Faster. Easier.
  • Plone 4 will be primarily a feature based release, not time-based
  • Better page composition story (Plone Deco Proposal)‏
  • Proposal snapshot
  •  
  • Prototype snapshot http://www.fourdigits.nl/plone4uidemo/v16
  •  
  • Blocks: Grid layout
    • Grid-based layout consisting of
    • Panels consisting of
    • Tiles which could be * transient or * persistent
  • Plone Deco Packages
    • plone.blocks
    • experimental.blocks
    • plone.tiles
    • plone.app.deco
  • For details
    • Plone Deco Project Area http://code.google.com/p/plone-deco
    • Plone Deco Google Group http://groups.google.com/group/plone-deco
  • Noticeably increase performance
  • Hanno Schlichting: “The slogan today is: Plone is getting twice as fast with every release.”
  •  
  • The possibility to easily use a non-Archetypes based content types (e.g. Dexterity)‏
  • Dexterity is considered as an alternative (to Archetypes) way for creating Plone content types
  • For details
    • Dexterity Project Area http://code.google.com/p/dexterity
    • Dexterity Google Group http://groups.google.com/group/dexterity-development
  • Improve technical base (Python 2.6 and WSGI)‏
  • plone-coredev buildout already requires Python 2.6 http://dev.plone.org/plone/changeset/26393
  • Plone versus Python 3 Possible Scenario :-) http://blog.hannosch.eu/2008/12/plone-versus-python-3.html
  • Plone is ...
  • Plone trunk is already running as WSGI application by means of repoze.zope2
  • Right now there are 22 Plone 4 PLIPs in plone trac project http://dev.plone.org/plone/report/24
  • Which mostly aim to simplify Plone base
  • Simplification 1
    • Remove external editor support
    • Remove wicked support
    • Remove CMFActionIcons
    • Do not ship with NuPlone anymore
    • Merge GroupUserFolder into PlonePAS
    • Plone core should no longer use portal_skins
    • Retire CMFQuickInstaller
  • Simplification 2
    • Make KSS optional
    • Provide a &quot;Plone Base&quot; distribution
    • Replace SecureMailHost with Zope mailhost
    • Get rid of base_properties
    • No longer use Kupu as our default visual editor
    • Remove PlacelessTranslationService
    • Focus on minimized package dependencies
  • To be continued ...
  • For details
      • http://plone.org