Forest Bond escribió:
> On Sun, Jul 29, 2007 at 05:49:54PM -, Henrik Lied wrote:
>
>> @Forest: I agree, it should be that simple. But let's say you've got a
>> comment reply plugin. How would we - through a middleware - manage to
>> intercept our usual comment system, and modify the HTML te
On Sun, Jul 29, 2007 at 05:49:54PM -, Henrik Lied wrote:
> @Forest: I agree, it should be that simple. But let's say you've got a
> comment reply plugin. How would we - through a middleware - manage to
> intercept our usual comment system, and modify the HTML template
> source to fit the plugin
@Forest: I agree, it should be that simple. But let's say you've got a
comment reply plugin. How would we - through a middleware - manage to
intercept our usual comment system, and modify the HTML template
source to fit the plugin? It's cases like these I see the potential
pitfalls of our way of t
On Sat, Jul 28, 2007 at 03:28:31PM -, Henrik Lied wrote:
>
> Ok, so I've been thinking some more.
>
> The model could be something like this:
> class Plugin(models.Model):
> """(Plugin description)"""
> pointer = models.FilePathField() ## Could work, right?
> name = models.CharFie
Henrik Lied escribió:
> When you say "installs", do you mean that the plugin is retrieved from
> the external site, and placed somewhere on the users host, or is it
> constantly querying the plugin on a remote computer?
>
> The first of those two options would definitely be the best. But I'm
> hav
Ok, so I've been thinking some more.
The model could be something like this:
class Plugin(models.Model):
"""(Plugin description)"""
pointer = models.FilePathField() ## Could work, right?
name = models.CharField(maxlength=200)
description = models.TextField(blank=True, null=True)
When you say "installs", do you mean that the plugin is retrieved from
the external site, and placed somewhere on the users host, or is it
constantly querying the plugin on a remote computer?
The first of those two options would definitely be the best. But I'm
having some problems working it out
Henrik Lied escribió:
> This is great, Chris, but the fact of the matter is that it won't
> appeal to the "Wordpress crowd".
> That group wants in-browser setup, easy plugin architecture etc.
> contrib.admin wouldn't do the trick. The admin-panel would have to be
> hand made.
>
> For the plugin ar
This is great, Chris, but the fact of the matter is that it won't
appeal to the "Wordpress crowd".
That group wants in-browser setup, easy plugin architecture etc.
contrib.admin wouldn't do the trick. The admin-panel would have to be
hand made.
For the plugin architecture: I have no idea how we'd
I think I mentioned earlier in this thread, that I do have my take on
creating a blog here -
http://www.satchmoproject.com/trac/browser/satchmoproject.com/satchmo_website/apps
It's pretty full featured right now and makes use of the tagging and
comment_utils libraries. It still needs the feeds bu
This sounds great. I created a project on Google Code:
http://code.google.com/p/django-blog-engine/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-u
On 20 Jul 2007, at 8:49 pm, James Bennett wrote:
On 7/20/07, Rob Hudson <[EMAIL PROTECTED]> wrote:
#2 is particularly interesting to me because I've written a simple
blog in Django and there are some non-obvious things that having a
reference implementation to look at would be nice. Things l
Hi Kyle,
On 7/18/07, Kyle Fox <[EMAIL PROTECTED]> wrote:
>
> It's easy to write a "basic" blog in Django. If that's all people
> want, then great. Something like that will work perfectly for the
> majority of bloggers (who probably won't get that much readership
> anyway)...
>
> But all this ta
On 7/20/07, Rob Hudson <[EMAIL PROTECTED]> wrote:
> #2 is particularly interesting to me because I've written a simple
> blog in Django and there are some non-obvious things that having a
> reference implementation to look at would be nice. Things like:
To be fair, though, a lot of these things
A lot of the same arguments against making a standard blog project
could probably be applied to Rails, but here's a blog app in Rails...
http://simplelog.net/
I think an open-source Django blog project would be good because
1) It would be Usable to many (as evidenced by this thread and others
bef
Stefan Matthias Aust escribió:
> Chris,
>
> 2007/7/19, Chris Hoeppner <[EMAIL PROTECTED]>:
>
>> There would still be the problem of people wanting to
>> "one-click-install" plugins and themes. But why would such a person even
>> think about using a framework instead of wordpress?
>
> My point wa
Chris,
2007/7/19, Chris Hoeppner <[EMAIL PROTECTED]>:
> There would still be the problem of people wanting to
> "one-click-install" plugins and themes. But why would such a person even
> think about using a framework instead of wordpress?
My point was that - assuming the Django community wants
Stefan Matthias Aust escribió:
> If it is so easy to create a blogging application with Django, then
> this should be an argument for a standard application, not against it
> IMHO.
>
> At minimum, it could become a nice example application, either as part
> of the django distribution or as a separ
Why not start a Google code repository and see how many people want to
chip in and help. This comes up often enough that it sounds like
there's enough interest.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Djan
If it is so easy to create a blogging application with Django, then
this should be an argument for a standard application, not against it
IMHO.
At minimum, it could become a nice example application, either as part
of the django distribution or as a separate download. And if it is
still easy enou
It's easy to write a "basic" blog in Django. If that's all people
want, then great. Something like that will work perfectly for the
majority of bloggers (who probably won't get that much readership
anyway)...
But all this talk about making a "full-featured" blog app in Django --
one that will r
We don't need such an app (well, I don't need it).
If I want it, I write it in 20 minutes. :-)
Kai
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-use
On 18-Jul-07, at 11:31 AM, James Bennett wrote:
> So I'm not necessarily convinced that there's a great need for a
> "standard" Django blog application; it would appease some folks, but I
> have a feeling that in the Django world a lot of people really would
> be happier, in the long run, writin
I wrote a blogging system for myself that can be had through
subversion at this url: http://svn.karmazilla.net/hobby_projects/Djogg
I'm still looking for a good place to deploy my own instance, though.
I've kinda given up getting it to work in dreamhost.
On Jul 18, 8:01 am, "James Bennett" <[
On 7/18/07, Paulo <[EMAIL PROTECTED]> wrote:
> No to mention a good blog app that people can standardize on would be
> a nice alternative to Wordpress[1] and Simplelog[2]. Having one would
> definitely be helpful in the "spreading the word about Django"
> department.
I'm not entirely disintereste
No to mention a good blog app that people can standardize on would be
a nice alternative to Wordpress[1] and Simplelog[2]. Having one would
definitely be helpful in the "spreading the word about Django"
department.
We made the switch to Django/Python over a year ago for our client
work and it was
It's definitely a good idea to roll your own but it is helpful to see other
code to help you out. I'm in the process of adding a blog to satchmo and
have uploaded the code to svn but have not put it into production.
As it stands now, the code works but does not have comments enabled yet. If
noth
On 17 Jul 2007, at 11:37 am, Eratothene wrote:
There a lot of other features missing in such solution: comments, spam
protection, rss feeds and a lot more. I am searching for full featured
blog engine.
Django has it's own comment feature in contrib which with James
Bennett's comment-utils
There a lot of other features missing in such solution: comments, spam
protection, rss feeds and a lot more. I am searching for full featured
blog engine.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django user
Hi,
On 17 Jul 2007, at 10:15 am, Eratothene wrote:
Please, recommend me some full featured blog engines developed in
django.
Though, I have found some posts in this user group about available
blog engines, I still want to ask this question, as all posts are
dated summer 2006.
I don't see wh
Check out
http://www.23excuses.com/2006/Jul/07/23-excuses-release-and-introduction/
too.
Eric Lake
On Nov 16, 7:49 am, Picio <[EMAIL PROTECTED]> wrote:
> You can also try to build It yourself following this, It's funny! ;)
>
> http://www2.lamptraining.com/screencast/1
>
> Picio
>
> 2006/11/16, G
You can also try to build It yourself following this, It's funny! ;)
http://www2.lamptraining.com/screencast/1
Picio
2006/11/16, Guillermo Fernandez Castellanos
<[EMAIL PROTECTED]>:
>
> There is a few examples if you look in the mailing list:
> http://code.djangoproject.com/browser/djangoprojec
There is a few examples if you look in the mailing list:
http://code.djangoproject.com/browser/djangoproject.com/django_website/apps/blog
http://www.fallingbullets.com/blog/2006/nov/02/falling-bullets-source-code-you-ninnies/
http://www.rossp.org/blog/2006/may/15/django-magic-removal-upgrade/
http
33 matches
Mail list logo
