[Grok-dev] The z3c.widget is broken

[TonyXu]

I am sorry, I made a mistake. It should be "z3c.widget-0.1.6-py2.5.egg"
instead of "megrok.kss-0.2.1-py2.5.egg".

Sorry for misleading you.



Steve Schmechel wrote:
> 
> 
> I don't follow.  It seems that you are suggesting to replace megrok.form
> and/or z3c.widget with megrok.kss.  
> 
> Granted, that may work as an alternate way to get "enhanced form
> controls", but it doesn't fix the other packages or make the how-to
> documentation work.
> 
> Neither of my failed buildout attempts with megrok.form or z3c.widget
> pulled in any megrok.kss - as one would expect.
> 
> Am I missing something, or are you just recommending the use of megrok.kss
> in place of the functionality offered by the other two packages because it
> does not have a broken z3c.javascript dependency?
> 
> Thank you for taking the time to offer a suggestion.  That really is
> appreciated.
> 
> Steve
> 
> --- On Thu, 2/19/09, TonyXu <txu at userful.com> wrote:
> 
>> From: TonyXu <txu at userful.com>
>> Subject: Re: [Grok-dev] The z3c.widget is broken
>> To: grok-dev at zope.org
>> Date: Thursday, February 19, 2009, 11:57 AM
>> I met this problem too. My solution is simple. Just ignore
>> z3c.javascript. 
>> what you need to do for the next steps are:
>> 1. get rid of  z3c.widget from setup.py. 
>> 2. run build out again
>> 3. add path of "megrok.kss-0.2.1-py2.5.egg" into
>> <porject>/parts/app/runzope
>> if you are
>> using zopectl.
>> 
>> Because the previous failed buildout has already downloaded
>> the
>> megrok.kss-0.2.1-py2.5.egg,
>> you just need to add the egg into path manually.
>> 
>> 
>> 
>> Steve Schmechel wrote:
>> > 
>> > 
>> >> After adding z3c.widget into setup.py I run
>> Buildout and get error of not
>> >> able to download the z3c.javascript egg file.
>> > 
>> > This also effects megrok.form as it pulls in
>> z3c.widget.
>> > 
>> > So both of these how-tos lead you to this error:
>> >
>> http://grok.zope.org/documentation/how-to/automatic-form-generation/
>> >
>> http://grok.zope.org/documentation/how-to/make-use-of-add-ons-via-eggs/
>> > 
>> > Some questions:
>> > Why doesn't buildout find z3c.javascript?
>> > 
>> > Is "autoforms" something people really use,
>> or does everyone create their
>> > own custom form templates?  
>> > 
>> > I tried geoHUZ's work-around, but the
>> z3c.javascript package builds on
>> > it's own but not inside my grokproject app.
>> > 
>> > Maybe there should be an "everything in every
>> how-to" tar file so that the
>> > documentation keeps working.  (I know it's not
>> that easy, I'm just
>> > frustrated.)
>> > 
>> > I wanted to throw together a quick demo application
>> for someone and I
>> > thought "autoforms" would be a time-saver. 
>> Now I spent more time trying
>> > to make them work than I would have creating them by
>> hand.
>> > 
>> > Versions:
>> >   grok-1.0a1
>> >   python-2.5.2
>> >   Linux 2.6.27
>> > 
>> > 
>> > 
>> >       
>> > _______________________________________________
>> > Grok-dev mailing list
>> > Grok-dev at zope.org
>> > http://mail.zope.org/mailman/listinfo/grok-dev
>> > 
>> > 
>> 
>> -- 
>> View this message in context:
>> http://www.nabble.com/Re%3A-The-z3c.widget-is-broken-tp22017551p22106175.html
>> Sent from the Grok mailing list archive at Nabble.com.
>> 
>> _______________________________________________
>> Grok-dev mailing list
>> Grok-dev at zope.org
>> http://mail.zope.org/mailman/listinfo/grok-dev
> 
> 
>       
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> http://mail.zope.org/mailman/listinfo/grok-dev
> 
> 

-- 
View this message in context: http://www.nabble.com/Re%3A-The-z3c.widget-is-broken-tp22017551p22166046.html
Sent from the Grok mailing list archive at Nabble.com.