Ribbon-like control for Lazarus

[LuizAmérico]

Hi,

Nice component.

I can do the port but before start i'd like to ask spook if the code can published with a permissive license like MPL or LGPL modified (same as Lazarus/fpc)?

Currently it uses a custom license

[JD]

Hi,

Nice component.

I can do the port but before start i'd like to ask spook if the code can published with a permissive license like MPL or LGPL modified (same as Lazarus/fpc)?

Currently it uses a custom license

Great, let's roll.....   

[spook]

Hi,

Nice component.

I can do the port but before start i'd like to ask spook if the code can published with a permissive license like MPL or LGPL modified (same as Lazarus/fpc)?

Currently it uses a custom license

I think, that LGPL modified will do just fine, it's absolutly ok with me.

Best regards -- Spook.

[JD]

Hi,

Nice component.

I can do the port but before start i'd like to ask spook if the code can published with a permissive license like MPL or LGPL modified (same as Lazarus/fpc)?

Currently it uses a custom license

I think, that LGPL modified will do just fine, it's absolutly ok with me.

Best regards -- Spook.

That's very nice of you, Spook.

[jixian.yang]

Or, in our case, we didn't implement the Office UI, we create a new one, from scratch which "looks" like the Ribbon.
In my honest opinion, as it is already free to implement, without royalties, we shouldn't have any problem developing a component like the Ribbon.

Any lawyer here? ^^

The jury is supposed to make the final decision, no matter how smart the lawyer will be.

And even if it is legal, the Ribbon is not regarded as a modern enough interface.

[Mando]

what is , in your oppinion,  a modern enough interface?

[spook]

Check this out:

http://msdn.microsoft.com/en-us/office/aa973809

It seems, that not the ribbon idea itself, but the Office UI is licensed. Windows 7 provides builtin COM ribbon control, which can be used in applications and is not subject to Office UI licensing (at least according to the linked page).

My component's look was of course based on the Office 2007 UI. However it can be easily redesigned to look more like Windows 7's ribbon, what - I believe - will solve the issue.

And finally, we may simply ask Microsoft, if out initiative is subject to the Microsoft Office UI licensing. It would solve the issue, I believe

Best regards -- Spook.

[JD]

And even if it is legal, the Ribbon is not regarded as a modern enough interface.

I waiting for your examples of modern interfaces....

[JD]

And finally, we may simply ask Microsoft, if out initiative is subject to the Microsoft Office UI licensing. It would solve the issue, I believe

En fin! That should put the controversy to rest.

[LuizAmérico]

Hi Spook,

I started conversion and like to confirm some bugs (found with help of fpc compiler)

procedure T2DIntRect.Move(dx, dy: integer);
begin
  inc(left, dx);
  inc(right, dx);
  inc(top, dx);
  inc(bottom, dx);
end;

dy is not used here

should not be:
  inc(top, dy);
  inc(bottom, dy);

----

function T3DVector.Scale(dx, dy, dz: extended): T3DVector;
begin
  result.x:=self.x * dx;
  result.y:=self.y * dx;
  result.z:=self.z * dx;
end;

only dx is used. It's the intended behavior? If so, dy and dz can be removed from declaration

[spook]

A copy'n'paste error, indeed. Shall be dx, dx, dy, dy and dx, dy, dz, respectively.

Best regards -- Spook.

[LuizAmérico]

Thanks.

BTW: can you post the source code of the binary demo you provided?

[spook]

Certainly.

http://www.spook.freshsite.pl/Temporary/ToolbarDemo.zip

Best regards -- Spook.

[LuizAmérico]

Hi,

I'm stuck with units SpkXMLParser and SpkXMLTools that are not present. Any chance publishing them?

[spook]

Sure.

http://www.spook.freshsite.pl/Temporary/SpkXML.zip

I'd suggest however, that later the component shall be modified to use the standard XML libraries. Mine cover only a subset of XML standard and are no longer developed.

Best regards -- Spook.