Nathan Sobo
670f3e4946
Add WorkspaceElement
2014-09-25 11:41:09 -06:00
Kevin Sawicki
13a5bfd1dd
Set default path on both files and folders
2014-09-25 09:45:54 -07:00
Kevin Sawicki
9e0c4d1fb6
Only set default path when opening files
2014-09-25 09:35:25 -07:00
Kevin Sawicki
cabcf19297
🐧 Default to project path in open dialog
2014-09-25 09:33:17 -07:00
Kevin Sawicki
9aa7331e6e
Upgrade to tabs@0.53
2014-09-25 09:10:27 -07:00
Kevin Sawicki
3daf505f3e
Upgrade to settings-view@0.146
2014-09-24 16:03:05 -07:00
Nathan Sobo
ae488fc7fe
Update document edited status in workspace model
...
This also fixes a previous oversight where the status wasn’t updated
when switching between pane items with different modified status.
2014-09-24 17:00:25 -06:00
Paul Betts
cd92f882bf
Merge pull request #3447 from atom/squirrel-installer
...
Build a Squirrel installer as part of CI build
2014-09-24 15:50:30 -07:00
Kevin Sawicki
707ac0b043
Upgrade to metrics@0.36
2014-09-24 15:45:19 -07:00
Paul Betts
4a812707d8
Merge remote-tracking branch 'origin/master' into squirrel-installer
2014-09-24 15:31:52 -07:00
Nathan Sobo
28deb9dec5
Maintain document.title in the workspace model, not the view
2014-09-24 16:26:54 -06:00
Paul Betts
f2ef7beae6
Include all PAK files
2014-09-24 15:07:41 -07:00
Kevin Sawicki
c64a4dd70f
Upgrade to tree-view@0.127
2014-09-24 14:58:57 -07:00
Nathan Sobo
186335d619
Mock out document.title with Object.defineProperty
...
Previously the WorkspaceView::setTitle was mocked in specs to prevent
the title from changing. But I would like to move the title update logic
without breaking assertions, so now we can assert directly on
document.title.
2014-09-24 15:56:50 -06:00
Paul Betts
3ab0b16923
Add a loading GIF that will display during initial install
2014-09-24 14:51:25 -07:00
Paul Betts
fac72fbf10
Update to Squirrel 0.4.95
2014-09-24 14:51:24 -07:00
Nathan Sobo
1c58438124
Move PaneContainerView::confirmClose to the model layer
2014-09-24 15:46:01 -06:00
Nathan Sobo
3e0477ffcb
Move shell command installation to workspace model
2014-09-24 15:28:35 -06:00
Nathan Sobo
368ef59b85
Remove stray log
2014-09-24 15:28:34 -06:00
Nathan Sobo
465d2afd95
Remove the old root view properly
2014-09-24 15:28:34 -06:00
Nathan Sobo
32f0eb4f76
Don’t emit repeated attached events for the same PaneView
2014-09-24 15:28:34 -06:00
Nathan Sobo
60a551b308
Only dispose PaneElement subscriptions when pane is destroyed
...
Not when the element is detached, because it might be reattached.
2014-09-24 15:28:34 -06:00
Nathan Sobo
f76f7e17d3
Upgrade space-pen for simulated dom attachment bug fix
2014-09-24 15:28:34 -06:00
Nathan Sobo
da87f321e8
Add PaneAxisElement
2014-09-24 15:28:34 -06:00
Nathan Sobo
11ede2d436
Upgrade autosave to fix specs
2014-09-24 15:28:34 -06:00
Nathan Sobo
2cc6c9e4c0
💄
2014-09-24 15:28:34 -06:00
Nathan Sobo
887a7bcaf4
Restore $.fn.element property
...
We define element in certain space-pen views, but this makes it
available for all jQuery objects. Can’t remove it from the prototype.
2014-09-24 15:28:34 -06:00
Nathan Sobo
df37d77895
Remove Pane::getViewClass as we now use a view provider
2014-09-24 15:28:34 -06:00
Nathan Sobo
cf8dc29cc5
Use Pane::onDidAddItem instead of ::observeItems
...
The former includes the index at which the item was added and the latter
does not.
2014-09-24 15:28:33 -06:00
Nathan Sobo
de29ca6906
Keep existing PaneView SpacePen API working as before
...
We will eventually deprecate all access to views via
`atom.workspaceView`, which is the only way to get a reference to
instances of PaneView. Draining the swamp!
2014-09-24 15:28:33 -06:00
Nathan Sobo
4ba3162f3e
Handle pane commands on PaneElement via command registry
2014-09-24 15:28:33 -06:00
Nathan Sobo
2710c06313
WIP: First stab at custom element for panes
...
Still need to create a SpacePen shim for access via `atom.workspaceView`
property so we’re backward compatible with packages, but it basically
works.
2014-09-24 15:28:33 -06:00
Nathan Sobo
7d71eeedf4
Break command dispatch as soon as currentTarget is null
2014-09-24 15:28:02 -06:00
Nathan Sobo
6d55bab4c8
Fix CommandRegistry::get/restoreSnapshot
...
I didn’t realize that deepClone was not handling functions correctly.
I’ve implemented clone manually to the exact depth needed instead.
2014-09-24 15:26:38 -06:00
Nathan Sobo
d506ccbaad
Merge pull request #3611 from atom/ns-activation-commands
...
Activation commands
2014-09-24 15:06:52 -06:00
Kevin Sawicki
8275ddd882
Catch errors thrown watching config file
...
Closes #3617
2014-09-24 13:54:27 -07:00
Nathan Sobo
b7765d9416
Process commands invoked with jQuery trigger in CommandRegistry
...
Especially in specs, trigger has been used to invoke events. jQuery does
not invoke native listeners in this situation, so we use ::on to listen
for them instead. If we didn’t handle the event with a native capture
handler, we’ll still support invoking via trigger.
2014-09-24 14:34:29 -06:00
Nathan Sobo
47f8f7eb11
Switch specs to use activationCommands instead of activationEvents
...
The activationEvents are converted to the same format as
activationCommands, and that property will be deprecated.
2014-09-24 14:34:29 -06:00
Nathan Sobo
63181a17c8
Support activationCommands field in package.json
...
This field mandates selectors in its structure and closely matches the
API of `atom.commands.add`. It will supplant `activationEvents` moving
forward.
2014-09-24 14:34:28 -06:00
Nathan Sobo
c71457e9d4
Default selector to .workspace when subscribing to activation events
2014-09-24 14:34:28 -06:00
Nathan Sobo
7d31b17273
Use the CommandRegistry to register activation event listeners
...
Commands registered with the command registry will always be handled
first, so as long as we disable any listeners in the registry that were
already invoked for the current command, we don’t need to disable jQuery
methods before replaying the command after activating the package.
This commit adds the ability to call .disableInvokedListeners on the
event passed to the command listeners. This returns a function which
can be called to reenable them.
2014-09-24 14:34:28 -06:00
Nathan Sobo
066f6bf03c
Forward stop[Immediate]Propagation to original event in CommandRegistry
...
Previously, stopping propagation would work on the synthetic bubbling
phase of the command registry itself, but the original event would
continue to propagate which is counterintuitive.
2014-09-24 14:34:28 -06:00
Nathan Sobo
40f8b990d0
Handle dispatching non-existent commands
2014-09-24 14:34:28 -06:00
Nathan Sobo
a492596f7f
Allow atom.commands to participate in activationEvents
...
* Activation events can be handled via atom.commands
* Pre-existing listeners registered via atom.commands are disabled when
replaying events for the activated package.
2014-09-24 14:34:28 -06:00
Nathan Sobo
2df5957f9b
Restore commands after each spec
...
This commit adds the ability to get and restore snapshots of command
listeners. Whatever commands are installed before specs begin are
preserved, but commands added during specs are always cleared away.
2014-09-24 14:34:28 -06:00
Nathan Sobo
a7196ec906
Dispatch activation commands with native DOM apis in specs
2014-09-24 14:34:28 -06:00
Nathan Sobo
c094b7a0ef
Extract package-manager-specs from atom-specs
2014-09-24 14:34:28 -06:00
Nathan Sobo
09b5ac887a
Return whether a dispatched command matched a listener
2014-09-24 14:34:28 -06:00
Nathan Sobo
67ff8f4382
Don’t clear commands after specs
...
Commands are typically registered once at eval time. Clearing them
means that commands aren’t available except in the first spec.
2014-09-24 14:34:27 -06:00
Nathan Sobo
0c9fd46030
Add CommandRegistry::dispatch for tests
2014-09-24 14:34:27 -06:00
