Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
Dexterity development
Home
About this group
Apply for group membership
Message from discussion Tahoe wrap-up and next release
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
David Glick  
View profile  
 More options Mar 20 2010, 2:50 pm
From: David Glick <dgl...@gmail.com>
Date: Sat, 20 Mar 2010 11:50:45 -0700
Local: Sat, Mar 20 2010 2:50 pm
Subject: Re: Tahoe wrap-up and next release
Print | View thread | Show original | Report this message | Find messages by this author

On 3/20/10 3:49 AM, Martin Aspeli wrote:

>>      - I think the UI for plone.formwidget.contenttree has broken,
>>     though it may be a Plone 4/Sunburst issue. The functionality is
>>     probably still OK.
>     Yes, I think this is probably related to Sunburst.

> Okay. We need to fix it at least so that it's on par with what we used
> to have.

Any volunteers to look into this one?

>>      - We need to release new versions of z3c.form, plone.z3cform,
>>     plone.app.z3cform, and plone.directives.forms. I can take care of
>>     those, although I don't know the status of the changes that went
>>     into these packages at the sprint.
>     There are a couple more adjustments I'd like to make to the slots,
>     based on talking with Alex and Joel.

> Ok. Can you outline what you're proposing?

Here are some requests that came up this past week:
1. (from Alex) Make it possible to inject additional markup *outside*
the <form> tag.
2. (from Joel) Make it possible to replace the form fields, but keep the
header, form tag, and actions.
3. (from Joel) Make it possible to replace just the title or just the
description.
4. (from Alex/me) Make it possible to inject markup into the HTML head.

In order to achieve these, I would like to:
1. Add a 'formwrapper' slot surrounding the <form> tag.
2. Add a 'fields' slot surrounding everything within the form tag
*except* for the actions.
3. Add 'title' and 'description' slots (these can already be replaced
via the form's 'label' and 'description' attributes, but those
don'tallow inserting markup).
4. This one is easy for unwrapped forms, but trickier when there's a
form wrapper.  We would need to make the form wrapper template check for
some attribute on the wrapped form.  I think there's no reason not to
complete the 3 above proposals, but this one I'm less convinced is the
right solution.

>     The work Alex and I did on the UI is on a branch, and not quite
>     done.  I hope to finish it up soon, but I think the work that's
>     been done on trunk is also releasable as is.  I can take care of
>     that when it's time.

> Ok, so what's on trunk and not in the branch?

A few bugfixes, and Ross' work on supporting Choice fields.
> How far off is the branch? It does look much nicer in the tahoe-ui
> branch. ;-)

I need to re-add support for setting field ids and for reordering
fields, to achieve feature parity with the old UI.

>>      - There's still a test failure related to datetimes, DateTimes
>>     and timezones in plone.app.dexterity
>     Really? I haven't seen that one and it doesn't seem to be showing
>     up in Hudson.

> Try to change your timezone and run the tests, maybe?

Can you open a ticket with the test output?

There are also some trivial test failures on Plone 4.0b1 due to
Acquisition wrappers repr-ing as <type
'Acquisition.ImplicitAcquisitionWrapper'> rather than <type
'ImplicitAcquirerWrapper'>

>>      - Is the image scale stuff ready? It'll need to be added to the
>>     manual at the very least.
>     No, not ready, although Andi has done a lot of the legwork this
>     week in plone.app.imaging for Archetypes.  It should be hard to
>     make a similar adapter for plone.namedfile.

> You mean it should *not* be hard? Any pointers to what we'd need to
> replicate?

plone.scale provides a function for doing scaling, and a storage that
can create and retrieve scales stored in annotations.  We need to create
an adapter that exposes them to traversal and specifies policy about how
the images are stored (e.g. in blobs, AT ImageScale instances, etc.) and
named (e.g. via configuring scale name => size mappings in the
imaging_properties sheet).  We can model this on the adapter Andi has
created for AT content in plone.app.imaging.

Note that Andi and I are assuming we'll switch to the new improved
approach to referencing scales from templates (see docs on
plone.app.imaging's new-scales branch). So at some point the listing
templates in Plone need to get updated to use that.  And until then,
Dexterity content won't actually show with images in listings, unless we
monkeypatch support for the tag method and /image_scalename traversal
onto the DexterityContent base class.

>>      - Is the new zc.relation-based field for Archetypes ready? Maybe
>>     not part of a Dexterity release per se, but it may be useful to
>>     put it into the KGS.
>     I'll defer to Ross and David on this one. :)

> It's not crucial for a release. It'd be nice to get this into Plone
> 4.1, though. :-p

We might be able to add it as an option in 4.1.  I doubt we can replace
the AT reference implementation wholesale in the 4.x series, unless we
also reimplement BBB replacements for the ReferenceEngine, Referenceable
mixin, and Reference class (even then, there's probably too much
third-party code out there that relies on the AT reference_catalog).

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google