Hello everybody <3

Let’s talk about ideas for deprecation / discouraging the use of get_context_data().

get_context_data() is useful to support legacy templates from the pre-CBV era, since CBV we can now access any attributes from the view instance with {{ view }}.

I’ve seen things like this in many projects, I wonder if it’s the case for other people too:

def get_context_data(self, **kwargs):
    c = super().get_context_data(**kwargs)
    c['something'] = self.something
    return c

And I’m guilty as charged you can find commits from myself like this all over internet.

Next CRUDLFA+ version with Materializecss preview !

https://www.patreon.com/materialize?utm_medium=social&utm_source=yourlabs&utm_campaign=plshare

Yessss! We are now a proud patron of Alan and Alvin on @Patreon, and you should be too ;) With LOVE

https://docs.google.com/document/d/1C-ceqQ3UxvURLPsMxd5Ej658ETuwxEK4hElKafwBsyQ/edit

What my work looked like in 2013 (French).

It’s an honour for YourLabs Business Service, 2 months after opening, to make a small donation to a new alternative lifestyle project: L’Hermitage. This donation will be used to organize the first DIY workshops and open source home automation and heat management for large houses! With LOVE

https://stackoverflow.com/jobs/160985/postgresql-database-specialist-gitlab

Gitlab recruits remote DB specialist.

Stumbled accross some really good looking web based debugger: https://github.com/Kozea/wdb

Sometimes, we need to make views around objects which are not stored in the database. They may be calculated on the fly in python, or come from some data source that’s not the database, or which aggregates several objects in the database.

This is supported out of the box with CRUDLFA+, the modern web framework for Django. All you need to implement is:

• a Model class with what you want in it, just set Meta.managed=False,
• implement save() and delete() like you want in it, if you want create, update and delete views to work,
• implement get_queryset() and get_object() like you want in the Router.

This example model from crudlfap_example uses a class attribute in the manager to store the object list in memory. That’s probably not what you want to do in your own project, but that works for the PoC because it demonstrates how to override save() and delete().

It’s my pleasure to announce the official birth of our new company, YourLabs Business Service. This company will work in conjunction with the YourLabs foundation and of course sponsor the Django apps ecosystem.

We are hiring freelancers to:

• maintain apps in the Django ecosystem that we use in CRUDLFA+, our modern web framework for Django,
• sysadmins and other hackers to co-manage our infrastructure: respond to monitoring alerts and this kind of things,
• contribute to our customer projects,

This is a 99% remote position, or 100% if you want to miss all the parties and conferences we’ll setup or join, but it’s not a full time job, yet, rather a paying side project for things you probably already do.

Well, it definitely stands for something ! And since this is becoming a FAQ, here’s my answer:

It stands for: Create Read Update Delete Form Autocomplete and more !

We started by making a CRUD because the customer was complaining his come was not DRY and that we should have a CRUD in Django - the customer comes from the modern PHP framework world.

We soon figured we needed a crudL, for the list. We wanted to add custom actions with custom forms and it became crudlF because we added the FormViewMixin. Then we wanted to add automatic autocomplete views so it became crudlfA, with the AutocompleteView (to be Open Sourced soonish). Then we wanted to just refactor custom views: turned out into we use ModelViewMixin, the mixin for a model view, ie. list, create … and ObjectViewMixin, mixin for a model instance view ie. detail update delete forms …