Re: start using less (and bootstrap!)
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." -- Evelyn Beatrice Hall (summarizing Voltaire)
> > "The people's good is the highest law." -- Cicero
>
> > --
> > 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.
>
> +1
>
> Given how flexible the admin is doing somethings is still pretty
> annoying. I feel like if it was a external project with its own
> release schedule more pro
Re: start using less (and bootstrap!)
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." -- Evelyn Beatrice Hall (summarizing Voltaire)
> "The people's good is the highest law." -- Cicero
>
> --
> 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.
+1
Given how flexible the admin is doing somethings is still pretty
annoying. I feel like if it was a external project with its own
release schedule more progress could be made. FWIW i'm experimenting
with an admin interface that relies heavily on class based views. So
far I like it. CBVs seem to have more useful hooks then the admin
currently has. At the very least I think the new admin needs to not be
backwards compatible with the current admin.
So my vote is for django-admin2 as an external project.
--
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!)
I'm sure Idan can add to this if he cares to, but at Djangocon kicking the
admin out of django.contrib for admin2 was something that was actively
considered, both during development and, depending on how it worked out,
possibly as its new home.
I'm massively +1 on that because it does allow a lot of "freedom" to people
wanting to experiment with it and new ways of handling administrative tasks.
-T
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." -- Evelyn Beatrice Hall (summarizing Voltaire)
> "The people's good is the highest law." -- Cicero
>
> --
> 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.
>
--
Travis Swicegood | @tswicegood (most everywhere) | Senior Open Source
Engineer @ Texas Tribune / Armstrong | 512.693.7051
--
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!)
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." -- Evelyn Beatrice Hall (summarizing Voltaire)
"The people's good is the highest law." -- Cicero
--
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!)
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.
Re: start using less (and bootstrap!)
On Thu, Feb 2, 2012 at 2:16 PM, Adam "Cezar" Jenkins wrote: > ... > As far as core. Bootstrap should be a 3rd party app, but possibly having > less support in core might be helpful. > > > Funny how that reads. Perhaps for clarity it should say but ' ... possibly having support for "less" in core might be helpful.' But then again, my English usually leaves a lot to be desired. -- 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!)
A note that if you use the project django-compressor you can put something
like the following into your templates and it will automatically compile
the less
{% compress css %}
{% endcompress %}
No need to compile by hand.
A note about bootstrap. I'm using it for my project and I've run across
some pretty glaring bugs in the javascript it ships with. They don't keep
the master branch stable, and are in the middle of merging the 2.0 work in
progress branch into master. So there is a little bit of instability. Not
the end of the world though, I still recommend it.
As far as core. Bootstrap should be a 3rd party app, but possibly having
less support in core might be helpful.
On Thu, Feb 2, 2012 at 2:36 PM, Adrian Holovaty wrote:
> On Thu, Feb 2, 2012 at 2:07 PM, Idan Gazit wrote:
> > * less.js has the distinct advantage of being easier to develop for than
> > sass for our purposes.If we go with a less.js solution (like bootstrap),
> we
> > might not need to require that all edits to admin "source" stylesheets
> > (less/scss) come with the recompiled CSS. This lowers the barrier to
> > contribution significantly, at the cost of a bit of site performance as
> less
> > gets compiled client-side. That being said, the admin isn't supposed to
> be
> > used as a a high-traffic site (or shouldn't be, I can't say how people
> abuse
> > it).
>
> Two points:
>
> * If we decide to change the admin site to use LESS, we should ship
> compiled CSS. No need to introduce the less.js overhead.
>
> * I have been working on a Python LESS compiler in my spare time, and
> there could be a use for it in here.
>
> 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!)
On Thu, Feb 2, 2012 at 2:36 PM, Adrian Holovaty wrote: > On Thu, Feb 2, 2012 at 2:07 PM, Idan Gazit wrote: >> * less.js has the distinct advantage of being easier to develop for than >> sass for our purposes.If we go with a less.js solution (like bootstrap), we >> might not need to require that all edits to admin "source" stylesheets >> (less/scss) come with the recompiled CSS. This lowers the barrier to >> contribution significantly, at the cost of a bit of site performance as less >> gets compiled client-side. That being said, the admin isn't supposed to be >> used as a a high-traffic site (or shouldn't be, I can't say how people abuse >> it). > > Two points: > > * If we decide to change the admin site to use LESS, we should ship > compiled CSS. No need to introduce the less.js overhead. > > * I have been working on a Python LESS compiler in my spare time, and > there could be a use for it in here. 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. > 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: Clarifications to ready for checkin policy / PEP-8 line lengths
On Mon, Jan 30, 2012 at 5:24 PM, Anssi Kääriäinen wrote: > And now for something completely different: what is the current view > of PEP-8 regarding line lengths? It seems lines longer than 80 > characters have been checked in somewhat regularly. How long lines are > OK, then? Yes, long line lengths are totally fine (and encouraged if it means more readable code). It's the year 2012. 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.
Re: start using less (and bootstrap!)
On Thu, Feb 2, 2012 at 2:07 PM, Idan Gazit wrote: > * less.js has the distinct advantage of being easier to develop for than > sass for our purposes.If we go with a less.js solution (like bootstrap), we > might not need to require that all edits to admin "source" stylesheets > (less/scss) come with the recompiled CSS. This lowers the barrier to > contribution significantly, at the cost of a bit of site performance as less > gets compiled client-side. That being said, the admin isn't supposed to be > used as a a high-traffic site (or shouldn't be, I can't say how people abuse > it). Two points: * If we decide to change the admin site to use LESS, we should ship compiled CSS. No need to introduce the less.js overhead. * I have been working on a Python LESS compiler in my spare time, and there could be a use for it in here. 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.
Re: start using less (and bootstrap!)
On Thursday, February 2, 2012 at 3:07 PM, Idan Gazit wrote: > The next major revision of the admin will definitely use either less or sass, > because it is uncivilized to work without such lovely tools nowadays. > > I'm less certain about bootstrap. It has some pros and cons: > > Pros: > * widely used (and thus widely understood) > * We won't need to invent our own style guide for the new admin. If you're > developing a plugin or an extension and you're using the bootstrap styles, > your thing willl mesh nicely with the rest of the admin. > * less.js has the distinct advantage of being easier to develop for than sass > for our purposes.If we go with a less.js solution (like bootstrap), we might > not need to require that all edits to admin "source" stylesheets (less/scss) > come with the recompiled CSS. This lowers the barrier to contribution > significantly, at the cost of a bit of site performance as less gets compiled > client-side. That being said, the admin isn't supposed to be used as a a > high-traffic site (or shouldn't be, I can't say how people abuse it). > > It should only get compiled the first time, after then it get's cached client side IIRC (for less.js). > > Cons: > * less has no equivalent to compass, which is chock full of reusable stuff. > * I'm already having a bit of a negative reaction to the ubiquity of the > bootstrap "look" on the web. That being said, it's relatively easy to alter > some styles, but then we make the job of 3rd party admin extenders harder, > because they must deviate from the default bootstrap style to fit into the > admin. > > -I > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-developers/-/QxpHySYhgDgJ. > 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: start using less (and bootstrap!)
The next major revision of the admin will definitely use either less or sass, because it is uncivilized to work without such lovely tools nowadays. I'm less certain about bootstrap. It has some pros and cons: Pros: * widely used (and thus widely understood) * We won't need to invent our own style guide for the new admin. If you're developing a plugin or an extension and you're using the bootstrap styles, your thing willl mesh nicely with the rest of the admin. * less.js has the distinct advantage of being easier to develop for than sass for our purposes.If we go with a less.js solution (like bootstrap), we might not need to require that all edits to admin "source" stylesheets (less/scss) come with the recompiled CSS. This lowers the barrier to contribution significantly, at the cost of a bit of site performance as less gets compiled client-side. That being said, the admin isn't supposed to be used as a a high-traffic site (or shouldn't be, I can't say how people abuse it). Cons: * less has no equivalent to compass, which is chock full of reusable stuff. * I'm already having a bit of a negative reaction to the ubiquity of the bootstrap "look" on the web. That being said, it's relatively easy to alter some styles, but then we make the job of 3rd party admin extenders harder, because they must deviate from the default bootstrap style to fit into the admin. -I -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/QxpHySYhgDgJ. 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!)
I don't think this is really appropriate in core. Django itself is completely agnostic as to what you output, it doesn't pay attention to html, xml, csv, css, or anything. However if this is just an app you are making then sure. For what it's worth Pinax (a sort of collection of apps/conventions built on top of Django) has "themes" in 0.9a2, and the default theme is a bootstrap theme/app somewhat like you are suggesting. On Thursday, February 2, 2012 at 2:56 PM, Brendan Smith wrote: > 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 > > (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 > (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: start using less (and bootstrap!)
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.
start using less (and bootstrap!)
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.
Re: Issue in sending email
Please post questions about using Django on django-users, not here. The topic of this list is the development of Django itself. -- 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.
Issue in sending email
Hi, I am trying to send email through Django, for the send i am using send_mail(sender, to, subject, body, **kw) API. When i am running this application i am getting "You are not currently sending out real email. If you have sendmail installed you can use it by using the server with --enable_sendmail" message on terminal. Please let me know the issue behind it and what is solution. With Regards, Abhishek -- 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: Feature request: Unicode collation algorithm in django
On Feb 2, 10:07 am, Łukasz Rekucki wrote:
> Just came to my mind, that we could just mimic the DBs and have a
> Collate operator (like Q, F, Count, etc.) + maybe some defaults on the
> model:
>
> M.objects.order_by(Collate("name", "uca"))
> M.objects.filter(name__gte=Collate('e', "fi"))
I have been thining a lot about allowing annotate and order_by to
accept basically anything that has an .as_sql() method. So that you
could do things like:
qs.annotate(name_upper=RawSQL("upper(%s)",
params=f('name')).order_by('name_upper')
of course, the above example is doable using current Django ORM.
or maybe:
qs.annotate(name_upper=RawSQL("upper(%s)",
params=f('name')).order_by(RawSQL('%s collate "%%s" desc nulls last',
params=(f('name_upper'), 'fi-FI'))
These would be much better than the .extra(), as aliases are relabled
properly and you can "chain" the RawSQL clauses. In the ORM the code
that deals with .extra handling is kinda hacky, and this would
probably make that part of the ORM cleaner.
I think those really are doable. Using objects in cols, order by etc.
inside the ORM instead of the current implementation would probably
make the ORM cleaner and faster. Of course, without patch this is easy
to claim...
Problem is, I don't have time to do anything about this right now, and
it seems the ORM-knowing core developers have the same problem.
- Anssi
--
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: Feature request: Unicode collation algorithm in django
2012/2/2 Łukasz Rekucki :
> On 2 February 2012 03:34, Anssi Kääriäinen wrote:
>>
>> Now, my proposed solution would be to have some way of doing:
>> SELECT name, ...
>> FROM authors
>> ORDER BY name collate 'fi';
>>
>> That some way might be something like
>> .order_by('name', collate='fi')
>> or maybe
>> .collate('fi').order_by('name')
>> and now collate would be in effect for filters (that is,
>> name__gte='e'), too.
>>
>
> The user should probably be able to specifiy the collation only for
> the fields he wants, as it most likely uses a different type of index
> and is more expensive then a standard ordering, so I like the
> .collate(name="fi") option (and a shortcut of .collate("fi") to apply
> to all text fields.
Just came to my mind, that we could just mimic the DBs and have a
Collate operator (like Q, F, Count, etc.) + maybe some defaults on the
model:
M.objects.order_by(Collate("name", "uca"))
M.objects.filter(name__gte=Collate('e', "fi"))
--
Łukasz Rekucki
--
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: Feature request: Unicode collation algorithm in django
On 2 February 2012 03:34, Anssi Kääriäinen wrote:
>
> Now, my proposed solution would be to have some way of doing:
> SELECT name, ...
> FROM authors
> ORDER BY name collate 'fi';
>
> That some way might be something like
> .order_by('name', collate='fi')
> or maybe
> .collate('fi').order_by('name')
> and now collate would be in effect for filters (that is,
> name__gte='e'), too.
>
The user should probably be able to specifiy the collation only for
the fields he wants, as it most likely uses a different type of index
and is more expensive then a standard ordering, so I like the
.collate(name="fi") option (and a shortcut of .collate("fi") to apply
to all text fields.
>
> Making Django's ORM do the above isn't the most trivial thing. And not
> all databases support collate clauses.
After a quick research, I think they actually do now (at least in
ORDER BY). MySQL[1] and SQLite[2] both have COLLATE, in Oracle we
could use NLSSORT()[3] which is something like locale.strxfrm.
>
> You can do the above with .extra() even now if your DB happens to
> support collations. Default collation for your database might also be
> an option for your particular problem. At least in PostgreSQL versions
> prior to 9.1 you have one collation for the DB, which you can set only
> at CREATE DB time.
>
[1]: At least since 5.0:
http://dev.mysql.com/doc/refman/5.0/en/charset-collate.html
[2]: SQLite doesn't support UCA by default, but lets you define any
collation:
http://docs.python.org/library/sqlite3.html#sqlite3.Connection.create_collation
[3]: http://docs.oracle.com/cd/B19306_01/server.102/b14225/ch9sql.htm#i1006311
--
Łukasz Rekucki
--
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.
