mseide-msegui-talk — General list for MSEide+MSEgui

Re: [MSEide-MSEgui-talk] IDE

[Fred vS <fi...@ho...>]

Hello Med.

Could you try this:

In menu Project/Project Options/Templates/New Forms/  Column "I"  (Inherited)---> See it only "Inherited Form" is checked, if nothing is checked there is problem.
Also check if DataModule is not checked.

See here:
https://github.com/mse-org/mseide-msegui/assets/3421249/c80f937a-7a57-45ae-8f96-2767f3a05810

Indeed a fix must be done, if nothing was checked.


________________________________
De : mohamed hamza <me...@ho...>
Envoyé : jeudi 28 septembre 2023 12:09
À : General list for MSEide+MSEgui <mse...@li...>
Objet : [MSEide-MSEgui-talk] IDE

Hello Fred,

When a project PRJ is opened .  The menu  File—New--Form—Datamodule display the dialog:
SELECT ANCESTOR  !!!

This does not happen in 4.6 Version.

Med.

Re: [MSEide-MSEgui-talk] IDE

[Fred vS <fi...@ho...>]

Hello Med.

Even worst, here the menu is in Russian and each item shows ANCESTROR.
I hope it is not a invasion...

The good new is that it does not appear with ideU, there all is normal.

Hum, very, very strange, thanks to note it.
I will jump into it asap (I am super busy this week).

Fre;D

________________________________
De : mohamed hamza <me...@ho...>
Envoyé : jeudi 28 septembre 2023 12:09
À : General list for MSEide+MSEgui <mse...@li...>
Objet : [MSEide-MSEgui-talk] IDE

Hello Fred,

When a project PRJ is opened .  The menu  File—New--Form—Datamodule display the dialog:
SELECT ANCESTOR  !!!

This does not happen in 4.6 Version.

Med.

[MSEide-MSEgui-talk] IDE

[mohamed h. <me...@ho...>]

Hello Fred,

When a project PRJ is opened .  The menu  File—New--Form—Datamodule display the dialog:
SELECT ANCESTOR  !!!

This does not happen in 4.6 Version.

Med.

Re: [MSEide-MSEgui-talk] Mailing list & mseide-db woes

[Fred vS <fi...@ho...>]

Hello Sieghard.

How, you did a lot of work, thanks!

I am hyper busy this week but sure I will jump into it this week-end.

Fre;D
________________________________
De : Sieghard via mseide-msegui-talk <mse...@li...>
Envoyé : jeudi 28 septembre 2023 01:42
À : mse...@li... <mse...@li...>
Cc : Sieghard <s_...@ar...>
Objet : Re: [MSEide-MSEgui-talk] Mailing list & mseide-db woes

Hello Fred,

as it's by far finished yet, there is a new version of the "newdialogs"
units available now, along with the accompanying projects "MSEclock" and
now also "PSQLbrowse" for examples of usage. And I did include a short
description of the (IMHO) relevant features in the "newdialogs" zip file,
named "newdialogs.desc" (a simple ASCII text file).
Most dialogs should work as it is now, but there were a couple obstacles to
overcome, and there's still the hurdle of the filedialog to take.

Have a nice time!

--
(Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung
nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem)
-----------------------------------------------------------
Mit freundlichen Grüßen, S. Schicktanz
-----------------------------------------------------------




_______________________________________________
mseide-msegui-talk mailing list
mse...@li...
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] Mailing list & mseide-db woes

[Sieghard <s_...@ar...>]

Hello Fred,

as it's by far finished yet, there is a new version of the "newdialogs"
units available now, along with the accompanying projects "MSEclock" and
now also "PSQLbrowse" for examples of usage. And I did include a short
description of the (IMHO) relevant features in the "newdialogs" zip file,
named "newdialogs.desc" (a simple ASCII text file).
Most dialogs should work as it is now, but there were a couple obstacles to
overcome, and there's still the hurdle of the filedialog to take.

Have a nice time!

-- 
(Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung
nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem)
-----------------------------------------------------------
Mit freundlichen Grüßen, S. Schicktanz
-----------------------------------------------------------

Re: [MSEide-MSEgui-talk] MSEgui and Wayland.

[Fred vS <fi...@ho...>]

Hello everybody.

Thanks Sieghard for the infos.

Some good news from the front.

I finally found a C demo that was working on a Wayland system.
Some tweak needed and some hair to loose to make it compile + run.

Then I tackled the big part: the conversion to Pascal.

My nearly-friend ChatGPT helped me (but loooot of errors and non-sense, but ok, he's still young).

Finally, after hard and painfull fight, I get it: a beautifull Wayland chessboard.

https://github.com/fredvs/wayland-pascal/assets/3421249/694787e4-0b2c-4961-bacd-efb247cee2df

The source is in https://github.com/fredvs/wayland-pascal

And I have a other scoop: I will terminate the combat, I am happy with the first steps, Wayland is accessible to fpc, all the tools are there and work.

But for deeper exploration of Wayland, asap ( as so long as possible).

Fre;D

Re: [MSEide-MSEgui-talk] New versions

[Fred vS <fi...@ho...>]

Hello Sieghard.

> just for your information: the new versions

Nice, I will jump into it, asap ( soon and soft ).

Many thanks.

Fre;D

[MSEide-MSEgui-talk] New versions

[Sieghard <s_...@ar...>]

Hello Fred,

just for your information: the new versions of my newdialogs, along with
the MSEclock and PSQLbrowser, are now available from my mse web site.

-- 
(Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung
nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem)
-----------------------------------------------------------
Mit freundlichen Grüßen, S. Schicktanz
-----------------------------------------------------------

Re: [MSEide-MSEgui-talk] MSEgui and Wayland.

[Sieghard <s_...@ar...>]

Hello Fred,

you wrote on Sat, 23 Sep 2023 02:41:00 +0000:

> Yes, sure and I am far to be ready for a msegui-wayland interface.
> 
> I think that I have all the tools now to use Wayland with fpc, all the
> demos of the demos-book are translated and compile.

Fine - I saw that you presented a Wayland client window picture already.

> But the problem now is the C code from the book, compiling the C demos
> with some surface and shell does not run. It crash at loading.

Well - as I don't have any notion (yet) about what's required here, I'm
totally clueless in this respect - sorry.

> And it seems because of the shell used in the demo are not the one used
> by Ubuntu-wayland. So I have to adapt the code using xdg_shell that is
> used by Ubuntu. And I am a totally newbie in that jungle.

Strange - shells should be freely interchangeable I thought, even on a
graphical system, using a terminal program. Isn't that a terminal window
what your Wayland picture shows? I.e. is that just an empty window without
anything able to accept application requests?
(So, you need a "shell" to run a shell program? Funny...)
...
> Imho, Wayland is far to be ready and x11 has still long days before to
> disapear.

I sure hope so for Linux, and it's no question for the BSDs and similar
systems anyway, as Wayland, AFAIK, is narrowly targeted on Linux only, and
beyond that, on Linux running systemd. I don't run a systemd Linux...
(And I do not want to.)

-- 
(Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung
nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem)
-----------------------------------------------------------
Mit freundlichen Grüßen, S. Schicktanz
-----------------------------------------------------------

Re: [MSEide-MSEgui-talk] MSEgui and Wayland.

[Fred vS <fi...@ho...>]

Hello Sieghard.

>I'd suggest to be a bit more conservative and keep the old structure at
>least until you got "many" signs of agreement from users you asked.

Yes, sure and I am far to be ready for a msegui-wayland interface.

I think that I have all the tools now to use Wayland with fpc, all the demos of the demos-book are translated and compile.

But the problem now is the C code from the book, compiling the C demos with some surface and shell does not run.
It crash at loading.

And it seems because of the shell used in the demo are not the one used by Ubuntu-wayland.
So I have to adapt the code using xdg_shell that is used by Ubuntu.
And I am a totally newbie in that jungle.

(Hum, and then, if I understand ok, with wayland you must compile your application with the shell used by the OS... not very "universal")

Imho, Wayland is far to be ready and x11 has still long days before to disapear.

Fre;D

Re: [MSEide-MSEgui-talk] MSEgui and Wayland.

[Sieghard <s_...@ar...>]

Hello Fred,

you wrote on Wed, 20 Sep 2023 22:27:38 +0000:

> Thanks for the precious infos.

Well. I hope, I'm not too far off with my appreciation.

> I'm (not) sure that MSEgui for Wayland will appear soon but as much
> information as possible is needed to make it appear.

Isn't there an interface to SDL already? According to the little
information I have as to how Wayland is to be used, this shoul be a really
good entry point. As I understood so far, Wayland seems to be more
concerned with separating and segregating applications from each other,
managing security measures and such than to produce a useable and useful
screen presentation. A high-security frmaebuffer manager, so to speak.

[/lib/kernel]
> I would vote to change /kernel/linux into /kernel/unix because there are
> code for BSD OS like FreeBSD, NetBSD, OpenBSD and DragonFlyBSD. And,

If the variations are just minor, some compiler conditionals in some files,
that's certainly warranted. If the BSDs need big chunks of specialized
code, it might be better to segregate that into separate subdiretories of
another level, say like "kernel/unix/linux", "kernel/unix/BSD",
"kernel/unix/Dragonfly" or so.

> because of maybe new graphic interfaces, create directory
> /kernel/unix/x11 and move all the x11-related units form /kernel/unix to
> /kernel/unix/x11.

These could perhaps handled similarly, and maybe in parallel, because the
X11 or Wayland code should be mostly common to all Unices.
And then, there are a few separate directories that might be better put
together into their own collection, like "math", "printer", "report",
"audio", "unicode", even "assistive". But here, the decision has to be made
between a small and deep "tree" structure and a flat and broad "shrub" one.

> For the users, just change in MSEide, config: Target OS = uinx (in place
> of linux). And add in Project/Options/make/Directories:
> ${MSELIBDIR}kernel/$TARGETOSDIR/x11

This is the downside, then - any such modification will require adaptions
on the part of the user, and that is certain to produce, arr, distractions.

> Maybe those change could be done with the new release with all the new

I'd suggest to be a bit more conservative and keep the old structure at
least until you got "many" signs of agreement from users you asked.

> properties, your new dialog files and the new MSEide binary release.

Thank you for your consideration. I will soon (as soon as the flaky
internet connection will allow) provide a new version of the "newdialogs",
but they're still not final yet. I did find quite some "ideosyncrasies"
there, implementations that look backwards to me, e.g. with the
"msecolordialog". That one is used in my "msefontdialog" as well, and that
show a weird effect of the "controller" structure, thwarting any attempt
to allow (some, at least) dialogs called within dialogs to be positioned
in an application defined manner. I "resolved" this problem for now by the
new "showatmouse" positiong function, but that's probabely not what
everyone would want. And I didn't even deal with the "msefiledialog" yet,
which, as you know, is a tremendous baest by itself.
But anyway, I'll provide what I have now, as there aremany corrections,
a new statfile functionality, and they're now needed for the "MSEclock"
and "PSQLbrowser" kind-of-reference applications. Sadly, I've still not
found (not had the time to, yet) sufficient information about the SQLite
internals needed for an equivalent database application for that, as that
would provide a lot of data to inspect, using the mozilla data repositories
from everyone's profiles. (Yes, and I didn't put together some exampl data
for database applications for the same reasons...)

And, BTW, you wrote on Thu, 21 Sep 2023 23:21:25 +0000:

> For the fun, I started a new Github project:
> https://github.com/fredvs/wayland-pascal

Hopefully, this can soon be "filled with life", but beyond this, many
thanks for the appending further links, I'll look over them when I can.

-- 
(Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung
nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem)
-----------------------------------------------------------
Mit freundlichen Grüßen, S. Schicktanz
-----------------------------------------------------------

Re: [MSEide-MSEgui-talk] MSEgui and Wayland.

[Fred vS <fi...@ho...>]

Hello Vasi.

Yes, I know but... I already found a solution and it works, so I will continue the fight (even that I admit that Wayland is not wow)!

See screenshot:
https://github.com/fredvs/wayland-pascal/assets/3421249/e8053dbc-a7e7-4c8a-a206-bbd7ded16a84

The trick was to create a library-for-work with the declared functions and use that library for linking.
That library is only need for linking, users dont need it.
So now I think I get great keys.

Hum, yes, sorry but once again ChatGPT helped me a lot.
Here his answer:

--------------------------------------

If the `wl_display_get_registry` and `wl_registry_add_listener` functions are inlined in the C/C++ headers and you cannot directly access them from Pascal due to the inlining, you may need to use a workaround.

One approach is to create C/C++ wrapper functions that encapsulate the inlined Wayland functions and then call those wrapper functions from your Pascal code. Here's an example of how you can create such wrappers:

1. Create a C/C++ file, e.g., `wayland_wrapper.c`, and define wrapper functions for the inlined functions:

```c
// wayland_wrapper.c
#include <wayland-client.h>

// Wrapper for wl_display_get_registry
struct wl_registry* my_wl_display_get_registry(struct wl_display* display) {
    return wl_display_get_registry(display);
}

// Wrapper for wl_registry_add_listener
int my_wl_registry_add_listener(struct wl_registry* registry,
                                const struct wl_registry_listener* listener,
                                void* data) {
    return wl_registry_add_listener(registry, listener, data);
}
```

2. Compile `wayland_wrapper.c` into a shared library (e.g., `libwayland_wrapper.so`):

```bash
gcc -fPIC -shared -o libwayland_wrapper.so wayland_wrapper.c -lwayland-client
```

3. In your Pascal code, use the `external` keyword to declare the wrapper functions:

```pascal
function my_wl_display_get_registry(display: pwl_display): pwl_registry; cdecl; external 'libwayland_wrapper';
function my_wl_registry_add_listener(registry: pwl_registry; listener: Pwl_registry_listener; data: pointer): cint; cdecl; external 'libwayland_wrapper';
```

4. Use these wrapper functions in your Pascal code as needed.

By creating C/C++ wrappers, you can access the inlined Wayland functions indirectly from your Pascal code. Make sure to link your Pascal program with the `libwayland_wrapper.so` shared library when building your Pascal project.

This approach allows you to work around the issue of inlined functions in the Wayland headers and use them in your Pascal code effectively.



________________________________
De : vasi vasi <fu...@gm...>
Envoyé : vendredi 22 septembre 2023 19:10
À : General list for MSEide+MSEgui <mse...@li...>
Objet : Re: [MSEide-MSEgui-talk] MSEgui and Wayland.

Fred,

let the Wayland team to solve the problems they created in forcing the move from X-Window with a half baked solution. We (me and my family) use X server because is the only one that correctly manages the Wacom tablet.

For now we don't care about Wayland is not useful for us and is really their problem.

Wait for when things are usable. Not worth the effort at the expense of your health.

On Fri, Sep 22, 2023 at 6:40 PM Fred vS <fi...@ho...<mailto:fi...@ho...>> wrote:
Hello everybody.

I am already blocked because some methods in wayland-client.so are inlined and not accessible for fpc.

I have asked it to the maintainer of the Wayland book with the demos:
https://github.com/bugaevc/writing-wayland-clients/issues/2

But I dont understand his solution.

Do you have a idea what should be done to access those methods?

Fre;D

________________________________
De : Fred vS <fi...@ho...<mailto:fi...@ho...>>
Envoyé : vendredi 22 septembre 2023 01:21
À : General list for MSEide+MSEgui <mse...@li...<mailto:mse...@li...>>
Objet : Re: [MSEide-MSEgui-talk] MSEgui and Wayland.

Hello everybody.

For the fun, I started a new Github project: https://github.com/fredvs/wayland-pascal

It takes inspiration of the demos from:
https://bugaevc.gitbooks.io/writing-wayland-clients/content/black-square/first-steps.html
(Yes, I confess, I was helped by ChatGPT for the translation of the C demos to Pascal.)

It uses the excellent fpc-wayland Bindings Generator for freepascal from Andrews Haines.
https://github.com/andrewd207/fpc-wayland

The goal is to discover step by step, with code, how to make Wayland work with fpc.
And maybe one day adapt this for msegui.

The first step is a Pascal program that connect to a Wayland Client (of course you need a Wayland session):

https://github.com/fredvs/wayland-pascal/assets/3421249/1a29cd1b-5af0-4fd4-9b70-d87a9a4e9148

Fre;D
_______________________________________________
mseide-msegui-talk mailing list
mse...@li...<mailto:mse...@li...>
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk


--
Vasi

Re: [MSEide-MSEgui-talk] MSEgui and Wayland.

[vasi v. <fu...@gm...>]

Fred,

let the Wayland team to solve the problems they created in forcing the move
from X-Window with a half baked solution. We (me and my family) use X
server because is the only one that correctly manages the Wacom tablet.

For now we don't care about Wayland is not useful for us and is really
their problem.

Wait for when things are usable. Not worth the effort at the expense of
your health.

On Fri, Sep 22, 2023 at 6:40 PM Fred vS <fi...@ho...> wrote:

> Hello everybody.
>
> I am already blocked because some methods in wayland-client.so are inlined
> and not accessible for fpc.
>
> I have asked it to the maintainer of the Wayland book with the demos:
> https://github.com/bugaevc/writing-wayland-clients/issues/2
>
> But I dont understand his solution.
>
> Do you have a idea what should be done to access those methods?
>
> Fre;D
>
> ------------------------------
> *De :* Fred vS <fi...@ho...>
> *Envoyé :* vendredi 22 septembre 2023 01:21
> *À :* General list for MSEide+MSEgui <
> mse...@li...>
> *Objet :* Re: [MSEide-MSEgui-talk] MSEgui and Wayland.
>
> Hello everybody.
>
> For the fun, I started a new Github project:
> https://github.com/fredvs/wayland-pascal
>
> It takes inspiration of the demos from:
>
> https://bugaevc.gitbooks.io/writing-wayland-clients/content/black-square/first-steps.html
> (Yes, I confess, I was helped by ChatGPT for the translation of the C
> demos to Pascal.)
>
> It uses the excellent fpc-wayland Bindings Generator for freepascal from
> Andrews Haines.
> https://github.com/andrewd207/fpc-wayland
>
> The goal is to discover step by step, with code, how to make Wayland work
> with fpc.
> And maybe one day adapt this for msegui.
>
> The first step is a Pascal program that connect to a Wayland Client (of
> course you need a Wayland session):
>
>
> https://github.com/fredvs/wayland-pascal/assets/3421249/1a29cd1b-5af0-4fd4-9b70-d87a9a4e9148
>
> Fre;D
> _______________________________________________
> mseide-msegui-talk mailing list
> mse...@li...
> https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
>


-- 
Vasi

Re: [MSEide-MSEgui-talk] MSEgui and Wayland.

[Fred vS <fi...@ho...>]

Hello everybody.

I am already blocked because some methods in wayland-client.so are inlined and not accessible for fpc.

I have asked it to the maintainer of the Wayland book with the demos:
https://github.com/bugaevc/writing-wayland-clients/issues/2

But I dont understand his solution.

Do you have a idea what should be done to access those methods?

Fre;D

________________________________
De : Fred vS <fi...@ho...>
Envoyé : vendredi 22 septembre 2023 01:21
À : General list for MSEide+MSEgui <mse...@li...>
Objet : Re: [MSEide-MSEgui-talk] MSEgui and Wayland.

Hello everybody.

For the fun, I started a new Github project: https://github.com/fredvs/wayland-pascal

It takes inspiration of the demos from:
https://bugaevc.gitbooks.io/writing-wayland-clients/content/black-square/first-steps.html
(Yes, I confess, I was helped by ChatGPT for the translation of the C demos to Pascal.)

It uses the excellent fpc-wayland Bindings Generator for freepascal from Andrews Haines.
https://github.com/andrewd207/fpc-wayland

The goal is to discover step by step, with code, how to make Wayland work with fpc.
And maybe one day adapt this for msegui.

The first step is a Pascal program that connect to a Wayland Client (of course you need a Wayland session):

https://github.com/fredvs/wayland-pascal/assets/3421249/1a29cd1b-5af0-4fd4-9b70-d87a9a4e9148

Fre;D

Re: [MSEide-MSEgui-talk] MSEgui and Wayland.

[Fred vS <fi...@ho...>]

Hello everybody.

For the fun, I started a new Github project: https://github.com/fredvs/wayland-pascal

It takes inspiration of the demos from:
https://bugaevc.gitbooks.io/writing-wayland-clients/content/black-square/first-steps.html
(Yes, I confess, I was helped by ChatGPT for the translation of the C demos to Pascal.)

It uses the excellent fpc-wayland Bindings Generator for freepascal from Andrews Haines.
https://github.com/andrewd207/fpc-wayland

The goal is to discover step by step, with code, how to make Wayland work with fpc.
And maybe one day adapt this for msegui.

The first step is a Pascal program that connect to a Wayland Client (of course you need a Wayland session):

https://github.com/fredvs/wayland-pascal/assets/3421249/1a29cd1b-5af0-4fd4-9b70-d87a9a4e9148

Fre;D

Re: [MSEide-MSEgui-talk] TR:FILTER

[Fred vS <fi...@ho...>]

Hello Med.

OK, I will commit it.
Thanks for the demos, I will commit it in mseuniverse asap.

Fre;D

________________________________
De : mohamed hamza <me...@ho...>
Envoyé : jeudi 21 septembre 2023 18:37
À : General list for MSEide+MSEgui <mse...@li...>
Objet : Re: [MSEide-MSEgui-talk] TR:FILTER

Hello Fred;

  That's  works, I think this change is usefull  because The dropdown ignores the filter set from tbnav.
 Now  we can  change this behaviour.  It's up  to you to decide.

Ps:See the new demo .

Med.

________________________________
De : Fred vS <fi...@ho...>
Envoyé : mercredi 20 septembre 2023 23:24
À : General list for MSEide+MSEgui <mse...@li...>
Objet : Re: [MSEide-MSEgui-talk] TR:FILTER

Re-hello Med.

The change to be done is in /mseide-msegui/lib/common/db/msedbedit.pas,
Line 237, add this:

 published
   property datalink: tnavigdatalink read fdatalink; // add this


Fre;D

________________________________
De : Fred vS <fi...@ho...>
Envoyé : jeudi 21 septembre 2023 01:09
À : General list for MSEide+MSEgui <mse...@li...>
Objet : Re: [MSEide-MSEgui-talk] TR:FILTER

Hello Med.

No, I dont think I made a commit to make it public already, it was a test-exploration.
Maybe you may try changing the code and assign it as public.

If all ok, we can do it.

Note that for all DB things I am extremely prudent because I dont master the land, so I commit things only if you agree.

Fre;D

________________________________
De : mohamed hamza <me...@ho...>
Envoyé : mercredi 20 septembre 2023 21:19
À : General list for MSEide+MSEgui <mse...@li...>
Objet : [MSEide-MSEgui-talk] TR:FILTER

Hello Fred,

   On one of your mail to show the tips for setting filter manually   Re: [MSEide-MSEgui-talk] FILTER (mail-archive.com)<https://www.mail-archive.com/mse...@li.../msg14879.html>

I tried that but I got error : identifier indents not member datalink.  I think because  datalink is not yet PUBLIC , is it?

Thank you, Med

Re: [MSEide-MSEgui-talk] TR:FILTER

[mohamed h. <me...@ho...>]

Hello Fred;

  That's  works, I think this change is usefull  because The dropdown ignores the filter set from tbnav.
 Now  we can  change this behaviour.  It's up  to you to decide.

Ps:See the new demo .

Med.

________________________________
De : Fred vS <fi...@ho...>
Envoyé : mercredi 20 septembre 2023 23:24
À : General list for MSEide+MSEgui <mse...@li...>
Objet : Re: [MSEide-MSEgui-talk] TR:FILTER

Re-hello Med.

The change to be done is in /mseide-msegui/lib/common/db/msedbedit.pas,
Line 237, add this:

 published
   property datalink: tnavigdatalink read fdatalink; // add this


Fre;D

________________________________
De : Fred vS <fi...@ho...>
Envoyé : jeudi 21 septembre 2023 01:09
À : General list for MSEide+MSEgui <mse...@li...>
Objet : Re: [MSEide-MSEgui-talk] TR:FILTER

Hello Med.

No, I dont think I made a commit to make it public already, it was a test-exploration.
Maybe you may try changing the code and assign it as public.

If all ok, we can do it.

Note that for all DB things I am extremely prudent because I dont master the land, so I commit things only if you agree.

Fre;D

________________________________
De : mohamed hamza <me...@ho...>
Envoyé : mercredi 20 septembre 2023 21:19
À : General list for MSEide+MSEgui <mse...@li...>
Objet : [MSEide-MSEgui-talk] TR:FILTER

Hello Fred,

   On one of your mail to show the tips for setting filter manually   Re: [MSEide-MSEgui-talk] FILTER (mail-archive.com)<https://www.mail-archive.com/mse...@li.../msg14879.html>

I tried that but I got error : identifier indents not member datalink.  I think because  datalink is not yet PUBLIC , is it?

Thank you, Med

Re: [MSEide-MSEgui-talk] TR:FILTER

[Fred vS <fi...@ho...>]

Re-hello Med.

The change to be done is in /mseide-msegui/lib/common/db/msedbedit.pas,
Line 237, add this:

 published
   property datalink: tnavigdatalink read fdatalink; // add this


Fre;D

________________________________
De : Fred vS <fi...@ho...>
Envoyé : jeudi 21 septembre 2023 01:09
À : General list for MSEide+MSEgui <mse...@li...>
Objet : Re: [MSEide-MSEgui-talk] TR:FILTER

Hello Med.

No, I dont think I made a commit to make it public already, it was a test-exploration.
Maybe you may try changing the code and assign it as public.

If all ok, we can do it.

Note that for all DB things I am extremely prudent because I dont master the land, so I commit things only if you agree.

Fre;D

________________________________
De : mohamed hamza <me...@ho...>
Envoyé : mercredi 20 septembre 2023 21:19
À : General list for MSEide+MSEgui <mse...@li...>
Objet : [MSEide-MSEgui-talk] TR:FILTER

Hello Fred,

   On one of your mail to show the tips for setting filter manually   Re: [MSEide-MSEgui-talk] FILTER (mail-archive.com)<https://www.mail-archive.com/mse...@li.../msg14879.html>

I tried that but I got error : identifier indents not member datalink.  I think because  datalink is not yet PUBLIC , is it?

Thank you, Med

Re: [MSEide-MSEgui-talk] TR:FILTER

[Fred vS <fi...@ho...>]

Hello Med.

No, I dont think I made a commit to make it public already, it was a test-exploration.
Maybe you may try changing the code and assign it as public.

If all ok, we can do it.

Note that for all DB things I am extremely prudent because I dont master the land, so I commit things only if you agree.

Fre;D

________________________________
De : mohamed hamza <me...@ho...>
Envoyé : mercredi 20 septembre 2023 21:19
À : General list for MSEide+MSEgui <mse...@li...>
Objet : [MSEide-MSEgui-talk] TR:FILTER

Hello Fred,

   On one of your mail to show the tips for setting filter manually   Re: [MSEide-MSEgui-talk] FILTER (mail-archive.com)<https://www.mail-archive.com/mse...@li.../msg14879.html>

I tried that but I got error : identifier indents not member datalink.  I think because  datalink is not yet PUBLIC , is it?

Thank you, Med

Re: [MSEide-MSEgui-talk] MSEgui and Wayland.

[Fred vS <fi...@ho...>]

Hello Sieghard.

Thanks for the precious infos.
I'm (not) sure that MSEgui for Wayland will appear soon but as much information as possible is needed to make it appear.

Also maybe it would be good to reorder-rename the sub-directories in /lib/kernel/.
Actually there is /kernel/windows and /kernel/linux.

I would vote to change /kernel/linux into /kernel/unix because there are code for BSD OS like FreeBSD, NetBSD, OpenBSD and DragonFlyBSD.
And, because of maybe new graphic interfaces, create directory /kernel/unix/x11 and move all the x11-related units form /kernel/unix to /kernel/unix/x11.

For the users, just change in MSEide, config: Target OS = uinx (in place of linux).
And add in Project/Options/make/Directories: ${MSELIBDIR}kernel/$TARGETOSDIR/x11

And just change the sub-directory to compile with a other gui interface.

Maybe those change could be done with the new release with all the new properties, your new dialog files and the new MSEide binary release.
Of course MSEgui Wayland and will only "todo"


Fre;D

[MSEide-MSEgui-talk] TR:FILTER

[mohamed h. <me...@ho...>]

Hello Fred,

   On one of your mail to show the tips for setting filter manually   Re: [MSEide-MSEgui-talk] FILTER (mail-archive.com)<https://www.mail-archive.com/mse...@li.../msg14879.html>

I tried that but I got error : identifier indents not member datalink.  I think because  datalink is not yet PUBLIC , is it?

Thank you, Med

Re: [MSEide-MSEgui-talk] MSEgui and Wayland.

[Fred vS <fi...@ho...>]

Hello Sieghard.

Thanks for the precious infos.
I'm (not) sure that MSEgui for Wayland will appear soon but as much information as possible is needed to make it appear.

Also maybe it would be good to reorder-rename the sub-directories in /lib/kernel/.
Actually there is /kernel/windows and /kernel/linux.

I would vote to change /kernel/linux into /kernel/unix because there are code for BSD OS like FreeBSD, NetBSD, OpenBSD and DragonFlyBSD.
And, because of maybe new graphic interfaces, create directory /kernel/unix/x11 and move all the x11-related units form /kernel/unix to /kernel/unix/x11.

For the users, just change in MSEide, config: Target OS = uinx (in place of linux).
And add in Project/Options/make/Directories: ${MSELIBDIR}kernel/$TARGETOSDIR/x11

And just change the sub-directory to compile with a other gui interface.

Maybe those change could be done with the new release with all the new properties, your new dialog files and the new MSEide binary release.
Of course MSEgui Wayland and will only "todo"


Fre;D

Re: [MSEide-MSEgui-talk] MSEgui and Wayland.

[Sieghard <s_...@ar...>]

Hello Fred,

you wrote on Sun, 17 Sep 2023 23:06:53 +0000:

> There is a advice about Wayland and how to do enable it for a widgetset
...
> it's just a wrapper around the C binding. It can render to SDL or GLFW.

So that could be a basic function set enabling msegui on Wayland?

> Actually for your case (porting an existing widget set to Wayland) that's
> an approach that might make sense, even though it may be quite different
> from the workings of your X11 GUI. Wayland doesn't provide drawing
> primitives - you create surfaces (e.g. a window, or part of a window),
> you attach a buffer to them and then you render into the buffer.

Well, that's not so different from the usual (and current)  approach,
drawing into a buffer and making the graphic system display that after
completion. The difference here is obviously that the graphic system does
NOT provide a full set of drawing functions, like X11 does. Thus, some such
function set, like SDL (or the X11 primitives), will be needed additionally,
requiring a complete rework of the basics. I.e. besides a "windows" and a
"linux" kernel abstraction layer, another, "wayland" or "sdl" or whatever,
will be needed, although "sdl" alone probabely won't suffice for lack of
the Wayland bindings.

> Hum, do you think that MSEgui could create that surface and attach to a
> buffer of is it the same problem as for "Save Form to BMP" that
> LagProgramming related?

Yes, to some extend that's a similar task and will require similar work.
Probabely the former (Wayland) will then provide the solution for the
latter just as a side effect.

-- 
(Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung
nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem)
-----------------------------------------------------------
Mit freundlichen Grüßen, S. Schicktanz
-----------------------------------------------------------

[MSEide-MSEgui-talk] MSEgui and Wayland.

[Fred vS <fi...@ho...>]

There is a advice about Wayland and how to do enable it for a widgetset here:

https://gist.github.com/probonopd/9feb7c20257af5dd915e3a9f2d1f2277?permalink_comment_id=4695433#gistcomment-4695433

The advice was:


ImGui has a Pascal binding<https://github.com/dpethes/imgui-pas>, even if it's just a wrapper around the C binding. It can render to SDL or GLFW.

Actually for your case (porting an existing widget set to Wayland) that's an approach that might make sense, even though it may be quite different from the workings of your X11 GUI. Wayland doesn't provide drawing primitives - you create surfaces (e.g. a window, or part of a window), you attach a buffer to them and then you render into the buffer.


Hum, do you think that MSEgui could create that surface and attach to a buffer of is it the same problem as for "Save Form to BMP" that LagProgramming related?

Re: [MSEide-MSEgui-talk] Mailing list & mseide-db woes

[Sieghard <s_...@ar...>]

Hello Fred,

you wrote on Sat, 16 Sep 2023 23:00:28 +0000:

[onmouseevent]
> Ha, ok, so I will add it in the "todo list of new properties" for next
> MSEide.

Alright. I've enabled it in my copy since the last version.

> >for the db code, I tested the PostgreSQL unit(s) using my "FieldError"  
...
> I did not test your last version, is it still on your web site?

No, sadly, there IS no latest version yet, since I didn't get along with
the PSQLbrowser test application yet, since I embarked on reworking my
"newdialogs".
This latter took me quite some time, since I couldn't find the reason why
some dialogs were "working perfectly" (or at least about as intended), but
others just wouldn't do what they apparently even DID - it just didn't show
up. The topic here is "automatically saving position [and perhaps other
data] for transiently created dialogs", menaing that it should not be
neccessary to keep their forms and data all the time an application runs.
The means to do this are "memory stat files", and they ARE able to perform
the task. But _some_ constructs - it seems, notably those using the dreaded
"controller" theme - use stat files in such an intricately convoluted
manner that it is nearly impossible to track their roamings and activities.
But by now, I've managed - albeit with some modifications to some existing
dialogs - to have them comply, except for those that use a controller
creating an unnamed and unowned internal form itself, leading to a clash
and a subsequent exception.

> But I fear that Med would be a much better tester than me for all about
> DB things.

If he wants to accept the task to do it on behalf of msegui deleopment
alone. Sure, it's helpful when someone does the testing of a new feature
using it in his application code, although really testing something needs a
lot more than that - many testing situations, on "all" supported systems,
and reporting problems, resolving them and re-testing again and again...

> >Well, yes, and that's a real challenge for a very small "team" of at
> >most a couple people as for mseide-msegui...  
> 
> Yes, I know, we are not many but we are brave. 😉

Well... How many are you? I'm afraid that would be the effective number of
testers and maintainers in the end...
You're doing a _really_ tough job, and you're doing it _really_ well.
And there should really be differnt people, with differnt opinions, working
together on that task, or should I write "mission"?

-- 
(Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung
nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem)
-----------------------------------------------------------
Mit freundlichen Grüßen, S. Schicktanz
-----------------------------------------------------------