JSDuck: Generated code documentation!
See CODING.md for how to run it.
Mistakes fixed:
* Warning: Unknown type function
-> Function
* Warning: Unknown type DOMElement
-> HTMLElement
* Warning: Unknown type DOM Node
-> HTMLElement
* Warning: Unknown type Integer
-> Mixed
* Warning: Unknown type Command
-> ve.Command
* Warning: Unknown type any
-> number
* Warning: Unknown type ve.Transaction
-> ve.dm.Transaction
* Warning: Unknown type ve.dm.AnnotationSet
-> ve.AnnotationSet
* Warning: Unknown type false
-> boolean
* Warning: Unknown type ve.dm.AlienNode
ve.dm doesn't have a generic AlienNode like ve.ce
-> Unknown type ve.dm.AlienInlineNode|ve.dm.AlienBlockNode
* Warning: Unknown type ve.ve.Surface
-> ve.ce.Surface
* ve.example.lookupNode:
-> Last @param should be @return
* ve.dm.Transaction.prototype.pushReplace:
-> @param {Array] should be @param {Array}
* Warning: ve.BranchNode.js:27: {@link ve.Node#hasChildren} links to non-existing member
-> (removed)
* Warning: ve.LeafNode.js:21: {@link ve.Node#hasChildren} links to non-existing member
-> (removed)
Differences fixed:
* Variadic arguments are like @param {Type...} [name]
instead of @param {Type} [name...]
* Convert all file headers from /** to /*! because JSDuck tries
to parse all /** blocks and fails to parse with all sorts of
errors for "Global property", "Unnamed property", and
"Duplicate property".
Find: \/\*\*([^@]+)(@copyright)
Replace: /*!$1$2
* Indented blocks are considered code examples.
A few methods had documentation with numbered lists that were
indented, which have now been updated to not be intended.
* The free-form text descriptions are parsed with Markdown,
which requires lists to be separated from paragraphs by an
empty line.
And we should use `backticks` instead of {braces} for inline
code in text paragraphs.
* Doc blocks for classes and their constructor have to be
in the correct order (@constructor, @param, @return must be
before @class, @abstract, @extends etc.)
* `@extends Class` must not have Class {wrapped}
* @throws must start with a {Type}
* @example means something else. It is used for an inline demo
iframe, not code block. For that simply indent with spaces.
* @member means something else.
Non-function properties are marked with @property, not @member.
* To create a link to a class or member, in most cases the name
is enough to create a link. E.g. Foo, Foo.bar, Foo.bar#quux,
where a hash stands for "instance member", so Foo.bar#quux,
links to Foo.bar.prototype.quux (the is not supported, as
"prototype" is considered an implementation detail, it only
indexes class name and method name).
If the magic linker doesn't work for some case, the
verbose syntax is {@link #target label}.
* @property can't have sub-properties (nested @param and @return
values are supported, only @static @property can't be nested).
We only have one case of this, which can be worked around by
moving those in a new virtual class. The code is unaltered
(only moved down so that it isn't with the scope of the main
@class block). ve.dm.TransactionProcessor.processors.
New:
* @mixins: Classes mixed into the current class.
* @event: Events that can be emitted by a class. These are also
inherited by subclasses. (+ @param, @return and @preventable).
So ve.Node#event-attach is inherited to ve.dm.BreakNode,
just like @method is.
* @singleton: Plain objects such as ve, ve.dm, ve.ce were missing
documentation causing a tree error. Documented those as a
JSDuck singleton, which they but just weren't documented yet.
NB: Members of @singleton don't need @static (if present,
triggers a compiler warning).
* @chainable: Shorthand for "@return this". We were using
"@return {classname}" which is ambiguous (returns the same
instance or another instance?), @chainable is specifically
for "@return this". Creates proper labels in the generated
HTML pages.
Removed:
* @mixin: (not to be confused with @mixins). Not supported by
JSDuck. Every class is standalone anyway. Where needed marked
them @class + @abstract instead.
Change-Id: I6a7c9e8ee8f995731bc205d666167874eb2ebe23
2013-01-04 08:54:17 +00:00
|
|
|
/*!
|
2013-01-15 23:38:49 +00:00
|
|
|
* VisualEditor UserInterface Context styles.
|
2012-07-19 21:25:16 +00:00
|
|
|
*
|
2013-02-19 23:37:34 +00:00
|
|
|
* @copyright 2011-2013 VisualEditor Team and others; see AUTHORS.txt
|
2012-07-19 00:11:26 +00:00
|
|
|
* @license The MIT License (MIT); see LICENSE.txt
|
|
|
|
*/
|
|
|
|
|
The Great ve.ui.Surface refactor of 2013
Prologue:
Farewell ve.Editor my good chap… Oh, hey there HTML frames - I didn't
see you there! In a world where iframes are outlaws, and symbols like
document and window are global, there were more than a few assumptions
about which document or window was being used. But fear not - for this
commit (probably) tracks them all down, leaving a trail of
iframe-compatible awesomeness in its wake. With the great ve.ui.Surface
now able to be used inside of iframes, let the reference editing
commence. But there, lurking in the darkness is a DM issue so fierce it
may take Roan and/or Ed up to 3 whole hours to sort it out.
Note to Roan and/or Ed:
Editing references seems to work fine, but when saving the page there
are "no changes" which is a reasonable indication to the contrary.
Objectives:
* Make it possible to have multiple surfaces be instantiated, get along
nicely, and be embedded inside of iframes if needed.
* Make reference content editable within a dialog
Approach:
* Move what's left of ve.Editor to ve.ui.Surface and essentially
obliterate all use of it
* Make even more stuff inherit from ve.Element (long live this.$$)
* Use the correct document or window anywhere it was being assumed to be
the top level one
* Resolve stacking order issues by removing the excessive use of z-index
and introducing global and local overlay elements for each editor
* Add a surface to the reference dialog, load up the reference contents
and save them back on apply
* Actually destroy what we create in ce and ui surfaces
* Add recursive frame offset calculation method to ve.Element
* Moved ve.ce.Surface's getSelectionRect method to the prototype
Bonus:
* Move ve.ce.DocumentNode.css contents to ve.ce.Node.css (not sure why it
was separate in the first place, but I'm likely the one to blame)
* Fix blatant lies in documentation
* Whitespace cleanup here and there
* Get rid of ve.ui.Window overlays - not used or needed
Change-Id: Iede83e7d24f7cb249b6ba3dc45d770445b862e08
2013-05-20 22:45:50 +00:00
|
|
|
.ve-ui-context,
|
|
|
|
.ve-ui-context-inspectors,
|
|
|
|
.ve-ui-context-menu {
|
2011-11-30 20:45:24 +00:00
|
|
|
position: absolute;
|
2011-12-01 22:43:50 +00:00
|
|
|
}
|
2011-12-02 00:30:50 +00:00
|
|
|
|
2013-05-14 23:45:42 +00:00
|
|
|
.ve-ui-context-menu .ve-ui-toolbar-bar {
|
2011-12-02 00:30:50 +00:00
|
|
|
white-space: nowrap;
|
2013-05-14 23:45:42 +00:00
|
|
|
border: none;
|
|
|
|
background: none;
|
2011-12-02 00:30:50 +00:00
|
|
|
}
|
2011-12-07 19:16:40 +00:00
|
|
|
|
2013-05-14 23:45:42 +00:00
|
|
|
.ve-ui-context-menu .ve-ui-toolbar-group {
|
2012-10-24 22:20:41 +00:00
|
|
|
border: none;
|
2013-07-09 22:59:24 +00:00
|
|
|
margin: 0;
|
2012-10-24 22:20:41 +00:00
|
|
|
}
|
|
|
|
|
2013-05-14 23:45:42 +00:00
|
|
|
.ve-ui-context-menu .ve-ui-buttonTool,
|
|
|
|
.ve-ui-context-menu .ve-ui-buttonTool:hover {
|
2012-10-24 22:20:41 +00:00
|
|
|
border: none;
|
|
|
|
}
|
|
|
|
|
2013-05-14 23:45:42 +00:00
|
|
|
.ve-ui-context-menu .ve-ui-buttonTool:active,
|
|
|
|
.ve-ui-context-menu .ve-ui-buttonTool-active {
|
2012-10-24 22:20:41 +00:00
|
|
|
background-image: none;
|
|
|
|
}
|
2013-05-15 23:31:02 +00:00
|
|
|
|
|
|
|
.ve-ui-context-embed .ve-ui-popupWidget-callout {
|
|
|
|
display: none;
|
|
|
|
}
|
|
|
|
|
|
|
|
.ve-ui-context-embed .ve-ui-popupWidget-body {
|
|
|
|
margin-top: 0.25em;
|
2013-07-09 22:59:24 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/* @noflip */
|
|
|
|
.ltr .ve-ui-context-embed .ve-ui-popupWidget-body {
|
|
|
|
margin-left: -0.75em;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* @noflip */
|
|
|
|
.rtl .ve-ui-context-embed .ve-ui-popupWidget-body {
|
|
|
|
margin-left: 0.75em;
|
2013-05-15 23:31:02 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
.ve-ui-context-embed .ve-ui-context-menu {
|
|
|
|
right: 0;
|
|
|
|
}
|
2013-07-09 22:59:24 +00:00
|
|
|
|
|
|
|
/* HACK: Compensate for ve-ui-frame-content setting the font size to 0.8em */
|
|
|
|
.ve-ui-frame-content .ve-ui-context {
|
|
|
|
font-size: 1.25em;
|
|
|
|
}
|