Hi,
On 01.05.2017 14:45, Wayne Stambaugh wrote:
> This is not entirely accurate. All new features must be implemented in
> GAL at a minimum. Implementing the same feature in the legacy canvas is
> optional. The only requirement is that any objects created in the GAL
> canvas must be properly r
This is not entirely accurate. All new features must be implemented in
GAL at a minimum. Implementing the same feature in the legacy canvas is
optional. The only requirement is that any objects created in the GAL
canvas must be properly rendered in the legacy canvas even if they
cannot be edited
It's been established that new features have to work with GAL, but they
don't need to work with legacy. What's not allowed yet is to BREAK legacy
by implementing a new GAL-only feature.
On Sun, Apr 30, 2017 at 9:43 PM, Simon Richter
wrote:
> Hi,
>
> what is the current outlook on the legacy canv
Hi,
what is the current outlook on the legacy canvas past v5?
Specifically, I have a feature branch that targets v6 because it
certainly won't be in time for v5. Does it make sense to invest effort
here to get it working with the legacy canvas?
Simon
signature.asc
Description: OpenPGP digi
4 matches
Mail list logo