ewanharris

Feature: Check folder access

  Background:
    Given folder:5 is a parent of folder:product-2021
    * folder:product-2021 is a parent of folder:product-2021Q1
    * folder:product is a parent of folder:product-2021

  Scenario: user:anne can read and write but not share folder:product-2021
    Given user:anne is an owner of folder:product
    When she accesses folder:product-2021

ewanharris

const fs = require('fs-extra');
const packageJson = require('./package.json');
const existing = require('./package.nls.json');

function handleStringEdit (str, obj, key) {
	if (!obj[key] || obj[key]?.startsWith('%')) {
		return;
	}
	existing[str] = obj[key];
	obj[key] = `%${str}%`;

ewanharris

[TRACE]  #import "TiAppiOSActivityAttributesProxy.h"
[TRACE]          ^
[TRACE]  /Users/awam/Documents/titanium-workspace/test-app/build/iphone/Classes/TiAppiOSActivityAttributesProxy.h:10:9: error: 'TitaniumKit/TitaniumKit.h' file not found
[TRACE]  #import <TitaniumKit/TitaniumKit.h>
[TRACE]          ^
[TRACE]  /Users/awam/Documents/titanium-workspace/test-app/build/iphone/Classes/TiAppiOSActivityAttributesProxy.h:10:9: note: did not find header 'TitaniumKit.h' in framework 'TitaniumKit' (loaded from '/Users/awam/Documents/titanium-workspace/test-app/build/iphone/build/Products/Debug-maccatalyst')
[TRACE]  #import <TitaniumKit/TitaniumKit.h>
[TRACE]          ^
[TRACE]  1 error generated.
[TRACE]  <unknown>:0: error: failed to emit precompiled header '/Users/awam/Documents/titanium-workspace/test-app/build/iphone/build/Intermediates/PrecompiledHeaders/test_app-Bridging-Header-swift_2S904Q57JC3MW-clang_38YETQ0XB7NQN.pch' for bridging header '/Users/awam/Documents/titanium-workspace/test-app/build/iphone/test_

ewanharris

{
	"branch": {},
	"branches": false,
	"defaultInstallLocation": "/Users/user/Library/Application Support/Titanium",
	"installLocations": [
		"/Library/Application Support/Titanium",
		"/Users/user/Library/Application Support/Titanium"
	],
	"installed": {},
	"releases": [

ewanharris

const win = Ti.UI.createWindow();

function createEvent() {
	let calendarId;
	for (const calendar of Ti.Calendar.allCalendars) {
		Ti.API.info(calendar.name, calendar.id);
		// This probably is not good enough for an app, the calendar most likely should be selected by the user
		if (calendar.name === 'Calendar') {
			calendarId = calendar.id
		}

ewanharris

/**
 * Requirements:
 * 
 * node 14
 * these dependencies - npm i @octokit/rest date-fns fs-extra
 */

import fs from 'fs-extra';
import { isAfter } from 'date-fns';
import Octokit from '@octokit/rest';

ewanharris

const win = Ti.UI.createWindow({ layout: 'vertical' });
const singleBtn = Ti.UI.createButton({ title: 'Select single', top: 50 });
singleBtn.addEventListener('click', () => {
    selectImage(false);
});
win.add(singleBtn);
const multiBtn = Ti.UI.createButton({ title: 'Select multiple' });
multiBtn.addEventListener('click', () => {
    selectImage(true);
});

ewanharris

#!/usr/bin/env bash

FOLDER=$1

echo "Checking $FOLDER"

# Check for references to UIWebView in the build .a files using strings
for file in "$FOLDER"/*.a; do
	strings "$file" | grep UIWeb > /dev/null 2>&1
	if [ $? -eq 0 ]

ewanharris

Add the below to your tiapp

<android xmlns:android="http://schemas.android.com/apk/res/android">
    <manifest xmlns:android="http://schemas.android.com/apk/res/android" android:versionCode="1">
      <uses-permission android:name="android.permission.REQUEST_INSTALL_PACKAGES"/>
      <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
      <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
    </manifest>
 

ewanharris

@import TSS for Alloy

NOTE: This is out-dated, I suggest using https://github.com/dbankier/ltss instead.

This alloy.jmk adds support for using CSS-like @import "file.tss"; statements in Alloy TSS styles.

The idea for this came when discussing adding the option of including a CSS-like reset stylesheet in Alloy to make up for platform differences in (background)color, but also some good practices.

I think one of the key issues in this discussion is that there is no such thing as the base style for an app. iOS fans would like to reset to iOS-like styles, Android fans like to reset to theirs, flat UI fanatics would like everything minimalized and Bootstrap adepts will ask for a huge library of styles.