Page 1 of 1

Throwing Out Ideas for Future of XYplorer

Posted: 04 Mar 2013 08:44
by Enternal
Hello. I'm a bit worried about the future of XYplorer due to the compiler issues (not being able to compile 64Bit) and other things so I'm just throwing out ideas. Just to note, I'm not a programmer or anything (just a hobbyist scripter at most) so the chance of me throwing out outrageous and stupid ideas is high.

One of the issues is XYplorer cannot handle 64Bit shell extensions due to it being a 32Bit program. Perhaps it's possible to write an external program in a different language (C++?) that can handle that? So on 64Bit, XYplorer pass off the work to process shell handles to the external program which then passes back the complete job to XYplorer to process? If it's on a 32Bit computer, then it will do as it normally does. The external program could probably do some of the multi-threading things. So although it's not exactly multi-threading, but I guess it could alleviate some of the issues regarding GUI lagging when XYplorer is doing certain things because it's still waiting to finish the current process. This also ties back to the problem in http://www.xyplorer.com/xyfc/viewtopic.php?f=2&t=9343 So XYplorer handles the listing of files and the external program does the icon caching or something like that. This could also apply to thumbnail processing over the network? This external program could be written in C++ or something like PureBasic which is another BASIC dialect. From what I see, it gets really good review and it's also lifetime license. It can compile programs for Linux, Mac, Windows (obviously), and in 32Bit/64Bit. It seems to also have a good library for a lot of things you might need.

So are any of these ideas plausible? Are they even good ideas? I do realize that by making an external program, you will no longer have a single executable that does everything but at the same time, you already have XYcopy that handles the file copying/backup/moving process so it won't be much to add to?

Re: Throwing Out Ideas for Future of XYplorer

Posted: 04 Mar 2013 09:42
by admin
Yes, these are possibilities. But I'm currently researching the option to simply add the 64-bit items "manually" (by reading the registry).

Re: Throwing Out Ideas for Future of XYplorer

Posted: 04 Mar 2013 15:47
by 40k
Can someone explain to a layman like myself why 64 bit is so important?
I can understand the need for 64 bit OS due to physical limits such as supportable memory size and such. But why does Xyplorer need 64 bit?

Re: Throwing Out Ideas for Future of XYplorer

Posted: 04 Mar 2013 16:43
by admin
40k wrote:Can someone explain to a layman like myself why 64 bit is so important?
I can understand the need for 64 bit OS due to physical limits such as supportable memory size and such. But why does Xyplorer need 64 bit?
http://www.xyplorer.com/faq-topic.php?id=ctx64

Re: Throwing Out Ideas for Future of XYplorer

Posted: 04 Mar 2013 17:16
by neminem
With a note that, while it should be possible to just install the 32-bit version of a program alongside the 64-bit version... a lot of programs with installers won't let you, saying something like "the program is already installed".

Re: Throwing Out Ideas for Future of XYplorer

Posted: 05 Mar 2013 12:43
by 40k
admin wrote:
40k wrote:Can someone explain to a layman like myself why 64 bit is so important?
I can understand the need for 64 bit OS due to physical limits such as supportable memory size and such. But why does Xyplorer need 64 bit?
http://www.xyplorer.com/faq-topic.php?id=ctx64
I understand now. That seems like such a typical "Windows" problem. I rarely ever use the shell context menu.

Re: Throwing Out Ideas for Future of XYplorer

Posted: 06 Mar 2013 04:26
by Enternal
Yeah it's an important problem if you use Shell extensions a lot. Either way, reading the registry to do that? That's quite interesting! Hope that could possibly solve the issue. How about the threading issue? Do you have any ideas on how to deal with that?

Re: Throwing Out Ideas for Future of XYplorer

Posted: 06 Mar 2013 17:40
by JDługosz
Not just shell extensions, but another issue:

In a 32-bit process, the emulation layer sees its own (e.g.) SYSTEM32 directory, not the real one. That can be confusing when trying to look at that directory, or copy files to/from such a directory.

There are documented ways to get the "real" location from a 32-bit process. I'd like to see a simple indicator that such a directory is 32-bit, and also switch between the 32/64 bit versions.