search

mdgriffith / atom-inline-messenger

Inline Messaging in the Atom Editor
MIT License
14 stars 2 forks source link

Selectable messages #2

Open steelbrain opened 9 years ago

steelbrain commented 9 years ago

Continuing from https://github.com/atom-community/linter/issues/633

steelbrain commented 9 years ago

Also merging https://github.com/atom-community/linter/issues/780 into this

mdgriffith commented 9 years ago

780 looks like it deals with selecting stuff in the panel. The inline messenger just deals with the highlights and the bubbles.

steelbrain commented 9 years ago

The more I think about it, the more I think it's a great idea to split the bottom panel and all the views into separate packages.

lierdakil commented 9 years ago

One thing with splitting stuff into separate packages is that Atom doesn't really support inter-package dependencies, so it would be up to end-user to install everything correctly, or some black magic in package initialization. Neither is perfect.

steelbrain commented 9 years ago

There's open PRs to both apm and atom to allow packages to depend on other packages, I think that'll solve our problem, but we'll have to wait for it.

On 31/07/2015, Nikolay Yakimov notifications@github.com wrote:

One thing with splitting stuff into separate packages is that Atom doesn't really support inter-package dependencies, so it would be up to end-user to install everything correctly, or some black magic in package initialization. Neither is perfect.

Reply to this email directly or view it on GitHub: https://github.com/mdgriffith/atom-inline-messenger/issues/2#issuecomment-126652832

lierdakil commented 9 years ago

If you mean package sets, then it's all good, but migration could be a nightmare, since existing users won't have those sets installed. Don't get me wrong, I'm all for modularity in packages (just look at ide-haskell stack :laughing:), but that's something to be super-aware of.