Problems with auto mode

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Problems with auto mode

LightGuard
Administrator
Since we're starting to see greater adoption of awestruct, both internally at Red Hat and also externally by technical and nontechnical people alike, auto mode and dependency tracking are going to become more and more of a problem if they don't function as people would expect. I'm writing this in hopes of getting some people to help, or to at the very least talk about some ideas.

I know of the following issues with auto mode/dependencies:

1. Partials aren't being tracked, so a change to a partial doesn't cause pages including the partial to be re-rendered.
2. Changes to FrontMatter aren't taken into account. If you change the front matter for a page, you have to restart awestruct
3. Changes to extensions aren't run until a full run of awestruct. Those of use creating extensions have to completely regen the whole site to see changes to extensions, this can be time consuming and tedious, especially on large sites.
4. Changes to Sass includes aren't causing regeneration (possibly LESS as well).
5. New files are not reflected in the regenerated output.

If there are others I haven't listed, please let them be made known so we can address them as well. These things are either big enough to cause 0.5.2 to wait (which I'd rather not do, partials are the last remaining issue in 0.5.2) or to be the main focus in an 0.5.3 (we can bump the current two issues). I'd like some feedback from all of you about that.

Fixing these things may mean a complete rework of the generation process, I'm hoping not, but it's possible. We may also need to expand or rework the current dependency implementation.

--
Reply | Threaded
Open this post in threaded view
|

Re: Problems with auto mode

LightGuard
Administrator
I've added to https://github.com/awestruct/awestruct/wiki/Dependency_Tracking in hopes of kick starting the discussion


On Mon, Jun 10, 2013 at 3:14 PM, Jason Porter <[hidden email]> wrote:
Since we're starting to see greater adoption of awestruct, both internally at Red Hat and also externally by technical and nontechnical people alike, auto mode and dependency tracking are going to become more and more of a problem if they don't function as people would expect. I'm writing this in hopes of getting some people to help, or to at the very least talk about some ideas.

I know of the following issues with auto mode/dependencies:

1. Partials aren't being tracked, so a change to a partial doesn't cause pages including the partial to be re-rendered.
2. Changes to FrontMatter aren't taken into account. If you change the front matter for a page, you have to restart awestruct
3. Changes to extensions aren't run until a full run of awestruct. Those of use creating extensions have to completely regen the whole site to see changes to extensions, this can be time consuming and tedious, especially on large sites.
4. Changes to Sass includes aren't causing regeneration (possibly LESS as well).
5. New files are not reflected in the regenerated output.

If there are others I haven't listed, please let them be made known so we can address them as well. These things are either big enough to cause 0.5.2 to wait (which I'd rather not do, partials are the last remaining issue in 0.5.2) or to be the main focus in an 0.5.3 (we can bump the current two issues). I'd like some feedback from all of you about that.

Fixing these things may mean a complete rework of the generation process, I'm hoping not, but it's possible. We may also need to expand or rework the current dependency implementation.

--



--
Reply | Threaded
Open this post in threaded view
|

Re: Problems with auto mode

Torsten Curdt
In reply to this post by LightGuard
I fear this will be quite some work to fix, too.
But I am with you - it needs to be done.
It's awfully annoying like it is atm.

cheers,
Torsten

---------------------------------------------------------------------
Archives: http://talk-archive.awestruct.org/
To unsubscribe, e-mail: [hidden email]