Subject: KampalaMeetingLog2016x09x01.txt Date: September 1, 2016 at 4:22:51 PM PDT [15:38] == peterthoeny__ [46d50276@gateway/web/freenode/ip.70.213.2.118] has joined #twiki_release [15:38] hi HideyoImazu-san [15:38] Hi Peter [15:38] my apologies for the delay [15:39] no worries [15:39] we had an emergency at work that needed my attention [15:39] what is new? [15:39] I'm in Shanghai on a business trip. [15:39] ah [15:40] Alipay everywhere [15:40] harald is in italy in vacation [15:40] even street vendors take Alipay [15:40] aha, good [15:40] progress [15:40] little chance for Apple Pay to become common, it seems [15:41] unlike in the usa that still pays by handwritten checks (we just sent signup fee for rocket event that way) [15:41] it's not as smooth and elegant as Apple Pay [15:41] alibaba has pretty much a monopoly in china [15:41] one time where a monopoly is good for consumers [15:41] but it's working at a huge scale [15:43] not much news on my side [15:43] just working on latest rocket [15:43] :) [15:43] and taking moe photos [15:44] my keyboard is dying, the down arrow no longe works, and the r key needs special pressure [15:44] the keyboard on your laptop? [15:45] let's start [15:45] macbook pro [15:45] http://twiki.org/cgi-bin/view/Codev/KampalaReleaseMeeting2016x09x01 [15:45] i'm using macbook pro now. [15:46]  1. Feature Requests for Kampala Release, 2. Extensions, 3. Review Urgent and Not So Urgent Bugs, 4. TWiki Roadmap Discussions, 5. Miscellaneous [15:46] ah nice [15:46] ---+ 1. Feature Requests for Kampala Release [15:46] http://twiki.org/cgi-bin/view/Codev/WebChanges [15:47] http://twiki.org/cgi-bin/view/Codev/TWikiPersonal [15:47] harald created a new version [15:48] ah, fixed i18n [15:48] http://twiki.org/cgi-bin/view/Codev/VarEDITFORMFIELDwithTextarea [15:48] by PTh [15:48] this is now in svn trunk and 6.0 branch [15:49] ok [15:49] that is all on features [15:49] anything else? [15:49] have you played around with TWikiPersonal? [15:50] no, not yet [15:50] you? [15:50] no [15:50] ---++ 2. Extensions [15:50] http://twiki.org/cgi-bin/view/Plugins/WebChanges [15:51] bug report in SyntaxHighlightingPluginDev for SyntaxHighlightingPlugin [15:51] i'll follow up on that [15:51] nothing else [15:51] anything? [15:51] I've been thinking to improve rendering of the plugin [15:51] SyntaxHighlightingPlugin [15:52] ah [15:52] at least, the code should be copy-able [15:52] what kind of improvements? [15:52] ah, yes, line numbers interfere [15:52] it's a bit of a shame [15:53] maybe easily doable with some jquery to hide/show toggle the line number column [15:53] not sure jquery is necessary [15:53] a button at the top to toggle show/hide [15:54] advantage of jquery is that no server roundtrip needed to show/hide [15:54] it's not so difficult to avoid line numbers being copied [15:54] many blogs and web sites showing codes with line numbers are doing it [15:54] how? if html table you don't have control over copy region [15:55] i don't remember how exactly, [15:55] but that's easily doable. [15:55] interested in learning how [15:56] with div layout you can't predict the height of a coding line (it might wrap) [15:56] probably the way to render code needs to be changed drastically from the current way. [15:57] so how to keep line number div at same height as code line div? [15:57] I don't remember. [15:57] you can see it on github and other places [15:58] ah, http://stackoverflow.com/questions/8957443/prevent-copying-text-in-web-page [15:58] user-select: none; [15:58] ah [15:59] i can be only a matter of css change [15:59] to hide line number cells from copy; not sure though if that works [15:59] that way I wasn't aware [16:00] ah, here is exactly our use case: [16:00] https://danoc.me/blog/css-prevent-copy/ [16:01] "I was recently helping a coworker build a code diff viewer that supports line numbers, wraps text properly, and prevents line numbers from being copied when selecting the code." [16:01] that looks like the ticket [16:01] ---++ 3. Review Urgent and Not So Urgent Bugs [16:02] http://develop.twiki.org/~twiki/cgi-bin/view/Bugs/WebChanges [16:02] nothing noteworthy of what we did not cover already [16:02] anything? [16:02] no [16:03] ---++ 4. TWiki Roadmap Discussions [16:03] roadmap at: [16:03] http://twiki.org/cgi-bin/view/Codev/TWikiRoadMap [16:03] current release focus at: [16:03] http://twiki.org/cgi-bin/view/Codev/KampalaRelease#Release_Focus [16:04] i think release focus is pretty much where i think we should focus [16:04] primarily on app platform [16:05] drag and drop on the attach screen is already there [16:05] the roadmap is very broad [16:05] ah, yes [16:05] in 6.0.2, which is pre-Kampala [16:06] yes [16:06] i am way behind with app packager [16:06] image drag and drop on wysiwyg would be greate [16:06] yes that would be nice [16:07] improving wysiwyg is a lo of work [16:07] blogger is doing it [16:08] one item missing on the list: realtime update of content, e.g. simultaneous edit of content [16:08] like in g docs and g sheets [16:09] a wiki is collaborative, so simultaneous edit is a good fit [16:09] I think it requires a major overhaul [16:10] that I agree [16:10] well, we almost have it for tables with the new twikisheetplugin [16:10] it's still with polling instead of websocket [16:10] once we use websocket the changes are in near real time [16:11] google doc/goole sheet like simultaneous editing should require a complete rethinking of the platform, I suppose [16:12] well, it could be an additional button: "Simu Edit" [16:12] or as a radical idea, a twiki page is always in edit mode, like in g docs [16:13] less radical is a new simu edit button [16:13] and twiki page will be heavily javascript [16:13] yes [16:14] do you see any poblem with this? [16:14] not a problem with that kind of features [16:14] it would be a departure fom twiki's very minimal env requirement [16:14] but my gut feeling is we should first work on a simultaneous editing platform/core [16:15] without thinking about current TWiki [16:15] i solved it already with twikisheetplugin (polling instead of websocket) [16:16] ok. maybe I need to look into it more. [16:16] it would require running a websocket server that gets update requests, updates content and sends update requests to all listeners [16:16] for some reason, it's not working with my custom skin [16:17] oh [16:17] wondering why [16:17] css/javascript issue [16:18] if you use default skin it works? [16:18] I can make it sort of work by manually tweaking a page with F12 on a browser [16:18] wondering if packaging issue [16:18] with pattern skin, no problem [16:18] ah [16:19] time check: +79 min [16:19] I need to have breakfast and then pack my luggage to check out [16:19] (well, delayed start) [16:20] ok, let's close the meeting [16:20] i'll post the logs and minutes [16:20] have fun in shanghai! [16:20] thanks and ttyl [16:20] ttyl HideyoImazu-san