amiga-news.de - SView5: Source code on sale

SView5: Source code on sale
Andreas Kleinert writes: "SView5 (once SuperView, then SViewII and up) has been around in the Amiga scene from 1993 on - with a migration to .NET and Linux being main focus from 2008 on. The Amiga version did not see any updates lately, i.e. the past 4-5 years.

Development actually did not pay off anymore starting from ca. 2004 on, for various reasons. However, even as a hobby I really do not have sufficient time anymore - being father of two little daughters hardly leaves any room for it for the next several years.

On the other hand, SView5 still may have some relatively unique features in that combination. Under Windows I'd say there's only a handful comparable tools in that area - but then a again many commercial offerings and all-in-all everything is either free or expected to be free.

After all, I'm considering to sell the source code to an interested party in order to see it further developed. However it won't be handed over for a nominal fee and also not for a student budget. Price would have to be subject to negotiations and perhaps required some commercial considerations to pay off for the buyer.

So I would be glad if any interested party would contact me on the matter. Any offer should somehow value the amount of man-years which went into its development and debugging.

Regarding the actual subject:

There's the last AmigaOS / MorphOS source code:
- SView5 as a tool (C source)
- SView5-Library with many sub-libraries (modules, C source) being used as a shared library
The most recent branch consisting of:
- SView5 as a tool (C++ source for .NET)
- SView5 toolkit consisting of platform-independent C++ classes which are structured similar to the previous C modules (also regarding the API) but have to be statically linked (some external code is used as DLL) - it works well under .NET but is completely endian-neutral and should also work on any Linux

It should be fairly easy on that basis to create a next-gen SView5-Library for AOS3/AOS4/MOS which internally builds up on the new C++ classes (but with externally compatible API) *or* backport the new classes' core to the old code scheme *or* use it for something entirely different.

Regarding kind of crowd-funding (bounty) and an OSS release I'd generally be open, but it would mean a few conditions to be discussed first. It might be more feasible to start with something more closed." (snx)

[News message: 29. Mar. 2014, 11:53] [Comments: 0]
[Send via e-mail] [Print version] [ASCII version]

< Next message

Prior message >