Current PHP7 status

[auroraeosrose]

• Pattern enums
• Pattern
• Gradient
• Linear
• Radial
• Solid
• Surface
• Raster
• Mesh
• Region
• Surface
• Matrix
• Status
• Versions
• Types

New features added

1. Matrices have their properties exposed and can be manipulated
2. Mesh and raster pattern support ( not yet complete)
3. Rectangles

Changes

1. Namespaced
2. License change
3. Has extension dep
4. Real enums

Odds and ends

• Mesh Tests
• Mesh Paths

[swen100]

Hi Elizabeth,

it has become a bit quiet here...
Have you found some time to work further? At the beginning you had so much energy, what went wrong?

Is all o.k with you? Are u fine?

Swen

[auroraeosrose]

I have had the fun of house remodeling, a hard drive crashing and taking my vms with it (ugh) and way too much stuff for work :( I'll try to get back on this

[swen100]

Hi Elizabeth,

i have cloned the project and began to port the code of the files which are still not compatible with PHP7 (surface, context, font,...). I have seen, what you have made and tried to adapt it, so that my changes are as compatible as possible with yours.
Please, can u tell me if you have some files for which you have already made something, so that i dont do the same things you have done already.

Recently surface.c and font_options.c got finished and it gives me no compile errors. But you, with your excellent C-knowledge, should take a look on it to find the things i have overseen.

I wil go on further. Please contact me if i should leave some files untouched, if you want to port them.

You can find my tree here: https://github.com/swen100/cairo/tree/php7

Swen

[swen100]

• Font
• FtFont
• ScaledFont
• Win32Font
• QuartzFont
• FontFace
• FontOptions
• Surface
• ImageSurface
• SubSurface
• PdfSurface
• SvgSurface
• PsSurface
• RecordingSurface
• Path
• Context

[swen100]

Hm, i filled up the method Cairo\Pattern\Surface::getSurface(), but it gives me a segfault and I don't know why...

Another question: should we change the status()-method-names (in Surface, FontFace, FontOptions, ScaledFont, ...) to getStatus() ?

[swen100]

ScaledFont ported, but all methods give me a segfauft :/ Seems to lie within the destructor...
Elizabeth where are you?
I need your help!

[auroraeosrose]

hah, let me take a look :)
the biggest issue is teh way you have to emalloc and efree any stored zvals
it makes it a little more complex when you're dealing with stuff

[swen100]

Hi Elizabeth,

i am back from a short vacation. Did you find the cause of the segfaults?

Swen

I think, i solved it on my own. Seems to work fine. Hopefully...

[swen100]

Ok, I solved the last (known) segfaults. Ready to be fully tested now.

Swen

[auroraeosrose]

aewsome! thank you

[swen100]

please keep in mind that I changed some method-names.

The difference between "source", "sourceSurface" and "target" was not clear in my opinion.
So I changed the names of the following methods to make it clear which type of argument the method expects (or returns):

Cairo/Context::setSourceSurface() --> setSurface( Cairo/Surface )
Cairo/Context::setSource() --> setPattern( Cairo/Pattern )
Cairo/Context::getTarget() --> getSurface()
Cairo/Context::getGroupTarget() --> getGroupSurface()
Cairo/Context::getSource() --> getPattern()

Additionally these method-names were changed also:
Cairo/Context::clipExtents() --> getClipExtents()
Cairo/Context::fillExtents() --> getFillExtents()
Cairo/Context::pathExtents() --> getPathExtents()
Cairo/Context::fontExtents() --> getFontExtents()
Cairo/Context::textExtents() --> getTextExtents()

Cairo/ScaledFont::textExtents() --> getTextExtents()
Cairo/ScaledFont::glyphExtents() --> getGlyphExtents()

status()-method-names in Surface, FontFace, FontOptions, ScaledFont, ... to getStatus()

[auroraeosrose]

sounds like a good api adjustment - most of the naming was straight from the C methods and used to try to "sync up" with the dual api - but without the dual api a lot of the naming doesn't make sense

[auroraeosrose]

any chance you can start doing some pull requests with parts of this? it's very large as is right now but I'd like to start integrating the new code

[swen100]

Sure :)
Here it comes: #23