Onboarding Atom users to Pulsar #63
Replies: 5 comments 6 replies
-
As for moving the config file, I think a smart way would be to give a couple options.
But beyond this, should we have these pop up as notifications? Additionally beyond that, if we do decide to use the |
Beta Was this translation helpful? Give feedback.
-
Also I posted this on Discord, since not everything talked about is relevant here, but thought I should probably copy/paste it here, just for easy reference later on: Also I just mentioned this on discussion #63, but what would we think about the following for the upcoming sunset. Use the
What do we think? |
Beta Was this translation helpful? Give feedback.
-
It was not my idea but I think it should be here: I have created a small tool that is able to convert cson to json5 and keeps comments. Since cson is missing specifications it might not always work. |
Beta Was this translation helpful? Give feedback.
-
As a current Atom user thinking about moving to a new editor, I would appreciate the "See how to do this yourself" option shown on the Pulsar-edit README. Perhaps that text could also be used to balance expectations about what packages will and will not work with Pulsar, i.e., what packages it will and will not be possible to migrate. |
Beta Was this translation helpful? Give feedback.
-
I'm a little late to the party.. disregarding the sunset notice until yesterday when Atom wouldn't even open on my Mac. |
Beta Was this translation helpful? Give feedback.
-
Onboarding Atom users to Pulsar
This is so we can discuss what might be needed in order to help onboard Atom users to Pulsar so that the change is as painless as possible, the last thing we need is to make it hard for Atom users to adopt Pulsar which might make them rethink the entire thing and go to another editor entirely.
We should be able to convert any config files, copy preferences, install packages etc. so that when Pulsar is opened it should be (as near as possible) functionally identical to their old Atom installation.
Once we agree on some/any steps we can look at creating a project to track the progress of this.
.atom
->.pulsar
.atom
dir to.pulsar
and/or allow a user to manually trigger the migration.init.coffee
->init.js
.cson
filescson
files (such askeymap.cson
) then we will need something similar to the above to convert those to the new format. Personally I see json5 as the strongest contender here so we may need something like the.coffee->.js
automatic conversion.Documentation
apm
->pulsar -p
)Beta Was this translation helpful? Give feedback.
All reactions