Developer mode and having widget changes written back to the filesystem

I'm just getting started with Widget development & the developer mode looks ideal for us being able to hook in version control & enable my team to work on widget development together. I've enabled it on my local PC (validated by seeing a Development option in the admin page);

I've got a few questions;

  1. If I find a default widget in the filesystem & make a change, that change is only visible in Widget Studio if I clear the app caches. Is that expected behaviour, or should the cache clear be automatic?
  2. When I make a change to a default widget via Widget Studio, the change isn't made to the files on disk (even after Publishing changes). Is that expected behaviour?
  3. When I make a change via Widget Studio & don't publish staged changes, I expected to be able to see my change in effect on pages where the widget was placed, but I don't, I only see the change when I publish changes.
    1. Maybe I'm meant to use the Preview option, but when I do that it pops up a message saying 'There are no pages configured to render this widget', which isn't correct, I can see that widget on a forum page and it has my previous edits applied to it.

The widget I picked on was 'Forums - Details', which is an easy change to validate on the site.

  • 1.  No we don't monitor the filesystem, really working in widget studio is the best as it will update the filesystem if you are running a custom provider in a Debug compilation mode

    2.  You can only change widgets for a provider in a debug configuration, which really means you only can modify widgets to the file level that you have access to compile source, so default widgets for community or other distributions would not be editable to the file system

    3.  This requires preview mode to be enabled in the front UI--it doesn't require following the preview link in widget studio.  This is under the pencil icon, Manage X Theme (X is the theme type for the page you entered the menu), Preview Staged Changes

  • After working with Telligent for a couple of weeks (2) was due to not having a Factory Default Provider.. once I'd got one of those the filesystem was being updated with widget changes as expected. That lets us hook in source control & do automated deployments to our Dev server.