TOPIC:

Regarding your "uidesigner_ext", why don't you rather use the Releases feature of github to distribute your binaries, instead of including them in the code repository? [github.com/fredvs/uidesigner_ext/releases] It is very easy to use on Github. Simply tag a commit with a release version, then go to the Release page and make a new release, selecting the release tag. Then upload your binaries against that release. That way you still have binary releases, and the source code repository doesn't have the huge binary file overhead (which makes your repository much larger to download). Github will automatically supply *.tar.gz and *.zip archives of the source code for each release.

Because i am afraid to do it wrong
Of course i would prefer to do as you explain, but i am not a Github pro and prefer not to touch to your repository for not doing mess.

Fre;D

hehehe... There is nothing to be afraid of, and you are working on your repository, not mine. If you do something wrong, you can simply delete the release and start again.

Here is Github's documentation on creating releases. It is very simple.
github.com/blog/1547-release-your-software

And here is Git documentation on tagging specific points in the code history:
git-scm.com/book/en/v2/Git-Basics-Tagging

much larger to download

Much larger, are you sure ? Do not forget that those binaries are pure fpGUI =>
All the binaries zipped (Windows32 + Windows64 + Linux32 + Linux64 + freeBSD64) => 2,5 megas

Thanks for gitHub links, will take a look.

Fre;D

I know fpGUI binaries are small. But still, a code repository is not designed or meant for large binary blobs (files). Git is designed to be efficient with text because it only stores differences between two commits. When it comes to binaries, almost every byte will be different between binary files, so it stores a whole copy of that file as is. Your repository also contains unziped binaries, so that makes it larger too (though zipping will not help Git either). Just thought I would mention it.

But still, a code repository is not designed or meant for large binary blobs (files). Git is designed to be efficient with text because it only stores differences between two commits. When it comes to binaries, almost every byte will be different between binary files, so it stores a whole copy of that file as is. Your repository also contains unziped binaries, so that makes it larger too (though zipping will not help Git either). Just thought I would mention it.

Ok, i am converted, will study it.

Hum, by the way, /.git folder in designer_ext folder is => 98 megas
How to reduce it ? => With your "release" tip, would it decrease the size of /.git ?

Thanks

Fre;D

Hum, by the way, /.git folder in designer_ext folder is => 98 megas

Yup, that is what I meant, and the amount somebody is going to download if they clone your repository. The whole fpGUI git history from 2006-2015 is only 28MB in the .git folder.

How to reduce it ? => With your "release" tip, would it decrease the size of /.git ?

No you can't reduce it (not as far as I know), it is now part of the repository history. I'll do some google searching tonight, but again, I don't think you can reduce it, other than starting a new repository.

---- LAB CT version 5.40 Tasks list ----

-Task30 pl_AsphyreSphinx, Port to QT, Carbon, Cocoa etc (Total Steps 5)
-Task31 pl_GLScene, Port to QT, Carbon, Cocoa etc (Total Steps 5)
-Task51 pl_Graphics32, Port to QT5 and fpGUI platforms (Total Steps 5)

Ooops, it is in your plan already...
OK, i let you work without disturb...

Hello.

Here, in attachment, typhon_ide.pkg to add fpGUI project/application in Typhon => new project/application.



[EDIT] I have try to announce it to Graeme web site => problem accessing... => News::NNTPClient: Can't connect socket:

Fre;D

Thanks Sir
we will test and add ASAP

Ok Sternas, super.

So, for enabling pure fpGUI in Typhon =>

1) Install pure fpGUI package =>
=> for Windows => <fpgui>/src/corelib/gdi/fpgui_toolkit.lpk
=> for *nix => <fpgui>/src/corelib/x11/fpgui_toolkit.lpk

2) Add "new fpGUI project" in "New Project" with => typhon_ide.lpk (attachment of previous post)

Fre;D

We working on this Sir

Wow, excellent.
I am very curious to see how you will do to integrate the fpGUI UIdesigner. (if you have problems with it, please ask it )

Fre;D

Sir
we finish step2 (total 5) of lab Task52: "FpGUI integration to CT"
Tested only on windows 32/64bits until now
Tomorrow we will start OSes road (Step3)...(Linux, FreeBSD, Solaris, etc)
and some screens on win64 with Typhon64
.

Hello.

There is a fix in typhon_ide.zip => Creation of form is done now by => fpgApplication.CreateForm() => = more features.



Fre;D