Thomas Schmidt schrieb:
> Re-sending message, because it did not make it to the
list.
>
> -------- Original Message --------
> Subject: Idea for improving swamp overview page
> Date: Sat, 24 Mar 2007 23:41:29 +0100
> From: Jürgen Pabel <jpabel akkaya.de>
> Organization: Akkaya Consulting GmbH
> To: swamp-devellists.sourceforge.net
>
> Hi all,
>
> I just took a look at the "home page" layout
in 1.5.5 and I must say
> that moving the workflows from the side menu into the
"content" section
> of the page is a good idea as it will allow for
installations with lots
> of workflows to be more user friendly. However, I would
like it if the
> workflows could be grouped - maybe in a tree structure,
where the
> overview page would only show the top level groups (or
workflows, if
> they are at the top level) and allow for the user to
expand those groups
> (tree items). A rough example of what we aim to
accomplish with swamp
> (and why such a grouping would be nice):
>
> - Development (Group)
> - Meeting (Workflow)
> - Build/Package version (Workflow)
> - ...
> - Testing (Group)
> - Deploy onto Test-Servers (Workflow)
> - ...
> - Product (Group)
> - Evaluation (Group)
> - Generate Evaluation-Key (Workflow)
> - Mail Demo CD (Workflow)
> - Order (Group)
> - Create Order (Workflow)
> - Generate Product-Key (Workflow)
> - Support (Group)
> - Handle incident (Workflow)
> - ...
>
> I think that the group membership should be a new
element in the
> workflow definitions - and the tree be generated
dynamically from that.
> It might also make sense to allow for multiple group
definitions in
> order to allow workflows to appear in different
locations of the tree.
Hi, that's a good idea, I will put this on my todo list.
Maybe we need an additional config file to define the
available groups.
>
> Also: I've quickly searched the mailing list but did
not find anything
> about i18n of workflows - are there any plans to add
support for
> languages to workflows (so that the workflow can
"render/run" in the
> language of the viewer/workflow starter)?
The current i18n only includes swamp and webswamp, texts
that come from
the workflow definitions are not translated. We thought this
is enough
as a first step,
because foreign installations can write the workflow
definition in their
language.
To enable i18n of workflow definitions we could either:
- Use the gettext approach of swamp with .po files for each
workflow.
For that we would need a script that greps the strings to
be
translated from
the workflow definition file and creates a .pot file
- Allow each language specific element of the workflow
definition to be
flagged with a
language (lang="de"...)
- ...?
Greetings
--
Thomas Schmidt (tschmidt [at] suse.de)
SUSE Linux Products GmbH :: Research & Development ::
Internal Tools
"Don't Panic", Douglas Adams (1952 - 11.05.2001)
------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
swamp-devel mailing list
swamp-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/swamp-devel
http://swamp.sf.net
|
