Re: GitHub migration

[Brendan Smith]

woohoo!  this is great,   good luck Adrian



Brendan Smith, IT Specialist
National Priorities Project
http://www.nationalpriorities.org
http://www.facebook.com/nationalpriorities
413 584 9556




On Apr 27, 2012, at 12:50 PM, Adrian Holovaty wrote:

> Hey guys, here's an important heads-up!
> 
> We're going to do the migration to GitHub today. This means we'll no
> longer be committing code to our Subversion repository. Committers,
> please hold off on making commits until the migration is done.
> 
> I expect it'll be done by late afternoon Chicago time. I'm going to do
> a dry run first to make sure all goes well, then I'll do the real
> thing.
> 
> Here are some random notes about the process --
> 
> * Any fork of the existing GitHub repository at
> https://github.com/django/django (which was a mirror of Subversion)
> will be broken. That is, it will no longer be able to get changes from
> upstream. Unfortunately, there's no way around this. But we'll provide
> some instructions here on django-developers on how to change your
> forks to use the new upstream repository in such a way that any of
> your local changes will be preserved. Worst case, you'll just have to
> generate a patch of your local branch's changes and apply it to a new
> fork.
> 
> * One interesting part of this is coming up with a definitive mapping
> between our old Subversion usernames and names/emails for Git. Brian
> Rosner and some other folks have done a great job of doing that
> research -- 
> https://github.com/brosner/django-git-authors/blob/master/authors.txt
> -- and we'll be using that file to convert committer data during the
> migration. Basically this means that if you've ever committed to
> Django, your commits will be associated with your current GitHub
> account -- as long as your GitHub account is associated with the same
> email address in that authors file. Due to the way Git works, there's
> no way of changing this data after the import is done. But we've
> accounted for everybody except two mysterious people "dcf" and "cell,"
> both of whom were given temporary commit bits during a sprint six
> years ago.
> 
> * If you're a Git/GitHub expert and are interested in helping, feel
> free to join us in #django-dev on Freenode.
> 
> * Thanks in advance for bearing with us during this process. There
> will be some pain, but it'll be worth it in the long run. I'm excited!
> 
> Adrian
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django developers" group.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/django-developers?hl=en.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: start using less (and bootstrap!)

[Brendan Smith]

i also regrettably give a +1 to github over bitbucket.   while I like others 
would love to see a python based solution, especially django, give github a run 
for it's money, i think github is years ahead of bitbucket in terms of features 
and ease of use.

i also think git itself is going to remain the king of the source control world 
for some time to come.  


On Feb 16, 2012, at 2:49 PM, Victor Hooi wrote:

> heya,
> 
> You know what, I have to say the same thing =).
> 
> BitBucket/Mercurial would seem like a better match.
> 
> Also, with the buy-out by Atlassian, they seem to be iterating more 
> frequently, in terms of features, and I would love to see a major Python 
> project, like Django, behind them.
> 
> Cheers,
> Victor
> 
> On Fri, Feb 17, 2012 at 02:02, Stan  wrote:
> 
> 
> On Feb 9, 1:49 pm, zalew  wrote:
> > > We're going
> > > to solve that with our move to Git/GitHub, which will make it much
> > > easier for people to fork and much easier for core developers to
> > > integrate contributions.
> >
> > a bit offtopic: why nothttp://bitbucket.org?similar features, it's on
> > python/django and already popular in django community.
> 
> +1 :-)
> 
> --
> You received this message because you are subscribed to the Google Groups 
> "Django developers" group.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/django-developers?hl=en.
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django developers" group.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/django-developers?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: start using less (and bootstrap!)

[Brendan Smith]

I had not heard about the move to GitHub but I am +10 on that move. 


On Feb 3, 2012, at 11:20 AM, Adrian Holovaty wrote:

> On Fri, Feb 3, 2012 at 12:25 AM, Harris Lapiroff
>  wrote:
>> The Django admin is a major—if not *the* major—selling point to
>> budding developers. I worry that externalizing it (hence making it a
>> *separate* piece of software that needs to be discovered and
>> installed, which seems simple but can be quite a challenge to new
>> coders) might take away Django's non-expert appeal. When I started
>> using Django, I knew no python. The only reason I was able to make
>> that work was because of the Django admin. If the admin gets kicked
>> out, I think it should be made *very* obvious where to find one.
> 
> I agree with this sentiment. I think separating the admin into a
> standalone app would be a step backward, at least at this point.
> 
> It strikes me that "the Django admin is hard for people to fork and
> modify" is a symptom of something else, not a problem in itself. The
> bigger problem is that our current development infrastructure
> (Subversion/Trac) doesn't allow for easy forking workflow. We're going
> to solve that with our move to Git/GitHub, which will make it much
> easier for people to fork and much easier for core developers to
> integrate contributions.
> 
> Before making any final judgment on separating the admin, we should
> see how our community's move to GitHub goes. I'm suspecting the pain
> points around forking will vanish at that point.
> 
> P.S. In case you haven't heard about the GitHub move, here's a blog
> post you should read: http://www.holovaty.com/writing/back-to-django/
> ETA is sometime soon after we launch 1.4.
> 
> Adrian
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django developers" group.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/django-developers?hl=en.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: start using less (and bootstrap!)

[Brendan Smith]

I give +1 to the idea of separating out the admin and letting people fork and 
modify to their hearts content

I also still give my +1 to having it utilize less, but I am also cautious like 
others about prescribing bootstrap specifically , especially the JS since as 
others have pointed out is somewhat unstable right now and not very easy to use 
at times (took me a long time to figure out modals)

Sent from my iPhone

On Feb 3, 2012, at 1:25 AM, Harris Lapiroff  wrote:

> The Django admin is a major—if not *the* major—selling point to
> budding developers. I worry that externalizing it (hence making it a
> *separate* piece of software that needs to be discovered and
> installed, which seems simple but can be quite a challenge to new
> coders) might take away Django's non-expert appeal. When I started
> using Django, I knew no python. The only reason I was able to make
> that work was because of the Django admin. If the admin gets kicked
> out, I think it should be made *very* obvious where to find one.
> 
> I'd be wary of putting them in core but I think using Bootstrap and
> Less for a new admin (whether internal or external) would make its
> development much faster. Dependencies should not be a problem. I think
> jQuery is a pretty apt analogy here. You probably won't write much
> javascript for the Django admin without learning jQuery. You can if
> you want to. But most people don't need or want to write javascript
> for the Django admin anyway. I think a framework like Bootstrap it
> would actually simplify adding new features. It provides so many CSS
> classes that there's a pretty good chance your feature wouldn't
> require you to write even a line of CSS. I was able to convert an
> unstyled app that I've been working on to functionally using Bootstrap
> in just about an hour after starting to learn it.
> 
> That having been said, I'd still be cautious with Bootstrap. It is a
> young piece of software that is incredibly impressive and mind-
> bogglingly easy to use, but obviously still in flux.
> 
> On Feb 2, 5:38 pm, Sean Brant  wrote:
>> On Thu, Feb 2, 2012 at 4:17 PM, Alex Gaynor  wrote:
>> 
>>> On Thu, Feb 2, 2012 at 5:01 PM, Adrian Holovaty  wrote:
>> 
 On Thu, Feb 2, 2012 at 2:49 PM, Sean Brant  wrote:
> Is this up somewhere public? I've been fighting the urge to do this as
> well. Using django-compressor with less on Heroku is a non-starter
> since you can't install node. Having this as a Python module would be
> handy.
>> 
 Not yet, alas, but hopefully soon.
>> 
 Adrian
>> 
 --
 You received this message because you are subscribed to the Google Groups
 "Django developers" group.
 To post to this group, send email to django-developers@googlegroups.com.
 To unsubscribe from this group, send email to
 django-developers+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/django-developers?hl=en.
>> 
>>> Perhaps this is too far in the future looking.  But at a certain point the
>>> admin must become a separate project.  One of the major goals of
>>> newforms-admin ('lo those years ago) was to demote the admin from special
>>> status, with hooks inside core left and right, to "just an app".  Let's
>>> carry that to the logical conclusion: just an app *outside of Django*.
>> 
>>> That gives the maintainers the freedom to reinvent it, and use tools like
>>> less or bootstrap without it needing to be an issue of policy for all of
>>> Django.  Because when I first read saw this thread my thought was, "Hmm,
>>> what unholy mess of requirements am I going to need if I want to just run
>>> the test suite.  Will I still be able to write new features in forms without
>>> needing to learn what the hell less or compass is?".  Several years ago, I
>>> opposed using jQuery in the admin, on the principle that Django should be
>>> completely free of entangling alliances.  I made that argument more or less
>>> out of habit, just because I felt it was an argument that ought to be made,
>>> but really I was pretty happy to get to use jQuery.  Now I'm saying, it's
>>> pretty clear that admin 2.0 (or 3.0, or 4.0, anyone counting?) is going to
>>> be a beast that far outstrips almost anything else in Djanog (besides the
>>> ORM ;)) in complexity, with more dependencies, more associated tooling, and
>>> more usecases (i.e. it's not just a tool for developers to use, it's also
>>> something for end users of *our* users' apps to use).  Keeping that in
>>> Django itself is going to stunt it's growth, and it's going to suck for new
>>> developers to Django who, like many of us (or at least myself), were and
>>> still are, Python developers at heart, who can write some HTML, badly.
>> 
>>> Alex
>> 
>>> --
>>> "I disapprove of what you say, but I will defend to the death your right to
>>> say it." -- 

Re: start using less (and bootstrap!)

[Brendan Smith]

for what's it worth, i really like the idea of this. 

i am also starting to use less for all of my projects and i love it.

 and for the record, with less.js it's not actually necessary to compile the 
.less files on the backend every time you make changes, you can have the 
compilation done on the front end and the browser will catch the results for 
future requests.



On Feb 2, 2012, at 2:28 PM, Ric wrote:

> hi, i want to propose a long term idea.
> 
> start using a less framework inside django.
> 
> i'm using bootstrap for my django app. it's really cool.
> 
> what i'am doing now is writing with less a new css to style django
> admin.
> 
> my idea is that django should provide a faster way to write an app,
> and while django is absolutely awesome for writing server side code,
> it does nothing to speed up css/html.
> 
> my idea is to write an app, with a setting object containing variables
> for less (colors and so on, font style ecc) and then compile a less
> for your current app.
> 
> a command like manage.py compileless could do the trick, and compile
> css code for your app.
> 
> django should provide an html base template (used in admin too) that
> is styled with a customizable less app.
> 
> it would be a great thing for django to give developers a fast start
> for new apps with a built in less framework.
> 
> i'm using bootstrap, and it's great, with a few settings an user could
> customize a base css, and do very cool things with few line of code.
> 
> i'm actually working to make it work with django, i hope it will be a
> cool app.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django developers" group.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/django-developers?hl=en.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Thoughts on defining and autoimporting signals.py

[Brendan Smith]

wrong list, you want django-users

but yes, you are on the right track with importing from __init__, at least 
that's how i've always done it 

-- 
Brendan Smith
IT Specialist
National Priorities Project
243 King Street Suite 109
Northampton, MA 01060
http://nationalpriorities.org/


On Wednesday, December 21, 2011 at 2:58 PM, Daniel Sokolowski wrote:

> Dear Django Developers,
> 
> Is there any consensus on where to define your signals for models and
> how to import them? I ask because to me it seems very odd that there
> doesn't appear to be a standard way to add your own signals and have
> them auto imported by the framework. I for example create a /
> project_root/project_app/signals.py file and auto import it in the
> __init__ of my project app.
> 
> I have read and searched the 
> https://docs.djangoproject.com/en/dev/topics/signals/
> however it fails short to provide any gudiance on this.
> 
> How do you do it, what are your thoughts on the making the auto import
> and signals.py file standard? Has this been already discussed?
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django developers" group.
> To post to this group, send email to django-developers@googlegroups.com 
> (mailto:django-developers@googlegroups.com).
> To unsubscribe from this group, send email to 
> django-developers+unsubscr...@googlegroups.com 
> (mailto:django-developers+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/django-developers?hl=en.
> 
> 


-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re:

[Brendan Smith]

lol

On Thu, Mar 31, 2011 at 6:47 PM, Rajendra Pondel <neosta...@gmail.com>wrote:

> Hi i m new to dejano?
>
> where can i find what it is?
>
> thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>


-- 
Brendan Smith, IT Specialist
National Priorities Project
http://www.nationalpriorities.org
http://www.costofwar.com
http://www.facebook.com/nationalpriorities
413 584 9556

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Brute force attacks

[Brendan Smith]

do you guys know about django-axes? (http://code.google.com/p/django-axes/)

it allows you to lock out IP or IP/User Agent combo on a given number of
failures.


On Fri, Mar 4, 2011 at 5:22 PM, Shawn Milochik <sh...@milochik.com> wrote:

> I have an immediate interest in this discussion. One of my company's
> Django apps was recently subjected to an external risk assessment team
> audit. They found the fact that three invalid password attempts didn't
> lock out the user to be completely unacceptable.
>
> Granted, this is something that I should have applied myself, and if
> it were automatically part of Django it would frustrate many
> developers because it would inconvenience their users.
>
> However, considering it's an OWASP concern, and likely a wheel which
> will be reinvented repeatedly, I would like to see it in Django. I am
> willing to put my time into the effort. If Rohit and his team end up
> taking on the project I will coordinate with them to see how I can
> help.
>
> It seems that any implementation of this would require another value
> for settings.py, and I know that's something not done lightly. Also,
> the thread referred to above discusses throttling, whereas the
> "recommendation" provided to us by the auditors was user lockout
> requiring administrator activity (human intervention) to unlock.
>
> So the next question is whether the core dev team is interested in
> discussing configurable lockout (number of attempts and human
> intervention or timeout to release the lock), throttling, or both.
> Then, how to best go about it.
>
> Incidentally, I'll be at PyCon if anyone wants to get together after
> hours to work on this during the main days (I won't be at the
> sprints).
>
> Shawn
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>


-- 
Brendan Smith, IT Specialist
National Priorities Project
http://www.nationalpriorities.org
http://www.costofwar.com
http://www.facebook.com/nationalpriorities
413 584 9556

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Multiple email connections

[Brendan Smith]

+1

On Tue, Feb 22, 2011 at 8:39 PM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:

> On Wed, Feb 23, 2011 at 9:02 AM, Niran Babalola <ni...@niran.org> wrote:
> > Multiple databases and caches can currently be configured in one's
> > settings file. It'd be nice if the same could be done with email
> > connections. For example, Amazon's SES starts out new users with a low
> > quota that they gradually increase, so splitting emails between SES
> > and other connections to start out with is a useful approach.
> >
> > Has any work been done on this? A quick Google turns up nothing. I've
> > written code that does most of this, but I wanted to make sure it has
> > general appeal before getting it in shape for a proper patch.
>
> I'm not aware of any work that has been done in this area.
>
> As you have noticed, we've been moving away from singletons where
> possible; DATABASES in Django 1.2, CACHES in Django 1.3.
> EMAIL_BACKENDS would be a logical next step. Most of the email APIs
> are already configured to allow for multiple email servers; it's
> really just a matter of changing the way that email settings are
> parsed in get_connection().
>
> So -- if you want to polish this up for a 1.4 feature, it could be an
> easy 1.4 feature.
>
> Yours,
> Russ Magee %-)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>


-- 
Brendan Smith, IT Specialist
National Priorities Project
http://www.nationalpriorities.org
http://www.costofwar.com
http://www.facebook.com/nationalpriorities
413 584 9556

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Template preprocessing (to improve template rendering speed, en page filesize)

[Brendan Smith]

Jonathan,   I don't know if this is the proper place to post this, unless
you are looking to have it added to core.  I have a feeling core
contributors are going to chime in and say this more than likely belongs the
in django-users mailing list.  When you post it there though, I for one
think this sounds like a great little project and will definitely e
interested in taking a look at this, if your company is willing to
open-source it.



On Fri, Oct 15, 2010 at 10:35 AM, Jonathan S wrote:

> Hi all,
>
> At my current job, I spent a week of programming on a preprocessor for
> Django templates.
> In short, what it does is compiling the templates in a more compact
> version, dropping all useless information and preprocessing
> templatetags where possible. The Apache benchmark tools showed a page
> load improvement up to twice as fast in Django 1.2, and 4 times as
> fast in the older Django version and HTML pages are now only half as
> big in filesize now.
>
> It is completely transparent, there are no changes needed to the
> templates, and should only be installed as a template loader (wrapping
> around the original loaders).
>
> What is does, in the Django language is:
> * preprocess {% trans %} and {% blocktrans %} when they don't take
> variables parameters. (the template loader will have a 'cache' for
> each language)
> * preprocess inheritance. Combining parent and child templates by
> replacing the blocks, and filling in {{block.super}}. {% block %} tags
> can be removed because all inheritance has been determined. (Note,
> this doesn't work with {% extends variable_name %}, but I think it's a
> bad idea to have variable inheritance. (but can be disabled if you
> would need it.)
> * preprocess {% include "path" %}, if path is not a variable.
> * grouping {% load statements %}
> * resolve all {% url %} when they don't take variable parameters.
> * preprocess {% now "Y" %}  (we will restart our server at least once,
> after a year transition. :p )
> * We have a few tags, like {% google_analytics %}, which constantly
> output the same code, this is implemented as a custom preprocessor
> extension for ourself.
>
> Now, if the template is HTML, we do a little more optimizations:
> * Remove all whitespace between block-level HTML tags
> * Removing empty class attributes, like class="", (which may appear as
> a result of class="{% block name %}{% endblock %}", where the child
> template din't implement the block.)
> * Merge all 

Re: Meebo - Seeking Django Developer (Contract & Telecommute is OK)

[Brendan Smith]

wrong list   see: django-us...@googlegroups

On Tue, Jul 20, 2010 at 1:50 PM, Kiko Griffin <k...@meebo-inc.com> wrote:

> Hello All,
>
> Please take a moment to review the job description below and share
> with your network.  We are seeking a contract Django Developer to join
> our UX team and work directly on developing the core site pages.  If
> interested, please reply to this email with your resume or LinkedIn
> profile.  I will be sure to follow up quickly if your background and
> experience matches the qualifications below.
>
> Django Developer (Contract):
> http://www.meebo.com/jobs/openings/djangodevcontractor/
>
> Meebo's Django Development Contractor will join the UX team and work
> directly on developing the core site pages. Our ideal candidate will
> have a passion for developing clean content-driven user interfaces, an
> eye for off-by-one pixel issues, and have ninja skills in the art of
> Django.
> This is a fantastic opportunity to apply your talents in a fun, fast
> paced startup environment. Members of our team tend to be nice,
> humble, genuine, and fun!
>
> Responsibilities include:
>
>* Work towards weekly and bi-weekly deadlines on the creation and
> development of high-visibility, high-quality content-driven user
> interfaces
>* Work collaboratively with developers and visual designers to
> create a compelling, well-built product
>* Assist in testing regularly scheduled releases
>* Willingness to have fun and be part of an exciting growing team!
>* Did we mention fun?
>
> Our ideal candidate will have:
>
>* 2+ years solid experience in building sites with Django
>* 2+ years of experience in HTML/CSS, visual/Web design
>* Degree in Human Computer Interaction, Computer Science (or equivalent)
>* Excellent communication and collaboration skills
>* A fastidious attention to detail (you noticed the double space
> in the intro paragraph)
>* Previous experience with DHTML, CGI, JavaScript, AJAX, Python
> and other Web applications a plus
>* An appreciation for visual design (e.g. color schemes,
> typography, and layouts)
>* An obsession with delivering the best user experience possible
>* A passion for visual design and Web technologies and the desire
> to work in a fast-paced, collaborative, and fun environment!
>* There is a possibility of this role becoming a regular full-time
> employee.
>
> I look forward to connecting with you soon!
>
> Thanks,
>
> Kiko
> k...@meebo-inc.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to django-develop...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com<django-developers%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>


-- 
Brendan Smith, IT Coordinator
National Priorities Project
http://www.nationalpriorities.org
http://www.costofwar.com
http://www.facebook.com/nationalpriorities
413 584 9556

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Multiple apps in one view

[Brendan Smith]

this should definitely be in django-users

look into *django-admin.py startapp twitter-gb* and start making your new
app


On Sat, May 22, 2010 at 9:13 AM, Jasper Kennis <tutorialhea...@gmail.com>wrote:

> Hi all,
>
> Can you run multiple apps in one view, and what would be the best way
> to do that.
>
> I've been having trouble doing this for a while, but maybe I'm
> conceptually wrong. I have a site that is an app, it doesn't have any
> db logics behind it (jet). I want to create a twitter-guestbook. In my
> opinion that twitter-guestbook should be an individual app, so that I
> could implement it in another site somewhere in the future, following
> the DRY principal and stuff. So I have my site app, and this guestbook
> app, and now I want the guestbook implemented in the site.
>
> Kind regards,
>
>
> Jasper Kennis
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to django-develop...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com<django-developers%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>


-- 
Brendan Smith, IT Coordinator
National Priorities Project
http://www.nationalpriorities.org
http://www.costofwar.com
http://www.facebook.com/nationalpriorities
413 584 9556

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.