![]() It's already been many years since we've seen a real feature-update (beside the v4.0 update, which was mostly a maintenance update to remove license registration, and a few small improvements, like SVG icons), or the risk is that it might eventually become an obsolete application, possibly unsafe to use. So, yes, it would be nice if you could confirm to use whether there are still plans to update the SDK in the future, or if the project is going to be stale. Is it still truth that you plan to release AS 4.0 SDK soon (not necessary on GitHub, if it is more work).Īnd, if I may add, there are other users monitoring this post and the GitHub repo waiting for an AS SDK update. ![]() I was looking into the SDK license to see if it allowed to publish it on GitHub - obviously having an official SDK maintained by Altap would be much better, and then just fork it and contribute. It'd be helpful to see how the API methods and comments were changed through the time, and understand meaning of some multi-argument functions ( fs is a good wouldn't it be enough to keep a "devel" branch as a baseline for all development commits and pull requests, and then just merge into master every version bump? This way you'll always have a clean "master" branch containing only release versions (and release tags), but still keep a full history of the various commits that were made between releases (which can also be handy to follow development). No need for complete history, simply just one commit per release (4.0, 3.08, 3.07, maybe a few more). SDK repo should also contain commit history. (WinSCP author) will be able to prepare 64-bit version of WinSCP plugin.A few more comments from me how the repositories should be organized: Idea also install 32-bit version of Altap Salamander. ![]() Unfortunately WinSCP plugin is missing in 64-bit Altap Salamander, so it is a good.Windows is redirecting access to this registry key. Reason: part of emulation layer for running 32-bit applications on 64-bit Altap Salamander will show different content for registry key HKEY_LOCAL_MACHINE\Software comparing to.Windows is redirecting access to this directory. Altap Salamander will show different content for directory %windir%\System32 comparing to.Reason: 32-bit applications can't load 64-bit shell extensions. Context menu displayed for files and directories will be different comparing to context menuĭisplayed from Windows Explorer.Running 32-bit Altap Salamander on 64-bit Windows has several drawbacks:.Both 32-bit and 64-bit versions of Altap Salamander are sharing the same configuration.The registration key is valid for both 32-bit and 64-bit versions of Altap Salamander.It is perfectly fine to install both 32-bit and 64-bit versions of Altap Salamander on 64-bit Windows.You can install a 32-bit version of Altap Salamander to both 32-bit and 64-bit versions of Windows.To install a 64-bit version of Altap Salamander you need a 64-bit version of Windows.Release Notes Previous Versions License Agreement Which Altap Salamander version should I install: the 64-bit or 32-bit version? System requirements: Any PC running Microsoft Windows 10, 8.1, 7 (both 32-bit and 64-bit versions). Language versions: English, Czech, Dutch, French, German, Hungarian, Romanian, Russian, Simplified Chinese, Slovak, and Spanish languages are included.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |