Changes between Version 3 and Version 4 of GuiUpdateProject


Ignore:
Timestamp:
03/09/12 10:52:16 (6 years ago)
Author:
samuli
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GuiUpdateProject

    v3 v4  
    1010There are also tons of [https://community.openvpn.net/openvpn/wiki/RelatedProjects#Inactiveprojects inactive client GUI projects] and probably dozens of in-house client GUI implementations. This fragmentation of development effort hurts both users (who never get to use a really good GUI) and developers (who have to reinvent the wheel over and over again).
    1111
    12 OpenVPN project has distributed a [http://openvpn.se/ Windows GUI] with it's Windows installers for years, but core OpenVPN developers have put very little emphasis on developing the GUI; this is understandable, as it's outside the scope of the project. However, bundling an obsolete (released 2005) WindowS GUI gives people the wrong impression of OpenVPN's capabilities and limitations. So, a Windows GUI overhaul is definitely needed.
     12OpenVPN project has distributed an OpenVPN-GUI with it's Windows installers for years, but core OpenVPN developers have put very little emphasis on developing the GUI; this is understandable, as it's outside the scope of the project. OpenVPN releases prior to 2.3-alpha1 included a [http://openvpn.se/ very old] (released 2005) OpenVPN-GUI. Releases starting with 2.3-alpha1 use a [http://sourceforge.net/projects/openvpn-gui/ more modern OpenVPN-GUI].
    1313
    1414Here's a list of potential reasons why so many OpenVPN GUIs exist: