Comments (4)
I’m especially sceptical of changing the extension internally in pcl(x) files, regardless of whether they are legacy or not. For bitmap projects this will only be a bit of an annoyance, but vector projects will get messed up by this when loaded in older versions (e.g. switching between stable and nightly), and our vector aficionado who suggested this change surely won’t take kindly to that. That aside, if we do go through with this let me suggest following the precedent set by pcls and call it something like pclp.
I generally agree with all of this. Changing the extension in the pclx file would not be backwards compatible and isn't worth breaking file compatibility for an aesthetic change in a place users shouldn't even be looking. I was going to suggest a pcl* name for the extension as well.
I don't see the making a new extension for the palette file as particularly important or useful in general, but I'm not opposed to the changes to importing/exporting as outlined here by @MrStevns. If it's for the interest of file management as suggested on the forum, it's trivial for users to adopt a file naming practice that makes it clear what the file is (ex.flowers.p2dpalette.xml
). There is some logic to making the change when looking at what we did for shortcuts though.
from pencil.
Although I concur that a special purpose extension is nicer, changing it now will cause something of a hassle for what is essentially a cosmetic change. I’m especially sceptical of changing the extension internally in pcl(x) files, regardless of whether they are legacy or not. For bitmap projects this will only be a bit of an annoyance, but vector projects will get messed up by this when loaded in older versions (e.g. switching between stable and nightly), and our vector aficionado who suggested this change surely won’t take kindly to that. That aside, if we do go through with this let me suggest following the precedent set by pcls and call it something like pclp.
from pencil.
You both make a excellent points regarding the internal project structure.
Depending on the workflow of our users and how much you value you put in file management, it could be considered a quality of life improvement, although cosmetic still.
The only way I see us being able to make it backward compatible, is to include both the old and new extension in the project, essentially keeping two copies of the project palette... I'm not saying we should do that though, I'm just mentioning it.
from pencil.
We could change only the file extension on exporting the palette without touching the filename in the pclx.
For backward compatibility, it should be fine if the newer versions of Pencil2D can consume both .xml
and .whatever-palette-ext
. The issue will be the forward compatibility as the older versions of Pencil2D won't be able to import the palette file with the new file extension.
Just want to discuss the possibility, I am personally neutral about this change.
from pencil.
Related Issues (20)
- Audio issues HOT 1
- After making a selection with the Select tool, auto-switch to Move tool HOT 2
- fix your curves for Christ sake HOT 1
- My Tools Dont Work (THERE'S MORE, THIS IS A BIG BUG!!!) HOT 1
- sound never plays in sync HOT 2
- Pen dabs are being added on top of each other HOT 3
- project becomes pixelated when i zoom in HOT 1
- Importing behavior for animations with different frame rates
- No escucho el sonido HOT 2
- DevOps | Removing macdeployqtfix HOT 1
- Line Tool Undo Painfully Broken HOT 2
- Update AppStream MetaInfo to meet new Flathub quality quidelines HOT 4
- Middle-Click or Right Click panning with the pen tablet breaks stuff. HOT 1
- wheel unzoom doesnt work properly HOT 3
- Crash when exporting movie HOT 2
- 0.7.0 Release Plan HOT 19
- Canvas not updating properly when view updates occur while some tools are active
- Assertion failure when selection is moved with arrows
- Assertion failure when redoing a selection transformation
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pencil.