On Mon, Jan 5, 2009 at 7:19 PM, Vincent Massol <[email protected]> wrote:
>>
>> I guess this could be done with a suggest input at the bottom as seen
>> in the link dialogs mockup.
>> I suggest to put this in the "possible improvements to keep in mind"
>> category since it's a power user need and we don't have that much
>> macros ftm.
>
> I'm pretty sure this is not a power user feature. It's like saying
> search are for power users... Google.com has probably proven it's not
> the case :)
Let me rephrase : since we'll have between, let's say, 10 and 30
macros I think having a search feature is overkill and will be useful
only to power users.
>>> * Rendered macros
>>
>> We must support them as well as "placeholder macros" IMO.
>
> I don't understand what a "placeholder macro" is (did you mean "macro
> placeholder"?). Maybe you mean a "placeholder mode" which can be
> toggled on/off. If so would be nice to include it in the UI proposal
> to see where it would be located.
>
I meant "macro placeholder", a graphical box (read-only div) appearing
in the wysiwyg instead of the rendered macro.
Macros arguments would be displayed in the same order and with the
same labels as in the edit dialog.
It wouldn't be configurable by the user, the macro itself would
determine if it should be displayed rendered or by a placeholder in
the WYSIWYG.
Examples :
--------------------------------------------
| Macro -- include |
~~~~~~~~~~~~~~~~~~~~~~~~~
| page : Main.WebHome |
--------------------------------------------
--------------------------------------------
| Macro -- map |
~~~~~~~~~~~~~~~~~~~~~~~~~
| location : 10 rue Pernety |
| service : google |
| message : test message |
| size : default |
| zoom : default |
--------------------------------------------
>>> * Outline around macro block when cursor is inside a macro rendered
>>> content
>>
>> I think we should always keep this outline to have a visual hint for
>> "everything in this box is not editable".
I think it would be even more clear if the rendered macros were
represented within a box like the ones above (just an idea, I don't
know if it is doable) :
--------------------------------------------
| Macro -- Table of content |
~~~~~~~~~~~~~~~~~~~~~~~~~
| |
| Rendered HTML |
| |
--------------------------------------------
WDYT ?
>>> * When is the rendered macro content refreshed? Manual refresh
>>> button?
>>> (the easiest I think)
>>
>> From the thread linked aboved I understood that we'd have to refresh
>> the whole page ? Do you suggest to have a top level refresh button or
>> did I missed something ?
>
> That's what we had discussed. Now I don't see that button in your UI
> proposal.
>
I'll make a proposal for this ASAP.
>>> * What about macros that take a lot of space like an {{include}}? Do
>>> we offer a button to "fold"/"unfold" macros?
>>
>> I think this is the kind of macro that should be represented by a
>> placeholder. Has stated in a previous thread having included document
>> displayed inline in the editor would distract editors from the page
>> content itself. This will be also needed by other macros like "map"
>> (mentioned by Jerome) where having an iframe in our WYSIWYG iframe
>> could be a problem and, if not, performance would certainly be.
>
See the ascii art above.
Thanks,
JV.
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs
