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

Atom 1.0 #3684

Closed
benogle opened this issue Sep 30, 2014 · 50 comments
Closed

Atom 1.0 #3684

benogle opened this issue Sep 30, 2014 · 50 comments
Labels

Comments

@benogle
Copy link
Contributor

@benogle benogle commented Sep 30, 2014

After the API freeze our goal is to implement and fix the very commonly requested features / bugs for a 1.0 release.

Tasks

Note these are not in any particular order.

Done

Open Issues

See https://github.com/atom/atom/labels/1.0-roadmap

@thomasjo
Copy link
Member

@thomasjo thomasjo commented Oct 1, 2014

Are these things you'd like to handle yourselves, or are you open to PRs?

@benogle
Copy link
Contributor Author

@benogle benogle commented Oct 1, 2014

Open to PRs for sure. What did you have in mind?

@thomasjo
Copy link
Member

@thomasjo thomasjo commented Oct 1, 2014

Thinking I might give #3683 a go, since it's a feature I really miss.

@benogle
Copy link
Contributor Author

@benogle benogle commented Oct 1, 2014

I do know @kevinsawicki was looking to implement that one soon. If you really want to do it, you might want to coordinate and bounce ideas off him.

@YemSalat
Copy link

@YemSalat YemSalat commented Oct 1, 2014

What does "Exception user experience" mean?

@kevinsawicki
Copy link
Member

@kevinsawicki kevinsawicki commented Oct 1, 2014

What does "Exception user experience" mean?

Trying to improve the options when uncaught errors occur, currently the dev tools just pop up.

We are looking to maybe make a custom view to show which packages are causing the exceptions and also provide quick commands to disable that package.

Also, the full stack traces only appear in the dev tools if the dev tools were already open when the error occurred, we are planning on capturing the full stack of the last N uncaught errors to make reporting easier since often the top line of the stack is not enough to try and reproduce issues.

@zhuochun
Copy link

@zhuochun zhuochun commented Oct 6, 2014

How about soft wraps problems #1894 #1783 ?

@lee-dohm
Copy link
Member

@lee-dohm lee-dohm commented Oct 10, 2014

Could I make a request to add to the roadmap? I'd like to nominate #2357 for inclusion in v1.0. This would be a very helpful tool for people to debug exactly which package is causing a problem. Right now, we have Safe Mode, which helps people to a point ... but then there's just a huge uphill slog trying to find exactly which package (or collection of packages) is causing the problem if it isn't Atom itself.

@benogle
Copy link
Contributor Author

@benogle benogle commented Oct 10, 2014

We definitely need a way to figure out which package is causing a problem

@kevinsawicki
Copy link
Member

@kevinsawicki kevinsawicki commented Oct 13, 2014

I'd like to nominate #2357 for inclusion in v1.0

👍 I think this fits with the Exception user experience bullet.

@lucasfeliciano
Copy link

@lucasfeliciano lucasfeliciano commented Oct 14, 2014

The version with this feature it is already released?

@benogle
Copy link
Contributor Author

@benogle benogle commented Oct 14, 2014

The version with this feature it is already released?

Which feature?

@lucasfeliciano
Copy link

@lucasfeliciano lucasfeliciano commented Oct 14, 2014

Ops, wrong topic, sorry about that.

I was referring to this feature: #3718

@thomasthorsen
Copy link

@thomasthorsen thomasthorsen commented Oct 24, 2014

Is Linux binary releases (deb/PPA, RPM, ...) on the table?

@kevinsawicki
Copy link
Member

@kevinsawicki kevinsawicki commented Oct 24, 2014

@thomasthorsen Yup, the next release will have an official RPM available from the releases page #3942

Also we are working on a PPA for Debian #2956

@Macsch15
Copy link

@Macsch15 Macsch15 commented Oct 24, 2014

I'm waiting for #3673 👍

@benogle
Copy link
Contributor Author

@benogle benogle commented Oct 24, 2014

@Macsch15 It's an ongoing process. There were some large speedups pushed in 138 and 139.

@karloluis
Copy link

@karloluis karloluis commented Oct 25, 2014

I'm really happy of how it's all coming together. I don't know where I might be of assistance but let me know or I'll figure it out eventually. I'll lurk the issues tab for a while longer for now.

@lee-dohm
Copy link
Member

@lee-dohm lee-dohm commented Oct 25, 2014

You're always welcome on Discuss, @karloluis. If you want ideas on how to help out, there is a recent topic about packages that people want to see:

https://discuss.atom.io/t/must-have-packages-that-dont-exist/12665

@karloluis
Copy link

@karloluis karloluis commented Oct 25, 2014

@lee-dohm This is awesome. I'll be sure to check it out.

@kevinsawicki
Copy link
Member

@kevinsawicki kevinsawicki commented Oct 27, 2014

I added #1806 to this list.

With the work in atom/node-pathwatcher#36 it should be straightforward to support it at the buffer level.

Then we can add tooling to the command palette, menu, or status bar to toggle it.

@kolgotko
Copy link

@kolgotko kolgotko commented Nov 1, 2014

Are there any plans for a working version of freebsd?

@kevinsawicki
Copy link
Member

@kevinsawicki kevinsawicki commented Nov 3, 2014

Are there any plans for a working version of freebsd?

@kolgotko Not currently, I'm not sure anyone on the Atom team currently uses or has any experience using FreeBSD.

But if pull requests were opened to address FreeBSD issues, they would gladly get merged.

@nathansobo
Copy link
Contributor

@nathansobo nathansobo commented Jan 5, 2015

@190n It means themes that blend in to their respective operating systems. We may remove that item from the 1.0 list.

@AbeEstrada
Copy link

@AbeEstrada AbeEstrada commented Jan 15, 2015

About "Per-project config settings" doesn't EditorConfig solves this problem?

@mark-hahn
Copy link
Contributor

@mark-hahn mark-hahn commented Jan 15, 2015

Many add-on packages are superseded by improvements to core.

On Wed, Jan 14, 2015 at 4:02 PM, Abe Estrada notifications@github.com
wrote:

About "Per-project config settings" doesn't EditorConfig
https://github.com/sindresorhus/atom-editorconfig solves this problem?


Reply to this email directly or view it on GitHub
#3684 (comment).

@190n
Copy link

@190n 190n commented Feb 18, 2015

What about automatic updates on Linux? I use Linux, and it's less than ideal to have to remember to check for updates and install them.

@steelbrain
Copy link
Contributor

@steelbrain steelbrain commented Feb 18, 2015

@190n You mean #2956 ? It's already on the roadmap

@190n
Copy link

@190n 190n commented Feb 18, 2015

Sorry, I didn't see that.

@jmm
Copy link

@jmm jmm commented Apr 14, 2015

Not sure what the difference is between the checkbox items in the first post and the issues tagged 1.0-roadmap, but I'd like to nominate all of the "Unable to watch path" issues (like #4849, #3628) to have a higher priority and be on the bugs list here.

@alexchandel
Copy link
Contributor

@alexchandel alexchandel commented Jun 13, 2015

Rather surprising that #4161 didn't make this list, given that crashes exist. Especially since 1.0 milestones are times for userbase expansion, and nothing says never again like losing 2 hours of work because something crashed and you didn't save, and your editor doesn't know what recovery or unsaved buffers are.

@mnquintana
Copy link
Member

@mnquintana mnquintana commented Jun 13, 2015

For anyone subscribing to this, this is not a complete list for what's planned for 1.0, just a high-level overview. Anything with the label 1.0-roadmap is currently still planned for 1.0 as far as I know - @alexchandel, the issue you linked to is one of them. In addition, that label is also a high-level overview of what's planned for 1.0, and many more issues maybe fixed / implemented yet in the next few weeks, if there's time. Also, 1.0 is not the be-all end-all release - it's not like the pace of development will slow down after 1.0. 1.0 just marks the beginning of the API that will be stable and supported until 2.0; the core team and maintainers will continue fixing bugs and implementing new features after 1.0 is released.

So, in conclusion, no one should be concerned if an issue they care about isn't on this list, because it in no way means that it's not going to happen eventually, or even soon.

@alexchandel
Copy link
Contributor

@alexchandel alexchandel commented Jun 16, 2015

@mnquintana Good to hear.

@robcalcroft
Copy link

@robcalcroft robcalcroft commented Jun 18, 2015

Is there a formal release schedule as of yet?

@kevinsawicki kevinsawicki mentioned this issue Jun 22, 2015
6 of 9 tasks complete
@stanier
Copy link

@stanier stanier commented Jun 26, 2015

#5166 is still relevant...

@kresogalic8
Copy link

@kresogalic8 kresogalic8 commented Mar 30, 2016

Hey guys, just want to say that atom is nice.

But using it with plugins is really hard. Can u actually work on optimization? Thanks

@martpie
Copy link

@martpie martpie commented Mar 30, 2016

That does not really mean something. "What" is really hard ? Performances ? Ease-of-use ? ...

@lock
Copy link

@lock lock bot commented Apr 10, 2018

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!

@lock lock bot locked and limited conversation to collaborators Apr 10, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
You can’t perform that action at this time.