goolobi.blogg.se - Smartsynchronize flatten

#Smartsynchronize flatten software#
#Smartsynchronize flatten license#
#Smartsynchronize flatten windows#

the Stashes mode allows to inspect the content of stashes and to apply or drop them.

the All Branches + Tags mode gives an overview of all branches and tags and can be used for checking out non-local branches or merging/cherry-picking from these branches.

the My History mode shows your local branches and will be sufficient for 95% of the daily commit-related tasks.

the Local Changes mode serves for committing, resolving conflicts, searching or modifying local files in the Working Tree and Index.

the toolbar offers the most important operations, guiding the user through the workflows.

the visible Git information is restricted to what is required by the workflows.

Every mode serves a specific purpose and is optimized for certain workflows and repository states:

#Smartsynchronize flatten windows#

The most important difference compared to the existing Log and Working tree windows is a GUI layout with different modes for Local Changes, My History, All Tags + Branches and Stashes. With the Standard window we are closing this gap by channeling Git functionality into workflows, to avoid potential pitfalls. This is especially great for power users, but it may be overwhelming to less experienced Git users. SmartGit is known to be a very powerful and flexible client when it comes to Git functionality.

#Smartsynchronize flatten license#

Your non-commercial license will work with these products out-of-the-box.įor version 22.1 (currently in development), we have introduced a new main window in addition to the existing Log and Working tree window: we call it the Standard window because it enforces some standards on the way Git is used. We have applied the same licensing changes for SmartSVN 14.3 and SmartSynchronize 4.4. Hence, if you as a hobby-user are affected by this licensing change, please consider to publish your work (why not?) – then we are happy to support you and your project, too. We strongly commit to open-source and the entire SmartGit business is built upon open-source projects itself (and contributes back to these projects frequently). For this reason, we unfortunately had to drop the hobby usage option entirely. Open-source usage and academic usage can be verified easily, closed-source hobby usage can’t.

#Smartsynchronize flatten software#

For a B2B-product in the Software industry, this is in stark contrast with the overall number of Software developers compared to the number of primary open source developers and academic users 😉 What about hobby usage? We have decided to take this step, because the current proportion of non-commercial users is above 60%. The new licensing conditions are now enforced by requiring a non-commercial license. Technically enforced licensing conditions On the other hand, SmartGit can’t be used for “hobby usage” anymore (see below why). employees or students on public academic institutions (before, it was only “for learning or teaching on a public academic institution”).everyone who spends the majority of their work on open-source projects (before, it was only “to actively work on open-source projects”, which is significantly more restrictive).įor more details on custom themes, have a look at Playing with themes.įor SmartGit 22.1, we have changed the non-commercial licensing conditions to be more permissive overall. If you think to have found a nice palette for version 22.1, please share with us at. nnector.16=derive(#ff0000, 0.8, 0.7)Ī compressed theme file graph-colors-v21.theme with exactly this configuration is attached to this post, it just needs to be unpacked.

red) and then duplicate these first 8 slots to slots 9-16: nnector.1=derive(#80ff00, 0.7, 0.7)

For example, to have an almost identical palette as for version 21.x, you have to add one more color (e.g. values, then configure this file in Preferences, User Interface.

If you prefer to have different colors, you can use a custom theme file which just overrides nnector. A drawback of the enlarged palette is that colors are not that distinctive anymore. This has become an important objective as we have changed the overall Graph coloring logic to use constant, hash-based colors per branch. Our main goal was to make collisions less likely. For SmartGit 22.1 we have extended the Graph color palette to 16 colors.