[Released] Maxthon 3.0.20 Portable

Does this paf version leave any traces on the computer (e.g. AppData, Registry)?

By the way, who came up with this stupid smiley button in the top left corner of the browser window? In many betas they had a decent menu hidden under a less obtrusive button at the same place...

You're right, I apologize for my tone, I didn't mean to offend anybody.

Here are my findings with the PortableApps.com Format details and related items. I haven't yet tested its functionality or portability.

• You shouldn't really use the Portable App Template; it's old, unsupported, less powerful and harder to use than the official PortableApps.com Launcher. It looks as though you've taken bits of the PAL template and PAT and mixed them up a bit. You should go to just the PAL template in its structure if you're going to use it at all (which you should). Looking at your configuration of it, this is the approximate configuration you need for Maxthon3Portable.ini:
  

  [Launch]
  ProgramExecutable=Maxthon3\Bin\Maxthon.exe
  CommandLineArguments=-appdatapath:"%PAL:DataDir%"
  
  [Activate]
  Registry=true
  
  [RegistryKeys]
  maxthon=HKEY_CURRENT_USER\Software\Maxthon3
  
  [Environment]
  PATH=%PATH%;%PAL:AppDir%\Maxthon3
  

  Consider whether the PATH addition is necessary.

  The only modification I've made there from your existing configuration is the command line arguments from using ..\..\Data to using "%PAL:DataDir%". The reason I suggest you should use %PAL:DataDir% rather than ..\..\Data if possible is that it means it's got an absolute path, so in Live mode you may be able to have [LiveMode]:CopyApp=false, which will make it faster to load as it doesn't need to copy Maxthon to the local disk. Also it proofs against any possible changes in how PortableApps.com Format apps can be structured (though no changes are foreseen at the moment). The quotes in the CommandLineArguments are for when running from a path with spaces; I don't yet know how that works with Maxthon3 as I haven't tested it.

• You're not allowed to manufacture your own PortableApps.com splash screen due to trademark and quality control reasons. We only create them when we have certified that it's all properly portable, in PortableApps.com Format, ready for release, etc. etc. If you're doing a test release of it here, it should be structured as a Development Test, meaning the DisplayVersion in appinfo.ini the should be "3.0.17.1109 Development Test 1", and the splash screen should be the black and white Development Test release splash screen (as included in the PAL app template).
• App\AppInfo\appinfo.ini: as a result of using PAT, you've got a badly formatted appinfo.ini which some incorrect or suboptimal values.
  

  [Format]
  Type=PortableApps.comFormat
  Version=2.0
  [Details]
  Name=Maxthon 3.0 Portable
  AppId=Maxthon 3Portable
  Publisher=Ray1 and Ldfa for Maxthon.fr
  Homepage=http://www.maxthon-fr.com/site/mx3/
  Category=Web Browser
  Description=Maxthon 3 Portable
  Language=Multilingual
  [License]
  Shareable=true
  OpenSource=false
  Freeware=true
  CommercialUse=false
  [Version]
  PackageVersion=1.5.0.0
  DisplayVersion=3.0.17.1109_multilingual
  [Control]
  Icons=1
  Start=Maxthon 3Portable.exe
  

  Here is what it should look more like:

  [Format]
  Type=PortableApps.comFormat
  Version=2.0
  
  [Details]
  Name=Maxthon 3.0 Portable
  AppID=Maxthon3Portable
  Publisher=Ray1 and Ldfa for Maxthon.fr
  Homepage=maxthon-fr.com/site/mx3/
  Category=Internet
  Description=Maxthon 3 is a fast and flexible browser, providing you with your choice of rendering engine.
  Language=Multilingual
  Trademarks=Maxthon is a registered trademark of Maxthon International
  
  [License]
  Shareable=true
  OpenSource=false
  Freeware=true
  CommercialUse=false
  
  [Version]
  PackageVersion=3.0.17.1109
  DisplayVersion=3.0.17.1109 Development Test 1
  
  [Control]
  Icons=1
  Start=Maxthon3Portable.exe
  

  That has a few things changed and the Trademarks line added - do you have an EULA you wish to show? If so, put it in the Other\Source directory, named EULA.rtf or EULA.txt. Also note that the Homepage (which omits http:// by convention) should be the homepage of the portable app; if you have a special page for the portable version or create one in the future that would probably be the correct link to have.

• You didn't replace the title in help.html. Also a much shorter tagline would be better (they're not more than a dozen or so words, normally closer to half a dozen).
• What is the product name to be? "Maxthon"/"Maxthon Portable", "Maxthon 3"/"Maxthon 3 Portable", or "Maxthon 3.0"/"Maxthon 3.0 Portable"? I've found references to all of these on your site, but I think Maxthon 3 is the most common?
• Language switching based on the values in the PortableApps.com Platform would be a good feature (standard for our multilingual apps); how does Maxthon 3 select and store the language?

Looking at it all, I'm not sure if you've looked at the PortableApps.com Format specification; if you haven't, it would be a good idea to read it.

Please ask me if you have any questions.

Generally, it's a bad idea to have the version in the directory/ appid. What happens when version 4 comes along? Will it still be "Maxthon 3Portable"? The AppID should be MaxthonPortable. If you anticipate making the older Maxthon portable at some point as well, it could be MaxthonClassicPortable, MaxthonRetro or similar. Or the new one could be MaxthonProPortable. On quick glance at the website, the difference between Maxthon Classic, Maxthon Latest and Maxthon 3 are a bit inobvious, so this could be a problem beyond just the portable version. If the others will be retired at some point anyway and Maxthon 3 is what the future will be, then having the AppID as MaxthonPortable would make the most sense and we'll just ignore the older versions.

OK, that's getting better

• There should be 8-bit (256 colour) icons in appicon.ico.
• You've left the old launcher Maxthon 3Portable.exe in next to the new PAL-based Maxthon3Portable.exe.
• The comment at the end of App\AppInfo\Launcher\Maxthon3Portable.ini should be removed.
  

  
  
  ; Details of the launcher.ini format are available in the PortableApps.com
  ; Launcher package. (You should not leave this comment in.)
  

• The files in Other\Source from the PAL app template should be left in. They're designed for the end user and so should stay in for closed-source apps, not just for open-source apps.
• App\readme.txt is missing from the PAL app template - we like to keep that in just to try to avoid people running the app without the launcher in a non-portable way (it just says "usually no need to touch stuff in here")

Now on to the actual app:

• Works well and portably across drive letters (so long as you don't use Trident - then the cache goes to the local computer). It also copes with moving the directory - bonus marks; set [Launch]:DirectoryMoveOK=yes in App\AppInfo\Launcher\Maxthon3Portable.ini for better PAL 2.1 compatibility with that. Good job.
• It runs its own updater; seeing as there's no update yet, I can't check how that works. Will that do any damage to the local system, a local installation or anything like that?
• If it's possible, you should disable the "default browser" check by default. It's too easy at the moment to break portability by doing that as it asks you as soon as you start. Better still, put some switch in the browser itself so the portable version can not offer that option at all (but I don't expect that).
• The separation of user stuff into Data\Users\guest etc. (I presume it would load your saved data from the web if you logged in) can be a bit of a pest. Does it keep a copy of every user's stuff that's logged in, or is there only one directory in Data\Users at a time?
• Language switching could work with Data\Users\guest\config\config.ini, in the [language] section. However, it has three language variables... PAL is only designed to cope with one. And the point above about what happens with multiple users stands too. I don't feel like getting an account with their system so you'll need to tell me

It's looking good, the issues are getting smaller. The next release you do (while on the same version of Maxthon) should be Development Test 2, etc. Also update the main post so that it's got the latest. It would be good if you would follow this structure for the page (as it's a Beta Test, not a request).

Hope you're enjoying working with us!

Nice work,thanks for sharing

Hello

throughout the software works well; but when I download a file, there is create a directory in (C:\Users\User\AppData\Roaming\Maxthon)and which remains after closing Maxthon

Thanks

Sorry for my English

I think we're ready on this now. If you'd like to do a final/stable build, I think we can release this this week. Same with the non-turbo one if you'd like to support that ongoing as well.