strepsirrhini/libreoffice-online
3
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
libreoffice-online/ios/Mobile/Base.lproj/Main.storyboard

128 lines
11 KiB
Text
Raw Normal View History

Intermediate commit of work in progress on an iOS app The app is unimaginatively called "Mobile" for now. Runs but crashes pretty quickly after loading the document by the LO core. Will need some heavy changes to get a ClientSession object created in there, too, to handle the (emulated) WebSocket messages from the JavaScript. It would then handle some of these messages itself, and forwards some to the ChildSession, which in this case is in the same process. Now the messsages from the JavaScript go to a ChildSession, which is wrong. As the assertion says, "Tile traffic should go through the DocumentBroker-LoKit WS"
2018-09-11 01:30:55 -05:00
<?xml version="1.0" encoding="UTF-8"?>
Work in progress on document creation using templates in the iOS app When the "Create Document" button in the document browser is pressed, we scan a set of ODF templates in the Templates subfolder of the app bundle, and we display that list as a collection view. (So far that view is not interactive, i.e. once it is displayed, you are stuck there.) Eventually, when the user chooses one of the templates, we will open that and immediately, before the user has done any edits, do a Save As of it as a real (not template) document in the app's document folder. What name to use for it is unclear yet. Further saves will thus don't need any dialog to choose the document name. More work will be needed on i18n of the template support. Should we have localised templates? At least localised template names. Etc. Change-Id: I5675779a5b16bc4c70a943109aa0dd53cf4bd903
2018-12-04 14:01:45 -06:00
<document type="com.apple.InterfaceBuilder3.CocoaTouch.Storyboard.XIB" version="3.0" toolsVersion="14460.31" targetRuntime="iOS.CocoaTouch" propertyAccessControl="none" useAutolayout="YES" useTraitCollections="YES" useSafeAreas="YES" colorMatched="YES" initialViewController="BYZ-38-t0r">
Make the template collection view look much better Now it finally looks like I want, but oh boy was that a pain. I am not sure at all I understand what I am doing in Xcode's Interface Builder. I tried hard at first to use the cell size 200x220 for the cell size of the UICollectionView, consisting of a 200x200 UIImageView and a 200x20 UILabel below. But that did not seem to work, it still used a (default?) size of 150x150. Weird. Anyway, let's commit this state now that seems to work. Change-Id: I4021133619fbf62cd633392d93f19c2bbc81311a
2018-12-06 09:14:47 -06:00
<device id="ipad9_7" orientation="portrait">
Intermediate commit of work in progress on an iOS app The app is unimaginatively called "Mobile" for now. Runs but crashes pretty quickly after loading the document by the LO core. Will need some heavy changes to get a ClientSession object created in there, too, to handle the (emulated) WebSocket messages from the JavaScript. It would then handle some of these messages itself, and forwards some to the ChildSession, which in this case is in the same process. Now the messsages from the JavaScript go to a ChildSession, which is wrong. As the assertion says, "Tile traffic should go through the DocumentBroker-LoKit WS"
2018-09-11 01:30:55 -05:00
<adaptation id="fullscreen"/>
</device>
<dependencies>
<deployment identifier="iOS"/>
Work in progress on document creation using templates in the iOS app When the "Create Document" button in the document browser is pressed, we scan a set of ODF templates in the Templates subfolder of the app bundle, and we display that list as a collection view. (So far that view is not interactive, i.e. once it is displayed, you are stuck there.) Eventually, when the user chooses one of the templates, we will open that and immediately, before the user has done any edits, do a Save As of it as a real (not template) document in the app's document folder. What name to use for it is unclear yet. Further saves will thus don't need any dialog to choose the document name. More work will be needed on i18n of the template support. Should we have localised templates? At least localised template names. Etc. Change-Id: I5675779a5b16bc4c70a943109aa0dd53cf4bd903
2018-12-04 14:01:45 -06:00
<plugIn identifier="com.apple.InterfaceBuilder.IBCocoaTouchPlugin" version="14460.20"/>
Intermediate commit of work in progress on an iOS app The app is unimaginatively called "Mobile" for now. Runs but crashes pretty quickly after loading the document by the LO core. Will need some heavy changes to get a ClientSession object created in there, too, to handle the (emulated) WebSocket messages from the JavaScript. It would then handle some of these messages itself, and forwards some to the ChildSession, which in this case is in the same process. Now the messsages from the JavaScript go to a ChildSession, which is wrong. As the assertion says, "Tile traffic should go through the DocumentBroker-LoKit WS"
2018-09-11 01:30:55 -05:00
<capability name="Safe area layout guides" minToolsVersion="9.0"/>
<capability name="documents saved in the Xcode 8 format" minToolsVersion="8.0"/>
</dependencies>
<scenes>
<!--Document Browser View Controller-->
<scene sceneID="tne-QT-ifu">
<objects>
<viewController id="BYZ-38-t0r" customClass="DocumentBrowserViewController" sceneMemberID="viewController">
<view key="view" contentMode="scaleToFill" id="8bC-Xf-vdC">
Make the template collection view look much better Now it finally looks like I want, but oh boy was that a pain. I am not sure at all I understand what I am doing in Xcode's Interface Builder. I tried hard at first to use the cell size 200x220 for the cell size of the UICollectionView, consisting of a 200x200 UIImageView and a 200x20 UILabel below. But that did not seem to work, it still used a (default?) size of 150x150. Weird. Anyway, let's commit this state now that seems to work. Change-Id: I4021133619fbf62cd633392d93f19c2bbc81311a
2018-12-06 09:14:47 -06:00
<rect key="frame" x="0.0" y="0.0" width="768" height="1024"/>
Intermediate commit of work in progress on an iOS app The app is unimaginatively called "Mobile" for now. Runs but crashes pretty quickly after loading the document by the LO core. Will need some heavy changes to get a ClientSession object created in there, too, to handle the (emulated) WebSocket messages from the JavaScript. It would then handle some of these messages itself, and forwards some to the ChildSession, which in this case is in the same process. Now the messsages from the JavaScript go to a ChildSession, which is wrong. As the assertion says, "Tile traffic should go through the DocumentBroker-LoKit WS"
2018-09-11 01:30:55 -05:00
<autoresizingMask key="autoresizingMask" widthSizable="YES" heightSizable="YES"/>
<color key="backgroundColor" red="1" green="1" blue="1" alpha="1" colorSpace="custom" customColorSpace="sRGB"/>
<viewLayoutGuide key="safeArea" id="0fo-ii-Aj5"/>
</view>
</viewController>
<placeholder placeholderIdentifier="IBFirstResponder" id="dkx-z0-nzr" sceneMemberID="firstResponder"/>
</objects>
<point key="canvasLocation" x="26" y="654"/>
</scene>
<!--Document View Controller-->
<scene sceneID="dkP-xk-x6W">
<objects>
<viewController storyboardIdentifier="DocumentViewController" id="M2k-L8-Olo" customClass="DocumentViewController" sceneMemberID="viewController">
<view key="view" contentMode="scaleToFill" id="SIE-Uh-Zny">
Make the template collection view look much better Now it finally looks like I want, but oh boy was that a pain. I am not sure at all I understand what I am doing in Xcode's Interface Builder. I tried hard at first to use the cell size 200x220 for the cell size of the UICollectionView, consisting of a 200x200 UIImageView and a 200x20 UILabel below. But that did not seem to work, it still used a (default?) size of 150x150. Weird. Anyway, let's commit this state now that seems to work. Change-Id: I4021133619fbf62cd633392d93f19c2bbc81311a
2018-12-06 09:14:47 -06:00
<rect key="frame" x="0.0" y="0.0" width="768" height="1024"/>
Intermediate commit of work in progress on an iOS app The app is unimaginatively called "Mobile" for now. Runs but crashes pretty quickly after loading the document by the LO core. Will need some heavy changes to get a ClientSession object created in there, too, to handle the (emulated) WebSocket messages from the JavaScript. It would then handle some of these messages itself, and forwards some to the ChildSession, which in this case is in the same process. Now the messsages from the JavaScript go to a ChildSession, which is wrong. As the assertion says, "Tile traffic should go through the DocumentBroker-LoKit WS"
2018-09-11 01:30:55 -05:00
<autoresizingMask key="autoresizingMask" widthSizable="YES" heightSizable="YES"/>
<color key="backgroundColor" white="1" alpha="1" colorSpace="calibratedWhite"/>
<viewLayoutGuide key="safeArea" id="BoZ-jc-2Y8"/>
</view>
</viewController>
<placeholder placeholderIdentifier="IBFirstResponder" id="Rl9-ES-qQn" userLabel="First Responder" sceneMemberID="firstResponder"/>
</objects>
<point key="canvasLocation" x="1031" y="654"/>
</scene>
Work in progress on document creation using templates in the iOS app When the "Create Document" button in the document browser is pressed, we scan a set of ODF templates in the Templates subfolder of the app bundle, and we display that list as a collection view. (So far that view is not interactive, i.e. once it is displayed, you are stuck there.) Eventually, when the user chooses one of the templates, we will open that and immediately, before the user has done any edits, do a Save As of it as a real (not template) document in the app's document folder. What name to use for it is unclear yet. Further saves will thus don't need any dialog to choose the document name. More work will be needed on i18n of the template support. Should we have localised templates? At least localised template names. Etc. Change-Id: I5675779a5b16bc4c70a943109aa0dd53cf4bd903
2018-12-04 14:01:45 -06:00
<!--Template Collection View Controller-->
<scene sceneID="juG-xb-Xrw">
<objects>
Make the template collection view look much better Now it finally looks like I want, but oh boy was that a pain. I am not sure at all I understand what I am doing in Xcode's Interface Builder. I tried hard at first to use the cell size 200x220 for the cell size of the UICollectionView, consisting of a 200x200 UIImageView and a 200x20 UILabel below. But that did not seem to work, it still used a (default?) size of 150x150. Weird. Anyway, let's commit this state now that seems to work. Change-Id: I4021133619fbf62cd633392d93f19c2bbc81311a
2018-12-06 09:14:47 -06:00
<collectionViewController storyboardIdentifier="TemplateCollectionViewController" autoresizesArchivedViewToFullSize="NO" id="Cwb-6T-NJd" customClass="TemplateCollectionViewController" sceneMemberID="viewController">
<collectionView key="view" clipsSubviews="YES" contentMode="scaleAspectFit" dataMode="prototypes" id="cHi-RU-96O">
<rect key="frame" x="0.0" y="0.0" width="768" height="1024"/>
Work in progress on document creation using templates in the iOS app When the "Create Document" button in the document browser is pressed, we scan a set of ODF templates in the Templates subfolder of the app bundle, and we display that list as a collection view. (So far that view is not interactive, i.e. once it is displayed, you are stuck there.) Eventually, when the user chooses one of the templates, we will open that and immediately, before the user has done any edits, do a Save As of it as a real (not template) document in the app's document folder. What name to use for it is unclear yet. Further saves will thus don't need any dialog to choose the document name. More work will be needed on i18n of the template support. Should we have localised templates? At least localised template names. Etc. Change-Id: I5675779a5b16bc4c70a943109aa0dd53cf4bd903
2018-12-04 14:01:45 -06:00
<autoresizingMask key="autoresizingMask" widthSizable="YES" heightSizable="YES"/>
Look for thumbnails of the templates and show them in the template browser Add such thumbnails. Rename the presentation templates to not have colons in their name, as that seems to be problematic for macOS and/or iOS, sigh. (Shadows of pre-OS X MacOS, where the coln was the path component separator, not the slash.) Hack on the storyboard scene for the template browser. More work is needed there; the thumbnails aren't scaled down for some reason. I need to make sure the aspect ratio is maintained, too. Maybe to get it to look like I want I need to do some coding and not just tweak the storyboard in the Xcode UI designer, sigh. Change-Id: I959d051352c2f033c8563188155af5281961c7d8
2018-12-06 08:33:39 -06:00
<color key="backgroundColor" white="0.33333333333333331" alpha="1" colorSpace="custom" customColorSpace="genericGamma22GrayColorSpace"/>
Work in progress on document creation using templates in the iOS app When the "Create Document" button in the document browser is pressed, we scan a set of ODF templates in the Templates subfolder of the app bundle, and we display that list as a collection view. (So far that view is not interactive, i.e. once it is displayed, you are stuck there.) Eventually, when the user chooses one of the templates, we will open that and immediately, before the user has done any edits, do a Save As of it as a real (not template) document in the app's document folder. What name to use for it is unclear yet. Further saves will thus don't need any dialog to choose the document name. More work will be needed on i18n of the template support. Should we have localised templates? At least localised template names. Etc. Change-Id: I5675779a5b16bc4c70a943109aa0dd53cf4bd903
2018-12-04 14:01:45 -06:00
<collectionViewFlowLayout key="collectionViewLayout" minimumLineSpacing="10" minimumInteritemSpacing="10" id="w0h-io-kZq">
Finally figured out how to get 200x200 cells in the template collection Change-Id: Idd977ccf52b2dd0e0aaae08f54f6d902791bcc6d
2018-12-07 03:20:10 -06:00
<size key="itemSize" width="200" height="200"/>
Work in progress on document creation using templates in the iOS app When the "Create Document" button in the document browser is pressed, we scan a set of ODF templates in the Templates subfolder of the app bundle, and we display that list as a collection view. (So far that view is not interactive, i.e. once it is displayed, you are stuck there.) Eventually, when the user chooses one of the templates, we will open that and immediately, before the user has done any edits, do a Save As of it as a real (not template) document in the app's document folder. What name to use for it is unclear yet. Further saves will thus don't need any dialog to choose the document name. More work will be needed on i18n of the template support. Should we have localised templates? At least localised template names. Etc. Change-Id: I5675779a5b16bc4c70a943109aa0dd53cf4bd903
2018-12-04 14:01:45 -06:00
<size key="headerReferenceSize" width="50" height="50"/>
<size key="footerReferenceSize" width="0.0" height="0.0"/>
<inset key="sectionInset" minX="50" minY="0.0" maxX="0.0" maxY="0.0"/>
</collectionViewFlowLayout>
<cells>
Make the template collection view look much better Now it finally looks like I want, but oh boy was that a pain. I am not sure at all I understand what I am doing in Xcode's Interface Builder. I tried hard at first to use the cell size 200x220 for the cell size of the UICollectionView, consisting of a 200x200 UIImageView and a 200x20 UILabel below. But that did not seem to work, it still used a (default?) size of 150x150. Weird. Anyway, let's commit this state now that seems to work. Change-Id: I4021133619fbf62cd633392d93f19c2bbc81311a
2018-12-06 09:14:47 -06:00
<collectionViewCell opaque="NO" clipsSubviews="YES" multipleTouchEnabled="YES" contentMode="center" insetsLayoutMarginsFromSafeArea="NO" reuseIdentifier="Cell" id="ppW-Sx-T3H">
Finally figured out how to get 200x200 cells in the template collection Change-Id: Idd977ccf52b2dd0e0aaae08f54f6d902791bcc6d
2018-12-07 03:20:10 -06:00
<rect key="frame" x="50" y="50" width="200" height="200"/>
Look for thumbnails of the templates and show them in the template browser Add such thumbnails. Rename the presentation templates to not have colons in their name, as that seems to be problematic for macOS and/or iOS, sigh. (Shadows of pre-OS X MacOS, where the coln was the path component separator, not the slash.) Hack on the storyboard scene for the template browser. More work is needed there; the thumbnails aren't scaled down for some reason. I need to make sure the aspect ratio is maintained, too. Maybe to get it to look like I want I need to do some coding and not just tweak the storyboard in the Xcode UI designer, sigh. Change-Id: I959d051352c2f033c8563188155af5281961c7d8
2018-12-06 08:33:39 -06:00
<autoresizingMask key="autoresizingMask"/>
Work in progress on document creation using templates in the iOS app When the "Create Document" button in the document browser is pressed, we scan a set of ODF templates in the Templates subfolder of the app bundle, and we display that list as a collection view. (So far that view is not interactive, i.e. once it is displayed, you are stuck there.) Eventually, when the user chooses one of the templates, we will open that and immediately, before the user has done any edits, do a Save As of it as a real (not template) document in the app's document folder. What name to use for it is unclear yet. Further saves will thus don't need any dialog to choose the document name. More work will be needed on i18n of the template support. Should we have localised templates? At least localised template names. Etc. Change-Id: I5675779a5b16bc4c70a943109aa0dd53cf4bd903
2018-12-04 14:01:45 -06:00
<view key="contentView" opaque="NO" clipsSubviews="YES" multipleTouchEnabled="YES" contentMode="center" insetsLayoutMarginsFromSafeArea="NO">
Finally figured out how to get 200x200 cells in the template collection Change-Id: Idd977ccf52b2dd0e0aaae08f54f6d902791bcc6d
2018-12-07 03:20:10 -06:00
<rect key="frame" x="0.0" y="0.0" width="200" height="200"/>
Work in progress on document creation using templates in the iOS app When the "Create Document" button in the document browser is pressed, we scan a set of ODF templates in the Templates subfolder of the app bundle, and we display that list as a collection view. (So far that view is not interactive, i.e. once it is displayed, you are stuck there.) Eventually, when the user chooses one of the templates, we will open that and immediately, before the user has done any edits, do a Save As of it as a real (not template) document in the app's document folder. What name to use for it is unclear yet. Further saves will thus don't need any dialog to choose the document name. More work will be needed on i18n of the template support. Should we have localised templates? At least localised template names. Etc. Change-Id: I5675779a5b16bc4c70a943109aa0dd53cf4bd903
2018-12-04 14:01:45 -06:00
<autoresizingMask key="autoresizingMask"/>
<subviews>
Make the template collection view look much better Now it finally looks like I want, but oh boy was that a pain. I am not sure at all I understand what I am doing in Xcode's Interface Builder. I tried hard at first to use the cell size 200x220 for the cell size of the UICollectionView, consisting of a 200x200 UIImageView and a 200x20 UILabel below. But that did not seem to work, it still used a (default?) size of 150x150. Weird. Anyway, let's commit this state now that seems to work. Change-Id: I4021133619fbf62cd633392d93f19c2bbc81311a
2018-12-06 09:14:47 -06:00
<view opaque="NO" contentMode="center" insetsLayoutMarginsFromSafeArea="NO" translatesAutoresizingMaskIntoConstraints="NO" id="riJ-1i-vBs">
<rect key="frame" x="0.0" y="0.0" width="150" height="130"/>
<subviews>
<imageView verifyAmbiguity="off" opaque="NO" userInteractionEnabled="NO" tag="1" contentMode="scaleAspectFit" horizontalHuggingPriority="251" verticalHuggingPriority="251" insetsLayoutMarginsFromSafeArea="NO" translatesAutoresizingMaskIntoConstraints="NO" id="79y-w8-uiT">
<rect key="frame" x="0.0" y="0.0" width="150" height="130"/>
<color key="backgroundColor" white="0.0" alpha="0.0" colorSpace="custom" customColorSpace="genericGamma22GrayColorSpace"/>
</imageView>
</subviews>
<color key="backgroundColor" white="0.0" alpha="0.0" colorSpace="custom" customColorSpace="genericGamma22GrayColorSpace"/>
<constraints>
<constraint firstAttribute="bottom" secondItem="79y-w8-uiT" secondAttribute="bottom" id="0I0-7w-Dde"/>
<constraint firstAttribute="trailing" secondItem="79y-w8-uiT" secondAttribute="trailing" id="UjO-rr-ITf"/>
<constraint firstItem="79y-w8-uiT" firstAttribute="leading" secondItem="riJ-1i-vBs" secondAttribute="leading" id="bBb-Cf-c4a"/>
<constraint firstItem="79y-w8-uiT" firstAttribute="top" secondItem="riJ-1i-vBs" secondAttribute="top" id="giz-fe-CV5"/>
</constraints>
</view>
<label verifyAmbiguity="off" opaque="NO" userInteractionEnabled="NO" tag="2" contentMode="left" horizontalHuggingPriority="251" verticalHuggingPriority="251" insetsLayoutMarginsFromSafeArea="NO" text="Label" textAlignment="center" lineBreakMode="tailTruncation" baselineAdjustment="alignBaselines" adjustsFontSizeToFit="NO" translatesAutoresizingMaskIntoConstraints="NO" id="fjg-QH-lLg">
<rect key="frame" x="0.0" y="130" width="150" height="20"/>
Work in progress on document creation using templates in the iOS app When the "Create Document" button in the document browser is pressed, we scan a set of ODF templates in the Templates subfolder of the app bundle, and we display that list as a collection view. (So far that view is not interactive, i.e. once it is displayed, you are stuck there.) Eventually, when the user chooses one of the templates, we will open that and immediately, before the user has done any edits, do a Save As of it as a real (not template) document in the app's document folder. What name to use for it is unclear yet. Further saves will thus don't need any dialog to choose the document name. More work will be needed on i18n of the template support. Should we have localised templates? At least localised template names. Etc. Change-Id: I5675779a5b16bc4c70a943109aa0dd53cf4bd903
2018-12-04 14:01:45 -06:00
<fontDescription key="fontDescription" type="system" pointSize="17"/>
Look for thumbnails of the templates and show them in the template browser Add such thumbnails. Rename the presentation templates to not have colons in their name, as that seems to be problematic for macOS and/or iOS, sigh. (Shadows of pre-OS X MacOS, where the coln was the path component separator, not the slash.) Hack on the storyboard scene for the template browser. More work is needed there; the thumbnails aren't scaled down for some reason. I need to make sure the aspect ratio is maintained, too. Maybe to get it to look like I want I need to do some coding and not just tweak the storyboard in the Xcode UI designer, sigh. Change-Id: I959d051352c2f033c8563188155af5281961c7d8
2018-12-06 08:33:39 -06:00
<color key="textColor" white="1" alpha="1" colorSpace="custom" customColorSpace="genericGamma22GrayColorSpace"/>
Work in progress on document creation using templates in the iOS app When the "Create Document" button in the document browser is pressed, we scan a set of ODF templates in the Templates subfolder of the app bundle, and we display that list as a collection view. (So far that view is not interactive, i.e. once it is displayed, you are stuck there.) Eventually, when the user chooses one of the templates, we will open that and immediately, before the user has done any edits, do a Save As of it as a real (not template) document in the app's document folder. What name to use for it is unclear yet. Further saves will thus don't need any dialog to choose the document name. More work will be needed on i18n of the template support. Should we have localised templates? At least localised template names. Etc. Change-Id: I5675779a5b16bc4c70a943109aa0dd53cf4bd903
2018-12-04 14:01:45 -06:00
<nil key="highlightedColor"/>
</label>
</subviews>
</view>
<constraints>
Make the template collection view look much better Now it finally looks like I want, but oh boy was that a pain. I am not sure at all I understand what I am doing in Xcode's Interface Builder. I tried hard at first to use the cell size 200x220 for the cell size of the UICollectionView, consisting of a 200x200 UIImageView and a 200x20 UILabel below. But that did not seem to work, it still used a (default?) size of 150x150. Weird. Anyway, let's commit this state now that seems to work. Change-Id: I4021133619fbf62cd633392d93f19c2bbc81311a
2018-12-06 09:14:47 -06:00
<constraint firstItem="fjg-QH-lLg" firstAttribute="trailing" secondItem="riJ-1i-vBs" secondAttribute="trailing" id="5X8-PS-XYq"/>
<constraint firstItem="fjg-QH-lLg" firstAttribute="leading" secondItem="riJ-1i-vBs" secondAttribute="leading" id="8fo-lW-iy0"/>
<constraint firstAttribute="trailing" secondItem="riJ-1i-vBs" secondAttribute="trailing" id="9OL-6w-5ui"/>
<constraint firstAttribute="bottom" secondItem="riJ-1i-vBs" secondAttribute="bottom" constant="20" id="FmN-mf-0fQ"/>
<constraint firstItem="riJ-1i-vBs" firstAttribute="leading" secondItem="ppW-Sx-T3H" secondAttribute="leading" id="fc4-fE-xoO"/>
<constraint firstItem="fjg-QH-lLg" firstAttribute="top" secondItem="riJ-1i-vBs" secondAttribute="bottom" id="ise-Cp-lOO"/>
<constraint firstItem="riJ-1i-vBs" firstAttribute="top" secondItem="ppW-Sx-T3H" secondAttribute="top" id="udK-op-sng"/>
Work in progress on document creation using templates in the iOS app When the "Create Document" button in the document browser is pressed, we scan a set of ODF templates in the Templates subfolder of the app bundle, and we display that list as a collection view. (So far that view is not interactive, i.e. once it is displayed, you are stuck there.) Eventually, when the user chooses one of the templates, we will open that and immediately, before the user has done any edits, do a Save As of it as a real (not template) document in the app's document folder. What name to use for it is unclear yet. Further saves will thus don't need any dialog to choose the document name. More work will be needed on i18n of the template support. Should we have localised templates? At least localised template names. Etc. Change-Id: I5675779a5b16bc4c70a943109aa0dd53cf4bd903
2018-12-04 14:01:45 -06:00
</constraints>
</collectionViewCell>
</cells>
<collectionReusableView key="sectionHeaderView" opaque="NO" clipsSubviews="YES" multipleTouchEnabled="YES" contentMode="center" insetsLayoutMarginsFromSafeArea="NO" reuseIdentifier="SectionHeaderView" id="Vbs-oR-qri" customClass="TemplateSectionHeaderView">
Make the template collection view look much better Now it finally looks like I want, but oh boy was that a pain. I am not sure at all I understand what I am doing in Xcode's Interface Builder. I tried hard at first to use the cell size 200x220 for the cell size of the UICollectionView, consisting of a 200x200 UIImageView and a 200x20 UILabel below. But that did not seem to work, it still used a (default?) size of 150x150. Weird. Anyway, let's commit this state now that seems to work. Change-Id: I4021133619fbf62cd633392d93f19c2bbc81311a
2018-12-06 09:14:47 -06:00
<rect key="frame" x="0.0" y="0.0" width="768" height="50"/>
Work in progress on document creation using templates in the iOS app When the "Create Document" button in the document browser is pressed, we scan a set of ODF templates in the Templates subfolder of the app bundle, and we display that list as a collection view. (So far that view is not interactive, i.e. once it is displayed, you are stuck there.) Eventually, when the user chooses one of the templates, we will open that and immediately, before the user has done any edits, do a Save As of it as a real (not template) document in the app's document folder. What name to use for it is unclear yet. Further saves will thus don't need any dialog to choose the document name. More work will be needed on i18n of the template support. Should we have localised templates? At least localised template names. Etc. Change-Id: I5675779a5b16bc4c70a943109aa0dd53cf4bd903
2018-12-04 14:01:45 -06:00
<autoresizingMask key="autoresizingMask"/>
<subviews>
<label opaque="NO" userInteractionEnabled="NO" contentMode="left" horizontalHuggingPriority="251" verticalHuggingPriority="251" fixedFrame="YES" text="Label" lineBreakMode="tailTruncation" baselineAdjustment="alignBaselines" adjustsFontSizeToFit="NO" translatesAutoresizingMaskIntoConstraints="NO" id="DE4-jV-CVW">
Make the template collection view look much better Now it finally looks like I want, but oh boy was that a pain. I am not sure at all I understand what I am doing in Xcode's Interface Builder. I tried hard at first to use the cell size 200x220 for the cell size of the UICollectionView, consisting of a 200x200 UIImageView and a 200x20 UILabel below. But that did not seem to work, it still used a (default?) size of 150x150. Weird. Anyway, let's commit this state now that seems to work. Change-Id: I4021133619fbf62cd633392d93f19c2bbc81311a
2018-12-06 09:14:47 -06:00
<rect key="frame" x="0.0" y="0.0" width="768" height="50"/>
Work in progress on document creation using templates in the iOS app When the "Create Document" button in the document browser is pressed, we scan a set of ODF templates in the Templates subfolder of the app bundle, and we display that list as a collection view. (So far that view is not interactive, i.e. once it is displayed, you are stuck there.) Eventually, when the user chooses one of the templates, we will open that and immediately, before the user has done any edits, do a Save As of it as a real (not template) document in the app's document folder. What name to use for it is unclear yet. Further saves will thus don't need any dialog to choose the document name. More work will be needed on i18n of the template support. Should we have localised templates? At least localised template names. Etc. Change-Id: I5675779a5b16bc4c70a943109aa0dd53cf4bd903
2018-12-04 14:01:45 -06:00
<autoresizingMask key="autoresizingMask" flexibleMinY="YES" flexibleMaxY="YES"/>
<fontDescription key="fontDescription" type="system" pointSize="17"/>
Look for thumbnails of the templates and show them in the template browser Add such thumbnails. Rename the presentation templates to not have colons in their name, as that seems to be problematic for macOS and/or iOS, sigh. (Shadows of pre-OS X MacOS, where the coln was the path component separator, not the slash.) Hack on the storyboard scene for the template browser. More work is needed there; the thumbnails aren't scaled down for some reason. I need to make sure the aspect ratio is maintained, too. Maybe to get it to look like I want I need to do some coding and not just tweak the storyboard in the Xcode UI designer, sigh. Change-Id: I959d051352c2f033c8563188155af5281961c7d8
2018-12-06 08:33:39 -06:00
<color key="textColor" white="1" alpha="1" colorSpace="custom" customColorSpace="genericGamma22GrayColorSpace"/>
Work in progress on document creation using templates in the iOS app When the "Create Document" button in the document browser is pressed, we scan a set of ODF templates in the Templates subfolder of the app bundle, and we display that list as a collection view. (So far that view is not interactive, i.e. once it is displayed, you are stuck there.) Eventually, when the user chooses one of the templates, we will open that and immediately, before the user has done any edits, do a Save As of it as a real (not template) document in the app's document folder. What name to use for it is unclear yet. Further saves will thus don't need any dialog to choose the document name. More work will be needed on i18n of the template support. Should we have localised templates? At least localised template names. Etc. Change-Id: I5675779a5b16bc4c70a943109aa0dd53cf4bd903
2018-12-04 14:01:45 -06:00
<nil key="highlightedColor"/>
</label>
</subviews>
<connections>
<outlet property="title" destination="DE4-jV-CVW" id="iy6-0m-CYp"/>
</connections>
</collectionReusableView>
<connections>
<outlet property="dataSource" destination="Cwb-6T-NJd" id="rwX-kb-u54"/>
<outlet property="delegate" destination="Cwb-6T-NJd" id="NdE-oH-qfI"/>
</connections>
</collectionView>
</collectionViewController>
<placeholder placeholderIdentifier="IBFirstResponder" id="RAw-E0-0p8" userLabel="First Responder" sceneMemberID="firstResponder"/>
</objects>
<point key="canvasLocation" x="1717.5999999999999" y="653.52323838080963"/>
</scene>
Intermediate commit of work in progress on an iOS app The app is unimaginatively called "Mobile" for now. Runs but crashes pretty quickly after loading the document by the LO core. Will need some heavy changes to get a ClientSession object created in there, too, to handle the (emulated) WebSocket messages from the JavaScript. It would then handle some of these messages itself, and forwards some to the ChildSession, which in this case is in the same process. Now the messsages from the JavaScript go to a ChildSession, which is wrong. As the assertion says, "Tile traffic should go through the DocumentBroker-LoKit WS"
2018-09-11 01:30:55 -05:00
</scenes>
</document>
Reference in a new issue Copy permalink