lekaha / gappproxy

Automatically exported from code.google.com/p/gappproxy
GNU General Public License v3.0
0 stars 0 forks source link

Should include gui.exe in 2.0.0 release #64

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. gui.exe was not found in release 2.0.0
2. gui.exe in release 1.2.0 beta works well with new proxy.exe

What is the expected output? What do you see instead?
gui.exe should be included in release 2.0.0

Original issue reported on code.google.com by luke...@gmail.com on 13 Sep 2010 at 3:20

GoogleCodeExporter commented 8 years ago
the author changes the output method,switch windows to console,so gui.exe 
will not be found if you make exe yourself.you need to change setup.py if you 
want gui.exe
i think there may be two reasons the author made the adjustment
1.the client and the server must be consistent.a lot of problems are caused by 
the inconsistency
2.maybe the gui uses too much memory.i make gui.exe myself,and using the gui 
takes up 50m of RAM while using python without gui only runs 10m of RAM

Original comment by vmsh...@gmail.com on 18 Sep 2010 at 9:56

GoogleCodeExporter commented 8 years ago
I guess you did not try the gui.exe in previous version before. It is designed 
to change configurations and make the client software as a system service up 
and runing during system start-up. It's not the client software itself.

Original comment by luke...@gmail.com on 18 Sep 2010 at 10:01

GoogleCodeExporter commented 8 years ago
i have no need to running it as service. I launch the gui.exe when i want to 
use it,and then the gui.exe will launch proxy.exe. If you need gui.exe, you can 
make it yourself as i said above 

Original comment by vmsh...@gmail.com on 18 Sep 2010 at 2:29