The PortableApps.com Launcher source code is divided up into lots of “segments”, each of which can run a number of “hooks”. This aids with code separation of different pieces of functionality, by grouping code by what it does rather than when it executes, providing a synergistically value-adding, mutually-beneficial strategic partnership between the developer and... and... well, whatever’s left. (A more useful workflow anyway. I’ll leave the marketing talk to the marketers.)
Why did you write that nonsense?
A few proposals have been put forward about such things as this, but as usual analysts have been unable to agree on the issue.
The simple answer is that we software developers have a quirky sense of humour. How else could you explain things like the recursive acronyms that all developers so love? At times it can get dull, just writing a program which does what it’s meant to do and that’s all, and so developers make time to put in what are commonly known as “easter eggs”: hidden functionality which they generally find amusing and which break the monotony of writing good software.
In particular here the point is writing documentation. Writing this documentation for the PortableApps.com Launcher is taking far longer than the actual writing of the code did in the first place (orders of magnitude longer). And so at times I decide to put strange things in for the fun of it.
It’s just one of those illogicalities of software developers.
Here is a list of the hooks which can be executed:
If you ever need to disable a segment or hook, you can do so. In general though if you can possibly avoid doing it you should; you can very easily break the PortableApps.com Launcher by disabling certain things. See Writing a custom segment for details.
Here is the current list of segments included in the PortableApps.com Launcher:
Enter search terms or a module, class or function name.