timriot
commented
12 years ago .ml JSON file to config asset folder (by default this is in the same directory as the PSD).
The configuration mechanism will search in the following directories and z-order:
/project (IE where the PSD exists on launch of the browser) /user home directory /app folder (a la presets) /app bundle
I would like to open a discussion here about the possibles options we have to make the export/save/ship happen. I think this is the most important part because we are producing files that devs are going to work on.
As discussed with @timriot during these months, the best scenario right now is a kind of template system, also using css preprocessors as stylus (my favorite) or less the one used by twitter bootstrap.
HTML5 integration and maintenance should be provided by http://html5boilerplate.com/
Javascript support will be provided (of course) by jQuery and at some point some binding data framework will come into play.
My opinion is that ml is just a possible ring of the chain, a tool that developers/designers can plug-unplug without destroying their actual workflow, and in order to succeed in this (big) goal we should integrate and work with as many open technologies as possible.
During the next meeting I would like to show to the team the way I usually work on my web project and my actual workflow, in order to start thinking about best practices and what ml should exactly ship to the user.
Open Question: How and where will export occur? If an explicit "save now" selection has to be made, is the magic of "no export" lost?