Re: Recomended front ends?

For web/mobile applications we use Mojolicious, https://mojolicious.org witch
work pretty well with Postgresql, is written in Perl and has plenty of nice
features.
Paolo Saudin

Il giorno gio 8 ago 2019 alle ore 22:09 DiasCosta <diascosta(at)diascosta(dot)org>
ha scritto:

> Hi,
> After many years of using Oracle Forms and Oracle Reports with Oracle DB,
> I have been using Lazarus and "Code Typhon"
> for many years now.
> Both work with Free Pascal Compiler and both are open source and free.
> Both have a very good IDE, the code produced is Pascal (very easily
> readable), and they connect directly to many DBMS including PostgreSQL,
> Oracle, MSSQL, SQLITE, etc..
>
> You can find information here:
> https://en.wikipedia.org/wiki/Lazarus_(IDE)
> and here: https://www.pilotlogic.com/sitejoom/
>
> Also here: https://en.wikipedia.org/wiki/Lazarus_(IDE)
> you can find some interesting information.
>
> Also here: https://www.getlazarus.org/learn/tutorials/intro/
> "If you are haven't used Lazarus <http://www.lazarus-ide.org> recently
> then this tutorial is for you. In it we give users a broad overview of
> Lazarus
> and some of its key features. We look at the type of applications you can
> create with Lazarus, and show you the core
> concepts to desktop application development it makes so very easy.
> Highlights include the two way design process, events handlers, testing
> and debugging, and deployment.
> A brief gallery of applications
> <https://www.getlazarus.org/community/showcase> I've personally created
> with Lazarus is included at the end, and I honestly believe it's
> the best tool in the world for developing platform agnostic desktop
> applications. Like the video says, give Lazarus a try
> <https://www.getlazarus.org/setup>."
>
>
> Dias Costa
>
>
>
>
>
>
>
>
>
> On 08-08-2019 20:26, Basques, Bob (CI-StPaul) wrote:
>
> All,
>
> No Web driven, but . . . . we’ve had some success with using LibreOffice(calc) as a frontend. Fairly easy to build forms, etc. Only limited experience so far, but was able to build domain lists from SQL calls, for form pulldown lists, etc.
>
> bobb
>
>
>
> On Aug 8, 2019, at 2:10 PM, Rich Shepard <rshepard(at)appl-ecosys(dot)com> <rshepard(at)appl-ecosys(dot)com> wrote:
>
> Think Before You Click: This email originated outside our organization.
>
>
> On Thu, 8 Aug 2019, Tim Clarke wrote:
>
>
> We tried Django without any pleasant results.
>
> Tim,
>
> That's unexpected and too bad.
>
>
> I'd also caution using MS Access, we're desperate to get away from it.
> Sharing code has challenges and it is horribly aggressive with caching
> unless you use un-bound forms and write all the CRUD interface code
> yourself.
>
> Slightly off-topic, but I've not seen anything good about Access. My
> understanding is it's a flat-file database intended as a user front end to
> Microsoft's relational database product. My experiences with those who use
> it have been painful.
>
> Just yesterday I downloaded a very large database of fisheries data from a
> federal agency and have started translating it to postgres using the
> mdbtools. There's no schema provided, only 32 pages of table columns and
> types without descriptions of the column names. No primary keys, no foreign
> keys, and only 66 tables were found in the .mdb file while all table names
> starting with s through z were not available. There are also many tables
> that hold redundant data which should not exist as the contents are easily
> generated by SQL queries. It will take me a while to make it a working
> relational database.
>
> Rich
>
>
>
>
>
>
> --
> J. M. Dias Costa
> Telef. 214026948 Telem. 939307421
>
> Se divulgar esta mensagem por terceiros, por favor:
> 1. Apague o meu endereço de correio electrónico e o meu nome.
> 2. Apague também os endereços dos seus amigos antes de distribuir.
> 3. Enderece como cópia oculta (Cc ou Bcc) para os SEUS destinatários.
> Agindo deste modo, dificultará a disseminação de "vírus", "spams" e
> "banners" e contribuirá para manter a privacidade de todos e cada um.
> Obrigado.
>
> Nota: Não se deverá ao acaso a ocorrência de palavras na minha escrita que não respeitem o
> malfadado acordo ortográfico.
>
>