On 20/02/2018 11:51 PM, Andy wrote:
use django-select2
Had a look at the docs and django-select2 doesn't address this use case.
However, I can see I will need it for ORM related selections in the near
term.
Thanks Andy.
Am Dienstag, 20. Februar 2018 01:17:26 UTC+1 schrieb Mike Dewhirst:
use django-select2
Am Dienstag, 20. Februar 2018 01:17:26 UTC+1 schrieb Mike Dewhirst:
>
> Here is an example of get_choices() output ... it comes from a method on
> the Question model.
>
> [('A', 'A - Once?'), ('B', 'B - Twice?'), ('C', 'C - Four times?'),
> ('D', 'D - Twelve times?'),
On 20/02/2018 11:16 AM, Mike Dewhirst wrote:
Here is an example of get_choices() output ... it comes from a method
on the Question model.
[('A', 'A - Once?'), ('B', 'B - Twice?'), ('C', 'C - Four times?'),
('D', 'D - Twelve times?'), ('E', 'E - Continously as changes are
made?')]
It is
Here is an example of get_choices() output ... it comes from a method on
the Question model.
[('A', 'A - Once?'), ('B', 'B - Twice?'), ('C', 'C - Four times?'),
('D', 'D - Twelve times?'), ('E', 'E - Continously as changes are made?')]
It is available before the the answer form is
On Mon, Jun 25, 2012 at 9:04 PM, Andy McKay wrote:
>> Now they want me to add to that how long
>> the browser takes to render the page after it gets the data.
>
> You can use the navigation timing API:
>
>
Just FYI - New Relic does a fantastic job of browser speed graphing - but
it is an expensive product.
On Fri, Jul 6, 2012 at 6:14 AM, Larry Martell wrote:
> On Thu, Jul 5, 2012 at 10:48 PM, Andy McKay wrote:
> >> I'm trying to use the Navigation
On Thu, Jul 5, 2012 at 10:48 PM, Andy McKay wrote:
>> I'm trying to use the Navigation Timing package to measure how long a
>> page takes to be rendered.
>
> So you don't want to include all the lookups? Just the "rendering" part?
Not sure what you mean by "lookups." I want to
> Thanks Andy. Super cool, and pretty much just what I was looking for.
> Seems to work fine in FF and Chrome, but in Safari I don't seem to
> have access to the performance.timing data. Should that be there or do
> I have do something to load or enable it?
Sadly, Safari does not support this :(
> I'm trying to use the Navigation Timing package to measure how long a
> page takes to be rendered.
So you don't want to include all the lookups? Just the "rendering" part?
> So that would be loadEventEnd-responseEnd,
> however I am finding that loadEventEnd is always 0 for me, even though
> I
On Mon, Jun 25, 2012 at 9:04 PM, Andy McKay wrote:
>> Now they want me to add to that how long
>> the browser takes to render the page after it gets the data.
>
> You can use the navigation timing API:
>
>
en calculate that?
> 2) How I can return it back to the server?
> 3) Since the database table is updated with the other statistics
> before the data is sent to the browser, assuming I could calculate the
> render time and send it back, how could I find the row and update with
>
On Mon, Jun 25, 2012 at 9:04 PM, Andy McKay wrote:
>> Now they want me to add to that how long
>> the browser takes to render the page after it gets the data.
>
> You can use the navigation timing API:
>
>
I stumbled upon this while looking about this timing stuff:
http://www.html5rocks.com/en/tutorials/webperformance/basics/
Seemed slightly more verbose than W3C formal documentation.
On Tue, Jun 26, 2012 at 10:38 PM, Melvyn Sopacua wrote:
> On 26-6-2012 5:04, Andy McKay
On 26-6-2012 5:04, Andy McKay wrote:
>> Now they want me to add to that how long
>> the browser takes to render the page after it gets the data.
>
> You can use the navigation timing API:
>
> https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Overview.html
Wow, really nice.
On Mon, Jun 25, 2012 at 9:04 PM, Andy McKay wrote:
>> Now they want me to add to that how long
>> the browser takes to render the page after it gets the data.
>
> You can use the navigation timing API:
>
>
On Mon, Jun 25, 2012 at 6:56 AM, Melvyn Sopacua wrote:
> On 25-6-2012 14:00, Larry Martell wrote:
>> On Mon, Jun 25, 2012 at 5:56 AM, bruno desthuilliers
>> wrote:
>>> On Monday, June 25, 2012 1:34:08 PM UTC+2, larry@gmail.com wrote:
> Now they want me to add to that how long
> the browser takes to render the page after it gets the data.
You can use the navigation timing API:
https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Overview.html
We use this in conjuction with graphite and django-statsd to produce
On 25-6-2012 14:00, Larry Martell wrote:
> On Mon, Jun 25, 2012 at 5:56 AM, bruno desthuilliers
> wrote:
>> On Monday, June 25, 2012 1:34:08 PM UTC+2, larry@gmail.com wrote:
>>>
>>> Now they want me to add to that how long
>>> the browser takes to render the
w can I even calculate that?
> 2) How I can return it back to the server?
> 3) Since the database table is updated with the other statistics
> before the data is sent to the browser, assuming I could calculate the
> render time and send it back, how could I find the row and update wit
On Mon, Jun 25, 2012 at 5:56 AM, bruno desthuilliers
wrote:
> On Monday, June 25, 2012 1:34:08 PM UTC+2, larry@gmail.com wrote:
>>
>> Now they want me to add to that how long
>> the browser takes to render the page
>
>
> How would server code ever know this ?
On Monday, June 25, 2012 1:34:08 PM UTC+2, larry@gmail.com wrote:
>
> Now they want me to add to that how long
> the browser takes to render the page
>
How would server code ever know this ?
--
You received this message because you are subscribed to the Google Groups
"Django users"
to the browser, assuming I could calculate the
render time and send it back, how could I find the row and update with
that info?
If anyone has already done something like this, or anyone has any
advise on how I could do it (especially item #1), I'd really
appreciate them sharing it with me.
TIA
22 matches
Mail list logo