> Can you be specific on how the current setup is preventing you from
> getting it done?
I think the easiest way is to look at my code on bitbucket, for
example my models.py:
https://bitbucket.org/bolhoed/django_disqus_comments/src/b2c6fbb025f6/models.py.
As you can see, I have to hack my own mod
Hi,
I am the student who worked on improving the comments framework a
couple of years back and have been absconding since then ;-)
Personally, I would love to see the comments app out of contrib
because of the need to maintain backwards compatibility especially for
an app with very few users.
On
cus attempts out there--have you looked at them? I haven't
> > bothered to notice if any use the comments framework but it sure would
> > be handy to make comments out of discus or backtype feeds or variants
> > thereof.
>
> > But whether it was in trunk or just somewhere on
lready put a few hours doing something like this. There's some
> django-discus attempts out there--have you looked at them? I haven't
> bothered to notice if any use the comments framework but it sure would
> be handy to make comments out of discus or backtype feeds or variants
>
Heh, already put a few hours doing something like this. There's some
django-discus attempts out there--have you looked at them? I haven't
bothered to notice if any use the comments framework but it sure would
be handy to make comments out of discus or backtype feeds or variants
the
On Sun, Nov 28, 2010 at 9:17 AM, Jamie Rumbelow wrote:
> Hello All,
> Kevin's got a point, and actually, why aren't Django's components abstracted
> as a generic rule? Things like django.contrib.session and
> django.contrib.comments could be easily abstracted to allow for pluggable
> drivers into
asy to make
backward-compatible and would be VERY helpful.
My best,
Jamie
On 27 November 2010 23:55, Kevin Renskers wrote:
> Hi,
>
> I'd like to make a suggestion about the build in comments framework.
> Right now, even though you can write your own extension to the
> comments
Hi,
I'd like to make a suggestion about the build in comments framework.
Right now, even though you can write your own extension to the
comments framework, it is always tied to database models. I am trying
to build an extension that uses the API offered by Disqus, meaning I
don't want
On Sat, Mar 27, 2010 at 2:31 AM, subs...@gmail.com wrote:
>> > 3) Models hoping to foreignkey to whatever comments model the app
>> I'm not sure what you're saying here. Are you complaining about the
>> way that we've implemented this particular feature, or about some edge
>> case that you've fou
> I can't think of any reason that a production server should behave
> differently to a development server on the sorts of issues you're
> referring to. If there's a problem, I would be highly surprised if
> it's caused by the fact you're running under wsgi, rather than the
> devserver. There may b
On Thu, Mar 25, 2010 at 4:36 PM, subs...@gmail.com wrote:
> I got myself into a situation with a project and some comments models.
> Perhaps with some discussion we can uncover genuine code-bugs, but my
> knowledge about this is limited and so I'm just calling for a
> documentation update. A major
I got myself into a situation with a project and some comments models.
Perhaps with some discussion we can uncover genuine code-bugs, but my
knowledge about this is limited and so I'm just calling for a
documentation update. A major reason I'm asking for some notice of
these things to appear somewh
Thanks for the reply. I have created a ticket (http://
code.djangoproject.com/ticket/9819). And added a small patch.
More patches to come.
On Dec 8, 10:10 pm, "Jacob Kaplan-Moss" wrote:
> On Mon, Dec 8, 2008 at 4:20 AM, Kegan wrote:
> > Is there an active effort in working on the docs?
>
> The
On Mon, Dec 8, 2008 at 4:20 AM, Kegan <[EMAIL PROTECTED]> wrote:
> Is there an active effort in working on the docs?
The fundamental rule of software is that the documentation always
needs improvement; django.contrib.comments is no exception.
Patches welcome!
Jacob
--~--~-~--~~
The documentation for Comments Framework,
http://docs.djangoproject.com/en/dev/ref/contrib/comments/
seems to be lacking. The things that are missing in the docs comparing
to what I found in the source code, django.contrib.comments, namely:
. flagging
. moderation/approval
. deletion
Is there
On Apr 22, 12:15 pm, SmileyChris <[EMAIL PROTECTED]> wrote:
> On Apr 22, 1:15 pm, Thejaswi Puthraya <[EMAIL PROTECTED]>
> wrote:
>
> > Hello Django Developers,
>
> > I plan to assist Jacob complete a major portion of the ToDo [1] list
> > that he has at the current moment. Hopefully by the end of
On Apr 22, 1:15 pm, Thejaswi Puthraya <[EMAIL PROTECTED]>
wrote:
> Hello Django Developers,
>
> I plan to assist Jacob complete a major portion of the ToDo [1] list
> that he has at the current moment. Hopefully by the end of this
> summer, the django-newcomments framework will be able to make qui
.
Here is a little bit more about my project:
Purpose of the project
---
Django comes with a comments framework that makes embedding comments
in apps very easy. Jacob Kaplan Moss is writing a replacement for the
comments framework that is intended to replace the current
On 5/6/07, Honza Král <[EMAIL PROTECTED]> wrote:
> I know Jacob was planning on rewriting the comments framework to work
> with newforms. Is there any work done there?
I believe the plan is -- much as with newforms-admin -- to take
advantage of the rewrite and build more flexibil
y? We have no problem committing to
maintaining the features in the long run - we will have to do that
anyway internally, it would only make things easier for us to do that
in django and avoid maintaining our own patch set...
I know Jacob was planning on rewriting the comments framework to work
20 matches
Mail list logo
