I'll also throw in my attempt to the ring. Or "pre-ring" perhaps I
should say. ;) I like the overall layout of Ben's template 9, but I
think that the graphical elements are too heavy, drawing too much
attention.
I took Ben's original template-9 and applied some concepts I've been
thinking, reading, etc. about. Bradford Paley has a lot of really
good things to say about interface design, outlined in this talk:
http://atlas-real.atlas.uiuc.edu:8080/refmov/ncsa/2005-11-04-0800pm.asx
(FYI: you can rip the stream with VLC, then watch it at 1.25X speed,
since he speaks with a lot of pauses).
Therefore, I made the 'structural' elements in the background as much
as possible to make the examples and text come forward. The color on
the header is to mark the patch as a help/reference patch, versus a
tutorial or all_about patch.
http://eds.org/~hans/template-HCS.png
.hc
On Sep 17, 2007, at 5:02 PM, B. Bogart wrote:
Hi Marius,
Thanks for taking the dive and contributing ideas to the wiki. I'll "strike" that task from your todo list. How is the wiki template
going?I think the discussion about externals was well played out, what have you ended up deciding? (Will your stylesheet system work on vanilla
PD 40?)I am a little confused about the purpose of these templates though,
as I thought you had issues with the way the information was structured in previous templates (and the over use of canvases) and now I see you
have even more canvases (cnv)!Here is some feedback:
- I think the idea of the stylesheet is a good one, especially as it
works for multi-lingual PD. Of course the comments would still be unilingual without lots of extra effort.
- Where did the three panel layout come from? Having two columns
for the content does not really flow well, as they are different sizes. The extra space for the patch area is nice, but I think most examples need more vertical space than horizontal, even with template 11 the example patch is still floating in a lot of empty space. See template 6 for an example of another alt design that had a bigger patch area.
- The purpose of the canvases in the previous templates is to break up
the content, so that are all the width of the text area or so, when
they are too short they no longer serve to break up the content because
they need to have more emphasis on the text.
- All in all I don't see any improvement of this design to template
11, Would you consider making template 11 stylesheet compatible?
See my other message about GOPing pddplink.
Great to see all this effort! :)
.b.
marius schebella wrote:
hey, just finished my templates. I did not concentrate so much on
content and layout, but on the question how to make different patch layouts with stylesheets. I think it is a good idea to make styles as flexible as possible. https://www.puredata.info/dev/pddp/pddp-drafts So what you see is one patch where you can switch between different styles. The style definitions are in a seperate textfile and control primarily canvases and text (but you can add your own style
definitions for guis...). You can set colors, fonts sizes, positions. please play around and create your own layouts! The layouts are rewritten everytime you open the patch, so you don't have to worry to overwrite when you save a patch. Besides the changes on gui objects, it is also possible to switch headers and footers (or create additional patches). They are GOPs and are scripted during runtime (when you open the patch). they can
change their appearance dependent on things like language settings,
operating system. But GOPS only support gui objects and comments, I really miss support for images and pddplink. you will need iemlib, zexy, pd 0.39. I only tested them on mac, so I would like to hear feedback about
other os. thnx. marius.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
Using ReBirth is like trying to play an 808 with a long stick. - David Zicarelli