germax Messages: 20 Registered: March 2017 Location: germany
Promising Member
Thanks for the Welcome!
I wouldn't say I solved it (I just litterally stumbled upon a premade solution)
In most examples and tutorials the Code is stripped down to an absolute minimum for good reason;
the problem with that is, when it comes to a 'better' explanation it lacks detail.
Bazaar is great, if "by accident" you run across the correct package.
I mean EyeCare is just a perfect example.. HOW in the world should I know to look at that example when looking for a trayicon issue I have?
that question came up before (more or less) in the forum with no solution provided really.
And looking at all examples tutorials and bazaar entries is quite time consuming if one only needs a very short order of operation.
I know it's tedious and most of all boring as hell to create examples
and even worse to document the code.
And you all have my sympathy;
but that really needs to be improved IMHO.
So I'd like to suggest something to help "find" and maybe even reduce need for documentation
Here's my proposal:
How about all packages in the selector get another column to list all Ctrls used (like SQLCtrl, EditString, TrayIcon... etc).
that should be easy to do programmatically and wouldn't need any human interaction when adding the package.
The manual description lacks on some Bazaar entries and is not very telling on many other packages either...
that way next one looking for a TrayIcon example could filter the packagelist (example, bazaar, tutorials etc) for all that do contain a TrayIcon (or an SQLCtrl or what have you...)
Doesn't even have to be a visible column, just a suggestionbox on the package picker with all controls listed and just filtering the package list
Members
Pages
Help
Register
Login
Home
