new version 1.60 of our Freeware Project CodeTyphon.

[raulparraco]

At 19-Apr-2011 we release a new version 1.60 of our Freeware Project CodeTyphon.

http://www.pilotlogic.com/sitejoom/index.php?option=com_kunena&func=view&catid=10&id=141&Itemid=169

 -ADD pl_UIB
   -ADD pl_OpenWire
   -ADD pl_FortesReport
   -ADD pl_PowerPDF

   -Update pl_BGRAbitmap   (SVN 18-4-2011)
   -Update pl_ZenGL        (SVN 18-4-2011)
   -Update pl_GLScene      (SVN 17-4-2011)
   -Update pl_LNetComp     (SVN 17-4-2011)
   -Update pl_KambiEngine  (SVN 17-3-2011)
   -Update pl_LNetComp     (SVN 17-4-2011)  

   -Fix arm-linux Cross-Element compilation problem

NOTE:  Lazarus 0.9.31   Source from SVN 18-04-2011 Rev 30371
       FreePascal 2.5.1 Source from SVN 01-04-2011
 Rev 17212

CodeTyphon version 1.60 Status
 
•   Full Source Code for Lazarus IDE, FreePascal Compiler, Components Packages and sample projects.
•   Full Multi-Operating Systems Architecture.
o   Multi-Operating Systems Code Compiler.
o   Multi-Operating Systems RAD IDE.
o   Multi-Operating Systems RAD IDE Packages .
o   Multi-Operating Systems Debugger.
o   Multi-Operating Systems Installer, one zip file, with "Build from the source" action.
o   Multi-Operating Systems HTML Help System.
o   Multi-Operating Systems Code Samples and Projects.
•   Negative Cross-Compile Architecture.
o   Cross-Compile Code Compiler.
o   Cross-Compile RAD IDE.
o   Cross-Compile RAD IDE Packages.
o   Cross-Compile Debugger.
•   4 CPU-Operating Systems Host Layers  (Win32, Win64, Linux32, Linux64).
•   16 CPU-Operating Systems Target Layers.
•   Win64 Layer has Dual Personality (Win64 and Win32).
•   Win32 Layer is Cross-Build Center with Cross Elements for:
o   arm-Wince
o   arm-Linux
o   arm-Embedded  (freepascal only)
o   arm-gba            (freepascal only)
o   arm-nds            (freepascal only)
o   i386-Win32
o   i386-Linux
o   i386-FreeBSD
o   i386-Haiku         (freepascal only)
o   x86_64-Win64
o   x86_64-Linux
o   x86_64-FreeBSD
o   powerpc-Linux
o   powerpc64-Linux  (freepascal only)
o   sparc-Linux
o   sparc-Solaris      (freepascal only)
•   Lazarus Extent-IDE , more packages and more functionality.
•   CodeTyphon Control Center  with:
o   Building Session with OS batch files.
o   Installation Control Session.
o   Packagers Control Session.
o   Cross-Build Session.
o   Tools Session.
•   CodeOcean part  with samples for:
o   AGG  61 projects
o   DirectX  31 projects
o   OpenGL  15 projects
o   GLScene  75 projects
o   Physics 2D  2 projects
o   Physics 3D 5 projects
o   Shapes 2 project
o   VirtualTrees 3 projects
o   Extra Controls 9 LAB projects

[LazaruX]

I think its a nice idea to make an ALL in ONE redistribution of Lazarus, like it happens in linux distributions.
Will it be available on all platforms? And on all operating systems?

Still I don't think its legal to make an Open Source project Freeware, it seems like if tomorrow I take the Linux kernel, i add some modules then i redistribuite it through my website as freeware. But I could be wrong.

[avra]

Still I don't think its legal to make an Open Source project Freeware

I think that they made freeware only their contribution (CodeTyphon center, installer...), and that Laz/FPC and other open sourced projects remain with their original licence.

[Sternas Stefanos]

I think that they made freeware only their contribution (CodeTyphon center, installer...), and that Laz/FPC and other open sourced projects remain with their original licence.

Thanks Sir, this is true
have fun...

[JimBeam]

Sorry to be nitpicky: freeware means that you don't have to pay for it. Freeware says something about the price for the executable (or possibly source code).
Open Source may or may not mean you don't have to pay for it. Open Source says something about your access rights to the source code.

The term you might be looking for is public domain: e.g. anybody may do anything with the code (and e.g. give away or charge for the resulting executable).
(I haven't looked at CodeTyphon licenses though, so I might very well be wrong....)

Anyway, I'm glad somebody is doing the hard work of collecting and integrating a lot of scattered components...

[marcov]

The term you might be looking for is public domain: e.g. anybody may do anything with the code (and e.g. give away or charge for the resulting executable).

Afaik "public domain" is a dangerous term, because it differs in Common Law and more French oriented (Code Penal) law as used in most of continental Europe

In such law systems, only works which copyright has expired are in public domain, and the phrase to place them there is thus meaningless, making it not an ideal license.

A better solution is (3-clause) BSD license. It doesn't add much, and its wording doesn't depend on local law.

[Takeda]

to Mr. Sternas :

My Questions are so simple ; 

1. Is there any possibility for anybody that use CodeTyphon to build commercial products without buy CodeTyphon? (cause I think, it was based from Lazarus that shipped with LGPL-modified, that permitting to anybody build their own commercial product using Lazarus as software development tool) 

2. If I must to buy CodeTyphon, how much I must pay for it?

3. Is there any restriction for anybody to build OpenSource products using CodeTyphon? 

4. Is there any plan from CodeTyphon's Company to change the license someday into commercial product, which say to your user to buy the license of CodeTyphon to use it? 

5. If CodeTyphon's License changed, is there any possibility it will be applied directly to the previous product which already shipped with CodeTyphon's "freeware license"?


Thanks Before,

Matsuki, Takeda.

[Sternas Stefanos]

Sir
CodeTyphon is FREE (again free) Distribution.
Simple, we release our develop tool for free (again free),
with the hope that some people help us to make it better.  

You can do anything you want with it, except to sell CodeTyphon.
Money and CodeTyphon are two opposite things.

We want to stop this "only for money" from pascal programmers behavior...
This behavior "Hold" pascal from growing, for so many years.

So
1."use CodeTyphon to build commercial products without buy CodeTyphon?" YES
2."how much I must pay for it?" : NOTHING.
3."Is there any restriction": Only to have fun...
4."Is there any plan from CodeTyphon's Company to change the license someday into commercial product, which say to your user to buy the license of CodeTyphon to use it?": NEVER
5. "If CodeTyphon's License changed....": NOT POSSIBLE

I will put this and to PilotLogic.com CodeTyphon page

Now Sir, I think my answer is "very clear"

[Martin_fr]

1."use CodeTyphon to build commercial products without buy CodeTyphon?" YES
2."how much I must pay for it?" : NOTHING.
3."Is there any restriction": Only to have fun...
4."Is there any plan from CodeTyphon's Company to change the license someday into commercial product, which say to your user to buy the license of CodeTyphon to use it?": NEVER
5. "If CodeTyphon's License changed....": NOT POSSIBLE

That is all very good.

"Freeware" and "open source" are not a type of license. They specify certain attributes of a product.

Also to give other developers peace of mind, you should (for your own code) specify a license (such as GPL, LGPL (with linking exception)).

Besides, those licenses may also protect you, in certain cases.

As your software is a distribution of multiply products, it would be best to point out the individual licenses of the included products.
 

[Sternas Stefanos]

That is all very good.

"Freeware" and "open source" are not a type of license. They specify certain attributes of a product.

Also to give other developers peace of mind, you should (for your own code) specify a license (such as GPL, LGPL (with linking exception)).

Besides, those licenses may also protect you, in certain cases.

As your software is a distribution of multiply products, it would be best to point out the individual licenses of the included products.
 

I don't have the same opinion, Sir
"products" are only for commercial Software
We don't use this word.
We NOT want any protection, free source code to anyone...
Yes, a revolution...

[Martin_fr]

I don't have the same opinion, Sir
"products" are only for commercial Software
We don't use this word.

Well this is a simple misunderstanding. "product" as in anything that was produced. >> This message is a product of my thoughts and typing <<
But does not matter what term you choose to describe your code, the code of others, or anything else...

We NOT want any protection, free source code to anyone...

You do not want to be protected against being taken to court?
Afaik, most licenses have disclaimers that limit a users right to warranty and other claims. (To what ever extend is legally possible). This is to prevent people from asking you to pay, because a bug in your code, caused them a loss of revenue from their clients.

I may be wrong on this, but afaik those things are part of what is covered by such licenses.

If the license you choose has restrictions that you do not want to apply, you can always add an exception (such as done for the LCL, with the linking exception)

-------
Also in adding a license, you do not restrict your users, you actually help them.
Without a proper license, your users may have no legal security about using your code (this may heavily depend on where they live).
By adding a license, you provide legal security to the users of your code.

----
Further more you can give them a choice, by saying the code can be used under license a, b or c, at the users choice.

[Sternas Stefanos]

Sir
I speak only for CodeTyphon as Distribution
and only for our source code.

All CodeTyphon parts have their licenses.

I can't speak for lazarus or freepascal or another
CodeTyphon part...have their licenses.

And we select only "free software parts"


 

[Glenn]

I'm not an expert in law or licenses at all, but there are several areas around the CodeTyphon project I've found worrying.

First of all, as stated earlier in this thread, there is no clear license around the project and separate products included.
In fact, until one of the recent releases of CodeTyphon, has the GPL been violated in two components, TColorProgress and TGifAnim originally created by Wile64. The component names was renamed to TplColorProgress and TplGifAnim and had their GPL statement replaced with a PilotLogic copyright notice.
I doubt these two components are the only one which has been modified that way, but I may be wrong.

(I'm not 100% sure about this point, so don't quote me on that)
- In the license.htm, is the licenses stated as a EULA, which in my head doesn't comply with GPL/LGPL products at all.
However, it looks like parts of the EULA has been lend from "Installation Notes for CodeGear Delphi and C++Builder 2009" as the title of all 3 .htm files says.


The CodeTyphon project is a good idea, no doubt about it. But all this uncertainty about licenses and who has delivered code for the various components - and their own licenses, makes me think twice before I would use CodeTyphon again.
In fact, this is one of my main motivations behind the ideas I have shared in other threads here, and as a result switched back to vanilla lazarus

Just my two cents.

Best regards
Glenn

[avra]

If anything bad happens to CodeTyphon, my work is safe since I can always turn back to native Lazarus. Then I would have to manually setup cross compilers and install many components, but nothing would be lost.

[Sternas Stefanos]

I'm not an expert in law or licenses at all, but there are several areas around the CodeTyphon project I've found worrying.

First of all, as stated earlier in this thread, there is no clear license around the project and separate products included.
In fact, until one of the recent releases of CodeTyphon, has the GPL been violated in two components, TColorProgress and TGifAnim originally created by Wile64. The component names was renamed to TplColorProgress and TplGifAnim and had their GPL statement replaced with a PilotLogic copyright notice.
I doubt these two components are the only one which has been modified that way, but I may be wrong.

(I'm not 100% sure about this point, so don't quote me on that)
- In the license.htm, is the licenses stated as a EULA, which in my head doesn't comply with GPL/LGPL products at all.
However, it looks like parts of the EULA has been lend from "Installation Notes for CodeGear Delphi and C++Builder 2009" as the title of all 3 .htm files says.


The CodeTyphon project is a good idea, no doubt about it. But all this uncertainty about licenses and who has delivered code for the various components - and their own licenses, makes me think twice before I would use CodeTyphon again.
In fact, this is one of my main motivations behind the ideas I have shared in other threads here, and as a result switched back to vanilla lazarus

Sir
We remove these two small components,
(TColorProgress and TGifAnim) from CodeTyphon
and I will remove and any other NO FREE part from CodeTyphon if exists...
you must update your info...