Several bugfixes for 0.6 series (bugfix while defining pod fields in a custom tool, bugfix in the creation flag, import of objects was broken...) and minor improvements in the layouting system (automatic generation of 'cell' layouts was optimized).

gen/plone25/skin/edit.pt

@@ -52,7 +52,7 @@
         <input type="hidden" name="action" value="Update"/>
         <input type="hidden" name="page" tal:attributes="value page"/>
         <input type="hidden" name="nav" tal:attributes="value request/nav|nothing"/>
-        <input type="hidden" name="is_new" tal:attributes="value contextObj/checkCreationFlag"/>
+        <input type="hidden" name="is_new" tal:attributes="value contextObj/isTemporary"/>
         <metal:show use-macro="here/skyn/page/macros/show"/>
       </form>
       <metal:footer use-macro="here/skyn/page/macros/footer"/>

gen/plone25/skin/page.pt

@@ -387,7 +387,8 @@
     layoutType         We must know if we must render the widgets in a "view",
                        "edit" or "cell" layout
 </tal:comment>
-<table metal:define-macro="widgets" cellpadding="0" cellspacing="0">
+<table metal:define-macro="widgets" cellpadding="0" cellspacing="0"
+       tal:attributes="width layout/width">
   <tr tal:repeat="widget python: contextObj.getGroupedAppyTypes(layoutType, page)">
     <td tal:condition="python: widget['type'] == 'group'">
       <metal:call use-macro="portal/skyn/widgets/show/macros/group"/>

gen/plone25/skin/widgets/string.pt

@@ -100,7 +100,7 @@
     <tal:comment replace="nothing">The list of values</tal:comment>
     <select tal:attributes="name widgetName" multiple="multiple" size="5">
       <option tal:repeat="v python:tool.getPossibleValues(name, withTranslations=True, withBlankValue=False, className=contentType)"
-              tal:attributes="value python:v[0]" tal:content="python: v[1]">
+              tal:attributes="value python:v[0]" tal:content="python: tool.truncateValue(v[1], widget)">
       </option>
     </select>
   </tal:selectSearch><br/>