Hi group,
I'm facing a very weird issue that causes a clash when I use swampdragon's
*SelfPublishModel* and django's *models.Model*.
This is the current model that I'm using.
class Activity(SelfPublishModel, models.Model):
content = models.TextField()
dateTime = models.DateTimeField()
Yes I am the author of that article.
Libraries does make life easier, as long as they are the right libraries
for the job.
If you are unfamiliar with Angular I would actually recommend not using it.
* Angular 2.0 is supposedly not going to be backwards compatible (it
actually looks like a tot
Michiel: Ah, that's myopic on my part. Both sides are important.
Jonas: I see I see. I keep thinking that libraries will make my life a bit
easier but maybe what I currently need now does not require the use of
them. And are you the author of
the article? (I'm assuming it's the same Jonas) Tha
Personally I don't use any library between Angular and Django (so I don't
know about django-angular).
I create specific templates for Angular so I don't have to change the {{
and }] syntax (you can also use the {% verbatim %} tag in your templates if
you don't want to create individual template
Hi,
A little side-note...
> That then led me to learn how much I can shift items like validation to the
> client side and leave Django to
> do the rest.
Even if you do client side validation, you still have to do it on the server
side too, to protect your application from malicious attacks.
Hi group,
I'd like to get some guidance on how to go about thinking about the
structure of the web app I'm trying to build.
>From a high level perspective, I'm trying to make a web app that
facilitates a small business doing camera rentals.
To give a use case, if a user makes a rental booking
6 matches
Mail list logo
