Synfig Project Forum

Thanks nikitakit and zelgadis for the testing!
I'll apply to master and wait for pixelgeek feedback.
I'll release a second candidate I think.

-G

_________________
Synfig needs your help!
Developers, packagers, bug testers, translators, artists, web developers, wiki writers... you can contribute!

I'll try and build & test it tonight - I had a busy weekend.

Much better, but the horizontal dock is a bit low.

Pixelgeek, the initial layout is going to be fixed. I'm working on that. What we need to know is if the mangling problem happens or not now. In linux I trigger it by resetting the initial window configuration and then close and open synfigstudio several times. One of the times (randomly) it used to mangle the dock sizes and ruin all the window layout.
-G

_________________
Synfig needs your help!
Developers, packagers, bug testers, translators, artists, web developers, wiki writers... you can contribute!

I'm not seeing that problem, but then again , I'm using GTK 2.16. Need me to upgrade?

Theoretically it is 2.18+ when the problem started. Are you going back to 2.16 or I'm wrong if I remember that you used 2.18 in the release of 0.62.00 for windows?
It seems that the problem with 2.18+ is solved with the patch but if you're using 2.16 in the next release it won't be a problem with the windows version.

Besides that, shouldn't we be consistent on windows releases so we don't get back to old gtkmm versions on newest releases? Some day we would need to use some of the new gtkmm 2.18+ library fucntions so the earlier we upgrade and make the problems arise, the earlier are them solved.

-G

_________________
Synfig needs your help!
Developers, packagers, bug testers, translators, artists, web developers, wiki writers... you can contribute!

I've been using 2.16 with Synfig for windows since August of 2009. Looks like 2.18 came out in December, and 2.20 in early April of this year, but I haven't downloaded them yet. Since we're bundling the binaries with Synfig now, I don't see any point in upgrading right now. Unless there are any benefits for doing so? New features we're using?

Chris

I think that we can continue using older ones in windows binaries. If in the future we need with no replacement any of the features of the new versions then you should upgrade. Linux problem is that libraries are going faster and we need to update code to "fix introduced bugs"
-G

_________________
Synfig needs your help!
Developers, packagers, bug testers, translators, artists, web developers, wiki writers... you can contribute!

LOL. Greatest joke! Genete, you are good at marketing!

_________________
Morevna project:
Recently completed tasks: Demo released
Top priority tasks: Website reorganization

Hi there.
I've committed changes to allow dual splash screen and also I've fixed the reset initial windows configuration to fit the primary monitor size.
I hadn't enough time to release the second candidate but you can test the changes in the master branch.

I've noticed that the feature that I introduced to change the cursors when using the Transform tool, ruins the other tools cursors as well as it seems that the keyboard wrapping is done in any tool state.
I think that there is a solution by forcing the tool status to keep the cursor all the time. It is a kind of hacking because I don't know why the keyboard is wrapped in any tool state but it might solve the cursor problem for all the tools.
Anyone has other idea?
-G

_________________
Synfig needs your help!
Developers, packagers, bug testers, translators, artists, web developers, wiki writers... you can contribute!

My son has a lenovo laptop with Windows7. I've installed in it the "all in one Synfig package", but it doen't work well: it doesn't draw the Blines or figures an it doesn't fill
the regions. I can try in it this release, but I need you to tell me how to do.

Better wait for a binary release from pixelgeek.
-G

_________________
Synfig needs your help!
Developers, packagers, bug testers, translators, artists, web developers, wiki writers... you can contribute!

Ok, things are very close to the end now.
Tasks done:
1) Write the Press Release. It still unpublished and has been nicely reviewed by pixelgeek, nikitakit and berteh.
2) Tag the git commit after a little mistake . Now it is stable.
3) Create the 0.62.01 tarballs and upload them to sf
4) Create the binaries and upload them to tuxfamily.

I wonder if we (pixelgeek) should reconsider to organize the uploading folders at sourceforge. I believed that it was a good idea to provide a tarball with the three etl, synfig and synfigstudio tarballs to make easier to download a single package for the distro developers. (they are here). But the windows binaries have been uploaded there too. I guess that it will be less confusing to the user to separate windows binaries from general propose code tarballs. I've created a windows-binaries folder for that (it is empty at the moment). What do you think pixelgeek? Can you move the older windows binaries to there and upload your windows binary in the new folder. If so, I will delete the deb and rpm from that ETL-Synfig-SynfigStudio folder and only upload there the package of the source code.
For linux versions I prefer to provide binaries (universal rpm, deb and targz) from tuxfamily, and leave sf for source and windows binaries.

It is pending:
1) Publish the Press Release
1) Update the download links
2) Send all the short press releases to the magazines etc. etc.

Please let me do the step of publish the Press Release after we agreed where the files will go on sf.
Cheers.

_________________
Synfig needs your help!
Developers, packagers, bug testers, translators, artists, web developers, wiki writers... you can contribute!

For Windows users - https://sourceforge.net/projects/synfig ... e/download
And after reading Genete's post, https://sourceforge.net/projects/synfig ... e/download also works

I'm not too worried about where they are as long as they show up, and can be downloaded easily.
Enjoy, Chris

I think it's better to store linux binaries onsf.net for 2 reasons:
1. Keep everything in the same place is logical.
2. We have unlimited space on sf.net. Considering that there will be lot of more releases... Let's save tuxfamily's resources for other purposes

So my suggestion:
* store release sources and binaries on sf.net
* store temporal builds (development snapshots) on tuxfamily. But maybe use sf.net for that too? They can be removed anytime...

I have a proposal for folder structure at sf.net:
* "ETL" - for all sources of ETL (without subfolders for each version - this is redundant)
* "synfig" - for all sources of synfig (without subfolders for each version - this is redundant)
* "synfigstudio" - for all sources of synfigstudio (without subfolders for each version - this is redundant)
* "binaries" - for Linux and Windows all-in-one packages
** "binaries/linux" - linux packages
** "binaries/windows" - windows installers
** "binaries/mac" - mac packages (someday)

Also, I think there's no reason to make all-in-one source packages. That's a wasting of web and time resources and having too much alternatives for downloading the same thing confuses users.

Note to all: please don't forget to replace "https" to "http" in urls.

_________________
Morevna project:
Recently completed tasks: Demo released
Top priority tasks: Website reorganization