trueinteractions / tint Goto Github PK

Ability to specify file types allowed on file open/save dialogs.

Refactor of internal tooltip caused a break, add new unit tests and fix bindings.

Ability to set at compile time an extension to associate with the application. In addition a handler to know when the application is launched with a file to be opened (editor mode fashion).

This feature would allow doc types for editors built in Tint.

When icons are stamped a new MD5/hash of the executable should be written, in addition the runtimes/tint compiler uses incorrect icons creating some confusion during the build process.

1. Custom UI's
2. Better three.js example
3. Intranet example (integration with Box API/Yammer)
4. Sales toolkit example
   ??

Ability to add/remove/position native window decorations such as fullscreen/min/max/close in both MacOSX and Windows.

https://developer.apple.com/library/mac/documentation/userexperience/conceptual/applehiguidelines/Windows/Windows.html

To make Tint backwards compatible with node-webkit, a public packager written on nodejs/javascript is needed for inclusion in node-webkit. This is dependent on node-webkit including support for embed:// protocol.

May only be available in MacOSX, further investigation on windows:

https://developer.apple.com/library/mac/documentation/userexperience/conceptual/applehiguidelines/Windows/Windows.html

https://developer.apple.com/library/mac/documentation/userexperience/conceptual/applehiguidelines/Windows/Windows.html

Both MacOSX/Windows - Ability to specify complete modal dialogs rather than just alert, confirm, prompt.

https://developer.apple.com/library/mac/documentation/userexperience/conceptual/applehiguidelines/Windows/Windows.html

Add librarian features to Tint as an on-going status.

Support for chrome packaged app api support and extensions (not necessarily the packaging system/launcher though)

Support native toolbars and their button options in both windows/macosx to provide more "native" like look and feel.

Design hasn't been finished. Jon isn't on github so this will be placed as a reminder.

Update the build/run process to check for security problems prior to running a packaged application. Right now it fails silently. In addition builds fail to run on NFS mounts or when using drive letters. Most of the issues seem to deal with relative/absolute paths and difficulties using various types of file pathing formats (e.g., drive letters)

To support more "native" look make the webview transparent while keeping the window frame the same.

1). Passing in multiple arguments into the runtime causes a crash. In addition, since chrome runs in multi process mode arguments cannot be properly retrieved since they don't appear in the rendering process.

2). The compiler needs to be enhanced to pass arguments into chromium in addition to setting the "webprefs" within the compiler (some preferences can't be set after the renderview or mainloop runs).

These are floating/dockable panel windows for inspecting elements, they wouldn't have a chromium webview but configurable components (buttons,sliders,etc) that can be added. In Windows these would be modal tool windows, MacOSX Panel windows.

https://developer.apple.com/library/mac/documentation/userexperience/conceptual/applehiguidelines/Windows/Windows.html

The ability to cancel a build that is currently on-going.

Chrome has many unnecessary features and resources included with Tint/node-webkit shell. Examine dependencies to determine unnecessary features for removal, recompile with /Os instead of /O3, in addition remove debugger into shared library so it can be only used while testing and removed for production.

Long term: all gypi compiled as shared libraries and dynamically bundled when Tint compiles to only include necessary libraries/code.

Possibly MacOSX only. Needs more investigation on windows.

https://developer.apple.com/library/mac/documentation/userexperience/conceptual/applehiguidelines/Windows/Windows.html

Both in MacOSX/Windows, no hosting chromium webview, simple "Icons", "Text" and onclick functionality (possibly add context menu shown?)

This produces a bound layover "Modal-Like" box that animates over hte current window similar to the opening a file in MacOSX. This hopefully can be a window style that can host a "glass" chromium view over it.

https://developer.apple.com/library/mac/documentation/userexperience/conceptual/applehiguidelines/Windows/Windows.html

Previously, the "run" option was very quick and you could launch the application within a second. In recent builds, the building required to run the program takes much longer. I believe this is to cut down on the size of the compiled executable. I find that one of best features of developing with "web technologies" is the rapid rate at which you can develope and debug. It would be very convenient, for the purposes of development and debugging, if there was either a way where "running" only produced enough so that launch was quick whereas the "build" button would produce the smaller compiled executable at the cost of a longer build time. Another idea would be to have some sort of feature through which the application could be "refreshed" similar to a webpage. In my evaluations, I've been using the browser for quick debugging and development, but that's no good once I start implementing Tint features or Node.js features in the application, which is among Tint's highlights.

Currently only 48x48 dimension icons are supported, increase this to support a wider range of icons (I believe Windows UI Guidelines as of Win8 specify: 16x16, 32x32, 48x48, 96x96, 128x128, 256x256).

MacOSX only embed one 512x512, see if this is possible on windows (with backwards compatibility for Vista/XP).

Native Font selection window in MacOSX and Windows.

https://developer.apple.com/library/mac/documentation/userexperience/conceptual/applehiguidelines/Windows/Windows.html

Ability to dynamically link and load C/C#/Objective-C libraries at runtime.

The ability to open recently saved/opened files in addition to (by default) opening the last used project.

Both MacOSX/Windows

https://developer.apple.com/library/mac/documentation/userexperience/conceptual/applehiguidelines/Windows/Windows.html

May only be available in MacOSX, further investigation on Windows:
https://developer.apple.com/library/mac/documentation/userexperience/conceptual/applehiguidelines/Windows/Windows.html

This would create easier "task based" applications and service type applications. Currently chrome/node-webkit require registering as a framed window application.