TOPIC:

Port of ver 5.0.3 on Solaris/OpenIndiana 64 finish

CodeTyphon Studio Power...
tomorrow Linux and FreeBSD ports




and big image

what are the ETA for 2.80?

Sir
ETA for ver 2.80, 5-6 days
if all lab tests are OK

sternas wrote: Sir
ETA for ver 2.80, 5-6 days
if all lab tests are OK

1. What about the glyph problem for some buttons as reported in this thread?

2. Can you tell which Cindy components will only work on Windows systems?

Thanks

Sir
Our opinion is that, these are small problems.

Please don't forget that
CodeTyphon Studio is a free project
and it's not a company product, we don't have customers...

We have friends with the same passion: Pascal Programming
we have friends with the same vision:
to create a Pascal Programming Platform (CT),
which will be the most powerful Programming Studio on this planet
And we also believe it's NOT a dream anymore...

With this philosophy, some errors will exist.
and we can work together to solve these issues.

Have fun...

Thank's by all

If I remenber well I use Pascal the first time with delphi 2
I try to help you sometime in the future

sternas wrote: Sir
Our opinion is that, these are small problems.

Please don't forget that
CodeTyphon Studio is a free project
and it's not a company product, we don't have customers...

I understand that. The questions were not meant as criticism. They were just questions

The cyAdvButton problem is not a small problem, if you want to use the cyAdvButton in a project. It just does not work. Again: no criticism, just an observation.

The question to be able to plan my projects: is that problem solved in release 2.80?

Which brought me to the next question: which packages or which components are not portable? In the current state, the cyAdvButton is not portable, because the WM_DRAWITEM message is not provided by the Linux implementations of Lazarus. If I want to produce a completely portable program, which components should I avoid?

Maybe, in the Lazarus' components directory, in the next release, you could add a file to describe that.

sternas wrote: With this philosophy, some errors will exist.
and we can work together to solve these issues.

I agree and I did: I already supported you guys by providing the missing skins for the Lava package.

It's just that the cyAdvButton problem is too complicated for me.

Regards ;-}
Dick

Cindy V5.05 released!

Big improvments (speed up using windows gdi) made in TcyBook component!

Cindy components V5.05
15/07/2012 - cyBook.pas - We can see now page behind on the turn page effect!
14/07/2012 - cyBook.pas - Small bugs fixed + improvments
14/07/2012 - cyBook.pas - Despite it is not coherent in real book, we can set page with odd (1,3,5 etc ...) numbers to CurrentLeftPage property
13/07/2012 - cyBook.pas - Added TTurnPageAnimation.DoubleBuffered: Boolean property
13/07/2012 - cyBook.pas - Replaced use of BitmapResize() that is too low by DrawCanvas()
12/07/2012 - cyBook.pas - Removed prFitMediumQuality and prStretchMediumQuality to TPageRender
12/07/2012 - cyBook.pas - Modified BeforePreparePage event in order to able custom page rendering or/and use external page resizing engine.
12/07/2012 - cyBook.pas - Added OnLeftPageClick and OnRightPageClick events
12/07/2012 - cyProgressionPanel.pas - Added property State to public declaration
12/07/2012 - cyAdvProgressionPanel.pas - Small bug fixed on .Open procedure (avoid error if we call several times open()
12/07/2012 - cyAdvProgressionPanel.pas - Added property State to public declaration
11/07/2012 - cyBook.pas - Some optimization and added read/write property access to TBookPageView (for exemple TBookPageView.Page: TBitmap)
11/07/2012 - cyBook.pas - Turn page with mouse if page dragged and not clicked
11/07/2012 - cyBook.pas - Added DblClick event
11/07/2012 - cyBook.pas - Added boFitSmallImages and boStretchSmallImages to Options

Regards,
Mauricio

Thanks Sir
ver 5.05 port finish
STRETCH_HALFTONE not exist to LCL, I use HALFTONE

I think now cybook is OK

I have changed to HALFTONE myself after checking that quality is the same.

"I think now cybook is OK "
You bet!

Regards,
Mauricio

There's a couple of bugs in cyAdvSpeedButton.pas. The bugs are all of the same nature: if a test is made against the State of the TcyAdvSpeedButton the state "bsHot" is always forgotten, resulting in an exception as soon as the cursor hovers over such a button.
The bugs can be fixed as follows:

Lines 408-409: case FState of bsUp {Add this:}, bsHot: {this one is less important}
Lines 493-494: case aState of bsUp {Add this:}, bsHot:
Lines 578-579: case aState of bsUp {Add this:}, bsHot:

Especially the last two generate an exception because the RenderProp, resp. PaintButton are not assigned!
This bug was already reported in #2094

The same bug would surface in cyAdvButton in the DrawButton and DrawBackground procedures, but these procedures are never called, because of the other bug ( #1796 ) which has been declared minor ( #2242 ) (although the cyAdvButton is completely useless because of it).

Thanks Sir
we added your fixes
after 6 months you found the problem

Same problem:
cySpeedButton.pas
line 314
line 374
cyBitBtn.pas
line 208
line 347
cyGraphics.pas
line 861

---

updated source

Here's another one:

In cySpeedButton.pas the line 425 reads:

if (aState = bsUp) and Hot // Show hot state on flat buttons :

This should be:

if aState = bsHot // Show hot state on flat buttons :

In this way, a flat speedbutton shows its "hot" state by drawing a rect around it.

In contrast to what you think, Sternas, the problem #1796 is not solved. That one is very difficult to solve because of a missing message.
Try the sample code from C:\codetyphon\CodeOcean\Cindy\samples\cyAdvButton\cyAdvButtonDemo.lpi You will not see any glyphs on the buttons because of this bug. Neither DrawButton nor DrawBackground are ever called.

Thanks for the modified code

Kind regards ;-}
Dick

Thanks Sir
we will check and this

sternas wrote: Thanks Sir
we will check and this

As far as the problem with cyAdvButton is concerned: item #2203 shows what's wrong. It also shows that the cyAdvButton (and the cyBitBtn) can only work in a Windows environment and even then need some adjusting.

Cindy v5.10 released (Delphi version) !

Packages with 59 components for all delphi versions to build windows applications:
Gradient controls (buttons, speedbuttons, panels) with features like colored bevels, wallpaper, shadowText, caption orientation etc...
TcyCommunicate and TcyCommRoomConnector allows communication between applications running in same computer session.
TcySearchFiles and TcyCopyfiles allow respectively search and copy files with pause/resume/abort features.
TcyResizer allow move and resize components at run-time like delphi 2009 does.
Advanced DBX components for easy table data handling (tcyDbxTable or TcyDbxSimpleTable), schema modifications (TcyDbxUpdateSql), reconcile handling (TcyDBXReconcileError) and table creation.
TcyMathParser can parse matematical expressions.
TcyWebBrowser allows view/edit html documents.
TcyDbAdvGrid is a DBGrid with advanced feature rendering like gradient fixed cells, multiselection handling, embedded graphic and memo fields etc ...
TcyDocER extract document information (mail, phone, amounts etc ...) using OCR results from any source like Tesseract (open source) or Transym (comercial but cheap, fast, easy and powerful).
TcyBook allow to see images in a virtual book with turn page effect and pages handling.

Each component demo (code sources and executables) avaible here:
sourceforge.net/projects/tcyc...ts/files/Demo/

Download source code for all Delphi version:
sourceforge.net/projects/tcycomponents/

Thanks Sir
we working on this ...

sternas wrote: Thanks Sir
we working on this ...

It's fantastic how fast the Cindy components are expanded. However, I do not understand your endorsement for these components as long as some of them do not work properly with Lazarus. Shouldn't you strive for a Lazarus implementation with a nice set of good, tested components that will work in all environments where Lazarus works?

Maybe I do not understand your mission with the CodeTyphon project. If that's the case, can you enlighten us, so that we know what to expect, now and in the future?

Our Philosophy is Code-Typhon Sir
a "Black Hole" for pascal source

Pascal, must have a Big, full open source programming distribution,
the Α-Ω for any pascal project.
Any good open source library can be part of CT
(like new pl_DWScript library, lab CT 3.00)
So, this is our strategy: Code-Typhon

How far can go our vision ?
We don't know,
but we have a lot of fun...

sternas wrote: Our Philosophy is Code-Typhon Sir
a "Black Hole" for pascal source

Pascal, must have a Big, full open source programming distribution,
the Α-Ω for any pascal project.
Any good open source library can be part of CT
(like new pl_DWScript library, lab CT 3.00)
So, this is our strategy: Code-Typhon

How far can go our vision ?
We don't know,
but we have a lot of fun...

I'm glad someone's having fun, I sure ain't

My question is a valid one: for which operating systems do you want CT to be working? If not all, please specify in the release list which components are for which environment.

And if you publish components that do not work in any environment (like TCyAdvButton), you're absolutely correct in saying it's a "Black Hole", because such components could just as well not exist.

But it would not be a problem if these components were clearly marked as "Under Development". In the way things are now, each user of CT has to find this out for himself, after debugging and a lot of testing. That's not having fun at all