Patrick PREMARTIN

For an internal app in a company or paid users Thinfinity can be a good simple solution. For a public website it's too expensive. Use Delphi as a server on Windows or Linux if you want and dynamic website solutions (from Delphi or others). For an e-commerce site it could be easier to use an existing solution like LiteCart (simple, easy to use) or Prestashop (more complex but full of features for any commerce) and synchronize its database to your real DB.

It's the Mac mini M1 I use. I bought it after the GTK to check if I could work on it with Windows VMs and never changed. The only thing that really annoys me is the SSD, which I also took to be too small and supplemented by external disks around the case. Buying an Intel Mac is a bad idea. Buy a "real" PC instead of that. The Intel based models can't soon use latests macOS releases and you won't be able to code for macOS or iOS. The M1 should still have 2 or 3 years before being deprecated.

Hi Is FireDAC.Phys.SQLiteWrapper added somewhere in your code by the IDE or is it used by FireDAC itself ? What happen when you remove it (in the first case). Is TFDPhysSQLiteDriver component used somewhere in the program ? Did you tried to change the driver type ("native" SQLite or FDE) ?

You don't need to set their Name. It's only necessary for the TFrame container. The Name property is only needed to link variables in the classes and the ressources in the DFM/FMX. When you create things by code the Name is not used. Inside the component store your objects instances in private or protected fields/variables instead of local variables in the methods. It won't depend on the possible auto generated names.

Just for the others, the webinar is this one "create components without creating components" : (in French, with auto caption and auto translation available in YT player). For the Name, yes. If you want to use more than ont "TFrame component" on your forms it's needed. And for the access to components, never use it : create public or published properties. The user of a component don't have to know its content. It can move, the components order can change, and with FMX if you deal with styles one day it's too dangerous. It's not a good plan for long-term maintenance.

Just one more thing : if you use a container (Control, Layout or TFrame) as a component, don't forget to align the components you create in it or manage the Resize(d) event to fixed their size in the container.

Hi I fixed the "essai" project. Here it is with a sample project. The Stored property must be used to avoid the copy of components in the DFM/FMX file. If you forgot it the program create local components in front of the objects created by the component. The click worked, but you couldn't click on the good button. To test if you do things good, use Alt+F12 in the form editor one or more times. If it adds components in the structure view, you missed the Stored and have to use it. You also need to (re)publish position&other properties on your Control descendant if you want to display it at the same position than in the IDE when you execute the program. I let you fixe your real component and tell us if its good or if you need more hep on it. 🙂 Essai-fixed.zip

After some check on my repositories, here are two FMX components you could use as sample to adapt your code : - A TBitBtn like component with a TText and a TGlyph as a TControl descendant. I created a TFrame to show what I need and transformed the code to this to obtain my component. (search "Stored" and see ho I manage the click event for the TControl) https://github.com/DeveloppeurPascal/Pairpix/blob/main/src/uGameButton.pas - The non visual component for my About Box dialog which does some things in the IDE and others on a real project like changing the main form Caption. (search "ComponentState" in the source and see how I manage the component properties) https://github.com/DeveloppeurPascal/AboutDialog-Delphi-Component/blob/main/src/Olf.FMX.AboutDialog.pas

Using a TFrame in the form editor don't manage its published properties. You have to register it as a real component for that. For the name, the simpler way to manage it is to add "Name := ''" in the TFrame constructor. The IDE will do the needed things to give one and if you create it by code you won't have the problem of duplicate names. The Click event should work but by doing like in your code you'll have a risk of duplicate components depending on how the users/developers use your component. Add published property as TNotifyEvent on the TFrame and put its value to your button in an override AfterConstruction method. It should work better. Don't forget to check ComponentState variable to do the good thing between IDE form editor and a real program.

The predictive suggestions is an OS feature, the STYLED recreate the memo feature instead of PLATFORM. No complaints here, but I have not enough Mac&iOS users to complain with a broken Apple feature which suggest wrong or strange words and replace good once by others in French.

Hi Did you asked to their support ? What release of macOS do you use ? Did you tried on an other Mac ?

Hi The USB token is not the only solution : some providers allow to use an online hosted token too. If you can't find an other solution than USB, you can perhaps use Exe Bulk Signing ( https://github.com/DeveloppeurPascal/ExeBulkSigning ) in client/server mode to sign on a distant computer from yours, but exposing a signing software is safer on a local network or a VPN than over the Internet.

Great, I'll check it and add your repo to the list I've done around this presentation.

Good idea. You can perhaps add a TImageCollection export with an icons selection list or the source code to use the SVG directly in a unit ? It could be a good alternative to use vector images in final projects.

The multi view is a good idea for smartphones but a menu on Windows and a toolbar on Mac are better. Why having to click somewhere to access things we could have on screen without clicking on it ? (and don't forget keys shortcuts) Depending on the app, don't forget Android can be used on Chromebooks and other devices with a real keyboard.