You are using a PDA or a related web browser. In order to view the Web site in its entirety, please use a suitable web browser. Only important content provided.
Thursday, July 24, 2008
français (France)

Blog

Discover all blog entries : Subscribe to our blog

Note for designer which would like to skin ModuleWorkFlow bar now

Blog entry by Host Account

If you plan to make a new design for this toolbar, just wait for the next release which will come very soon. I manage to integrate toolbar differently from W3C valid xHTML and CSS : this will be realized using a whole new DIV architecture. For more, a skin selector will be introduced at the same time, and, in kindly hope, tutorials, tips, and skin samples. If you want to make a design for the next version, just the me a screenshot at sebastien.fichot@aricie.fr ; then I will check the structure to be sure than your design will be realizable.

The coming DOM structure will probably be something like this, with float, inline, pixel fixed width CSS attributes :

 

  <div id="modulewokflow_wrapper">
    <div class="modulewokflow_wrapper_content">
      <div class="modulewokflow_top_wrapper">
        <div class="modulewokflow_bar">
          <div class="left modulewokflow_bar_0"></div>
          <div class="left modulewokflow_bar_1">
            <!-- Control state 1 goes here -->
          </div>
          <div class="left modulewokflow_bar_2">
            <!-- Control state 2 goes here -->
          </div>
          <div class="left modulewokflow_bar_3">
            <!-- Control state 3 goes here -->
          </div>
          <div class="left modulewokflow_bar_4"></div>
          <div class="left modulewokflow_bar_5">
            <div class="bar_swapper_control">
              <!-- SectionHeads goes here -->
            </div>
          </div>
          <div class="top_swaps">
            <div class="bloc" id="swap_1">
              <!-- Control Info goes here -->
            </div>
            <div class="bloc" id="swap_2">
              <!-- Control Comments goes here -->
            </div>
            <div class="bloc" id="swap_3">
              <!-- Control Actions goes here -->
            </div>
            <div class="bloc" id="swap_3">
              <!-- Control Localization goes here -->
            </div>
            <div class="clear">&nbsp;</div>
          </div>
          <div class="clear">&nbsp;</div>
        </div>
      </div>
      <div class="module_wrapper">
        <div class="bloc">
          <!-- Control Module goes here -->
        </div>
      </div>
      <div class="bot_wrapper">
        <div class="bloc bottom1">
          <!-- Control CustomBlogActions goes here -->
        </div>
        <div class="clear">&nbsp;</div>
      </div>
      <div class="clear">&nbsp;</div>
    </div>
  </div>

This should be probably templatizable in the coming release.

 

Cheers,

Sébastien Fichot - Développeur

How to install ModuleWorkFlow external provider ?

Blog entry by Host Account
ModuleWorkFlow is an extensible module, of which the use can be shared on several modules by the use of providers, which contain the instructions of data formatting for a standard module or a group of module. Let's see how to install an external provider for ModuleWorkFlow.

We to date provide several providers, including one provider by default allowing to use the Core modules with ModuleWorkFlow, but also the providers for:

* - Engage Publish: A very powerful manager of articles.
* - DnnForge News Article: A manager of article also.
* - Opt - in email: A very complete manager of newsletter.

This list of module supported should grow soon. We will provide very soon a guide detailed to help you to build your clean providers and to extend the capacities of your module.



Here procedure to follow to install an external provider:

1. - Ensure that your Dotnetnuke installation including/understanding ModuleWorkFlow and the third module functions,
2. - Download the provider ModuleWorkFlow associated from the download tab on our site,
3. - Decompress the zip file and place the DLL in the repertory bin/of your Dotnetnuke application,
4. - Edit the file \ DesktopModules \ Aricie.ModuleWorkflows \ Aricie.ModuleWorkFlows.Providers.config with a text editor.
5. - Add the file contents to the associated provider section.
6. - You should now be able to encapsulate a module whose type is supported by the provider that you have just installed.



We will develop for a coming version a provider manager, which will simplify the management and the installation of this type of external components.
We will speak about it here, therefore, remain connected on Aricie blog!