So, 2014 becomes {{year}}, and we make sure to inject the variable year into all templates as we generate the code.

We should run an integration test over the generated samples. One thing we could do is analyze generated dart code to make sure that there aren't any errors or warnings.

@sethladd

i.e., write more documentation

Unclear what this template would be.

To partially address the huge WSK template problem.

I think this would scan better:

• helloworld - the most basic command line app
• webapp - a basic HTML app
• publib - a library, with tests

with publib as package.

@sethladd

When we display the notice to users about the usage of analytics, we can link to http://goo.gl/6wsncI so they can learn more.

See also: https://github.com/yeoman/insight

Tracking bug to integrate stagehand into the Editor.

Would be great to have a Dart + Paper generator :)

• give the users notice about analytics tracking
• and give them the option to opt out of tracking

https://github.com/google/stagehand/blob/master/lib/analytics/analytics_io.dart#L58

An idea:

a tool (tool/upgrade_wsk.dart) that:

• git clones wsk into lib/generators/...
• patches an html file
• adds a dart entrypoint file

but the net-net is that we'll want to be able to track new versions of the WSK with minimal manual effort.

As requested by @devoncarew

To give users control, let's clear the client ID when the user disables analytics.

• How many projects have been created, and of which type

In the event there is no network connectivity, store events and crashes in a log file. Once network connectivity is restored, replay the log file and then clear it.

Curious, why is lib/stagehand.dart's setEntrypoint not a setter?

There's a tension now, as an instance of Generator is serving two roles:

• Descriptor of a particular generator
• The doer of the work of generating

This manifests itself when trying to use the projectName when creating files. Currently, the constructor is created at the beginning of the app, but the constructor is also where the files are declared. And we need to set a file name based on a particular run of a generator.

Mobile first!

Hi @devoncarew

Was thinking about names, and helloworld isn't that obvious to me. I think this is intended to be the template for command-line apps, so how about console or console-app ?

I.e., the last developer to change a template remembered to run ./grind build-templates.

This commit (https://github.com/sethladd/stagehand/commit/5c989da0f5470ba5a7f8deb28bf75e51b47d0a0f#diff-8aa4d80e74b2068bf0fa16749b5b03d0R69) introduces an explicit call to exit(int) in the cli tool. The tool itself is being tested as parts of our tests. Calling exit explicitly means that the tests (dart all/test.dart) can't run :(

@sethladd, fyi

See screenshot

For the library generator, we need to make pub.dartlang.org happy. To make pub.dartlang.org happy, we need:

homepage
authors

Perhaps others.

Default to BSD, just like Dart.

Mobile first!

We should create readme.md files for the created projects.

Adding the same boilerplate files into each generator subclass isn't great. Example: I had to add LICENSE to both helloworld and webapp.

Shouldn't Generator take care of that?

Seems weird that the user said 'awesome' but the script is bin/helloworld.dart.

@devoncarew any objections?

Complete with illustration and HOWTO stuff.

Look to get stagehand.io too?

Trying to use WSK and I don't think it's ready. It's OK to remove WSK for now, and we'll revisit.

For example:

Unhandled exception:
The null object does not have a getter 'bar'.

NoSuchMethodError: method not found: 'bar'
Receiver: null
Arguments: []
#0      Object.noSuchMethod (dart:core-patch/object_patch.dart:45)
#1      main (file:///Users/sethladd/tmp/error.dart:3:13)
#2      _startIsolate.isolateStartHandler (dart:isolate-patch/isolate_patch.dart:214)
#3      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:122)

Should at least be:

Unhandled exception:
The null object does not have a getter 'bar'.

NoSuchMethodError: method not found: 'bar'
Receiver: null
Arguments: []
#0      Object.noSuchMethod (dart:core-patch/object_patch.dart:45)
#1      main (error.dart:3:13)
#2      _startIsolate.isolateStartHandler (dart:isolate-patch/isolate_patch.dart:214)
#3      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:122)

Note that in line #1 that most of the file: path was removed.

Tracking bug to integrate the templates into the Chrome Dev Editor.

It would be nice to be able to have templates stored on disk as subprojects. It would make it easier to edit them and it would let us more easily include large projects as templates.

Both web apps and CLI apps would need to be able to load a template. We should do an experiment to see how feasible this is.

Related to https://github.com/google/stagehand/issues/2.

and display a message like "Version 0.2.5 is available! Run foo bar to get the latest.

To turn on analytics, we need a way to prompt the user and ask questions such as:

May stagehand anonymously report usage statistics to improve the tool over time?

It would be nice if stagehand could provide generators a way to ask for some info.

Is there anything we can do short term to remove some of the WSK size overhead? Drop a few fonts? Ideally it would be something that chops off a large percentage of the size w/o negatively impacting the template.

@blois has some ideas here