#django

has the static tag been removed from Django 1.7 templates?

softinio: ... why would it?

my django app was working with django 1.6 now running it under 1.7b is giving me invalid block tag. thanks for confirming it hasn't i will invetigate the error further

softinio: do you have {% load staticfiles %}

?

+1 on djapo

what's the preferred form field to use for multiple values without choices? like free-form text entry

djapo: this is what I have: <link rel="stylesheet" href="{% static "assets/css/style.min.css" %}">

softinio: and that used to work? any traceback?

softinio: also, why not 1.7rc1?

snurfery: huh? multiple values? or free-form text? which is it?

djapo: added {% load staticfiles %} to template and all seems to be fine now. No longer getting that error

FunkyBob: yes will be upgrading to rc1 shortly

this evening

FunkyBob: both, like I'm submitting an array of free-form text

I don't need to validate it against a list of choices

snurfery: well, you'll need a related model to store the values in

this is plain form stuff

not model stuff

thanks for your help chaps as always learning all the time thanks to this great community of developers

snurfery: formset

I just want a field that accepts an array of strings

ew, no

exactly what "TypedMultipleChoiceField" and "MultipleChoiceField" are doing, but without checking the input against a list of choices

snurfery: fixed or variable number of values?

much like the 2 above fields, a variable number

formset

meh

what?

I'm just gonna hack together my own field

but it's not _a_ field

it's many fields

it's one field that accepts multiple values

you could pass it as many values of the one field name

much like MultipleChoiceField

of course, it might help if you'd explain what this is for

email compose interface... 'to' holds multiple email addresses, and I'm doing everything restfully so django isn't rendering any html here

django forms aren't about rendering HTML, anyway

of course

but formsets will want to put in their management form

which is pretty easy if django was doing the rendering, but more bothersome when it's not

I think I'll just subclass TypedMultipleChoiceField and override validate() so it won't try to check choices

I'm just surprised this isn't a thing

but maybe I'm just being entitled ;)

of course, if it's RESTful, you may not even have a form...

depending on which restful lib you're using, if any

but, sure... multi-value field shouldn't be hard

yeah, that was pretty easy =)

4 lines

heh

of course, if you're not validating it, you can just pluck it straight from request.POST

but I don't think that code is quite right

yeah I still wanted 'required' at least, seems to be working fine so far

as far as I can tell valid_value just checks if it's in choices

and handles cases where there's an list of lists of choices (optgroup or something)

a list*

so... building a webmail, eh?

an interface to send messages, yeah... not the whole gamut of functionality thankfully

ah, ok

I keep toying with the idea

now with all these css frameworks, and other stuff... even I can produce one that looks ok :P

oh yeah, I'm super thankful for bootstrap

even with it holding my hand I still make these super clutzy interfaces

heh

bootstrap, foundation, uikit, .... so many to choose from :)

bootstrap for css/basic interface stuff and angularjs for actual interactivity

the old version of my app was built with a mountain of terrible, terrible jquery

it's a thing of horror

first time here

how active is this channel?

there's literally no one here

;)

damn

it's pretty active

cool

so is it like django devs?

and the occasional confused "django unchained" fan

yeah

lol

cool

what's the protocol if I have a question?

ask

it's rather quiet now, being the weekend

ok

I'm building somethign and I want to use django-rest-framework to make some models available as resources then use backbone or somethign simiarl for the frontend.

I would like to set up subdomains so I can have api.thisapp.com and www.thisapp.com

but, i'm deploying to heroku and have no idea how this would be done.

CNAMES? if so how?

or different apps on different projects?

this is really more of a heroku question

i am super in the dark about how this would be done.

oh, okay

there reall is no big need, initially, to separating the domains

in that case, on what type of deployment/platform would the django-subdomains package/setup work on?

indeed, it will actually make things a little trickire, when dealing with sessions, for instance

Yeah, I realize that now.

I think I'm going to go with *.com/api instead

yeah, what's what I do

cool

same here

how do we feel about django-rest-framework generally?

and DRF wants you to do that too, for the most part

like http://www.kogan.com/au/api/product/

though I don't use DRF

I'm a huge fan, the more I use it the more I love it

documentation is hands down the best I've seen of any project

in my young opinion, its way better than tastypie.

yeah, the docs are splendid

I've heard good things about that too, so either way we're blessed

=)

cool beans

even though if you're gonna take the plunge with a frontend framework, I'd love to lure you into AngularJS

I'm a backend guy, and it made me love working with js

yeah, DRFs docs are great