Re: [MSEide-MSEgui-talk] Some news from Github issues.
On 01/05/2020 6:01 pm, fredvs wrote: > Thanks to Johann Elsass we have now a bridge that allows to use units > without the need to add 'mclasses' after 'classes'. Well done to all involved. When I saw Martin start fork standard FPC classes, I knew it was going to be a terrible idea. Very glad to hear a alternative/revert solution was found. 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] Some news from Github issues.
Hi Fred; How is it possible to clean automatically mseide unit from unused modules in Uses clause. De : mohamed hamza Envoyé : samedi 2 mai 2020 17:06 À : General list for MSEide+MSEgui Objet : RE: [MSEide-MSEgui-talk] Some news from Github issues. Hi Fred; How is it possible to clean automatically mseide unit from unused modules in Uses clause. De : fredvs Envoyé : vendredi 1 mai 2020 17:01 À : mseide-msegui-talk@lists.sourceforge.net Objet : [MSEide-MSEgui-talk] Some news from Github issues. Hello everybody. Hold on! There was some movement in MSEgui code. We have now a bridge! Before the bridge, if you used a unit that uses 'classes' in uses section, you needed you add 'mclasses', just after 'classes'. This because MSEgui uses his own class definition. Thanks to Johann Elsass we have now a bridge that allows to use units without the need to add 'mclasses' after 'classes'. Of course the bridge dont ignore the definition of 'mclasses', but makes life easier and more transparent for end users. By default the bridge is enabled but you may disable it with the -dno_bridge parameter. It does not affect the mesgui code because all the "tweaked fpc files" of /fpccompatibility are renamed with mse_***. Of course the code in msegui was adapted for that new names. One of the big advantage of the bridge it that now msegui is compatible with external units, like BGRABitmap, that works perfectly now with msegui. Also, if you dont need to use external unit or if you have already tweaked them, you may disable the bridge and all will be like it was without bridge. Re-hold on and have lot of fun! 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] Some news from Github issues.
Hi Fred; How is it possible to clean automatically mseide unit from unused modules in Uses clause. De : fredvs Envoyé : vendredi 1 mai 2020 17:01 À : mseide-msegui-talk@lists.sourceforge.net Objet : [MSEide-MSEgui-talk] Some news from Github issues. Hello everybody. Hold on! There was some movement in MSEgui code. We have now a bridge! Before the bridge, if you used a unit that uses 'classes' in uses section, you needed you add 'mclasses', just after 'classes'. This because MSEgui uses his own class definition. Thanks to Johann Elsass we have now a bridge that allows to use units without the need to add 'mclasses' after 'classes'. Of course the bridge dont ignore the definition of 'mclasses', but makes life easier and more transparent for end users. By default the bridge is enabled but you may disable it with the -dno_bridge parameter. It does not affect the mesgui code because all the "tweaked fpc files" of /fpccompatibility are renamed with mse_***. Of course the code in msegui was adapted for that new names. One of the big advantage of the bridge it that now msegui is compatible with external units, like BGRABitmap, that works perfectly now with msegui. Also, if you dont need to use external unit or if you have already tweaked them, you may disable the bridge and all will be like it was without bridge. Re-hold on and have lot of fun! 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] Some news from Github issues.
Hello Med. Nice to read you. > How is it possible to clean automatically mseide unit from unused modules > in Uses clause. Do you mean before compilation? You may use a script and set it in Project Options - Make - Command before. You may also use the -B parameter (re-build all), but it does not work each time (old fpc bug forever), and better to use a script before to compile. Or manually delete all the files that are in /units. What is your OS?: For Linux, IMHO, just do a script with something like that: $ cd ./units $ rm *.* By the way, you are the professor MSEgui database, and I am very interested by your advice about the new bridge of MSEgui. I hope that all the MSE DB part is still working ok. I did some tests, all seems ok, but you are deeper in MSE database than me. 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] Some news from Github issues.
Re-test to sent a mail. Re-hello Med. > > How is it possible to clean automatically mseide unit from unused > modules in Uses clause. I think I did not understand ok and my previous post has nothing to do with your question. Are you talking of all the units added automatically by the MSEdesigner after the uses section that are, sometimes, not needed? If so, I remember to have asked this to Martin some years ago: Why so much unused files? What I did understand is that the policy of MSEgui is to compile all what could be needed and let, at the end, the linker take what objects is needed for linking. And yes, many times there are lot of compiled objects that are not linked. 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] Some news from Github issues.
Ha, it seems to work now, so I retry. Re-re-hello Med. After the answer of Martin , I did some tests: remove all the unused files in the uses section and compare the result of the binary produced after compilation. And I have to admit that it makes no difference, the binaries with all unused files are exactly the same, with same size, than the one compiled without the unused files. Strange because with other widget-set it blow up the exe if there are unused files. So the conclusion is: dont waste your time to clean up all the unused files, it will be done at linking. 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] Some news from Github issues.
Re-hello Med. > > How is it possible to clean automatically mseide unit from unused > modules in Uses clause. I think I did not understand ok and my previous post has nothing to do with your question. Are you talking of all the units added automatically by the MSEdesigner after the uses section that are, sometimes, not needed? If so, I remember to have asked this to Martin some years ago: Why so much unused files? What I did understand is that the policy of MSEgui is to compile all what could be needed and let, at the end, the linker take what objects is needed for compilation. And yes, many times there are lot of compiled objects that are not linked. 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] Some news from Github issues.
On 03/05/2020 12:40 am, fredvs wrote: > What I did understand is that the policy of MSEgui is to compile all what > could be needed and let, at the end, the linker take what objects is needed > for linking. 100% correct. When it comes to FPC, unused units in the uses clause it not much of a problem like in other languages. The compiler and linker will remove units, methods etc that is not needed, when it generates a "release build" of your project. 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] Some news from Github issues.
Hello fredvs, you wrote on Sat, 2 May 2020 16:25:13 -0700 (MST): > What I did understand is that the policy of MSEgui is to compile all what > could be needed and let, at the end, the linker take what objects is > needed for compilation. That's a nice feature of the linker. > And yes, many times there are lot of compiled objects that are not linked. But is it really required by any means to always _compile_ a lot of unused stuff, even when this does not blow up the final result (which is commonly quite loaded anyway). I think not, and it might be useful to devise some tools to get rid of most of the unneeded ballast. (If I find a place to start at, I might attempt to build one. Probabely scriptable, to be used from the "tools" menu or so, like the olden "i19n" utility modification, which I've never heard of 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