Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

  • Blama
    replied
    Hi Isomorphic,

    I assume this is sth. like hidden, decimalPad, decimalPrecision, detail, emptyDisplayValue, title, but it would be great to have an approved list inside the docs of SimpleType.fieldProperties.

    Best regards
    Blama

    Leave a comment:


  • Isomorphic
    replied
    They are the client-side properties of DataSourceField. Basically, any property that purely influences client-side behavior is allowed.

    Leave a comment:


  • Blama
    replied
    Hi Isomorphic,

    I got that. But what are the clientside properties, that are not already named in explicitly in SimpleType, that one could set with SimpleType.fieldProperties?

    Thank you & Best regards
    Blama

    Leave a comment:


  • Isomorphic
    replied
    From the docs:

    These are properties that are essentially copied onto any DataSourceField where the property is applied. The supported properties are only client-side properties.
    customSelectExpression is a server-side property, so it wouldn't work here. We may support server-side properties at some point in the future (and it would be a valid Feature Sponsorship).

    Leave a comment:


  • Blama
    replied
    Hi Isomorphic,

    commenting in this thread I remembered we had problems with SimpleType before - here in this thread.
    Revisiting it is still not clear for me what additional properties of DataSourceField (that not already listed in the SimpleType docs by name) SimpleType.fieldProperties supports.
    Can you post an example or if you think it's worth a sample, create a sample? Also a list of the supported properties would be great to have in the fieldProperties-docs.

    Thank you & Best regards
    Blama

    Leave a comment:


  • Blama
    replied
    OK, I'll wait for the docs update then.

    Leave a comment:


  • Isomorphic
    replied
    So again, you can use fieldProperties in a .type.xml file but only properties with client-side effects will work. We will be updating the docs to make this clearer.

    Leave a comment:


  • Blama
    replied
    Hi Isomorphic,

    understood.

    W.r.t. current state of fieldProperties as attribute of SimpleType: If it is useable to configure some client side settings from .ds.xml, these are not clear, as it is not doc'd in SimpleType. Or are all the properties here under SimpleType a synonym for fieldProperties, when you write about this?

    W.r.t the features used here:
    As of today, I'd like to use the feature for "DRY", so to have smaller .ds.xml, where it is also possible to change all instances of a user-defined type in a single place.
    So far, the use cases here involve:
    • boolean fields, used attributes:
      • sqlStorageStrategy
      • escapeHTML
    • repeated configurations of creator/modifier/createdAt/modifiedAt fields. used attributes:
      • canEdit
      • canSave
      • primaryKey
      • includeFrom
      • foreignKey
      • customSelectExpression
      • escapeHtml
      • displayField
      • sortByField
      • hidden
      • length
      • title fmt-subtag
    W.r.t involved organizations:
    This thread and the linked one are from my colleague and me. Any other user please feel free to +1 this.

    Best regards
    Blama

    Leave a comment:


  • Isomorphic
    replied
    It looks like in that other thread there is indeed one mention of trying to use includeFrom from a SimpleType. All the other properties mentioned are client-side properties that do work via fieldProperties.

    While includeFrom has client-side effects, it's true that it is principally a server-side property and we see how you might have concluded that server-side properties were valid in fieldProperties, despite the docs suggesting otherwise. Sorry for any confusion there. We are already in the midst of updating the docs so that such confusion cannot arise.

    As far as any possible future support for additional server-side properties in the SimpleType declaration, we won't be doing that by making properties specified in fieldProperties suddenly begin having server-side effects. Rather we'll add support for individual properties that make sense and doc such properties on SimpleType.

    So far as we understand there is just a single organization requesting such support in this thread, but let us know if that's not the case - user votes count in our prioritization process, of course.

    We'd also like to understand which specific properties are most desirable.

    Leave a comment:


  • Blama
    replied
    Hi Isomorphic,

    the problem for all this time we invested now is that here you make it sound like it is working serverside in .ds.xml for the very task we are asking about. Please see that you are referring to DataSourceLoader in your response there.
    This all is a bit unfortunate. Also this would be a great feature for everyone, even without Feature Sponsorship.

    Best regards
    Blama

    Leave a comment:


  • Isomorphic
    replied
    If you mean that fieldProperties is not affecting server behavior, that's what the docs indicate. It's doc'd as a client-side property but not a server-side property.

    An enhancement to the SimpleType system to make this possible makes sense, but it's not a trivial change (and isn't a bug) - this would be something to look at as a Feature Sponsorship.

    Leave a comment:


  • Blama
    replied
    Hi Isomorphic,

    of course we checked these docs.
    The problem is that the tag <FieldProperties>, which you claim as working here in the way I tested in that thread, is not working for us and is not documented in the SimpleType-ds.xml docs (or I did not find it).
    So we tried different methods, some of those Developer12145 shows in this thread, but never got it working.

    Goal is - as my thread from 2013 describes to offload repeating field configurations in a type that then is referenced.
    In my case these were displayFields for fields of type createdBy and modifiedBy and in the case here it's the storage-definition of boolean-fields.

    This is a) very repetitive and tedious to change if needed and b) is responsible for a considerable portion of the document size of the DataSourceLoader result.

    Best regards
    Blama

    Leave a comment:


  • Isomorphic
    replied
    Still not understanding this question. It's as if you think SimpleType isn't documented, but it is:

    https://www.smartclient.com/smartgwt...impleType.html
    https://www.smartclient.com/smartgwt...impleType.html

    Maybe the problem is that you have not seen that there is a general overview of how to use XML for such declarations here?

    https://www.smartclient.com/smartgwt...e-summary.html

    Note also that fieldProperties is not part of what can be set on the server, so you cannot set server-side properties that way.

    Leave a comment:


  • Developer12145
    replied
    Hi Isomorphic,

    what I meant was what information I could possibly declare for the field in SimpleType?
    e.g.:
    displayField="some_name" title="some_title" required="true" sqlStorageStrategy="singleChar10" escapeHTML="true" etc. Regarding to this https://forums.smartclient.com/forum/smart-gwt-technical-q-a/28970-simpletype-to-outsource-more-than-validation-display?p=184344#post184344 You said it could be done with simpleType.fieldProperties. [FONT=arial, helvetica, sans-serif]My question is how would I write it in a .type.xml file? Like this: [/FONT]
    Code:
     <SimpleType xmlns="some_link" xmlns:fmt="some/fmt" name="booleanType" inheritsFrom="boolean" >     <fmt:bundle basename="some_base" encoding="utf-8" />     <FieldProperties[B] sqlStorageStrategy="singleChar10" escapeHTML="true">[/B]</FieldProperties> </SimpleType>
    or like this:
    Code:
     <SimpleType xmlns="some_link" xmlns:fmt="some/fmt" name="booleanType" inheritsFrom="boolean" [B]sqlStorageStrategy="singleChar10" escapeHTML="true"[/B]>     <fmt:bundle basename="some_base" encoding="utf-8" /> </SimpleType>
    I read the docs, but I can't find anything about it, only how it works with validators. I also tried to find something in the forum but without success. So it would be very nice if You could clarify 1. what field information are supported e.g. sqlStorageStrategy, escapeHTML like asked above 2. how can I use them? Do I need to specify them in the <SimpleType...> tag or in a <FieldProperties...> tag? A little example in xml-format would be highly appreciated. Thanks in advance and Kind Regards

    Leave a comment:


  • Isomorphic
    replied
    Sorry, we don't understand the question.

    What is documented is what is supported, as with all other classes.

    Could you clarify what you're asking?

    Leave a comment:

Working...
X