Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

[Sieghard via mseide-msegui-talk]

Hallo Fred,

vous ecrit au Mon, 31 Oct 2022 23:48:54 +:

> > What? You DID WRITE IT YOURSELF that you had created such a"folder"
> 
> Yes, sorry, I did try lot of things before to discover the
> hidden .msetools folder. By default my files manager does not show
> hidden folders.

That's, IMHO, "bad practice" for a developer, especially when he's
also the system administrator. At least for me, I can say that one
definitely NEEDS to have a detailed view of one's system, specifically
the part one "owns dearly".

> So in one of the try I added the parameter -dstocklangs_from_libpath.

And did you also put the files at the implied destination
("/usr/share/locale//LC_MESSAGES/")? It should have
worked then. And the destination is "in plain sight" to everyone.

> And forgot to remove it when I discovered .msetools and add it
> in /home/fred/.msetools. When I removed that parameter, all was ok.

Well, in turmoil, trouble may happen...

> About the use of files out of the all-in-one, yes, I agree with you
> ( but only for hidden-config files, and in the home folder if
> possible.  :-) )

IMFO the user's home directory isn't really a very good location, if
more than one user exists and is meant to use the files. Of course,
this doen't apply for single-user desktop installations, especially
those of the Debian style (that I dislike), where the "main" user is
the system administrator as well - and therewith, if compromised, the
whole system is trashed. (BTW, on my system, I created user accounts
with reduced right to access external ressources, i.e. internet sites,
even for email and news.)

> >  Did you get it to _work_ now? You don't tell.
> 
> Yes, of course and it works great.

Ok, I'm contend if it works - it's work in progress, and rather a
suggestion than a finished implementation. You may fiddle with all
the knobs turnable, e.g. the locations of files, the handling of
preferences or whatever.

Wasn't it a rewarding feature when you can claim that mseide-msegui has
THE superior localization system? Although, I'm afraid, that's still a
long way to go until there...

Best wishes, and keep up the good work!

-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

[Fred van Stappen]

Hello Sieghard.

> What? You DID WRITE IT YOURSELF that you had created such a"folder"

Yes, sorry, I did try lot of things before to discover the hidden .msetools 
folder.
By default my files manager does not show hidden folders.

So in one of the try I added the parameter -dstocklangs_from_libpath.
And forgot to remove it when I discovered .msetools and add it in 
/home/fred/.msetools.
When I removed that parameter, all was ok.
Voila, for the story.

About the use of files out of the all-in-one, yes, I agree with you ( but only 
for hidden-config files, and in the home folder if possible.  :-) )

>  Did you get it to _work_ now? You don't tell.

Yes, of course and it works great.
But I have to study deeper your code.

Many thanks Sieghard.

Fre;D
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

[Sieghard via mseide-msegui-talk]

Hallo Fred,

vous ecrit au Mon, 31 Oct 2022 08:27:22 +:

> OK, I get it ( had not see the .msetools folder because it was
> hidden).

What? You DID WRITE IT YOURSELF that you had created such a
"folder" (I heartily dislike this denomination), and you presented a
listing of its contents with your last posting!
I thought to remember that it's usually created by mseide-msegui's
installation process, but searching for it, I cannot find it mentioned
anywhere there. So this might have been a wrong reminiscence of mine,
and it should better go somewhere else. But that's not a problem, as
this is STILL an unfinished - and perhaps even unwelcome, project.

> So your idea is to split the po files into a "main_msegui" in
> home/user/.msetools/lang and the "app_lang" po files.

Yes, so to speak. (Although I aimed at .mo files, rather.)

> Yes, of course usefull if you have mainy msegui applications
> installed. I am not sure if I like it inside a hidden folder, I
> prefer open things, but yes, why not.

It pays even if you've only two of them installed. But yes, oh my, I
realize the response: "but memory, especially disk memory, is so cheap
these days"... I'm just not of this crowd.
But it _also_ pays for the application writer - they will no longer
have to create translations for all of the stock items over and over
again, as they can rely on these being pre-translated and ready for
use. (But if need be, they _can_ override them.)
And what about your preference for open things - yes, gladly, what do
you suggest?

> Personnaly I prefer all in one (all files in directory of app) and

This WILL NOT WORK on Windows, AFAIK - they explicitely deny an
application to access data residing in the executable installation
area, I heard. But it was said that there's a sneaky way how the system
fakes such a possibility for unbehaving applications.

> out-of-the-box (no files to be installed outside the folder of app)
> but I know it is not the  accademic Linux way.

No, you know wrong here - it's perfectly possible for an application
_a user installs in his home directory_. It's just not feasible (and
not really useful, nor advisable) to do that for a system wide
installation.
Say, someone wanted to install the "msegit" and "msespice" applications
for all users of his machine. Then, they are to be installed so that
- the application executable should go into "/usr/bin" or
  "/usr/local/bin"
- any application specific libraries go into "/usr/lib" or
  "/usr/local/lib" (doesn't apply for fpc applications)
- and system-wide available application specific data usually reside in
  some application directory within "/usr/share" or "/usr/local/share".
- Additionally, USER SPECIFIC data should go into an application
  dependent directory in his home directory, usually "hidden", if
  created directly, or under ".config", which is often predefined, or
  below a special (hidden) directory created by a "sub system" (like
  msegui, i.e. ".msegui", ".msetools" or some such)

Sometimes, an application will be installed in the "/opt" hierarchy,
under "/opt/", that then contains its
own "bin", "lib" and data subparts, has to manage these itself, and
often provides links to the executable(s) within the common "/usr/bin"
or "/usr/local/bin" directories. E.g. VirtualBox does it that way, or
FreeCAD, if they're not installed by a distribution packet manager.

> But you are right, splitting the po/mo is better way.

Did you get it to _work_ now? You don't tell.

-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

[Fred van Stappen]

Hello Sieghard.

It seems that you did not red my last post.

Here the copy:



Re-hello Sieghard.

OK, I get it ( had not see the .msetools folder because it was hidden).

So your idea is to split the po files into a "main_msegui" in 
home/user/.msetools/lang and the "app_lang" po files.

Yes, of course usefull if you have mainy msegui applications installed.
I am not sure if I like it inside a hidden folder, I prefer open things, but 
yes, why not.

Personnaly I prefer all in one (all files in directory of app) and 
out-of-the-box (no files to be installed outside the folder of app) but I know 
it is not the  accademic Linux way.

But you are right, splitting the po/mo is better way.

Fre;D

___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

[Sieghard via mseide-msegui-talk]

Hallo Fred,

vous ecrit au Sat, 29 Oct 2022 23:40:04 +:

> Here the contents of my /home/fred/.msetools/lang/ folder:
...
> my /home/fred/testfpc/sieghard/podemo_mo4stock/lang/ folder:
...
> And here the result of podemo app:

Interesting...
This looks entirely correct and equivalent to my setup here.
I just unpacked the .zip file into an empty directory again, created a
"units" subdirectory, as advised by the project ptions, and with no
further modifications let the ide compile it. After that, running the
program yields the full list of languages in the selector grid
according to the files found in the ~/.msetools/lang directory, here.
I can even activate an entry and get the translated display.
I suppose you DID use the packaged podemo.prj project file? r did you
created a new project for testing, and forgot to enable the
"mse_dynpo" symbol? If that's missing, the project, interestingly, also
compiles, but then, of course, the language files cannot be found,
because they're not searched in the first place. This DOES give me the
bland "English"-only selector display as well. But, CAN that be?
After all, that is a demonstration of the "dynpo" mechanism, so
building it without that mechanism enabled just plainly deosn't make
any sense at all?
But, on the other hand, if that's not the cause of your problem, I'm at
a loss as to what might go on here, at least for now...

-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

[Fred van Stappen]

Hello Sieghard.

Here the contents of my /home/fred/.msetools/lang/ folder:
https://user-images.githubusercontent.com/3421249/198856195-d27a4ae3-55cc-4d7b-a1b8-f820f8a08356.png

Here the contents of my /home/fred/testfpc/sieghard/podemo_mo4stock/lang/ 
folder:
https://user-images.githubusercontent.com/3421249/198856197-71efed12-6054-4a1a-a357-d38d9f0ada07.png

And here the result of podemo app:
https://user-images.githubusercontent.com/3421249/198856206-673d79de-f8f7-4ad7-aad8-e3bdbbd9c6b2.png

So I miss something (or I am too stupid ).

Fre;D


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

[Sieghard via mseide-msegui-talk]

Hallo Fred,

vous ecrit au Sat, 29 Oct 2022 11:48:53 +:

> Sadly I did not make it work.
> 
> I did a copy of folder /podemo_mo4stock/lang into new hidden
> folder /home/fred/.msetools/. There is now /home/fred/.msetools/lang
> with all the podemo_xx.mo and podemo_xx.po files.

Yes. No, not so. Didn't I tell you to copy the contents of the
directory "/home_user/.msetools/lang" there? ALL of these files have
names of the pattern "msegui_.?o" (? in [m, p]), NOT
"podemo_.*". These are the files containing the central
component of the translation system, (hopefully) ALL of the text items
provided by the msegui libray lang_consts units. They're kept there in
a CENTRAL place to avoid multiple redundant and possibly inconsistent
duplicates.
The latter ones are the APPLICATION SPECIFIC residual language files,
and they DO go with the application into a local "lang" subdirectory
indeed. And if you inspect these files, you will find they only contain
a really small subset of the captions used in the program. (I kept the
".po" files in both parts for easy inspection.)

And that's the purpose of the "trick": NOT to have to repeat ALL the
text items used in an appliction over and over again, but to SEPARATE
them from the "stock" items, which reside in a specific location just
as ONE SINGLE COPY for all the applications using them.

> But at running, only English is loaded.

After you put all of the "msegui_.mo" files into
"/home/fred/.msetools/lang", you should get ALL languages selectable,
and provided you put the file "lang/podemo*" into the "lang"
subdirectory below of where the demo program ("podemo") resides, even
the special items ought to be translated, even
"This is a test of internationalization.", "That is another test."
and "This is the end."
And there's even a switch to allow you to always use the stock items,
even when some of them have been redefined (by accident) in the
application files. It's called "preferStock", default value "false",
and has to be set just before calling the "createnewlang" procedure.
It's not used for the demo, though.
(Also not used for the demo is a quirky conditional define called
"stocklangs_from_libpath" that changes the place for the stock item
subdirectory to the system wide msegui library directory,
"/usr/lib[64]/msegui/lib/common/lang_consts/lang" as an alternative
place. It's meant for discussion whether such a storage place might
be advisable, as a mere user installation probabely would not have
this place at all.)

> May I ask you why not use the /lang folder that is
> in /podemo_mo4stock/lang (lang folder in the same directory as the
> binary-application) ? For testing, it would be much more
> out-of-the-box.

For that, I have to respond: It's in a CENTRAL place because it is
meant to CENTRALIZE often used items to avoid multiple - and then also
possibly inconsistent - versions of these items. Just as dynamic link
libraries do for application programs.

> Also it would be easier to test it in Windows.

Even Windows ought to have a method to put such "library" type things
in a - possibly even user specific - centralized place. In the olden
times, there was the "\Windows" directory, where many programs put
their specific, but application independent, data, sometimes within
special subdirectories, sometimes in subdirectories provided by the
system, and sometimes even directly. I just don't know what the current
practice is under windows and how this could be done there.

I hope you will get it to work with the above information.
You probabely selected the most involved - and likely the most
unfinished - part of all the stuff on my msegui site. But maybe that's
not to bad, since it shows what has to be done to make it easily usable
and what information is neccessary for the prospective user.

Thank you for your interest and the time spent for evaluatiuon, and
I wish you success to get it to work. I hope you can appreciate the
stuff, and perhaps you can make use of it.

-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

[Fred van Stappen]

Hello Sieghard.

Thanks for the explanations.

Sadly I did not make it work.

I did a copy of folder /podemo_mo4stock/lang into new hidden folder 
/home/fred/.msetools/.
There is now /home/fred/.msetools/lang with all the podemo_xx.mo and 
podemo_xx.po files.

But at running, only English is loaded.

May I ask you why not use the /lang folder that is in /podemo_mo4stock/lang 
(lang folder in the same directory as the binary-application) ?
For testing, it would be much more out-of-the-box.

Also it would be easier to test it in Windows.

Fre;D
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

[Sieghard via mseide-msegui-talk]

Hallo Fred,

vous ecrit au Fri, 28 Oct 2022 13:37:23 +:

> I try your demo /podemo_mo4stock/podemo.prj
> 
> It compiles without problem but at run, there is only one language
> avalaible: English. So it seems not to find the /lang folder with all
> the po/mo files.

These are just providing the application specific parts of the
trnalation items used. Tha application is built for use with a stock
item "library" residing in the users' home directory (as provided by
the files in the directory "home_user" in the zip file), where they
reside in a common "lang" subdirectory of the ".msetools" "standard"
configuration directory. Did you extract these files there? I guess,
probabely not, because there's not a whole lot of information about
that given. I meant to refer to my "previous" (and now ages old)
posting of "just before" when I announced the new stuff. I posted the
announcement in message
<20220901163620.93571e64fa32e3212c874...@arcor.de>, but as no reaction
came, no follow-up with specific information ensued. I mentioned it
again several times later on as well (MIDs
<20220916232140.0ac01a4e23a0fccef24ac...@arcor.de>,
<20220918225740.1afdca9af13cd1479aa01...@arcor.de> and
<20221024221025.e2303ad4e74b30f6594b9...@arcor.de>), but that was after
your mishap with your computer been stolen. Sorry for the lack of
information, I hope the above should get you on track with this
undertaking, which is by no means finished yet.

> I did try to copy the /podemo_mo4stock/lang folder in other locations
> but always get only English language as choice.

No, this won't help - this ist the APPLICATION part only, and has to go
with the application as before. You DO need to institute the general
stock language file, useable by all such applications. For now, they
should reside in your home directory under "~/.msetools/lang", as
stated above, but they could also be installed system-wide like any
other set of language files on Linux, in the "/usr/share/locale"
hierarchy. I implemented both possibilities, as described in the
commentary part at the head of the "mo4stock" unit source file.

> What do I miss ?

Probabely what I didn't mention so obviously to immediately find, I
think - it's too long since this was produced initially...
I hope, I could set you "on track" with the above writings, and you
will get the demo to work correctly now. If not, please ask again,
telling what you did and didn't work; I'll try to help you out.
It MUST work, since it did for me just right now, immediately after
unpacking and compiling, "out of the box", so to speak.

Success, and "have a lot of fun"!

-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

[Fred van Stappen]

Hello Sieghard.

I try your demo /podemo_mo4stock/podemo.prj

It compiles without problem but at run, there is only one language avalaible: 
English.
So it seems not to find the /lang folder with all the po/mo files.

I did try to copy the /podemo_mo4stock/lang folder in other locations but 
always get only English language as choice.

What do I miss ?

Fre;D

De : Sieghard via mseide-msegui-talk 
Envoyé : jeudi 27 octobre 2022 21:30
À : mseide-msegui-talk@lists.sourceforge.net 

Cc : Sieghard 
Objet : Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

Hallo Fred,

vous ecrit au Thu, 27 Oct 2022 16:23:53 +:

> About your site.
>
> Yep it works and I see "podemo_mo4stock.zip".
> OK, "podemo_mo4stock.zip" downloaded without problems.

Thank you for the feedback.

And I hope you can make sense of the stuff you got from your download...
(By now, that's just an experiment, trying to make the stock items more
readily available. They really ought to be better integrated in the gui
& ide interfaces, I think.  And there's an accompanying "project", name
"stockbutton[.zip]" providing a list of these items - intended to be
integrated into the ide object inspector, perhaps, later. When I may
have found out how this could be done.)

--
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

[Sieghard via mseide-msegui-talk]

Hallo Fred,

vous ecrit au Thu, 27 Oct 2022 16:23:53 +:

> About your site.
> 
> Yep it works and I see "podemo_mo4stock.zip".
> OK, "podemo_mo4stock.zip" downloaded without problems.

Thank you for the feedback.

And I hope you can make sense of the stuff you got from your download...
(By now, that's just an experiment, trying to make the stock items more
readily available. They really ought to be better integrated in the gui
& ide interfaces, I think.  And there's an accompanying "project", name
"stockbutton[.zip]" providing a list of these items - intended to be
integrated into the ide object inspector, perhaps, later. When I may
have found out how this could be done.)

-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

[Fred van Stappen]

Hello Sieghard.

About your site.

Yep it works and I see "podemo_mo4stock.zip".
OK, "podemo_mo4stock.zip" downloaded without problems.

I will study it asap, write you later.

Fre;D



___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

[Sieghard via mseide-msegui-talk]

Hallo Fred,

vous ecrit au Mon, 24 Oct 2022 20:42:37 +:

> Server Error 500: Internal Server Error )

This took me some time, mostly because of the intense (non-)"help" from
my provider. (Somewhat understandable though, because I'm using the
cheapest tariff they offer.)
Anyway, after quite some experimenting, even building a cgi script to
prepare a directory listing for a web page, it seems I found the reason
for the problem. It probabely was just a  newly "outlawed" web option
that triggered the server to balk. But it might also have been the
nesting depth of the directory, which I had to move up one level.
After all, the web page SHOULD be accessible again, although now under
a new subdirectory, not "downlod/ms" any more, but "download_mse" now,
mind the underscore ("_") in the name.
If you get to try it, I would be glad if you provide a notice of the
result, whether you had successs or not.

Thank You and have a good time!

(BTW, I just downloaded your new release and will install it
"immediately".).

-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

[Sieghard via mseide-msegui-talk]

Hallo Fred,

vous ecrit au Mon, 24 Oct 2022 20:42:37 +:

> > But I would like to get your opinion about the contents of the
> > "podemo_mo4stock.zip" archive.
> 
> With great pleasure ( if
> http://your_site/download/mse/podemo_mo4stock.zip is accessible, I
> did try and get:
> Server Error 500: Internal Server Error )

Oh well. Lastly, my provider made some updates to their software, and
following that, these directories yielded this error when accessed.
I did some "experiments" using different methods for web-site-indexing,
and seemed to have been successful. At least I myself could get access
to the directory, and downloading a file "blindly" did work for me.
Did you try that, too, and got the error, or was it just on trying to
access the directory as a web page?
But I see, I WILL have to pursue this somewhat deeper, although the
provider doesn't seem to be interested to help, sadly. I'm not really
eager to publish these things on my web site directly, or would you
accept to do it that way?

-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

[Fred van Stappen]

Hello Siegard.

> But I would like to get your opinion about the contents of the 
> "podemo_mo4stock.zip" archive.

With great pleasure ( if http://your_site/download/mse/podemo_mo4stock.zip is 
accessible, I did try and get:

Server Error 500: Internal Server Error )

Fre;D
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

[Sieghard via mseide-msegui-talk]

Hallo Fred,

vous ecrit au Sun, 23 Oct 2022 21:41:03 +:

> The proposition of new release is mainly because of lot of bug-fixes.

These are very important, indeed.

> And I feel sad to know that people will download the last release
> with those bugs. There are no new feature but fixes for our mse_dynpo

Although it's really hard to avoid such things, I think that, contrary
to current practice, a release ought to be as thoroughly tested as
possible. You do a really good job at that usually, and I presume the
newly discovered problems were not testable before. So, if they're
fixed now, then go ahead and release the corrected version.

> I did not add yet the code from your site nor the MSEClock demo, I
> wait for your green light for that.

Ok, this might have to wait some more - although the formsanner seems
to work for static forms (those created on program start), it doesn't
do so during runtime. That's one of the places I'm at yet.
The modified versions of the two programs "msegit" and "msespice"
should be ok, but at least the latter requires thorough testing yet,
and I do not have a windows machine to assure they work there.
And that's about it anyway.
Perhaps to be considered might be the "mseide-msegui-shadow.zip" file
containing a few amendments to the library files, mostly to avoid
"mse_dynpo" conditinals (and these work ok for me, I have them
installed), but also some measures to remove compiler warnings or
notices for unused variables and such.

But I would like to get your opinion about the contents of the
"podemo_mo4stock.zip" archive. This is an attempt to provide a common
set of localizable standard captions, soewhat like a "library" of them,
making it unneccessary to always repeat them for every new project.
It also contains a simple demo for its use. I've also built a selector
form for stock captions that might be integrated into the object
inspector when I found out how to do that, but that's not yet included.
(I can't remember all the details any more since it's so long that I
last worked on the stuff...)

> So, ok, I will do last hard test tonight and then do the release.

Good luck, success, and keep up the good work!

-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

[Fred van Stappen]

Hello Sieghard.

The proposition of new release is mainly because of lot of bug-fixes.

And I feel sad to know that people will download the last release with those 
bugs.
There are no new feature but fixes for our mse_dynpo feature and in the MSEide 
for form manager options and some check not done if form from designer was 
assigned.

I did not add yet the code from your site nor the MSEClock demo, I wait for 
your green light for that.

So, ok, I will do last hard test tonight and then do the release.

Have a perfect night and day.

Fre;D


De : Sieghard via mseide-msegui-talk 
Envoyé : dimanche 23 octobre 2022 20:49
À : mseide-msegui-talk@lists.sourceforge.net 

Cc : Sieghard 
Objet : Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

Hallo Fred,

> > A new release should IMHO be done when definite flaws have been
> "definitely" mended. "Cosmetic" modifications don't warrant that, I
...
> Sorry but I do not understand, what do you think is not "definitely"
> mended?

Repaired for all attainable systems for as many cases as possible. Yes,
that _is_ time consuming and tedious, but in the past you did a very
good job at that, so I'm sure you will do so in the future as well.
But still, a new relaese is a major turning point and so to be
considered thoroughly. Without information about the pertaining changes
I cannot judge this in any respect.
Unfortunately, I didn't find sufficient time for the period past to
do much work on the innards of msegui - not even proceed with getting
msegit to real work or to extend the formscanner to work dynamically
on a running program. I just hope I might get at it some again, and
immediately got sidetracked again experimenting to generalize your
extension to my "MSclock", using not only a round-cornered windoe but
also rounded field frames. This seems to be not a simple feat...

Anyway, go ahead and proceed with your undeniably good work!

--
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

[Sieghard via mseide-msegui-talk]

Hallo Fred,

> > A new release should IMHO be done when definite flaws have been
> "definitely" mended. "Cosmetic" modifications don't warrant that, I
...
> Sorry but I do not understand, what do you think is not "definitely"
> mended?

Repaired for all attainable systems for as many cases as possible. Yes,
that _is_ time consuming and tedious, but in the past you did a very
good job at that, so I'm sure you will do so in the future as well.
But still, a new relaese is a major turning point and so to be
considered thoroughly. Without information about the pertaining changes
I cannot judge this in any respect.
Unfortunately, I didn't find sufficient time for the period past to
do much work on the innards of msegui - not even proceed with getting
msegit to real work or to extend the formscanner to work dynamically
on a running program. I just hope I might get at it some again, and
immediately got sidetracked again experimenting to generalize your
extension to my "MSclock", using not only a round-cornered windoe but
also rounded field frames. This seems to be not a simple feat...

Anyway, go ahead and proceed with your undeniably good work!

-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

[Fred van Stappen]

Hello Sieghard.

> Hard to say without knowing what was fixed or modified.

https://github.com/mse-org/mseide-msegui/compare/5.6.8...main

> A new release should IMHO be done when definite flaws have been
"definitely" mended. "Cosmetic" modifications don't warrant that, I
think.

Sorry but I do not understand, what do you think is not "definitely" mended?

Fre;D

___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

[Fred van Stappen]

Hello Sieghard.

> Hard to say without knowing what was fixed or modified.

https://github.com/mse-org/mseide-msegui/compare/5.6.8...main

> A new release should IMHO be done when definite flaws have been
"definitely" mended. "Cosmetic" modifications don't warrant that, I
think.

Sorry but I do not understand, what do you think is not "definitely" mended?

Fre,D




De : Sieghard via mseide-msegui-talk 
Envoyé : samedi 22 octobre 2022 21:17
À : mseide-msegui-talk@lists.sourceforge.net 

Cc : Sieghard 
Objet : Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

Hallo Fred,

vous ecrit au Sat, 22 Oct 2022 09:58:08 +:

> About the version of MSEide and MSEgui.
>
> There was lot of fixes since last release, maybe it is time to do a
> new release.
...
> Are you ok for a new release or better wait a few ?

Hard to say without knowing what was fixed or modified.
A new release should IMHO be done when definite flaws have been
"definitely" mended. "Cosmetic" modifications don't warrant that, I
think.
Others may plead differently.

--
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide-MSEgui ?

[Sieghard via mseide-msegui-talk]

Hallo Fred,

vous ecrit au Sat, 22 Oct 2022 09:58:08 +:

> About the version of MSEide and MSEgui.
> 
> There was lot of fixes since last release, maybe it is time to do a
> new release.
...
> Are you ok for a new release or better wait a few ?

Hard to say without knowing what was fixed or modified.
A new release should IMHO be done when definite flaws have been
"definitely" mended. "Cosmetic" modifications don't warrant that, I
think.
Others may plead differently.

-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide ?

[Sieghard]

Hello fredvs,

you wrote on Sat, 19 Sep 2020 05:26:36 -0700 (MST):

> But does still exist somebody that uses msegui?

Not on real projects right now, but I still do some internal work with
it if ever I get enough time to do so.
Latest engagement was your "msefiledialogx", you know, but right now I'm
somewhat stuck at other things. I'll report on my findings when I'll find
enough 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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide ?

[fredvs]

Hello Med.

 >till now I did not find any serious bugs but only some missings.

Please could you give more infos, what bug did you find and what is missing?

Thanks.

Fre;D




--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide ?

[mohamed hamza]

Hi All,

   I am still using MSEIDE-MSEGUI to create business/database programs. till 
now I did not find any serious bugs but only some missings.

Med

De : Graeme Geldenhuys 
Envoyé : samedi 19 septembre 2020 22:52
À : mseide-msegui-talk@lists.sourceforge.net 

Objet : Re: [MSEide-MSEgui-talk] New release of MSEide ?

On 19/09/2020 1:26 pm, fredvs wrote:
> But does still exist somebody that uses msegui?

I do. (the IDE part) :-)
 But I'm a bit silent on the mailing list front these days.


Regards,
  Graeme

--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

My public PGP key:  http://tinyurl.com/graeme-pgp


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide ?

[Graeme Geldenhuys]

On 19/09/2020 1:26 pm, fredvs wrote:
> But does still exist somebody that uses msegui?

I do. (the IDE part) :-)
 But I'm a bit silent on the mailing list front these days.


Regards,
  Graeme

-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

My public PGP key:  http://tinyurl.com/graeme-pgp


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide ?

[fredvs]

Hello.

There is a new release of MSEide binary:
https://github.com/mse-org/mseide-msegui/releases/tag/5.2.0

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide ?

[fredvs]

Hello Dear Roland.

> You began to do that  here
>  

Ok, I did edit-update the modification done only for fpc >= 3.2.0, like
asked in the post.

Now about all other modifications, I will add a short description in the
release-text.

If you have other ideas, what to change in the readme.txt or whatever, dont
hesitate to note.

Have a perfect day.

Fre;D 



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide ?

[Roland Chastain]

Dear Fred,

Thank you for your efforts. Yes, a new release would be welcome, if you have
time for it.

And if you still have time after that, it would be useful to put somewhere
clear indications of the important changes that you have made. You began to
do that  here
 
, but some indications are a bit short. For example, you could add links to
discussions where the problems and solutions were discussed.

You know that commits are not always easy to read.

Best regards.

Roland



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide ?

[fredvs]

Hello everybody.

Bon, ok, I will answer to me, so there is at least one answer.

"Hello Fred.

Thanks for all your hard and big work to test and retest msegui with each
new commit of fpc and fix all to make mse still the best widgetset of the
world.

Yes, I think that a new release of mseide with all the bug fixes, the
classes bridge and new widgets would be welcome.

But I think too that it is time for you to give the hand to somebody else
that has interest to continue maintaining mse.

Thanks for all.

Fre;D"






--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide ?

[fredvs]

Hello everybody.

Hum, not too much answers here.

But does still exist somebody that uses msegui?

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide ?

[fredvs]

Hello Med.

Huh, no I dont do it already because I first want your advice for the
opportunity to do a new release.

For the change since last release, please take a look at the commits done:

https://github.com/mse-org/mseide-msegui/compare/5.0.0...master

Fre;D 



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide ?

[mohamed hamza]

Hello Fred,

 I do not see the changes version history in VERSION.TXT ?
Try to insert them.  Thank you

Med

De : fredvs 
Envoyé : jeudi 10 septembre 2020 11:55
À : mseide-msegui-talk@lists.sourceforge.net 

Objet : [MSEide-MSEgui-talk] New release of MSEide ?

Hello everybody.

There was lot of bug fixes, bridge added, new components, ... in trunk
mseide-msegui since last release.

What do you think about release a new release?

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[Sieghard]

Hello fredvs,

you wrote on Fri, 10 Apr 2020 17:57:15 -0700 (MST):

> > Why do you think so? AFAIK, it is _meant_ to be handled in such a
> > way.   
> 
> But how will you do is the library dont provide the "nude" symlink and
> only provide the soname, like libportaudio.so.2?
> Oblige people to create by their self a symlink libportaudio.so ?

What I wanted to say is meant to be handled in such a way is the
_transition_ from one API to an incompatible follower that requires
modifications to the code using it.
I must concede, though, that I'm not at all thoroughly familiar with the
matter. What I wrote is just what I read and gathered from the available
sources.

> Sorry but I prefer to link directly to libportaudio.so.2.

That is only required if your program explicitly needs that specific
version. Otherwise, the system linker takes (should take) care of providing
the neccessary links to the current library file.
That means, if your programm requires libportaudio.so.2, because it uses a
feature not provided by, say libportaudio.so.3*, you have to specify the
specific link. This could in principle even go further down the version
tree.

> You have to take in account that the soname is updated each time that a
> minor version appear, so you are always uptodate if you use the soname
> (the soname is the name of the library + ".so" + the first number).

How this is to be handled depends on the requirements of your program. If
it can work with "any" version of the library, no version needs to be
specified. If it requires a specific version, this has to be given. If it
can work with any version up to somw specific one, it depends on whether
sysmbol versioning is implemented by the library. If it is, you should be
able to specify the oldest version providing the required functions, and
then you (or the user) might have to provide an appropriate link. (That is,
if "ldconfig" doesn't do this already.)
That's at laest as I see this and as far as I understood the matter.

you wrote on Thu, 9 Apr 2020 18:10:11 -0700 (MST):

> > _What_ "bug"?  
...
> Fpc will strip the code into libX11.so, without the so number.
> You are obliged to create a symlink libX11.so that point to ink to
> libX11.so.6.

That's what the system linker (helper "ldconfig") should have taken care
of when it (re)created the current library links after an update.

> The bug is not about using dev package (even if it should not be needed
> for fpc users).

In this respect, I've found arguments that someone doing development - and
that certainly applies to fpc users - should be required to provide the
neccessary preconditions, including installing required packages.
Providing specific development packages isn't even that old a custom, the
distribution I use, Slackware, e.g. doesn't have specific development
packages at all.
If, for a distribution that does have them, an fpc package does _not_
provide the pertaining dependencies (e.g. for a Debian package), that
package can be considered thoroughly broken.

> Now I can install fpc and msegui on a RPi with Raspbian distro without the
> need to be connected to install some no needed dev-package.

The Debian "dev" package (and probabely those of other distributions)
also contains the header files for the API functions. You'll only get
away without _these_ if your compiler provides it's own API data, which
fpc does by means of the precompiled .ppu files. Then, one really only
needs the library link, which can also be set by the package installer,
usually by means of a post-install script.
So, in the end, the "bug" you reproach against fpc is just the omission
to provide the neccessary library link.
(And the reason I didn't even notice this is my not using a distribution
requiring development packages, even already having the library headers
installed before installing an "official" fpc package.)

That's at least, to repeat, as I see and understand the matter.
Sorry for the long text.

-- 
-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[fredvs]

> Why do you think so? AFAIK, it is _meant_ to be handled in such a way. 

But how will you do is the library dont provide the "nude" symlink and only
provide the soname, like libportaudio.so.2?
Oblige people to create by their self a symlink libportaudio.so ?

Sorry but I prefer to link directly to libportaudio.so.2.

You have to take in account that the soname is updated each time that a
minor version appear, so you are always uptodate if you use the soname (the
soname is the name of the library + ".so" + the first number).

Fre;D 



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[Sieghard]

Hello fredvs,

you wrote on Fri, 10 Apr 2020 09:34:42 -0700 (MST):

> > And that's a barricade for my advance with the new mseide right now.  
> 
> I did not understand exactly what is the problem with dialogs form, I have
> to study better your post.
> 
> But, trust me, we will find a solution, for sure.

Don't mind, it doesn't matter anymore - it DOES work now, although I don't
really know why. The working version doesn't use anything related to
modality or dialog, the only window option used is "wo_noframe".
I _believe_ I had it this same way before, and the window didn't even show.
But as I changed it in so many ways to achieve the desired function, I
cannot say for sure anymore. However, it does work now, and I will pack it
together with the FileRequest stand-alone dialog shortly for you. You may
use it or not, publish it or keep it private.

Other than the dialog problems, everything I tried worked correctly, as I
said before, although right now I don't have a lot of use for mseide-msegui
software, because the big project I set out for with it has not seen any
further development for years now. No problems either, though, which is
good...
Still, a Raspberry Pi version could open new fields for applications,
especially if it was possible to cross-compile on a larger machine and
transfer only the finished application to the target board.
I'm very curious to get my hands on it; and I'd even like to help to get
it done, if possible. (As I'm running Slackware, I could provide a package
for it, if wanted.)

-- 
-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[Sieghard]

Hello fredvs,

you wrote on Fri, 10 Apr 2020 09:56:29 -0700 (MST):

> > Ok, then it's understandable. This version will then be limited to this
> > specific version of libX11.   
...
> X11.org project is dead, there is absolutely no plan for a new major
> release.

Not even small corrections, you're certain?

> Even if there will be a fix, this will be on a minor release, and the
> soname can deal with that.

And what about the successor(s)? At least Wayland - which isn't even ready
for deploying - provides translation libraries, and these might evolve in
time, maybe in some way that needs to be taken into account. But then, this
might not be really soon.

> Take a other example: library openssl they recently release libssl.so.1.1,
> the previous version was libssl.so.1.0.2.

Yes, I did realize that both versions exist in parallel, and there's a
large number of programs still requiring the old version. With the
coexisting versions, there's time to gradually change the code without
haste.

> And all your applications will be unusable, you have to recompile all with
> fpc 3.2.0 that have updated the code for libssl.so.1.1.

Fine, that's the way it should be done, I think. A mere recompile isn't
such a great deal, after all.

> It is not the right way because if you install libssl.so.1.1., usually the
> old libssl.so.1.0.2 is still in the distro.

Why do you think so? AFAIK, it is _meant_ to be handled in such a way.

But this is NOT the same situation as with X11. Openssl still evolves,
while the X11 people seem to be tired an discouraged about its future and
about the current development. They seem to be ready to give up and let
it die, even though there's nothing around that could completely take over
the task. As I see it, the alternative - and there's only one visible by
now, Wayland - is by no means reaady yet. It will probabely take another
few years until it's really viable, similar to systemd (which comes from
the same people, AFAIK) that took around a decade and still has quite a few
quirks.

-- 
-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[fredvs]

> Ok, then it's understandable. This version will then be limited to this
> specific version of libX11. 

Yes and this till the end of time.

X11.org project is dead, there is absolutely no plan for a new major
release.
Even if there will be a fix, this will be on a minor release, and the soname
can deal with that.

Take a other example: library openssl they recently release libssl.so.1.1,
the previous version was libssl.so.1.0.2.

The 2 versions are not compatible.

With fpc 3.0.4., all the code in openssl fpc-package was done for
libssl.so.1.0.2. and link so to libssl.so.

But if you install the last release libssl.so.1.1 and the dev pack,
libssl.so will point to libssl.so.1.1 that is not compatible.

And all your applications will be unusable, you have to recompile all with
fpc 3.2.0 that have updated the code for libssl.so.1.1.

It is not the right way because if you install libssl.so.1.1., usually the
old libssl.so.1.0.2 is still in the distro.

Fre;D







--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[fredvs]

> And that's a barricade for my advance with the new mseide right now.

I did not understand exactly what is the problem with dialogs form, I have
to study better your post.

But, trust me, we will find a solution, for sure.

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[Sieghard]

Hello fredvs,

you wrote on Fri, 10 Apr 2020 05:25:35 -0700 (MST):

> fpc will autocratically remove the prefix part "lib" and the extension
> part ".so.6".
> 
> But it you use the patched version of fpc that can link soname, it will
> link to libX11.so.6'.

Ok, then it's understandable. This version will then be limited to this
specific version of libX11.

...
> Please Sieghard, do me a favor, read carefully all the notes of Martin and
> me here:

Ok, noted, and I will look them through when I can.

BTW, I'm sorry for the statement about the - correctly named - "Exec Line
Hint" dots - they _do_ show up correctly and with a useful size now. I just
didn't realize that they are only shown when you _execute_ the program, not
already after compilation. When I tried your correction, I just recompiled,
but didn't attempt to start the program, and thus there were no markers to
be seen... Sorry again.

Right now I'm struggling with the working of modal dialogs, as I attempted
to extend my "FileRequest" dialog program to allow for execution of an
external program file-by-file, with the option to select per file whether
the action should be executed.

Sadly, to no avail as yet. And this is not at all due to any of the recent
modifications - the same misbehaviour also happens with the "eon old" 4.6.2
release of mseide!

I got it to work in two failure modes by now. Both modes only work with the
additional window option "wo_terminateonclose" set, otherwise the dialog
window doesn't show at all.

Setting the window option "fo_createmodal" for the dialog window, it first
displays an uninitialized dialog window that has to be closed explicitely,
only then the real dialog shows up and does what it's supposed to do.

Setting the window option "fo_modal" (without "create") for the dialog
window, it does show up corretly the first time, without the extraneous
uninitialized display before, but after that, it never shows up again and
always returns the (modal) result "mr_none".

I wasn't able yet to find any useful information even following the long
convoluted way through the host of functions that ought to manage window
construction, display, handling and removal, they're just to many and just
to intricately woven together.

And that's a barricade for my advance with the new mseide right now.

-- 
-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[fredvs]

Please, read previous mail.

> X11" to 'libX11.so.6' in "mseguiintf.pas"; 

It was a big hope of Martin, I am sorry that we couldn't convince fpc team
to fix the bug.

Finally, after all that years, it appends, but wtchl a patched fpc that is
here:

https://github.com/fredvs/freepascal





--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[fredvs]

> "X11" to 'libX11.so.6' in "mseguiintf.pas";

Yes, it will have no affect if you use original fpc.
fpc will autocratically remove the prefix part "lib" and the extension part
".so.6".

But it you use the patched version of fpc that can link soname, it will link
to libX11.so.6'.

https://github.com/fredvs/freepascal

Please Sieghard, do me a favor, read carefully all the notes of Martin and
me here:

https://bugs.freepascal.org/view.php?id=32367

and here:

https://www.mail-archive.com/mseide-msegui-talk%40lists.sourceforge.net/msg11386.html

Fre;D
 



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[Sieghard]

Hello fredvs,

you wrote on Wed, 8 Apr 2020 14:38:44 -0700 (MST):

> > Thank you again, I'll get it as soon as I can.  
> 
> To re-compile MSEide, load /mseide-msegui/apps/ide/mseide.prj + compile.

Thanks, I got me an eon old Makefile that does the job without having to
load an older ide version. The new master version (9th April 2020 23:31)
does work now, and I recompiled my "current" project.
Seems, you "solved" the coding line marker problem by completely removing
them? BTW, I realized that these markers are correctly called "Exec Line
Hints", as shown in the "Target" submenu of the ide at the bottom, where it
is possible to en- or disable them. I had them enabled before, probabely by
default, and that's why I noticed the difference. I have them still enabled
now, but now, nothing appears anymore. I even dis- and reenabled them, but
there's still nothing shown. It's not a problem, they're just eye candy
anyway. I mentioned it just because I noticed the different appearance.

Another question: You changed the definition of "Xlibmodulename" from just
"X11" to 'libX11.so.6' in "mseguiintf.pas"; That way, you request a specific
version of this library. So programs _may_ break just because of this, when
a newer Xlib version appears, even if they might function correctly with
this version. Is this due to some incompatibility that's shown up recently
or has it some other reason? Or is it not really used at all?

-- 
-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[fredvs]

> Thank you again, I'll get it as soon as I can.

To re-compile MSEide, load /mseide-msegui/apps/ide/mseide.prj + compile.

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[Sieghard]

Hello fredvs,

you wrote on Tue, 7 Apr 2020 15:29:20 -0700 (MST):

> > OK, fixed in last commit:
> > https://github.com/mse-org/mseide-msegui/commit/255207  

Thank you again, I'll get it as soon as I can.
(Made some modifications to my machine, got to make it behave again...)

-- 
-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[fredvs]

Hello Sieghard.

In my previous post:

> OK, fixed in last commit:
> https://github.com/mse-org/mseide-msegui/commit/255207

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[fredvs]

Hello Sieghard.

Did you try the last commit?



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[Sieghard]

Hello fredvs,

you wrote on Sun, 5 Apr 2020 14:44:53 -0700 (MST):

> Ha, ok, I get it, indeed the blue point is too big and in the wrong side.
> I will fix it asap.

Thank you.

> But now that you point it, there may be also a problem with the shortcut
> icon that is there too.

Yes, that is to be expected - everything that may appear in the gutter
_may_ cover up something else, so the locations had to be selected
thoroughly, or the markers should be set according to some defined priority
scheme.

> Hum, ok, this need some cups coffee.

Ask the community what they suggest/prefer...

-- 
-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[fredvs]

>  > Sorry I do not catch this, what are the coding line markers? 

OK, fixed in last commit:
https://github.com/mse-org/mseide-msegui/commit/255207

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[fredvs]

 > Sorry I do not catch this, what are the coding line markers?

Ha, ok, I get it, indeed the blue point is too big and in the wrong side.
I will fix it asap.

Thanks to note it.

But now that you point it, there may be also a problem with the shortcut
icon that is there too.

Hum, ok, this need some cups coffee.

Fre;D





--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[fredvs]

Hello Sieghard.

> The - now - big blue blobs appearing in the left hand "gutter" after ...

Sorry but my English is not yet perfect and in this case I fear that only a
picture could fresh my mind.

Is it not possible to add a screenshot of what you want to describe?

Thanks.

Fre;D 



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[Sieghard]

Hello fredvs,

you wrote on Sun, 5 Apr 2020 04:31:33 -0700 (MST):

> > I noticed that the coding
> > line markers have gotten enormously blown up.   
> 
> Sorry I do not catch this, what are the coding line markers?

The - now - big blue blobs appearing in the left hand "gutter" after
compiling a program. They show which lines did create some code, so they're
missing at comment lines, procedure headers, declarations etc., but
otherwise found at nearly any line of code, and thus any line where you can
put a breakpoint. But the tiny littel red (?) dot marking a breakpoint gets
by far overwhelmed by these big blue blobs now. Formerly, they were much
smaller, and the breakpoint markers were the same size, and both did fit in
the gutter side by side. But I think it would be sufficient to just change
the marker color to red (or whatever) to signal an active breakpoint, should
overpainting cause too much trouble.

-- 
-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[fredvs]

Seems that previous mail did not pass...

OK, I retry.

Hello Med.

TDataSetState is set in mdb.pas with this:

TDataSetState = (dsInactive, dsBrowse, dsEdit, dsInsert, dsSetKey,
dsCalcFields, dsFilter, dsNewValue, dsOldValue, dsCurValue, dsBlockRead,
dsInternalCalc, dsOpening, dscheckfilter);

So in your code is missing last element: dscheckfilter.

Try this (see last element):

DatasetStates:array[tdatasetstate] of string =('Inactive', 'Browse', 'Edit',
'Insert', 'SetKey',

 'Calc', 'Filter', 'NewValue', 'OldValue', 'CurValue',
'BlockRead','InternalCalc', 'Opening', 'CheckFilter') 

May I ask you what earlier version of MSEgui did you use?

Because in previous release, dscheckfilter was already implemented, I did
not add it.

Fre;D





--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[fredvs]

> But it seems that it was fixed it you create a new program. 

No it was not fixed but it is fixed now with last commit:

https://github.com/mse-org/mseide-msegui/commit/ff265a6

Thanks to note it.

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[fredvs]

Hello Graeme.

You did the biggest part of that new release.
Without your fixes it will never append.

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[fredvs]

Hello Sieghard.

About color, yes I think it was a error in default code, warning should be
yellow and error red.

But it seems that it was fixed it you create a new program.
Of course all old programs-demos have this inversion and it is not difficult
to change it (mseide-config-editor-colors).

A other solution is ... to use ideU instead.
In ideU, in extra-config, you may assign the color by project or global.

> I noticed that the coding
> line markers have gotten enormously blown up. 

Sorry I do not catch this, what are the coding line markers?

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[Sieghard]

Hello fredvs,

you wrote on Fri, 3 Apr 2020 14:51:29 -0700 (MST):

> > I'll rebuild all of my "private" utilities   
> 
> Nice, it will be welcome.
> And dont forget to create a GitHub account!

Won't be warranted for that few pieces of code crap. I'll put'em on my web
site again and send you a notice about it.

But, BTW, I got a couple "gripes" (bemol, as you like to name it).
- At least here in Europe, AFAIK, by convention the color "red" means
something like "danger", "problem", "failure", while a mere warning is
expressed by the color "yellow". In mseide, this color assignment is
switched: warnings are marked "red", while errors are flagged "yellow".
This made me uneasy every time when it newly occurred. Of course, it can
be easily configured to the "normal" way. But - if our Asian friends here
won't oppose (as they don't neccessarily have the same conventions about
color use as we Europeans) - I'd suggest to switch it over to the
conventional assignment.
- After the first attempt to compile some code, I noticed that the coding
line markers have gotten enormously blown up. That makes for a "slight"
problem when using breakpoints: the breakpoint markers, which didn't
receive the same pressure obviously, can hardly be recognized any more. If
the blown up markers should stay, I propose to apply the same pressure to
all of them, and make sure breakpoints are shown _above_ all other markers,
because they're the ones you _need_ to see when they're used.

-- 
-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[Graeme Geldenhuys]

On 02/04/2020 7:26 pm, fredvs wrote:
> The mse-org team is very happy to announce the new release of
> MSEide+MSEgui.

Well done Fred for being a champion in taking this project forward no
matter what! As somebody else alread said - it echos out that
MSEide+MSEgui is still alive and kicking. Martin will be proud that his
baby is not abandoned, and still lives on!

Keep up the great work Fred, and everybody else.


Regards,
  Graeme

-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

My public PGP key:  http://tinyurl.com/graeme-pgp


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[fredvs]

Hello Sieghard.

> I'll rebuild all of my "private" utilities 

Nice, it will be welcome.

And dont forget to create a GitHub account!

;-)

Fre;D




--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[Sieghard]

Hello fredvs,

you wrote on Thu, 2 Apr 2020 11:26:32 -0700 (MST):

> Hello everybody.
> 
> The mse-org team is very happy to announce the new release of
> MSEide+MSEgui.
> 
> MSEide+MSEgui is a Pascal Cross Platform GUI Development System.
...

Thanks a lot - I'll see to get it ASAP and give it a try.

I'll rebuild all of my "private" utilities (you know most of them), and
will report of any neccessary modifications (if any) and provide additions
I made in the meantime (very, extremely few...).
It will still take some time. though...

> Have a lot of fun.

Not only on SuSE Linux systems, BTW...
(That's where the slogan comes from.)

> Fre;D
> 
> PS: Announce was done to fpc and Lazarus too:

Fine, that's probabely very important, to hopefully extend its user group.

-- 
-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[Roland Chastain]

No, I didn't know. Thank you for the information.

Regards.

Roland



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[fredvs]

Salut Roland.

Thanks for the links and for the thanks.

By the way, did you see that you are administrator of the mse-forum?
http://mse-org.111682.n8.nabble.com/

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[Roland Chastain]

Announcements on french and german forums.

https://www.developpez.net/forums/d2061879/autres-langages/pascal/autres-ide/nouvelle-version-mseidepmsegui/
https://www.lazarusforum.de/viewtopic.php?f=53=12827




--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[Roland Chastain]

Well done Fred. Bravo pour ton travail.



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[fredvs]

Hello everybody.

The mse-org team is very happy to announce the new release of MSEide+MSEgui.

MSEide+MSEgui is a Pascal Cross Platform GUI Development System.

- Compiles with FPC 2.6.4, 3.0.0, 3.0.2, 3.0.4 or 3.2.0.
- For FreeBSD-x86_64, Linux-i386, Linux-x86_64, Linux-arm(Raspberry Pi),
  Windows-i386, Windows-x86_64.
- Links to xlib and gdi32, no external widget library needed.
- Internal character encoding is utf-16.
- Uses anti aliased fonts on Linux (Xft).
- All screen drawing is double buffered.
- Has docking forms and MDI.
- Has embedded forms (similar to TFrame).
- Has sophisticated database access components and data edit widgets.
- Internationalization functionality with resource modules.
- Report generator.

IDE:
- Integrated debugging.
- Source code highlighting.
- Source code navigation with support for include files.
- Code completion for classes.
- Procedures list.
- Integrated visual form designer with source code update for components and
  events.
- Flexible and handy build system with switchable macros.
- Visual form inheritance.
- Integrated report designer.

Release of binary MSEide for Windows 64/32, Linux 64/32, FreeBSD 64 and Rpi
ARM can be found here:
https://github.com/mse-org/mseide-msegui/releases/

Source code of MSEide+MSEgui are here:
https://github.com/mse-org/mseide-msegui

Many thanks to fpc team that helped so much for that release (particularly
Sven).

Have a lot of fun.

Fre;D

PS: Announce was done to fpc and Lazarus too:

http://free-pascal-general.1045716.n5.nabble.com/New-release-of-MSEide-td5735149.html
https://forum.lazarus.freepascal.org/index.php/topic,49168.0.html

 



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[code dz]

2020-04-02 11:45 UTC+02:00, fredvs :
> Hello everybody.
>
>> Also, I propose to name the new release 5.0.0, (it seems that Martin
>> changed
>> the first number when a new fpc version was allowed).
>
>> And change, maybe, the copyright with:
>
>> Copyright (c) 1999-2020 by Martin Schreiber and friends.
>
>> OK ?
>
> I still wait for your green light.
>
> Fre;D
>

go ahead ;)


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[mohamed hamza]

De : fredvs 
Envoyé : jeudi 2 avril 2020 09:45
À : mseide-msegui-talk@lists.sourceforge.net 

Objet : Re: [MSEide-MSEgui-talk] New release of MSEide.

Hello everybody.

> Also, I propose to name the new release 5.0.0, (it seems that Martin
> changed
> the first number when a new fpc version was allowed).

> And change, maybe, the copyright with:

> Copyright (c) 1999-2020 by Martin Schreiber and friends.

> OK ?

I still wait for your green light.

Fre;D

Hi All,

   I suggest   Copyright (c) 1999-2020 by  Martin Schreiber  Group.

Med.


--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[fredvs]

Hello everybody.

> Also, I propose to name the new release 5.0.0, (it seems that Martin
> changed
> the first number when a new fpc version was allowed).

> And change, maybe, the copyright with:

> Copyright (c) 1999-2020 by Martin Schreiber and friends.

> OK ?

I still wait for your green light.

Fre;D




--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[fredvs]

Hello Sieghard.

> Isn't your latest version, adapted for fpc 3.3.1? 

Yes, yes, and of course also fpc 3.0.X and 3.2.0 compatible.

> Yes. Do it, so people see that mseide is still alive! 

OK, I will do it.

But there is a bémol, Martin did add 2 binaries for ARM cpu.

Sadly I only have a Raspberry pi B (ARM cpu) with installed a
Raspbian-eabihf distro.
I dont have nothing to test+compile with the old eabi OS.

So I could make the binaries for Windows 64/32 bit, Linux 64/32 bit, FreeBSD
64 bit and Linux ARM Raspbian eabihf.

Also, I propose to name the new release 5.0.0, (it seems that Martin changed
the first number when a new fpc version was allowed).

And change, maybe, the copyright with:

Copyright (c) 1999-2020 by Martin Schreiber and friends.

OK ?

Fre;D




--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[fredvs]

--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[Sieghard]

Hello fredvs,

you wrote on Mon, 30 Mar 2020 14:20:45 -0700 (MST):

> Now that fpc 3.2.0 has been officially released:
...
> Maybe we could release also a new binary release of MSEide.

Should be warranted, as the last issue of mseide (4.6.2) is several years
old by now

> Sadly this release in not yet compatible with fpc 3.2.0.

Isn't your latest version, adapted for fpc 3.3.1?
Does this contain too many other changes that you rather want to refrain
from using it as a release version? If so, could you back port the
modifications that make it compatible, as they probabely will also work
with this slightly older fpc issue?

> So, maybe it is time to release new binaries compatible with foc 3.2.0.
> What do you think?

Yes. Do it, so people see that mseide is still alive!

-- 
-- 
(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
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] New release of MSEide.

[code dz]

good idea , but 3.2 is still in release candidate


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk