[Grok-dev] The z3c.widget is broken
Douglas Cerna
douglascerna at yahoo.com
Mon Feb 23 23:04:39 EST 2009
Did you try to add:
find-links = http://download.zope.org/distribution/
to your buildout.cfg file and rerun bin/buildout?
I guess z3c.javascript never had an egg in pypi. I fixed the error using that url.
I hope this helps you. Regards, Douglas
"... allí es cuando te das cuenta que las cosas malas pueden resultar bastante buenas..." - Lionel Messi
Por favor, evite enviarme adjuntos de Word, Excel o PowerPoint.
Vea http://www.gnu.org/philosophy/no-word-attachments.es.html
--- On Mon, 2/23/09, Steve Schmechel <steveschmechel at yahoo.com> wrote:
> From: Steve Schmechel <steveschmechel at yahoo.com>
> Subject: Re: [Grok-dev] The z3c.widget is broken
> To: grok-dev at zope.org, "TonyXu" <txu at userful.com>
> Date: Monday, February 23, 2009, 7:34 PM
> No problem.
>
> This does work, in as much as it allows the
> DropDownDateWidget to be used, but it does seem to be a bit
> of a hack.
>
> In the current paster environment, the egg path must be
> added to the "paster" script file. Every time you
> run buildout, this file is overwritten and you must add it
> again.
>
> Is there a way to add a specific egg reference in a static
> way?
>
> Adding a reference in buildout.cfg will pull in the
> dependencies just like setup.py (failing on z3c.javascript).
> Appending the path to project code doesn't work as the
> grokkers can't find the widget at configuration time.
>
> It also worries me that if I inadvertently decide to use
> the autocomplete or flashupload features of z3c.widget in my
> code, they do require z3c.javascript and will likely fail.
>
> How can we get z3c.javascript to work in a buildout? This
> must have worked at one time when the how-to's were
> written. (It mentions eggs.)
>
> What changed? Do things just disappear from the PyPI
> index?
>
> --- On Mon, 2/23/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: Monday, February 23, 2009, 11:27 AM
> > 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.
> >
> > _______________________________________________
> > 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
More information about the Grok-dev
mailing list