Open GoogleCodeExporter opened 9 years ago
Addendum to datatype-specific operators:
As Heron will know the type of data, Heron can do basic sanity checking of
inputs before sending off the query.
I.e.:
For > searches, complain if input isn't a number.
Original comment by jonathan...@warwickshire.gov.uk
on 30 May 2013 at 3:37
Two questions:
- drop-down widths
is this still an issue? was this for the layer names or the operators?
- datatype-specific operators
this remains a hard issue to solve: all comparison building/handling is done
deep within GXP. Also we need to have a more exact list which comparisons
should be enabled for which data types. One could e.g. argue that '>' makes
sense for strings as it could be an alphabetic comparison Streetname > L gvae
me addresses whose streetname starts with L or above. The QueryBuilder is sort
of a rough search tool.
Sometimes numbers appear to be strings in the database and then "like" may make
sense. It is all checkable but the user may be unaware.
Original comment by jus...@gmail.com
on 15 Jul 2013 at 2:33
Drop down widths:
Still an issue. It applies to both layer names and the opperators (well, the
"between" operator anyway).
Datatype specific operators - I'd punt this one back to GXP then. Seems like a
logical feature request.
I think the specs probably say somewhere what type of operators should work on
what type of structure.
Original comment by jonathan...@warwickshire.gov.uk
on 15 Jul 2013 at 2:46
Also the dropdown widths are defined in GXP. This makes it quite time-consuming
to debug and fix and the gain is rather cosmetic. At least I would like to
bring out 0.74 so the trunk is free to get new functionality in (see Roadmap)
which benefits all.
Original comment by jus...@gmail.com
on 16 Jul 2013 at 12:23
It's not strictly a cosmetic issue. See attached - because the drop-down is
cutting off the end, it's impossible to know which of these two layers is which.
I'd punt this to GXP too then if it's an issue there.
Original comment by jonathan...@warwickshire.gov.uk
on 16 Jul 2013 at 12:30
Attachments:
Is it possible that you add the two issues to the GXP Github issue list?
For reference and tracking we can then include their URLs here and keep this
issue open until solved/verified by GXP.
Original comment by jus...@gmail.com
on 17 Jul 2013 at 11:13
Which is the GXP github. I've got at least three possiblities coming up, but
I'm guessing it's:
https://github.com/opengeo/gxp - can you confirm please.
Original comment by jonathan...@warwickshire.gov.uk
on 17 Jul 2013 at 11:24
Yes this is the master GXP repo. The issues are here:
https://github.com/opengeo/gxp/issues
(also our other issues).
Original comment by jus...@gmail.com
on 17 Jul 2013 at 11:31
https://github.com/opengeo/gxp/issues/201 - drop-down width
https://github.com/opengeo/gxp/issues/202 - Operator types and data types.
Original comment by jonathan...@warwickshire.gov.uk
on 17 Jul 2013 at 11:59
https://github.com/opengeo/gxp/issues/201 - updated. Suggests:
Your code should have a line
Ext.QuickTips.init();
Then it should work out of the box.
As an interim solution.
Original comment by jonathan...@warwickshire.gov.uk
on 18 Jul 2013 at 1:35
Original comment by jus...@gmail.com
on 8 Sep 2013 at 7:59
Moving out of 0.76, for now unplanned.
Original comment by jus...@gmail.com
on 1 Nov 2013 at 12:46
Original issue reported on code.google.com by
jonathan...@warwickshire.gov.uk
on 30 May 2013 at 3:22