Re: [Framework-Team] Re: wicked integration w/ plone 3

2007-01-08 Thread Tom Lazar


On Jan 8, 2007, at 11:29 AM, Martin Aspeli wrote:


On 1/8/07, whit [EMAIL PROTECTED] wrote:


[ ]  enable wiki
[ ]  use media wiki syntax
- enabled types -
   Event
   Page
   News


Why do we need both an enable wiki option and a list of enabled
types? If all the types are deselected, wiki syntax is off by
definition, no?


plus perhaps a JS-enabled 'select all types' checkbox. also, the  
blacklist approach seems to lend itself here, to auto-enable new  
types, no?


tom


Martin

___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team




___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team


[Framework-Team] Re: Re: wicked integration w/ plone 3

2007-01-08 Thread Alexander Limi
On Mon, 08 Jan 2007 08:35:18 -0800, whit  
[EMAIL PROTECTED] wrote:



Martin Aspeli wrote:
On 1/8/07, whit [EMAIL PROTECTED]  
wrote:



[ ]  enable wiki
[ ]  use media wiki syntax
- enabled types -
   Event
   Page
   News


Why do we need both an enable wiki option and a list of enabled
types? If all the types are deselected, wiki syntax is off by
definition, no?


yeah, I just did it to be explicit and so everything could be turned off
in one click. should I pare it down to types and the media wiki toggle?


No need to spend too much time on it as long as the info is in there. The  
wiki stuff shouldn't be a separate control panel, but be part of the types  
control panel (just like Tom's new markup support).


As long as we have enough code to infer how to set things on and off, we  
should be able to stick this into a formlib-powered version of the types  
panel.


--
Alexander Limi ยท http://limi.net


___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team


[Framework-Team] Please adopt my baby

2007-01-08 Thread Philipp von Weitershausen
At the Seattle sprint, Alec and I implemented the Customize button for 
Zope 3 views in a package called five.customerize. It completely works 
in the sense that you can customize any Zope 3 browser page that's Page 
Template based. There are a few things that still need to happen with 
it, however:


* Currently there's a nasty Unauthorized error lurking somewhere. There 
may be other bugs. It needs a bug exterminator treatment.


* It needs tests tests tests. Alec and I wrote many, but not enough

* It needs a polished UI. Currently there's minimal support for the ZMI. 
That needs to be completed. I also assume you guys want to hook it into 
the Plone UI.


* It needs to be released and integrated in the Plone 3 bundle, assuming 
you guy really want this feature in Plone 3.


I don't have the bandwidth to do any of this, hence I'm looking for 
someone to adopt this baby. I'll be willing to guide that somebody thru 
the tasks I outlined above, but I'll unlikely find time to do any coding 
on this.


Any takers?

--
http://worldcookery.com -- Professional Zope documentation and training
2nd edition of Web Component Development with Zope 3 is now shipping!


___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team