Re: [Vym-devel] VYM on Windows
Brought to you by:
insilmaril
From: Dr. K. H. <ka...@gm...> - 2013-03-10 18:02:04
|
Hello Patrick, > I normally prefer msvc for applications, since that makes debugging normally far easier (with smaller binaries & debug information files). I don't have any preference for the compiler, I am sure both are good, and since you have more experience with Qt/KDE on Windows, we should go with msvc. > Since I know applications that use quazip, I would think this is not a bad idea. I will have a look at quazip and VYM open/save code >I just read your blog post and have the following comments: >zip/unzip required should of course either be changed via packaging (I can try and package a new version which removes that need, but personally I would prefer to have vym use quazip directly). >The handling of spaces both in the installation directory path and the path of files should work imho, so I would prefer if these bugs get fixed rather than using workarounds. The blog post was intended to give a solution to the existing setup/binaries, I agree with you we should fix these bugs instead of using workarounds. >So if you are interested in working on the windows port, maybe we can get this done together? I am very interested on working on VYM Windows, and it will great to work with you on in it. The following is the list of Windows main issues/bugs as far as I know: 1) Using quazip to handle opening/saving files, making sure it works with long file/folder names with spaces. Importance: High 2) Making cut, copy and paste work (it might be a simple bug, I have not looked at the code yet). Importance: High 3) Making undo/redo work. Importance: High 4) Saving settings files vym.ini inside %appdata%\vym folder, if it stayed under default "c:\program files\vym" the program can't save to the file unless it is run as an Administrator. Importance: High 5) Set application to open pdf files as explorer. Importance: medium 6) Package help file vym.pdf with setup. Importance: low 7) Remove dbus in Windows (is dbus really needed/useful under Windows?). Importance: low Are you aware of other bugs? I will start with issue one (zip/unzip), since it is the most important. Hopefully we can release a stable Windows version soon. Best regards, Kais -----Original Message----- From: Patrick Spendrin [mailto:ps...@gm...] Sent: Sunday, March 10, 2013 1:46 AM To: vym...@li... Subject: Re: [Vym-devel] VYM on Windows Am 09.03.2013 13:40, schrieb Dr. Kais Hassan: > Hello Uwe, > > > > Thanks for your replay. > > > > I have started looking at VYM code and managed to build it on Windows after removing the dbus bits, I am aware that there is dbus support on Windows but not sure if it is needed for VYM (Windows). However, I don't think this is a major issue for now. > > > > I have also read Patrick post about using emerge to reproduce the > Windows build, so I will follow that > > > > https://sourceforge.net/mailarchive/message.php?msg_id=29618892 > > > > Is Patrick still doing the Windows builds? Yes, if I find some time, I can do some builds. > > > > I have looked at Clementine on Windows and they are using mingw, so I > think you gut feeling is right J I normally prefer msvc for applications, since that makes debugging normally far easier (with smaller binaries & debug information files). > > > > I will look more into quzip and there is also OSDaB, have you considered it? > > > > http://osdab.42cows.org/snippets/zip.php?mode=advanced Since I know applications that use quazip, I would think this is not a bad idea. > > > > Since, I depend on and love using VYM I am motivated to work on the Windows port. I just read your blog post and have the following comments: zip/unzip required should of course either be changed via packaging (I can try and package a new version which removes that need, but personally I would prefer to have vym use quazip directly). The handling of spaces both in the installation directory path and the path of files should work imho, so I would prefer if these bugs get fixed rather than using workarounds. So if you are interested in working on the windows port, maybe we can get this done together? > > > > Best regards, > > Kais > regards, Patrick ---------------------------------------------------------------------------- -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Vym-devel mailing list Vym...@li... https://lists.sourceforge.net/lists/listinfo/vym-devel |