Dear All,
It's been a while since last update. I had been, and still will be, busy on
a big event here at the end of this month. Yet I managed to find time over
the long weekend to do some works on the plugins. The alpha-3 file is
available at
https://dl.dropbox.com/u/23745840/pre_release-1.5.0-alpha-3%2B0.7.7.html.
Comments/Suggestions/Bug reports are always welcome!
I plan to release 1.5.0 on Feb 08, one day before the Chinese New Year's
Eve. In this coming version most of the block elements -- tables, lists,
headers, foldable contents (with FoldHeadingsPlugin), preformats,
blockquotes, and blockexamples -- shall be editable. The name of the
TWtable plugin shall be changed to TWtid (TW tiddler) in accordance with
the feature expansion. TWted retains its name with a different meaning --
*tiddler
editor* instead of table editor.
Main changes in alpha-3 are
1. Move list items with Ctrl-up/down keys.
1. Still primitive, please find bugs and tell me about them.
2. Moving elements is complicated with the current code structure. I
plan to rewrite some parts of the codes to make it simpler.
2. Added option chkTWtedInViewMode (default to true) to toggle editing
manner.
- If set to true (the default), one can edit those editable elements
in TW's view mode while keeping the default edit box in edit mode the
same
old way.
- Otherwise the view mode remains just for viewing, and TW's default
edit box is replaced with a WYSIWYG-like editor.
- In this manner one can still bring back the default edit box by
one of the following ways,
- disable TWtable or TWted (re-enable to enter the WYSIWYG-like
mode
again),
- double-click in a no-element area (click away/Ctrl-Enter/Esc
to go back to WYSIWYG-like mode).
3. Bug fixes for partial transclusion synchronization.
4. Bug fixes for locating a missing cell.
Have fun!
Vincent
On Thursday, December 13, 2012 11:17:49 AM UTC+8, Vincent Yeh wrote:
>
>
> Thanks for the feedback, Ton and Yakov, I will take them into
> consideration for sure.
> I'll be busy and won't be doing much on these plugins for several weeks,
> we'll talk later.
>
> Vincent
>
> On Wednesday, December 12, 2012 9:32:46 PM UTC+8, TonG wrote:
>>
>> Hi Vincent,
>>
>> I played around with your latest prelease and can see future
>> possibilities.
>> On the other hand it would be nice to just have a no frills table
>> editor. Table editing was always very difficult in TW and is now a
>> pleasure with your plugin(s). I'am using the (stable) version 1.4.6
>> daily and there I only miss the keyboard navigation you already
>> implemented in prereleases. A (stable) 1.4.x release with added
>> keyboard navigation would be much appreciated.
>> I second Yakov's remarks about the Edit mode in the prerelease: do not
>> combine general editing with table/headings/list editing. As Yakov
>> already stated: there is no fallback anymore (at the moment you cannot
>> even edit body text).
>>
>> Cheers,
>>
>> Ton
>>
>> On Dec 11, 12:21 pm, Yakov <yakov.litvin.publi...@gmail.com> wrote:
>> > Hello :)
>> >
>> > > Good timing!
>> >
>> > Indeed!
>> >
>> > <<<
>> > Well, during development I noticed that clicking a link can trigger two
>> > actions: opening the link and the edit box, due to event bubbling. But
>> I
>> > didn't like it that way so I introduced the option to restrict it to
>> one
>> > action, either opening the link or opening the edit box. Now I know
>> that
>> > two actions can be expected in some cases, I will figure a way to put
>> it
>> > back.
>> > <<<
>> >
>> > No-no-no, two actions were expected but they are not desired, so
>> everything
>> > is fine. I just want to be sure that there wouldn't be two actions in
>> some
>> > untested situations, that's what I was talking about. But as I
>> understand,
>> > you basically stop bubbling the onclick event, so that shouldn't happen
>> > anyway, right?
>> >
>> > The new alpha looks good, but I have one important question: why did
>> you
>> > move inline editing into the edit mode? On the one hand, inline editing
>> has
>> > this nice feature that one doesn't need to scroll up to the menu --
>> well,
>> > double-click now makes editor open right in place, but to close edit
>> mode
>> > one has to scroll up and click "done"/"cancel"; on the other hand, with
>> > usual edit mode, one has a usual fallback to edit what is unsupported
>> for
>> > now. I think
>> > * the ordinary edit mode shouldn't be hijacked, but rather two options
>> > should remain
>> > * there should be an option to be "permanently in the inline edit
>> mode",
>> > like it was implemented before
>> >
>> > Best regards,
>> > Yakov.
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>>
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/tiddlywiki/-/CK-hs3Gjf0sJ.
To post to this group, send email to tiddlywiki@googlegroups.com.
To unsubscribe from this group, send email to
tiddlywiki+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/tiddlywiki?hl=en.
