Reuse the pinch-zoom for mobile implementation for this.
Conflicts:
loleaflet/src/layer/tile/CanvasTileLayer.js
loleaflet/src/map/Map.js
loleaflet/src/map/handler/Map.TouchGesture.js
Signed-off-by: Dennis Francis <dennis.francis@collabora.com>
Change-Id: Ic7c50708a3071f4661c996dd2aae7083feed64da
(cherry picked from commit 202fd1a3bfef22549e3402dcb7b6d9fad9b4f07d)
Conflicts:
loleaflet/src/layer/tile/TileLayer.js
Signed-off-by: Dennis Francis <dennis.francis@collabora.com>
Change-Id: Idb4685257ea03b09d4e77c9bf04d3009f8d60e2a
(cherry picked from commit bbd8955a4eb6234c520233d619a361f2937b09b2)
Conflicts:
loleaflet/src/layer/tile/TileLayer.js
Signed-off-by: Dennis Francis <dennis.francis@collabora.com>
Change-Id: Ia51699f8b5619c4169a45312ee0c3b826fac9d0e
(cherry picked from commit 1eaa46b1e93247652778293e5594bc109769364b)
We now have a very specific design for cell-area selections which
involves many paths. However we don't need the same styling for text
selections. Use a simple CPolygon based drawing for text-selections till
we come up with a better styling for them.
Conflicts:
loleaflet/src/layer/tile/GridLayer.js
loleaflet/src/layer/tile/TileLayer.js
Signed-off-by: Dennis Francis <dennis.francis@collabora.com>
Change-Id: Ieed0ff688e1333aa8d7c8ddd923933d49855c130
(cherry picked from commit a929a2a5d34a3f6438466e105a9cbff5e426272e)
* Autofillmaker should follow the grid (not go overboard as it is now)
* Add one white border to the selection (but very discreet, 1 pixel)
* The autofillmarker, selected outline and cell cursor should share the
same color. That color should come from css var (so it fits better
with surrounding elements, cell headers etc).
Caveats:
* Autofill-marker in mobile devices was positioned and sized
differently. With this change, they stay the same except for the color
and the contrast border. Styling this needs more thought.
Conflicts:
loleaflet/css/loleaflet.css
loleaflet/src/layer/tile/TileLayer.js
Signed-off-by: Dennis Francis <dennis.francis@collabora.com>
Change-Id: I64c2baa43a6f13ecd29266a5fd96eb3f53d00215
(cherry picked from commit e1a16d56681935758369c3b86a11a549de87de34)
console.logException is used only for debugging
purposes
Change-Id: I7d761d0cd7b55c820b7b7dea4079dae0f6d09043
Signed-off-by: Henry Castro <hcastro@collabora.com>
- Do not bother user with multiple dialog at the loading time
- Add additional timer after the welcome dialog is closed before
calling feedback again
Signed-off-by: Pedro Pinto Silva <pedro.silva@collabora.com>
Change-Id: Ib432e13205b1b3bef4dfa7ed8752a6561a4f0466
Increase timer value which avoids
user being prompted immediately after opening the app
to do---------
Nevertheless an additional commit should be implemented: If in presence
of a shouldWelcome() instance do not show
feedback dialog until user closes it
- Upon closing it Feedback dialog should not be shown instantly
, instead it should start a new timer and then show it.
Signed-off-by: Pedro Pinto Silva <pedro.silva@collabora.com>
Change-Id: I47f980fc4e86a480f70337c685cc639d78be4509
In order to not conflict with other
registered listeners.
Change-Id: I2fa15f4d5a04f0365ae4e940afa847dcb6e375cd
Signed-off-by: Henry Castro <hcastro@collabora.com>
To ensure that feedback dialog is not shown for builds where
it's not supposed to appear. This is just a cautionary measure since
Map.Feedback.js is included only when feedback is enabled
Signed-off-by: Pedro Pinto Silva <pedro.silva@collabora.com>
Change-Id: I378361d644dd76666ae3339a3d4f697a0a032e5f
Define the "feedbackLocation" variable only if it is enabled
Change-Id: I75ab9eec9f2f074eefe8551e876bb7dc07a30b4c
Signed-off-by: Henry Castro <hcastro@collabora.com>
- Desktop: Do not rely on margin to position dialog instead,
use percentage to find the center of the screen and account
for dialog width in that.
- Mobile:
- Add layout, styles, fonts etc
- Fix containers and wrapper dimensions
Signed-off-by: Pedro Pinto Silva <pedro.silva@collabora.com>
Change-Id: I7e2bf9d7ed015ea7ec96c3c36213802276e7f778
- Following the same style as the other dialogs
- Pass cssvar via url
Signed-off-by: Pedro Pinto Silva <pedro.silva@collabora.com>
Change-Id: I7ef0b9e0249939028163b6bf93f7083636f1dd1e
Does not need to be a badge in this particular case since it's above
a physical primary button; also make it completely white to be consistent
with the button's theme.
Signed-off-by: Pedro Pinto Silva <pedro.silva@collabora.com>
Change-Id: I8c85fbe33d1b3897f0fddd44dd7a5d0517f92e93
Changes to mobilewizard (not mobilewizard.menuwizard)
- Present locker as a floating badge
- Add shadow to communicate that it's different from the button
underneath and that it's clickable
- Locker and the icon underneath shouldn't be confused
- Make that difference clear
- Change position to it is more deliberated abode the icon but not
centered, so to not cover the feature
- Alight to top left since there are many icons using accent elements
on the top and bottom right
Signed-off-by: Pedro Pinto Silva <pedro.silva@collabora.com>
Change-Id: Idf19ddb3965efefdafd4d4be042bc7e47022208c
With latest changes on positions, Vex on mobile needs now to be set
to fix and additional rules are now not needed. Inherit from main
CSS file.
Signed-off-by: Pedro Pinto Silva <pedro.silva@collabora.com>
Change-Id: I2b67c0990d625d84077f0114ab198c9fe704a88a
- Distinguish menuwizard from normal mobilewizard
- Avoid using percentages so we are sure where the things are being
positioned
- When on mobilewizard (not menuwizard) avoid showind two lockers
- Also do not replace icons, let them be and add additional locker
so the user can still see which feature is supposed to be unlocked
Signed-off-by: Pedro Pinto Silva <pedro.silva@collabora.com>
Change-Id: I4d3d5f331162d16c63cf5cad667f0d5fab4dd9bc
When on mobile do not rely on background position and instead add
img element so we can properly resize it and adjust it:
- Less in your face
- To not disturb or overshadow the actual active elements
When on Classic mode:
- Hamburger items: Use smaller lockers so to do not get in the way
of reading the actual item label
Signed-off-by: Pedro Pinto Silva <pedro.silva@collabora.com>
Change-Id: I46218254a975b3a70d1e4c03eb1795d87f3861c9
specifically more focus on the top toolbar in classic mode
Signed-off-by: Pranam Lashkari <lpranam@collabora.com>
Change-Id: I33eebe79addebe3acfcea4d20912cc31b759ffce
- Fixes map z-index so annotation can be have higher z-index
- Now map and due to the latest changes introduced in:
8ca57fad3344f6da1b42158944bf9903f0ac528b we cannot use
container's border-top as our bezel divider
- Elements such as annotation need to go under
- So Fix toolbar-wrapper to use bottom border
- Notebookbar: Fix toolbar-wrapper background-Color which
was being set as transparent and thus elements passing under
were being visible
- Ruler: fix cropped ruler (was not going full width)
Signed-off-by: Pedro Pinto Silva <pedro.silva@collabora.com>
Change-Id: I8778619da43c51d1994dbb12d1112d4f1d42ff43
Depends on: https://gerrit.libreoffice.org/c/core/+/116265
Fixes checkbutton (Use separators) position by placing it
before divider label ('separatoroptions') thus, improving readability. User
can now see it clearly that all those separator options are related
and hierarchically under a main option: #toseparatedby.checkbutton.
Signed-off-by: Pedro Pinto Silva <pedro.silva@collabora.com>
Change-Id: I97b133e3e873a76ca75290728adaf1a45c9bcece
- Make it thicker
- Make it visible by default
- Hide it only when there is nothing to scroll
Signed-off-by: Pedro Pinto Silva <pedro.silva@collabora.com>
Change-Id: Ibffead10c09eda979ef8d3d2201173aca3553503
Do not show radio buttons in this case since we have images
for each option (radio images and textorient options images
were overlapping ) also fix width and add hover state
Signed-off-by: Pedro Pinto Silva <pedro.silva@collabora.com>
Change-Id: I7e3d8ef4da400024137d0c9207c67807ded281c5
Use the topLevel flag to keep us safe, and avoid problems when
constructing too.
Change-Id: Ifba6f0204dac359b0b028b3295a7227576b03dd6
Signed-off-by: Michael Meeks <michael.meeks@collabora.com>
Some bigtoolitem icons (namely About) were being skewed and others
were being set at a smaller size to what they were supposed to have.
Fix it by adding height value
Signed-off-by: Pedro Pinto Silva <pedro.silva@collabora.com>
Change-Id: I5ec375358e9dcf46a6b8b17570bea78963e188c8
a) removed event firing for catching tile messages
- injected socket onmessage function and made a middleware instead
- the middleware can catch any socket messages
b) Replaced "fake sleep" and while loop for keystroke messages
with setInterval function.
c) disabled processing incoming messages for multiple views
- Optimizing the front end for JSDOM seems to be hopeless.
the benchmark numbers for JSDOM and Real browser does not match
and most of the time are unrelevant. In most cases where JSDOM is
slower take almost no time for Real browser. These cases will not
make real experience smoother if somehow fixed. In addition,
rendering hundereds of socket messages makes nodejs use 100% of the cpu
and benchmarking the loolwsd or loolforkit properly becomes impossible
since nodejs cannnot handle messages in time and send keystroke messages
with respecting the interval.
- This way we can only focus on the backend performance and find the
problems that "mesh the keyboard" events produce.
d) Recording stats will now count the num of socket messages received
Signed-off-by: Mert Tumer <mert.tumer@collabora.com>
Change-Id: If7d11ecea00ca175463a5d3b8bbe7c29a4b6b32e
