Sounds great for me,<br><br>I would also remove the static folder, profiles and skins ( no need as its not beeing used on plone 5) so the package is much smaller and easier to maintain. There are two big zcml conditions depending if its plone 5 or not and all resources don't need to be there anymore.<div><br></div><div>Ramon<br><br><div class="gmail_quote">El Mon Jan 26 2015 at 07:03:35, David Glick (Plone) (<<a href="mailto:david.glick@plone.org" target="_blank">david.glick@plone.org</a>>) va escriure:</div><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Yeah, maybe leave the base widgets in
plone.app.widgets, and just move the Dexerity- and Archetypes-
specific code (e.g. widget subclasses) and configuration to Plone
5-specific branches of plone.app.dexterity and
Products.Archetypes.</div></div><div bgcolor="#FFFFFF" text="#000000"><div><br>
<br>
On 1/25/15 10:00 PM, Nathan Van Gheem wrote:<br>
</div></div><div bgcolor="#FFFFFF" text="#000000">
<blockquote type="cite">
<div dir="ltr">We could keep most of plone.app.widgets and just
move all override stuff into other packages(at_bbb.py,
dx_bbb.py, skins). I'd then also just cut a plone 4 only branch
of plone.app.widgets.
<div><br>
</div>
<div>Sound better?</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sun, Jan 25, 2015 at 11:44 PM,
Nathan Van Gheem <span dir="ltr"><<a href="mailto:nathan@vangheem.us" target="_blank">nathan@vangheem.us</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">ahh cool. I was just reading the docs and
didn't notice any specifics about that.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">
<div>
<div>On Sun, Jan 25, 2015 at 11:42 PM,
David Glick (Plone) <span dir="ltr"><<a href="mailto:david.glick@plone.org" target="_blank">david.glick@plone.org</a>></span>
wrote:<br>
</div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div>
<div bgcolor="#FFFFFF" text="#000000"><span>
<div>On 1/25/15 9:34 PM, Nathan Van Gheem
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sun, Jan 25,
2015 at 11:33 PM, David Glick (Plone)
<span dir="ltr"><<a href="mailto:david.glick@plone.org" target="_blank">david.glick@plone.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On
1/25/15 9:24 PM, Nathan Van Gheem
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Hi All,<br>
<br>
<br>
I'd like to merge
plone.app.widgets into all of
other plone packages for plone
5.<br>
<br>
In doing so, I need to create
some plone 4 only branches for
plone.app.dexterity and
plone.app.contenttypes.<br>
<br>
Any objections?<br>
</blockquote>
<br>
</span> I don't really understand
the benefit of spending effort to
move the code. Is there an important
reason I'm forgetting?</blockquote>
<div>plone.app.widgets overrides
things in other packages to work so
it's a bit of indirection. I'd like
to cut off plone.app.widgets and
whoever wants to maintain it for
plone 4 can if they care to.</div>
</div>
</div>
</div>
</blockquote>
<br>
</span> Okay. I agree it would be ideal to avoid
those overrides, although it maybe should be
considered lower priority than fixing bugs in
Plone 5.<br>
<br>
It looks like we already have branches for these
packages -- Plone 4.3 is using the 2.0.x branch
of plone.app.dexterity and the 1.1.x branch of
plone.app.contenttypes (at least according to
sources.cfg in buildout.coredev).<span><br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div> <br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
Also, what does everything think
about Archetypes and
plone.app.widgets. Should that
code be merged as well or do we
just start ignoring Archetypes
in plone 5 a bit?<br>
<br>
</blockquote>
</span> I think if we ignore
Archetypes in Plone 5, it will
significantly discourage users with
custom AT content types from
upgrading to Plone 5.<br>
</blockquote>
<div>Alright, we might need a branch
for Archetypes also then :)</div>
<div> </div>
</div>
</div>
</div>
</blockquote>
</span> Also already exists -- Plone 4.3 uses
the 1.9.x branch of Products.Archetypes.<br>
</div>
<br>
</div>
</div>
<span>______________________________<u></u>_________________<br>
Framework-Team mailing list<br>
<a href="mailto:Framework-Team@lists.plone.org" target="_blank">Framework-Team@lists.plone.org</a><br>
<a href="https://lists.plone.org/mailman/listinfo/plone-framework-team" target="_blank">https://lists.plone.org/<u></u>mailman/listinfo/plone-<u></u>framework-team</a><br>
<br>
</span></blockquote>
</div>
<span><br>
<br clear="all">
<div><br>
</div>
-- <br>
<div>
<div dir="ltr">Nathan Van Gheem
<div>Solutions Architect</div>
<div>Wildcard Corp</div>
</div>
</div>
</span></div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div>
<div dir="ltr">Nathan Van Gheem
<div>Solutions Architect</div>
<div>Wildcard Corp</div>
</div>
</div>
</div>
</blockquote>
<br>
</div>
______________________________<u></u><u></u>_________________<br>
Framework-Team mailing list<br>
<a href="mailto:Framework-Team@lists.plone.org" target="_blank">Framework-Team@lists.plone.org</a><br>
<a href="https://lists.plone.org/mailman/listinfo/plone-framework-team" target="_blank">https://lists.plone.org/<u></u>mailma<u></u>n/listinfo/plone-<u></u>framework-<u></u>team</a><br>
</blockquote></div></div>