-
Login control - reset pas...
Forum: General
Last Post: marktalluto
10-31-2024, 05:38 PM
» Replies: 3
» Views: 789 -
BLOBs: Multiple feature r...
Forum: Feature Requests
Last Post: stam66
10-18-2024, 12:10 PM
» Replies: 5
» Views: 710 -
LiveCode licence needed?
Forum: General
Last Post: marktalluto
10-17-2024, 08:49 PM
» Replies: 3
» Views: 731 -
Script as text
Forum: Feature Requests
Last Post: linda
10-11-2024, 11:37 PM
» Replies: 1
» Views: 448 -
List Files issue
Forum: Bug Reports
Last Post: stam66
10-11-2024, 01:17 AM
» Replies: 5
» Views: 718 -
Buttonbar
Forum: Feature Requests
Last Post: marktalluto
10-08-2024, 11:58 PM
» Replies: 1
» Views: 351 -
Hey
Forum: Introduce Yourself
Last Post: marktalluto
10-08-2024, 11:47 PM
» Replies: 3
» Views: 3,459 -
I'm interested in opinion...
Forum: General
Last Post: marktalluto
10-08-2024, 10:52 PM
» Replies: 4
» Views: 4,616 -
Appli Founder Message for...
Forum: Announcements
Last Post: marktalluto
10-02-2024, 12:26 AM
» Replies: 0
» Views: 359 -
An interesting Find in Ap...
Forum: General
Last Post: MichaelJes
09-19-2024, 12:19 AM
» Replies: 3
» Views: 10,036
- Forum posts:207
- Forum threads:72
- Members:1,192
- Latest member:EnriqueHeifs
When using ‘get_date_time ,with output format HH;MM AM/PM, you still get 24-hour times - e.g. 17:24
The docs for the convert functions are wrong, inconsistent.
Some use ‘output’ for the location for the result (correct), but ‘convert time’ uses ‘output’ for the format of output,
And it uses ‘formatoutput’ for the location, …….
Mark Talluto has sent a sample Appli sample that is able to send an audio message via an Appli program and convert that audio to text and save it in a table. Think about what this means. In certain situations, texting via a keyboard can be time-consuming. This is exciting. I have included a link to the Appli sample video that you can upload it and review.
https://www.appli.io/pub/Clarence/messages.mp4 You will get a better viewing if you download the file and watch it locally with a video viewing program.
This is a great sample of what Appli can do.
I'd like to get some feedback from other users on ELement Naming Conventions for Appli Elements.
I use naming conventions for my Appli Projects, including lowercase letters and Camel Case text.
Some examples: vRecordID for variables, lbl*** for label text fields, txt*** for text fields, ele*** for element fields, btn*** for button elements - sample btnReturn, and so forth. I find that using this type of element and field elements makes it easier to identify these elements when using low code objects. I would like to get some feedback from other users on what your thoughts may be on this subject. I realize that we all have preferences but it would be interesting to get some feedback.
Thanks, in advance.
If you need to determine the Platform that your Appli Application is running on this might help. See attached.
I am super happy with the new low code features.
In this post I will focus on two of them: "get the Platform" and control Structure "Switch" and 2 different use cases.
I have noticed some differences in Appli applications depending on the Platform that Appli is used.
I use this low code to determine the platform the Appli Application is running under - the "get_the_platform." This function looks for a variable name to place the platform value into, and I created a variable named varPlatform. Also not that I put all of this coe under the event "When openApp.
Next, I created a conditional - switch variable to catch the cases of ANDROID, MacOS, IOS, and WINDOWS.
See attached file below.
You may experience a slow or a total inability to access the SFO region due to an outage with one of the backbone providers.
There is nothing we can do directly. These things happen, and you can bet they are working hard to fix the issue.
https://www.product-reviews.net/down/lev...ge-status/
We are sorry about this. If you have any questions, please feel free to reply here.
-Mark
Hello Appli,
I'm guessing you have a bunch of additional Elements in the works.
Just raising my hand in favour of implementing a slider element (as well as more graph types and gauges) in the near term.
Given the inbuild data capabilities of the platform, I envisage Appli as being a nice place to dashboard.
Kind regards, Andrew
Hello Mark & Team,
Upon login (I move past the Login screen to the home screen), I then receive a dialog that says "Appli Setup", "Cannot access billing, subscription, or usage information. Failed to locate server.","OK" .
If I click ok, I get a "Loading Apps" dialog that never resolves.
Prior to now I have been able to login.
I love the direction of your project.
Kind regards, Andrew
We are working on a significant update to the low-code features in Appli. For this reason, we did not post any updates for 1.5 weeks. The changes to the low-code editor will temporarily cause your actions for your elements not to work. We are working on an update that will auto-update your actions for you. If you can not wait, you can copy and paste your actions back into an event. Doing so will make the actions work again.
You can now fold your action flows for easier reading. Copy and paste of actions are here. Shift-click your code to highlight your flows and right-click to copy and paste. Did someone say code validation is needed? When your action flow is red, you may have forgotten to complete an action. A green action flow indicates all is good. More events are now available. We are still working on fully supporting some of the new events.
We revamped the onboarding screens with more consistent visuals that better match the Appli branding. The experience is easier on the eyes and makes more sense as you build projects.
We significantly improved notch and chin support on phones. All you need to do is identify the elements you want to be drawn into a notch zone. For example, the background to your header may draw into the notch area. If your header is a group, select the group and check the box for 'Stretch Y to fill notch' in the property inspector.
We hope you are enjoying the new project support in Appli. You can easily see all your apps in a single project. We expanded the number of devices you can create per project from one to as many as you want. You can make as many phones, tablets, and desktop apps as you see fit in the same project.
The deciding factor usually is your data. If you need different apps to access the same data or subsets of the same data, now you can do it. If you are making software for a client that needs different apps for their business, this feature has you covered.
We added a visual tool for binding your data to your elements. Click on the form element's no-code. The standard table binding feature and a new button to 'Add Key' will be seen. From here, you can bind your keys to your elements.
It is always good catching up with all of you. Have a great weekend, and we will see you next week!
-Mark Talluto
The kind of data-driven apps that (IMO) no/lo-code is well suited for have a number of common patterns.
One in particular is so common it's almost ubiquituous:
- an 'overview' page (either layout or table element) showing all/some of the records of a table.
- a button within the per-record part of that display which takes you to a view or edit page
- a button which adds a new record, and takes you to a page almost identical to the view or edit page above
It is wrong (IMHO) that you need to write *any* code at all to achieve this. There should be an option in the right-hand pane while editing a button which allows you to specify that this button changes screen (and gives maybe a drop-down of other screen to select which one to go to), and sub-options to indicate whether new record or the recordID of the current record in the layout.
On those lines, the sample app for contacts has 3 almost identical pages - add, detail and edit. As far as I can see, these have each been described (at some length), though they vary only very slightly (labels on the cancel/save/add buttons, whether or not the 'back' button is visible). There ought to be a way to share the commonality of the pages. For instance, if you decided to add a field (or rename a field like 'first name' to 'given name') you'd have to do it in multiple places.
So there's an additional tiny feature request - copy/paste screen.