Speaking as an Action-writer, one thing that I often struggle with is
the balance between interface complexity and features. Freeway’s
Actions API doesn’t let you create parameters on the fly, so adding
features means that you have to predict every possible option and
provide a “slot” for it in your program. Even if you then hide all the
additional options so the interface doesn’t overwhelm, you can still
end up with more complexity (look at the many layers of CSS Menus
already) that your users then need to discover and manipulate.
Walter
On Mar 21, 2011, at 3:53 AM, Joe Billings wrote:
Hi Thomas,
We’ll take a look,
Joe
On 21 Mar 2011, at 07:29, Thomas Kimmich wrote:
Hi folks,
having actually a discussion about an external Desktop-App called
CSS3 Menu Maker:
Implementing the menus from CSS3 Menus is easy enough to accomplish. Making use of the action that uploads additional files (search: upload extra resources @ actions forge) not generated by Freeway makes it even easier.
Perhaps a quick tutorial about how to mesh the two apps together would assist others such as myself who are code challenged and find the features of CSS3Menus.com too inviting to ignore.