Why not become a lifetime supporting member of the site with a one-time donation of any amount? Your donation entitles you to a ton of additional benefits, including access to exclusive discounts and downloads, the ability to enter monthly free software drawings, and a single non-expiring license key for all of our programs.

You must sign up here before you can post and access some areas of the site. Registration is totally free and confidential.

As some of you may know, I wrote a text expander / replacer for NANY 2011. It was a bugger to write, and it seemed to polarise opinions from certain parties but it achieved its goal. Certainly I use it literally the whole time so in that respect I guess it was worth the effort, and based on feedback from a fair number people, seems to be a reasonable example of this type of app.

But! Development has stalled - I do have a list of features I'd still like to implement, however at the moment I certainly don't have the time. I think it deserves some more attention, and has plenty of potential if it were actively developed further.

The project is written in Delphi and I would open all sources except the keyboard hook which will remain available only as a dll.

What do you reckon, folks? Anyone up for wading in there?

And if so, what sort of license model would work for this? I don't want some clod lifting the source code, re-badging and selling it on.

I'm not sure what your goals are, but it seems to me that the GPL is the right way to go for what you've described.

Since you still retain copyright, you can do whatever you want, but with a GPL license for everyone else, nobody can legitimately lift it and repackage it without passing on those same rights from the GPL.

I don't program in Delphi (hated Pascal in university), but I would probably be interested in looking at it simply for interest and to learn a bit.

Is there an existing community that will pick up development? From what I've read, you will simply spend the time stimulating the community around your project instead of developing otherwise.Just open sourcing a project doesn't make it active.

What about giving yourself an incentive to develop it by making it a commercial product?

Is there an existing community that will pick up development? From what I've read, you will simply spend the time stimulating the community around your project instead of developing otherwise.Just open sourcing a project doesn't make it active.

What about giving yourself an incentive to develop it by making it a commercial product?

This. Or actively solicit help from other parties before you attempt to open source it.

Every time I restart my PC, it resets the colors used for the popup text tips - and it resets them to black text, black background! For both selected and unselected. So if I forget to change it, I get little black boxes popping up as I type.

I've tried setting the values, exiting out of Auspex & re-running it, but the result is the same - black on black popups.

Not sure where it stores these settings, why it is forgetting them or why it is using default values that make the popups useless. I'm just hoping I can get away form having to reset the colors every time I reboot.

Logged

- Jimdoria ~@>@

There are two kinds of people in the world: Those who divide everybody into two kinds of people, and those who don't.

Every time I restart my PC, it resets the colors used for the popup text tips - and it resets them to black text, black background! For both selected and unselected. So if I forget to change it, I get little black boxes popping up as I type.

I've tried setting the values, exiting out of Auspex & re-running it, but the result is the same - black on black popups.

Not sure where it stores these settings, why it is forgetting them or why it is using default values that make the popups useless. I'm just hoping I can get away form having to reset the colors every time I reboot.

That'll be Auspex unable to save its colors to disk for some reason. Can you try 'run as administrator' to see if that solves the issue?

The default color combo should be black text on white, so it's very odd that you get black on black in any case. I'll change the defaults slightly and do a new release on the weekend.

I tried running it as administrator, making my changes, exiting and re-running. That didn't work.I tried Windows 7's Compatibility wizard, doing the same thing. Also didn't work.Black on black always comes up when I run the program.

Is this stored in the registry somewhere? Couldn't find an entry for it under HKCU/Software...

Logged

- Jimdoria ~@>@

There are two kinds of people in the world: Those who divide everybody into two kinds of people, and those who don't.

I love seeing this sort of thing. This is what makes DC so great (one of the things, anyway): someone has a slight problem with a months-old app, and lo and behold, the developer is still around, and willing to fix it!

And if so, what sort of license model would work for this? I don't want some clod lifting the source code, re-badging and selling it on.

Most open-source licenses don't really stop people from doing this - and even if they technically did, good luck enforcing it when you have a relatively small and unknown product. I think there's a lot of DC'ers that can remember a particular GPL ripoff happening here...

Seriously, why exactly would you want to open source Auspex? If it's for any reason other than to turn it over gratis "to all mankind" then don't do it.

I'm big on open source and the concepts and philosophy behind it. But I'm also a card carrying child of the 70s so my political and moral values reflect that - and, quite frankly, may not be as relevant to today's realities as they once were. Especially when it comes to computing and software.

One problem may also be it's written in Delphi. I don't know what sort of license goes with Delphi, but there may (or probably are) terms in Delphi's license that precludes you making it "open." As the FSF often reminds people, there's nothing in the GPL that overrides any other license terms you may be under as a developer. Which is why they try to keep the "tool chain" squarely within the realm of the GPL as much as possible - to avoid any issues down the road.

Best suggestion I could offer would be to find somebody who may be willing to take your project over, work out your own deal or license with them, and forget about open sourcing it.

And if you ultimately do decide to "go open" with it (and Delphi's license allows you to), make it a point to assign ownership of your code to the Free Software Foundation. At least if you want to have any hopes an open license will be enforceable on it. As f0dder pointed out, a software license is only as good as your ability to enforce it is. Without a champion in your corner you, as an individual, have little hope of doing that.