PureBasic Forums - English

PB wrote:how many of you have colored your gadgets?

I never ever colour any gadgets.

I monked around with colors when the windows surface was new,
and then again when I got the Visual Studio (back in 99 or so),
and it always ended up with windows looking like chicken shit.

back then on '95 / '98 was NO advantage in coloring anything different from the User settings,
and on XP / Vista with all the skinning stuff it's worse.

so why waste time with making your apps window look like a lemon drop you cat slept on
than rather improving the functionallity of your app?
I even saw apps that had problems with differnt fontsize settings of Windows,
this also is a point to put work in to improve.
leave the colors what they are: Users' problems.

ts-soft wrote:

blueznl wrote: This may sound funny, but can someone explain to me the advantage of libraries over includes?

1 Libraries have it's own Global VariableScope, private Procedures.
2 Contexthelp with F1 and ToolTip in the IDE
3 No problems with "Includepath"
4 Can written in any language that support static libs
5 Reduce compiletime

greetings
Thomas

1 Okay... Namespaces or modules would fix that, but this one I do understand Smart renaming could fix this for a bit...

2. Yeah, context help would be nice. I'm now using CTRL+F1 with CodeCaddy for this reason, but integrated into the IDE would be better. It's however an IDE thing, I could imagine a solution where all 'source-libs' and associated help / docs would be placed in a specific folder so the IDE could handle it.

3. Ah Could again be fixed by using a dedicated folder.

4. Point taken but I was more thinking about libraries written in PureBasic itself. You're totally right when it is about other languages.

5. Okay... any idea how much this speed win would be in reality?

thefool wrote: @bluez:
1) not everything is written in PB
2) maybe they don't want to share the sources, which is understandable.

Well, as I rule I do not use stuff that may be broken with the next version of PureBasic... I'd be using a DLL with a wrapper, no problem, I just wouldn't want to screw up something when 4.3 arrives... 4.4... 4.5... etc.

freak wrote:Because i don't see many being denied for the "not crossplatform" reason, except maybe the registry commands.

Hi Freak,

registry command can be cross platform, if you accept that you don't really need a registry database to store stuff into.
I have seen cross platform registries implemented by using the file system itself for storage.
On the top level this 'registry' was just a directory within the app's data directory. All keys were subdirectories, with the final variable simply being a text file with content.
Depending on the platform in use, these keys were written to the file system or to the windows registry.
There's other uses for a file system based registry, as these can be stored on a netwok share and used by multiple clients.
Lastly, since PB offers cross platform database access, a somewhat slower file system based registry could easily be replaced by faster database storage.

> If you really want some of your favorite functions in a PB library then use
> Tailbite. There is already an immediate solution.

That's not what I mean, and neither is color. Color was just an example.
I can see that nobody here really grasps my concept, which is my fault
as I probably haven't explained it properly. Oh well. At least I tried.

One day my concept will probably happen and I'll quite happily link to
this thread and say: "See? I asked for this way back in 2008!"