Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Path is now transformable. #9

Open
wants to merge 12 commits into
base: master
Choose a base branch
from
Open

Path is now transformable. #9

wants to merge 12 commits into from

Conversation

qhwa
Copy link

@qhwa qhwa commented Mar 19, 2014

Hi @awebneck ,
I've made paths, sub paths and directions able to be transformed now.

For example

# for path
path = Parser.parse %Q{C211.003,239.997,253.003,197.997,304.003,197.997}
path.scale( 0.5, -0.5 )
path.translate( 0, 100 )
path.to_command
#=> "C105.5015-19.9985 126.5015 1.0015 152.0015 1.0015"

More examples can be found in spec/transformable_spec.rb .

Some directions are considered "not fully transformable". e.g. HorizontalTo directions are not directly rotatable. An error will be raised if they are being rotated or skewed.

So two methods , to_transformable_commands! and fully_transformable? are added to paths and sub_paths, to help them get transformed.

However, this is transparent to users. Users only need to call transform , scale or other methods. Savage turns paths fully transformable before applying transforms.

Could you take a review at this?

@qhwa
Copy link
Author

qhwa commented Mar 19, 2014

Sorry for the calculating mistakes.

@qhwa
Copy link
Author

qhwa commented May 21, 2014

I've created another gem savage-transform

@mrmeszaros
Copy link

@qhwa @awebneck is this project dead?

@awebneck
Copy link
Owner

@mrmeszaros pretty much, yeah - haven't updated the lib in ages, don't have any plans to do in the future.

@mrmeszaros
Copy link

mrmeszaros commented Dec 27, 2017

@awebneck I have no experience in doing releases to rubygems.org - so if you could add some starting momentum (eg. a README.md section on the build/release process), I would gladly take the responsibility of maintaining the project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants