> *To: *>
> *ReplyTo: * django...@googlegroups.com
> *Subject: *Re: Comments in real time
>
> You could also look into the EventSource JavaScript API.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
>
Aug 2014 10:37:22
To:
Reply-To: django-users@googlegroups.com
Subject: Re: Comments in real time
You could also look into the EventSource JavaScript API.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this grou
You could also look into the EventSource JavaScript API.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to th
On 08/20/2014 05:11 PM, Aaron Reabow wrote:
> Hi all,
>
> I use a proprietary application that let people on multiple browsers
> comment.
>
> In real time their comments are displayed for everyone to see.
>
> What is quite nice, is that you can then order and group these comments.
>
> I have looked
Thanks bro! Just got the logic! Cheers. @Daniel keep up the good work,
even if you once hit me in the ass on StackOverflow! :)
On Feb 14, 3:47 pm, Tom Evans wrote:
> On Tue, Feb 14, 2012 at 2:45 PM, coded kid wrote:
> > Below the status. I'm not sure if I fixed this. How will I make it
> > displ
On Tue, Feb 14, 2012 at 2:45 PM, coded kid wrote:
> Below the status. I'm not sure if I fixed this. How will I make it
> display comment? Please.
>
This page has some hints:
https://docs.djangoproject.com/en/1.3/ref/contrib/comments/#displaying-comments
Cheers
Tom
--
You received this messag
Below the status. I'm not sure if I fixed this. How will I make it
display comment? Please.
On Feb 14, 12:32 pm, Daniel Roseman wrote:
> On Tuesday, 14 February 2012 12:02:58 UTC, coded kid wrote:
>
> > Hi guys, I'm using Django.contrib.comments in my Django web app. After
> > installing django c
On Tuesday, 14 February 2012 12:02:58 UTC, coded kid wrote:
>
> Hi guys, I'm using Django.contrib.comments in my Django web app. After
> installing django comments and setting up all other things, I decided
> to give it a try by commenting on my status.
>
> I commented and I was redirected to /c
Oh ok. Just render the comments as usual then use jquery of pure
javascript to hide it by default. Tie the link to the onclick event
such that it triggers the unhiding of the comment div. Simple.
On 2/13/12, coded kid wrote:
> Okay. Just like this. Comment
> Link Name
>
> Where "Comment Link N
On 02/13/2012 11:12 AM, Fabio Natali wrote:
http://stackoverflow.com/questions/1456267/django-comments-want-to-remove-user-url-not-expand-the-model-how-to/4766543#4766543
This link worked fine for me. :-)
--
Fabio Natali FNstudio
http://fnstudio.it
fabio_natali@skype
--
You received this mess
On 02/13/2012 11:44 AM:
Yeah, thanks for the reply. I followed the doc but it's not working
for me.
[...]
Hi there!
If you have an object my_object passed by your view to your template, I
think you can write:
{% load comments %}
{% get_comment_count for my_object as comment_count %}
{% get_co
Okay. Just like this. Comment
Link Name
Where "Comment Link Name" is the name you want to give to your link.
So when a user click on it, it should show the comment form on the
same page. I hope you now get my point?
On Feb 13, 1:26 pm, Babatunde Akinyanmi wrote:
> Please Rephrase. I don't get
Please Rephrase. I don't get the part of "comment link name"
On 2/13/12, coded kid wrote:
> Hi Guys, How can I link to “Django Comment form”, so that when a user
> clicks on the “Comment Link Name” It will display the Comment Form on
> the same page with the post. I hope you get my point? If you
Hey Fabio,
How do you get your comment form to display? Been fighting with this
for the past 5hrs. Please any idea? Thanks.
On Feb 13, 11:12 am, Fabio Natali wrote:
> On 02/13/2012 10:52 AM, Vovk Donets wrote:
>
> > It's not really great solution, but maybe it will give you a hint: you
> > can ad
On 02/13/2012 10:52 AM, Vovk Donets wrote:
It's not really great solution, but maybe it will give you a hint: you
can add/remove fileds to the form on the fly. And for not logged in
users show all fields, but for authenticated only subset of the all form
fields.
Ehi Vladimir, thank you for your
It's not really great solution, but maybe it will give you a hint: you can
add/remove fileds to the form on the fly. And for not logged in users show
all fields, but for authenticated only subset of the all form fields.
2012/2/13 Fabio Natali
> Hi everybody,
>
> I am using comments app from cont
You might want to use some logic involving anonymous users. See here:
http://docs.djangoproject.com/en/dev/topics/auth/#anonymous-users
On Sun, Dec 5, 2010 at 2:29 PM, andy wrote:
> Well you don't have to make the foreign key field required, that way
> comments belonging to guest users can have
Well you don't have to make the foreign key field required, that way
comments belonging to guest users can have a blank foreign key
Possibly you could also create a default guest user that is assign to
comments made by guest users. I generally having my application
depending on the creation of som
On Oct 21, 4:31 am, David De La Harpe Golden
wrote:
>
> Hmm. Appears to work okay for me (only tested Django-1.1.2), at least
> for instance.delete(). Perhaps you could try the operation directly at
> ./manage.py shell to see if there's anything odd going on:
>
Found the problem - I had overri
On 21/10/10 08:22, shacker wrote:
> Thanks David, but I'm not sure I'm getting this. I've added that line
> to the class, but it doesn't give me cascade delete behavior (I can
> still delete a row and the comments linked to it remain in the db). Is
> there something else I need to do?
Hmm. Appe
On Oct 19, 9:42 am, David De La Harpe Golden
wrote:
>
> So to get deletion behaviour you want, you need to define a reverse
> generic relation back to comment on your model for django's deletion
> cascade to follow the deletion in the generic case. On your own models,
> this is of course straig
On 19/10/10 17:16, shacker wrote:
> If Django comments are attached to a record (like a news item) and
> that item is deleted, the comment remains in the database. In other
> words, comments don't get cascade delete treatment like foreign key
> relationships do.
The django comments contrib uses t
One possibility is to add a post-delete signal which listens for
instances of news items and uses the content type to clean up comments
with that content type and primary key.
I'm pretty sure this isn't considered a bug, but I couldn't address
the issue of whether it was a planned part of the desi
Wow, I feel totally stupid... works like a charm now :)
On May 12, 2:14 pm, Karen Tracey wrote:
> On Wed, May 12, 2010 at 1:52 PM, Yanik wrote:
> > Hello,
>
> > I'm trying to do something that seemed simple, but can't get to work:
> > displaying comments using Django (1.2 RC)'s Comment framework
On Wed, May 12, 2010 at 1:52 PM, Yanik wrote:
> Hello,
>
> I'm trying to do something that seemed simple, but can't get to work:
> displaying comments using Django (1.2 RC)'s Comment framework inside a
> loop.
>
>
> {% for entry in entries %}
>{% get_comment_list for entry as comments %}
got some of this working, i'll leave this here so the next guy that
searches can find some info
install flatpages and comments, that much is easily found in the
django docs
flatpages comes with a field for enabling comments per flatpage, I'm
not sure how that control works yet this info below see
I used a cheap hack. The comment object has an ID of the item that the
comment was attached to. You can then give users a link to that to
click, or auto-redirect them to that. If you use slugs, you can create
a view that catches that ID, grabs the slug, and thus redirects them
again to the origina
On Thu, Nov 5, 2009 at 2:30 PM, David wrote:
> Is it possible to redirect upon successful comment submission to the
> previous page when using Djangos built in render_comment_form ?
>
I'm not sure if there's a more direct way, but you can override the
"comment_done" named URLconf with a custom v
On Sep 22, 11:15 pm, Daniel Roseman wrote:
> On Sep 22, 2:07 pm, RodneyTopor wrote:
>
> > Suppose a user posts a comment about a particular object, using
> > django.contrib.comments, as described in Practical Django Projects.
> > How can one get access to this object in a template such as
> > pos
On Sep 22, 2:07 pm, Rodney Topor wrote:
> Suppose a user posts a comment about a particular object, using
> django.contrib.comments, as described in Practical Django Projects.
> How can one get access to this object in a template such as
> posted.html, so that one can include a link directly back
Looks like the next parameter doesn't really work though.
See:
http://groups.google.com/group/django-users/browse_thread/thread/109763039cef5c3d/470d678e46d7dfe0?hl=en&lnk=gst
And: http://code.djangoproject.com/ticket/8968
2009/6/3 Ian Lewis
> Iperk,
>
> Is this perhaps what you are looking for
Iperk,
Is this perhaps what you are looking for?
http://docs.djangoproject.com/en/dev/ref/contrib/comments/#redirecting-after-the-comment-post
On Mon, Jun 1, 2009 at 6:38 AM, lperk wrote:
>
> Does someone know how to redirect posted comment to another page if
> you have your own form for sendi
Does someone know how to redirect posted comment to another page if
you have your own form for sending comments?
On May 31, 9:55 pm, lperk wrote:
> Hey.. I'm trying to send comment with django comments option and
> everything is ok..I see it form..but when I send comment I got error:
>
> Comment
Hi,
> You don't say what version of Django you are using. This sounds like you
> want exactly the kind of customization described here:
>
> http://docs.djangoproject.com/en/dev/ref/contrib/comments/custom/
Yes, I already following it, but with 1.0.2 django version :)
> That page doesn't exist i
On Wed, Apr 1, 2009 at 3:05 PM, Michel Thadeu Sabchuk wrote:
> I created a custom comments app to make use of captcha. I didn't
> change the mode, I just change the form to make use of django-simple-
> captcha [1].
>
> To make all magic works I need to do some hacks in django comments
> framework.
I found a better way to hack :)
In the django.contrib.comments.__init__ file, I changed the get_model,
get_form and get_form_target method to something like:
def get_form():
if get_comment_app_name() != __name__ and hasattr(get_comment_app
(), "get_form"):
return get_comment_app().ge
Well, to answer with my current solution:
> My one idea is to intercept comments/posted/?c=... and then write a view to
> redirect back to the original page. Is this the route to take?
I did this:
urls.py
# Catch url for comment just posted (preview or error)
(r'^wiki/comments/posted/.*$','othe
OK - this was more or less resolved by following the advice here:
http://tinyurl.com/63rd76 This allowed me to essentially check for
valid comment deletion permissions before forwarding to the main
comment delete view. The only difference was my wrapper view; I
checked if the currently-logged-in u
Maybe a little brevity is in order - how do I grant temporary
privileges to a user to delete a comment rather than keeping that
power fully in the hands of a comments moderator?
- Tim
On Jan 3, 7:23 pm, Tim wrote:
> Hi all -
>
> I am having a bit of difficulty with the Django comments framework
jrivero wrote:
> yes! but the previous solution was useful to paginate the result with
> a another templatetag
>
> {% get_comment_list for entry as comment_list reversed %}
> {% paginate comment_list 10 as page using comment_list_page %}
> {% for comment in comment_list_page %}
> comment.commen
yes! but the previous solution was useful to paginate the result with
a another templatetag
{% get_comment_list for entry as comment_list reversed %}
{% paginate comment_list 10 as page using comment_list_page %}
{% for comment in comment_list_page %}
comment.comment
{% endfor %}
what method u
jrivero wrote:
> Is possible obtain the comments of django.contrib in reversed order?
>
> In old version:
> {% get_free_comment_list for workgroups.workgroup group.id as
> comment_list reversed %}
>
> But in new version the templatetag not have control of this parameter.
> The method for order is
On Fri, Sep 26, 2008 at 6:31 AM, Janmansilver <[EMAIL PROTECTED]> wrote:
>
> I have tried to implement comments in a blog I'm building with this in
> my template:
...
> In template /home/weiter/webapps/django_v1/lib/python2.5/django/
> contrib/comments/templates/comments/form.html, error at line 2
Bobby Roberts wrote:
> What would I attach to using this form statement as a
> starting point:
>
> {% render_comment_form for [object] %}
>
> ie what should the object be?
Semantically comments application is not intended for creating new
first-class data on your site, so the fact that you have
Wiadomość napisana w dniu 2008-09-08, o godz. 19:13, przez Thejaswi
Puthraya:
>> Is there any document with new comment framework customization tips?
>> I'd like to switch finally to 1.0 but I don't know how to accomplish
>> few things (or have ugly workarounds):
>
> Well, that is one feature t
On Sep 8, 2:47 pm, Jarek Zgoda <[EMAIL PROTECTED]> wrote:
> Is there any document with new comment framework customization tips?
> I'd like to switch finally to 1.0 but I don't know how to accomplish
> few things (or have ugly workarounds):
Well, that is one feature that hasn't been documente
Jarek Zgoda wrote:
> Is there any document with new comment framework customization tips?
> I'd like to switch finally to 1.0 but I don't know how to accomplish
> few things (or have ugly workarounds):
>
> * do not display preview page after succesful posting of comment, go
> to commented
Wiadomość napisana w dniu 2008-09-08, o godz. 14:19, przez Julien
Phalip:
>> * do not display preview page after succesful posting of comment, go
>> to commented document instead (currently I have redirecting view and
>> handle it in my urlconf before urlconf of django.contrib.comments is
>> i
Jarek Zgoda wrote:
> Is there any document with new comment framework customization tips?
> I'd like to switch finally to 1.0 but I don't know how to accomplish
> few things (or have ugly workarounds):
>
> * do not display preview page after succesful posting of comment, go
> to commented docume
Ok, it looks like the comments aren't listing in the admin either, I'm
guessing the admin uses the same function to list them. Is there
something wrong with my database maybe?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google G
Where would you propose i do this?
On Jun 18, 12:15 pm, "Michael Wieher" <[EMAIL PROTECTED]>
wrote:
> did you try fiddling with the backslashes? django is ... clumsy with
> backslashes and urls. the trailing backslash in particular
>
> On Wed, Jun 18, 2008 at 11:09 AM, joshuajonah <[EMAIL PROT
did you try fiddling with the backslashes? django is ... clumsy with
backslashes and urls. the trailing backslash in particular
On Wed, Jun 18, 2008 at 11:09 AM, joshuajonah <[EMAIL PROTECTED]> wrote:
>
> Tried switching it to a normal object_detail generic view, same issue.
> >
>
--~--~--
Tried switching it to a normal object_detail generic view, same issue.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubs
levi,
the following website has a good example online
http://www.b-list.org/weblog/2006/07/16/django-tips-hacking-freecomment
cornelius
Levi McCallum schrieb:
> Hi,
>
> I have been looking into building my first Django project, and I guess
> a blog was the most simplest thing I could think of
On 12/23/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
There might be some work on the comment views to make them use the
newforms framework, but other than that, I can't say I know of any
work that is planned.
I know that the idea of "pluggable" comment models keeps coming up
(where we'd
Thanks, guys -- developer list it is
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send
On 21-Dec-06, at 2:09 AM, ringemup wrote:
Before I start seriously hacking the comments framework or
implementing
a replacement, I was wondering if anyone knows if any further work is
being done on the comments framework, and if so, what's planned, or
where I could find any more info?
chec
On 12/21/06, ringemup <[EMAIL PROTECTED]> wrote:
Hi folks --
Before I start seriously hacking the comments framework or implementing
a replacement, I was wondering if anyone knows if any further work is
being done on the comments framework, and if so, what's planned, or
where I could find any
On 11/30/06, hotani <[EMAIL PROTECTED]> wrote:
> I noticed in the most recent documentation that we should now be able
> to use the {# comment #} multi-line commenting tags in templates.
> However, after doing an 'svn update' and restarting apache it does not
> seem to be available. Which begs the
Sorry, back from a trip.
Happy to see that some people tried it and that it works. Thanks!
> I've been looking at this as well. It appears that the ratings and
> comments are tied together and must be submitted together. Is this
> true? I'd like a user to submit a comment along OR rate it OR
I 'm a little bit sad about django has some part without document and
test.
we'd better add patch for them. and it's hard to refactor code in trunk
if you're not the main author.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Goo
I 'm a little bit said about django has some part without document and
test.
we'd better add patch for them. and it's hard to refactor code in trunk
if you're not the main author.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Go
patrickk wrote:
> as far as I know, rating only works with submitting a comment. you
> could probably change this by hacking the comment-manipulator.
> nevertheless, since ratings are stored in the comments-table, you get
> the wrong numbers when you do "comment_count".
> for what you want to do
On Wed, 2006-10-25 at 03:58 -0700, timc3 wrote:
> I have successfully managed to integrate the comments system into my
> Django application and its looking good (with some YUI ajax nonsense to
> top it off). But one thing that I would like is non-registered,
> non-logged in users to be able to po
as far as I know, rating only works with submitting a comment. you
could probably change this by hacking the comment-manipulator.
nevertheless, since ratings are stored in the comments-table, you get
the wrong numbers when you do "comment_count".
for what you want to do I´d suggest to write
I've been looking at this as well. It appears that the ratings and
comments are tied together and must be submitted together. Is this
true? I'd like a user to submit a comment along OR rate it OR both.
Is that possible?
--~--~-~--~~~---~--~~
You received this m
sorry, my fault ... with following your tutorial everything´s fine ...
thanks,
patrick
Am 24.10.2006 um 18:47 schrieb patrickk:
>
> thanks for the tutorial.
>
> I did exactly what is described there and ran into a (small) problem:
>
> give karma results in
> This comment has 1 points of karma,
thanks for the tutorial.
I did exactly what is described there and ran into a (small) problem:
give karma results in
This comment has 1 points of karma, 1 positive and 0 negative.
take karma results in
This comment has 1 points of karma, -1 positive and 1 negative.
any ideas?
thanks,
patrick
Hi,
Thanks for all your answers. I have found them all useful.
I am studying right now the code and the Jeff Lost-Theories code (and
will look fo other examples in other projects). It is indeed a very
helpful example! I will try to write a bit about what I find.
Baxter, concerning the Karma fun
Guillermo,
here have many projects created with Django that you can download and know it:
http://code.google.com/hosting/search?q=label:django
http://code.djangoproject.com/
2006/9/13, DavidA <[EMAIL PROTECTED]>:
>
>
> Guillermo Fernandez Castellanos wrote:
> > I am thinking of using the commen
Guillermo Fernandez Castellanos wrote:
> I am thinking of using the comments framework for a project, although
> besides the FreeComment there's no real documentation about it that I
> have found besides the source.
This might help:
http://www.b-list.org/weblog/2006/07/16/django-tips-hacking-fre
Yup, Jeff's code uses it, and I'm using it, but I'd be the first to
admit I don't really know what's going on. I'd love to implement the
Karma functions, but don't have a clue.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Googl
On 9/13/06, Guillermo Fernandez Castellanos > My questions are:
> - Did someone use it in a project accesible to others so I can get
> inspired from his example?
Jeff made the source code behind his lost-theories.com site available
freely, and IIRC it uses the registered comments system. See here
That's right! Thanks for spotting this silly mistake.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this
Patrick J. Anderson wrote:
> {% load comments.comments %}
>
>
> {% for p in latest %}
> {% get_free_comment_count for blog.post object.id as comment_count
> What could be the reason for failed lookup on key[id]?
Shouldn't that be 'p.id' rather than 'object.id' in the
get_free_comment
I have the same problem here. Manage to follow the tutorial till part
3. And any comments made to a particular post actually shown in all
posts. Still try to solve this problem. Guess Bryan advice might be
helpful, should look into details how django blog example in
code.djangoproject.com.
--~--
On 3/11/06, PythonistL <[EMAIL PROTECTED]> wrote:
>
> Does anyone use successfully Comments module(django.contrib.comments).
> I followed tutorial about blog at
> http://www.rossp.org/blog/2006/jan/23/building-blog-django-1/
> but the blog that uses comments module does not work properly for me.
>
Andrew Gwozdziewycz wrote:
> Hello,
>
> I'm trying to use the contrib.comments in the magic-removal branch.
> I'm running into some problems though...
>
> {% get_free_comment_list for excuses.topic topic.id as
> comment_list %}
>
> Is the part that is failing. This was adapted from the
>
On Wednesday 21 Dec 2005 5:35 am, iGL wrote:
> I must have missed it in the doc. Would you like to give me the
> corresponding link?
look for 'legacy database' in the docs
--
regards
kg
http://www.livejournal.com/users/lawgon
tally ho! http://avsap.org.in
ಇಂಡ್ಲಿನಕ್ಸ வாழ்க!
I must have missed it in the doc. Would you like to give me the
corresponding link?
TIA,
Giorgi
Kenneth Gonsalves wrote:
> On Wednesday 14 Dec 2005 5:34 pm, [EMAIL PROTECTED] wrote:
> > native method (SQL). I'd much rather build my database up using
> > a nice GUI then get Rails to 'plug' into
braver wrote:
> I was reading
>
> http://www.loudthinking.com/arc/000545.html
>
> and it has an emphasis on Ruby's "beauty", and parsimony, as
> demonstrated by the code excerpt (David: "I was more surprised to learn
> that someone would actually prefer something like"):
>
> class Project(meta.
If anyone is interested in more on this very topic:
http://blog.ianbicking.org/more-on-python-metaprogramming.html
Same discussion as here.
On 12/15/05, Robert Wittams <[EMAIL PROTECTED]> wrote:
> Personally, I think class attributes are fine.
Also given how Django describes the schema and from there builds the
database as opposed to RoR which wants you to design the database up
front, I think the names of the Django functions like
Po
braver wrote:
> A symbol which is a unique string is not the story here, it turns out
> -- dynamic language is!
>
> has_many :milestones
>
> is apparently a call which generates code inside of the class! Can it
> be replicated in python for ORM purposes?
>
>
Not really. Read up on metaclasse
A symbol which is a unique string is not the story here, it turns out
-- dynamic language is!
has_many :milestones
is apparently a call which generates code inside of the class! Can it
be replicated in python for ORM purposes?
Afternoon wrote:
On 14 Dec 2005, at 12:04, [EMAIL PROTECTED] wrote:
Its another surplus layer which complicates the process.
That's one way to look at it, but the other is that the Django model
contains more information than an SQL create statement. It centralises
all information abou
On 12/14/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> True. SQL was designed and has continued development for the sole
> purpose of data manipulation. Why then replace SQL with Python to
> describe this data structure.
For me, it's a question of portability; even though SQL is a
"standar
True. SQL was designed and has continued development for the sole
purpose of data manipulation. Why then replace SQL with Python to
describe this data structure.
On 12/14/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> True a GUI can't totally replace hand coded SQL. However, it certainly
> speeds a lot of the process up. Fine tuning can be done afterwards.
Guess that is a very subjective measurement. Working out the model in
Django's models/ direc
True a GUI can't totally replace hand coded SQL. However, it certainly
speeds a lot of the process up. Fine tuning can be done afterwards.
On 14 Dec 2005, at 12:04, [EMAIL PROTECTED] wrote:
Its another surplus layer which complicates the process.
That's one way to look at it, but the other is that the Django model
contains more information than an SQL create statement. It
centralises all information about the layout and con
Kenneth Gonsalves wrote:
On Wednesday 14 Dec 2005 5:34 pm, [EMAIL PROTECTED] wrote:
native method (SQL). I'd much rather build my database up using
a nice GUI then get Rails to 'plug' into it. Instead with Django
you have to code a database structure in Python which Django then
produces u
On Wednesday 14 Dec 2005 5:34 pm, [EMAIL PROTECTED] wrote:
> native method (SQL). I'd much rather build my database up using
> a nice GUI then get Rails to 'plug' into it. Instead with Django
> you have to code a database structure in Python which Django then
> produces using SQL.
you can code
There's little difference then. In Django you write Python code to
represent your database. In RoR you produce the database first in its
native method (SQL). I'd much rather build my database up using a nice
GUI then get Rails to 'plug' into it. Instead with Django you have to
code a database
On 12/13/05, braver <[EMAIL PROTECTED]> wrote:
>
> Um, I guess I wonder what it "means" in terms of syntactic sugar -- the
> semantics is clear, and that's the claimed ruby's hallmark. I don't
> yet have a handle on those "symbol" things like :poll ("they're like
> strings" --huh?), and what's be
Um, I guess I wonder what it "means" in terms of syntactic sugar -- the
semantics is clear, and that's the claimed ruby's hallmark. I don't
yet have a handle on those "symbol" things like :poll ("they're like
strings" --huh?), and what's belongs_to? I wonder what would be the
closest pythonic sy
On 12/13/05, braver <[EMAIL PROTECTED]> wrote:
> OK, can someone please explain to a pythonista what exactly does a
> phrase like
>
> has_many :milestones
>
> mean, and what in python prevents us from mimicking it more closely?
It's expressing a many-to-many or many-to-one relationship. For
examp
OK, can someone please explain to a pythonista what exactly does a
phrase like
has_many :milestones
mean, and what in python prevents us from mimicking it more closely?
On 12/13/05, braver <[EMAIL PROTECTED]> wrote:
> and it has an emphasis on Ruby's "beauty", and parsimony, as
> demonstrated by the code excerpt (David: "I was more surprised to learn
> that someone would actually prefer something like"):
Except David glosses over an awful lot in that example; be
Alexy,
although I am not Adrian, I still felt compelled to comment. :)
On 12/13/05, braver <[EMAIL PROTECTED]> wrote:
> class Project(meta.Model):
> project_manager = meta.ForeignKey(ProjectManager)
> milestones = meta.OneToOneField(Milestone)
> categories = meta.ManyToManyField(Category)
>
100 matches
Mail list logo
