ViewPort in GWT
22 views
Skip to first unread message
Peter
Jan 12, 2012, 6:19:22 PM1/12/12
to raphaelgwt
Hello,
I am looking at sources of RaphaelGWT and can't find something like
the ViewBox of the canvas ( see http://raphaeljs.com/reference.html#Paper.setViewBox
). Does anybody know if this is supported in RaphaelGWT ?
Please provide examples if possible.
Thanx.
I am looking at sources of RaphaelGWT and can't find something like
the ViewBox of the canvas ( see http://raphaeljs.com/reference.html#Paper.setViewBox
). Does anybody know if this is supported in RaphaelGWT ?
Please provide examples if possible.
Thanx.
Geoff Speicher
Jan 12, 2012, 8:56:41 PM1/12/12
to rapha...@googlegroups.com
Keep in mind that RaphaelGWT was built on top of Raphael 1.x, so there are features in the current Raphael (2.x) release documentation that are not yet supported by RaphaelGWT. I have a feeling that setViewBox may be one of them.
The Raphael project has been historically sparse with documentation (RaphaelGWT even more so, admittedly), so I don't know of any way to determine which features are new in 2.0 without painstakingly comparing the new API to the old one. Maybe Dmitri released a series of tweets and/or discussions with some details, but I have the impression that it was not documented in such formal terms and that the API has simply undergone "organic" improvement without regard for backward compatibility. That's not meant as a criticism, just as an observation of reality.
To complicate the issue for RaphaelGWT users, the raphaeljs.com no longer hosts 1.x documentation. I am presently at somewhat of a loss as to the best way to deal with this for users of RaphaelGWT. Maybe we could link to the 1.x docs in the Wayback machine, or maybe we could host the old docs ourselves with permission.
I am also at a loss as to whether there an upgrade path to 2.x can achieved while maintaining backward compatibility for RaphaelGWT users. We may be able to simply drop in the new Javascript library and start adding methods; or we may have to start over. I imagine that any programmer who has sufficient experience with the pure Javascript library could provide some input, but then my guess is that most people who fit that description may not be interested in RaphaelGWT. Some people have expressed their desire and/or intentions to support Raphael 2.x in RaphaelGWT, and I am definitely open to any contributions but I recognize that time is a scare resource for everyone.
Geoff
The Raphael project has been historically sparse with documentation (RaphaelGWT even more so, admittedly), so I don't know of any way to determine which features are new in 2.0 without painstakingly comparing the new API to the old one. Maybe Dmitri released a series of tweets and/or discussions with some details, but I have the impression that it was not documented in such formal terms and that the API has simply undergone "organic" improvement without regard for backward compatibility. That's not meant as a criticism, just as an observation of reality.
To complicate the issue for RaphaelGWT users, the raphaeljs.com no longer hosts 1.x documentation. I am presently at somewhat of a loss as to the best way to deal with this for users of RaphaelGWT. Maybe we could link to the 1.x docs in the Wayback machine, or maybe we could host the old docs ourselves with permission.
I am also at a loss as to whether there an upgrade path to 2.x can achieved while maintaining backward compatibility for RaphaelGWT users. We may be able to simply drop in the new Javascript library and start adding methods; or we may have to start over. I imagine that any programmer who has sufficient experience with the pure Javascript library could provide some input, but then my guess is that most people who fit that description may not be interested in RaphaelGWT. Some people have expressed their desire and/or intentions to support Raphael 2.x in RaphaelGWT, and I am definitely open to any contributions but I recognize that time is a scare resource for everyone.
Geoff
Reply all
Reply to author
Forward
0 new messages