In my use case there is no model involved.
I have a django url-mapping (regex to view) not model.
Regards,
Thomas Güttler
Am Montag, 30. April 2018 15:55:44 UTC+2 schrieb TonyF-UK:
>
> What is wrong with a special type of Field - which is a URL, but also
> have augmented data items which are
What is wrong with a special type of Field - which is a URL, but also
have augmented data items which are stored on the model?
As far as I know - there is no rule that states that each 'Field' on a
model has to have one and only one field in the database. Even if you
have one and only one
ers@googlegroups.com] On
Behalf Of guettli
Sent: Monday, April 30, 2018 2:25 AM
To: Django users
Subject: Re: Crazy Idea: OOP for "Hyperlink"
Am Donnerstag, 26. April 2018 15:54:31 UTC+2 schrieb Matthew Pava:
I’ve been thinking about your idea, and I wonder if there could instead
Am Donnerstag, 26. April 2018 15:54:31 UTC+2 schrieb Matthew Pava:
>
> I’ve been thinking about your idea, and I wonder if there could instead be
> some kind of widget for URL objects (or views).
>
>
>
A widget ... Let me think about it. A widget is a libray, is source code.
The code needs
Idea: OOP for "Hyperlink"
Am Mittwoch, 25. April 2018 17:29:36 UTC+2 schrieb Jani Tiainen:
Hi.
Most probably you get there by creating custom template tag and bunch of other
code.
It would be easier to grasp your idea if you have some kind of an
implementation to
Am Mittwoch, 25. April 2018 17:29:36 UTC+2 schrieb Jani Tiainen:
>
> Hi.
>
> Most probably you get there by creating custom template tag and bunch of
> other code.
>
> It would be easier to grasp your idea if you have some kind of an
> implementation to reference.
>
> Or is there something
I would like to keep both things separated:
- Attributes for URLs
- Access without login
What do you think?
Regards,
Thomas
Am Mittwoch, 25. April 2018 14:04:22 UTC+2 schrieb TonyF-UK:
>
> Interestingly, I am thinking on something similar too - having a
> report/notifications/actions view
Hi.
Most probably you get there by creating custom template tag and bunch of
other code.
It would be easier to grasp your idea if you have some kind of an
implementation to reference.
Or is there something that stops you from proceeding?
ma 23. huhtikuuta 2018 klo 12.00 guettli
Interestingly, I am thinking on something similar too - having a
report/notifications/actions view that have an auto generated URL. The
idea (on my concept) is that by getting this unique URL via email, a
user can access the report/action without needing to actually login -
the fact that a
Thank Adrien for sharing your knowledge.
Our use cases have some parts that are common and some
parts that are distinct.
You want actions, I want static attributes.
You define them on the model.
I use URLs. In my case sometimes there is a 1:1 relationship between URL
and model,
but sometimes
Hi,
On 04/23/2018 10:59 AM, guettli wrote:
I have a vague idea to use OOP for a hyperlink.
A hyperlink has these attributes for me:
- href
- verbose name
- Permission: Is the current user allowed to follow the link?
- Preview (on-mouse-over tooltip)
We have developed something similar in
I have a vague idea to use OOP for a hyperlink.
A hyperlink has these attributes for me:
- href
- verbose name
- Permission: Is the current user allowed to follow the link?
- Preview (on-mouse-over tooltip)
I like Django because it handles the "href" part very smart (via reverse()).
My current
12 matches
Mail list logo
