Blog: Posts from June, 2019

Labels
AJAX(112) Apple(1) Application Builder(242) Application Factory(207) ASP.NET(95) ASP.NET 3.5(45) ASP.NET Code Generator(72) ASP.NET Membership(28) Azure(18) Barcodes(3) BLOB(18) Business Rules(1) Business Rules/Logic(140) BYOD(13) Caching(2) Calendar(5) Charts(29) Cloud(14) Cloud On Time(2) Cloud On Time for Windows 7(2) Code Generator(54) Collaboration(11) command line(1) Conflict Detection(1) Content Management System(11) COT Tools for Excel(26) CRUD(1) Custom Actions(1) Data Aquarium Framework(122) Data Sheet(9) Data Sources(22) Database Lookups(50) Deployment(22) Designer(177) DotNetNuke(12) EASE(20) Email(6) Features(99) Firebird(1) Form Builder(14) Globalization and Localization(6) Hypermedia(2) Installation(4) JavaScript(20) Kiosk(1) Low Code(3) Mac(1) Many-To-Many(4) Maps(6) Master/Detail(36) Microservices(4) Mobile(63) Mode Builder(3) Model Builder(3) MySQL(10) Native Apps(5) News(15) OAuth(5) OAuth Scopes(1) OAuth2(6) Offline(14) Oracle(10) PKCE(1) PostgreSQL(2) QR codes(2) Rapid Application Development(5) Reading Pane(2) Release Notes(163) Reports(48) REST(26) RESTful(21) RESTful Workshop(13) RFID tags(1) SaaS(7) Security(75) SharePoint(12) SPA(5) SQL Anywhere(3) SQL Server(26) Stored Procedure(4) Teamwork(15) Tips and Tricks(81) Tools for Excel(2) Touch UI(93) Transactions(5) Tutorials(183) Universal Windows Platform(3) User Interface(331) Video Tutorial(37) Web 2.0(100) Web App Generator(101) Web Application Generator(607) Web Form Builder(39) Web.Config(9) Workflow(28)
Archive
Blog
Posts from June, 2019
Tuesday, June 11, 2019PrintSubscribe
Changing Styling of Values and Labels in Forms
Use simple CSS rules to change the presentation of data in the forms. For example, you can  make the label of a particular field to appear bold and color the value of another like this:



Place the following CSS rules in the file ~/app/css/mystyles.css.

[data-field="CompanyName"][data-control="label"] {
    font-weight: bold;
}

[data-field="ContactName"][data-control="field"] {
    font-weight: bold;
    color: blue;
}

Make to press Ctrl+F5 to refresh the resources loaded in the browser. This will integrate the new stylesheet in the app. Do so every time you make changes.

This is how the customization will look in the Dark theme with Citrus accent.


If you do choose to use colors then make to test presentation with a few theme and accent combinations.

CSS is a powerful mechanism to alter presentation of HTML documents without making physical changes to the markup itself.
Wednesday, June 5, 2019PrintSubscribe
June 2019 Hot Fix #2
Release 8.7.13.0 introduces the following enhancements and bug fixes:
  • (Code Gen) Generic property declarations do not reference "this" anymore.
  • (Framework) Implementation of class FieldValue performs a simpler calculation of Modified property value for efficiency and to provide compatibility with the compact JSON encoding of field values for Offline Sync. The new algorithm resolves the issue of saving of records with many-to-many fields.
  • (Framework) "Code" business rules created in MyProfile controller now inherit from MyProfileBusinessRulesBase class.
  • (Framework) Data Access Objects have a new implementation of SelectSingle method making it compatible with the filters produced in SELECT statements from  dynamic access control rules.
  • (Touch UI) Use import.batchSize option in ~/touch-settings.json to control the number of items submitted for insertion and optional duplicate testing from the client to the server for processing. The default size of the batch is 10 items. The larger batch size will allow fewer client/server requests to process large import files.
    {
      "import": {
        "batchSize": 100
      }
    }
See the description of the June 2017 release here
Labels: Release Notes
Monday, June 3, 2019PrintSubscribe
June Hotfix 1
Hot Fix Release 8.7.12.0 addresses the following issues:


  • (Touch UI) Fixed incorrect display of static lookup values in "read" mode.
  • (Framework) BLOB fields are referenced in the definition of the handler by "FieldName" if the there is no matching column in the physical data model or when data model is not defined.
See the description of the June 2017 release here
Labels: Release Notes