Hi Tobias
Very long answer.
On Feb 9, 9:49 am, Tobias Beer <[email protected]> wrote:
> As fot applying a theme... got it. I totally overlooked that low-
> constrast toolbar.
I don't want the toolbar, to disturb the presentation.
> After having played a bit more with freestyle, I have a few questions.
As I wrote, any feedback is welcome. Thx. If I don't know, how others
see the project, there will be no improvement. It works for me :)
> Would it make sense to extent the drop functionality, such that one
> can not only set the name of that template element but also its main
> parameter(s), e.g. the width (or the corresponding emastic shorthand)?
See the UUUps down there first:)
There are 2 possibilities to edit the content.
1) The dropdown, that comes with the pen symbol, if you look at
the code of the portlet. Everything written there goes back to the
##Code section. At the moment you can't change the name of an element.
2) The box names are wikified. If you click them, the tiddler is
displayed.
*Function: .. I inserted this seciton, because I got lost several
times, when I didn't describe the function of an element.
*Code: .. There can be any code, like it is in the different TW
templates. See (1)
*List .. List of eg: boxes that are part of a colomn. This stores the
elements.
> You could easily implement a delimiter like "##" so one could input
> "name##width".
Code: example
*ColTopMene: <div class='dp100 topMenu'><list /></div>
**class='dp100' .. defines the width
**topMenu .. the class for CSS definition in stylesheet.
**<list /> .. gets replaced by the content of tiddlers listen in !List
more details can be found here:
[1]http://code.google.com/p/emastic/wiki/Tutorial
[2]http://code.google.com/p/emastic/ Demo section
UUUPs: As I had written the above text already, I understood your
sugestion, but I leave the text there.
eg: NewBox Popup got the name: NewBox##dp60##FunnyTiddler
Result: <div class='dp60' tiddler='FunnyTiddler'></div>
-> good sugestion !:)
> Why did you make it a two-click process to get to that "edit" button
> for the template-code? Are you intending to add more features to that
> top-left corner of the template-element-header? Otherwise.. why not
> open the code directly in edit mode?
The "down arrows" are intended to get an overview of the code
sections.
I thougt, the edit popup would be a good idea. (nice effect). But now
I know, that describing the function of a element is very important I
think editing the whole tiddler is more effective.
The button is still there because I does an automatic refresh.
> If I understand right, this is intended to be a designer to facilitate
> the creation of a template(-system?) which - in order for it to run -
> is then to be imported into a kind of emastic-ready-tiddlywiki
> (leaving the designer-bulk outside your "realworld tw")... which you
> prepare by importing what is listed in "needed components".
Yes.
I think I will prepare a default TW for that :)
> To understand the concept better, does a single "template" then
> consist of several template-element-tiddlers depending on, calling for
> and embedding each other upon display? ...or, would that rather be one
> big template to be imported? ..
One big Template, that is generated if you click "Create FreeStyle
Theme". eg. DefaultTheme is the whole theme. Because I started to work
with MonkeyPirate TW It has exactly that structure, to be used with
SelectThemePlugin.
> .. My current guess is to import all tiddler
> created during the design process ...all that which I thus gave a
> certain template-name, correct?
eg: You want a Theme named: MyTheme.
The "New FreeStyle Project" button asks for a name: "MyTheme"
and creates: "MyThemeProject"
The "Start FreeStyle Project" creates: "tmpDefaultThemeProject"
And finally the "Create FreeStyle Theme" button creates the "MyTheme"
tiddler. That is the one of desire!!
I wanted to automatically delete the tmpXXX tiddler. But it turns out,
that it is easy to find an existing project by typing "tmp" into the
GotoBox and get a list of all existing "playgrounds".
> Also, is it possible with this emastic system to "live-swap"
> templates, e.g. to call an alternative "left-column" depending on a
> certain tag? If yes, how?
I think, this is not a matter of the grid system. I could extend my
SelectStoryMacro (see the blue sqares in MainMenu). Or you can use
Erics TaggedTemplateTweak, to switch the template, by a certain tag.
> In my thinking, all these boxes "only" make much sense if there are
> ways to trigger "context sensitive" content. ..
Yes in my thinking too. But I think, it needs some more plugins. I
didn't find the core functions for that.
> .. Meaning, for example, if
> I had some context-box in a right column and I opened a certain
> tiddler in what one might call the main-content-box, I would want for
> that context-box to be flexible, such that its content depends on what
> is displayed in the main-content-box. ..
yes
>..One could easily imagine
> something alike for a kind of context-sensitive topmenu. Without such
> context-sensitive triggering, ..
yes
> ..the whole emastic grid seems to merely
> display static content. ..
Since FreeStyle can use _any_ grid system, to make the whole TW UI
more flexible, I don't second this statement. I think "It's merely
a matter of time, to have more functions".
Have a look at EditTemplateDesigner. Move the taggerBox on top of the
body. create a new theme. reload. done.
Or tmpDefaultThemeProject. You can drag the left menue column to the
right side. Drop the index panel below the main menu if you want.
Create a new theme. reload. that's it. I have read many posts about
these topics. It's easy now.
The only thing to do is, to get some more boxes with definitions for
the different plugins.
AND my maingoal: get FreeStyle working an TiddlyWeb / TiddlySpaces
for group editing.
> .. Well, one might try and do some DOM-inspection
> in the respective box to figure out which tiddler is being displayed
> in another one (and their properties, such as tags). After all, this
> context-sensitivity is what I would consider the main reason for using
> such a template system.
There is a very nice feature in the TW5 alpha, where a View/
EidtTemplate has an accapt parameter. (eg: accept documentation) What
I prefere, would be a dynamic link, between any tiddler list and any
box.
eg:
Drag a tiddler from timeline to the box.
The box tells you: "This tiddler has 3 tags: X Y Z!. If you drag the
next tiddler for 20 px in any direction and release it, it will be
opended by me! Which tag is for me?" That would be a cool function.
Some thoughts
Or a chain of boxes, that work together, because the life in the same
column. eg:
<div class='workWithBoxMaster' tiddler='##AnySection' macro='view
text'></div>
<div class='workWithBoxMaster' tiddler='##AnySection' macro='edit text
with: MinEditTemplate'></div>
Adding a Viewtemplate to any box (but I didn't figure out, how that
works)
> Hope I didn't bombard you with too many questions. ;-)
No problem. Your (and more) feedback is very welcome!
kind regards
Mario
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/tiddlywiki?hl=en.
