Assessment of Strengths, Weaknesses and Opportunities

Jump to bottom Edit New page

wass3r edited this page Jul 4, 2012 · 9 revisions

What is TideSDK's Core Value

Unique object bridge (Kroll)
- Python/PHP/Ruby integration
Common API for Desktop
Code base
Documented API
Packaging
Crossplatform (Windows, MacOS, Linux)
It's an out of the box solution (RC.4)
MacOS 64 bit support
Apple Store Support
Webkit upgrade on Mac was painless
Webkit on Mac and Webkit-GTK Linux are developed by many companies.
Three years in the market

Some interesting features:

Drag and Drop support
Icons
Toolbar, tray icon support
Current tooling support with Titanium Studio

What are TideSDK's Current Weaknesses

Code condition (broken master and poorly maintained by Appc)
Modularity
Difficult to maintain
Separately maintained Webkit (Apple's webkit on Mac, Wincairo on Windows, Webkit-GTK on Linux)
- Wincairo is not very supported. (but it was on June 2012 by bfulgham)

How Can TideSDK's Value Integrate with Other Open Projects

TideSDK's API could be layer over an existing CEF, nodejs implementation such as appjs.

How can we Help each Other

Packaging (ie. packaging over network for supported operating systems)
Builds and common build software (ie. Scons, gyp, premake, cmake)
Test Framework (ie. Drillbit/Mocha (?)
Continuous Integration System

Where are TideSDK's Opportunities

Node.js integration
Current userbase
CEF could be used as a unique webkit on Windows and Linux.

Road Map