plone.formwidget.masterselect or should it go in collective?

[JMehring]

Martin or David,

I am just finishing up a new widget based on Products.MasterSelect
that allows other form fields to be controlled by a master select
(drop down) field for z3cform / dexterity.

Should I keep the naming (plone.formwidget.masterselect) and add it to
dexterity packages in the plone repo or rename it and shove it over on
the collective?

I also wrote selenium tests using plone.app.testing framework for it
as well. The selenium tests are in its own test directory. I want to
get them working with Hudson somehow as well. Some neat things I got
working with Selenium so far is the ability to use jQuery as the
selector (locator) and ability to detect when all ajax events are
complete (self.waitForAjaxToComplete())

I should be able to make the widget work with archetypes, if that
would be a benefit (although I have absolutely no experience with
archetypes, the original code should be able to be used for that
portion).

Jason

[Martin Aspeli]

On 16 November 2010 10:57, JMehring <nrg...@yahoo.com> wrote:
> Martin or David,
>
> I am just finishing up a new widget based on Products.MasterSelect
> that allows other form fields to be controlled by a master select
> (drop down) field for z3cform / dexterity.
>
> Should I keep the naming (plone.formwidget.masterselect) and add it to
> dexterity packages in the plone repo or rename it and shove it over on
> the collective?

If you have contributor access, then putting it in the Plone
repository is a good idea.

> I also wrote selenium tests using plone.app.testing framework for it
> as well.  The selenium tests are in its own test directory.  I want to
> get them working with Hudson somehow as well.  Some neat things I got
> working with Selenium so far is the ability to use jQuery as the
> selector (locator) and ability to detect when all ajax events are
> complete (self.waitForAjaxToComplete())

Cool :)

> I should be able to make the widget work with archetypes, if that
> would be a benefit (although I have absolutely no experience with
> archetypes, the original code should be able to be used for that
> portion).

You can't have a plone.formwidget.masterselect that depends on
Archetypes. You could create a sister package with the same look and
feel, possibly with some shared code in e.g. a plone.masterselectcore
or something like that.

Martin

[Cédric Messiant]

Hello everyone,

I updated the widget and tested it on Plone 4.2 a few months ago.
Right now, it is on my repository (https://github.com/cedricmessiant/plone.formwidget.masterselect) but I should probably put it on the collective ?

Cédric

[Lennart Regebro]

On Tue, Apr 23, 2013 at 8:51 AM, Cédric Messiant
<cedric....@gmail.com> wrote:
> Hello everyone,
>
> I updated the widget and tested it on Plone 4.2 a few months ago.
> Right now, it is on my repository
> (https://github.com/cedricmessiant/plone.formwidget.masterselect) but I
> should probably put it on the collective ?

I see no reason not to.

//Lennart

[Cédric Messiant]

Done ! https://github.com/collective/plone.formwidget.masterselect

Cédric