#foswiki 2015-09-08,Tue

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)

WhoWhatWhen
rouiljWhat's the current best way to add tagging of pages to an existing web?
looks like tags plugin, tagme plugin and classification plugin are possible choices. I want to use it in a NatSkin environment.
I think I used the TagMe Plugin with an older twiki install at my last job, well tried to use it. My boss deemed it ugly and moved it from the top of the page to the bottom of the page where nobody ever saw it or rated anything. (plus one of the tags was obsolete, so people never saw it and thus got old outadtaed info with no warning).
however tagging was orthogonal from the normal search and not as useful. I don't have Solr search installed on the new foswiki I want to install tagging on.
But having if Solr search will make tags and searching work together better, I'll see about installing it.
Looks like Classification plugin is trying to take over the whole web and I am not sure how well it will work with an existing web structure.
[00:35]
........................................................ (idle for 4h39mn)
***ChanServ sets mode: +o CDot [05:21]
..................................... (idle for 3h3mn)
ChanServ sets mode: +o MichaelDaum [08:24]
...... (idle for 28mn)
GithubBot[distro] cdot pushed 1 new commit to master: http://git.io/vZqg0
distro/master d2517b1 Crawford Currie: Item13583: need to correctly encode special macro used in the login form
[08:52]
***GithubBot has left [08:52]
FoswikiBothttp://foswiki.org/Tasks/Item13583 [ Item13583: Login form populated with incorrect path info ] [08:52]
................................... (idle for 2h51mn)
LavrMichaelDaum. The SlideShowPlugin cannot scroll anymore. That is a huge problem because most slideshows made by normal people has one or more slides that are too tall and then people need to scroll down a bit.
How do we get the scroll slider back in the browser?
I have tried to remove overflow:hidden !important; but the scroll bar is still invisible.
[11:43]
MichaelDaumthats a new feature
scrolling slides might have been okay on the old slideshowplugin but wasnt intended to be supported
[11:57]
LavrIn real life slides are often longer than the screen height. People need to be able to scroll vertically [11:59]
MichaelDaumMichaelDaum never seen anybody scrolling slides in my academic career [11:59]
LavrTry the real world [12:00]
MichaelDaumpatches welcome [12:00]
LavrI am trying to fix it but I cannot get them back. Where is it disabled? I assumed first it was the css
html {
overflow:hidden !important;
background:#ff
[12:00]
MichaelDaumshow me one presentation on http://www.slideshare.net/ that has scrolling slides ... ;) [12:01]
LavrI have a conference call. Will come back.
The hour after this a PM will show a slideshow where 3 of his slides needs scrolling.
A schedule with milestone
s
A metric page with two graphs and they are too tall
And yes he should split it but normal people don't!
[12:02]
MichaelDaumscale the content to max-height:100%
btw powerpoint scales up/down font-size based on the number of rows ... to prevent the text to overflow at the bottom.
slides are made to fit on one screen
[12:04]
***ChanServ sets mode: +o Lynnwood [12:09]
MichaelDaumI'll try a patch [12:11]
***ChanServ sets mode: +o gac410 [12:23]
...... (idle for 27mn)
LavrI am back from my meeting [12:50]
gac410MichaelDaum did you see Item13684 - yet another extension runs into cUID _xx issues. :( [12:58]
FoswikiBothttp://foswiki.org/Tasks/Item13684 [ Item13684: Solr Full Index Crashes with ERROR ] [12:58]
MichaelDaumLavr, could you file a bug item. got the fix already done. there were some more bugs fixed on the way, i.e. an occasional jQuery not defined javascript error [13:04]
LavrMichael http://foswiki.org/Tasks/Item13685 [13:05]
MichaelDaumSpreadSheet -> SlideShow [13:05]
LavrDarn sorry [13:07]
gac410already fixed it
( the typos, not the bug :) )
[13:07]
LavrI double fixed it [13:08]
gac410hm How did that happen? Page cache still give you the old version? [13:08]
LavrThe use cases I have are typically where a project manager shows a schedule with milestones in a table. And the number of milestones depend on 2-3 topics where major milestones are marked as Italic. So you never really know how many show up
Another is a list of level A and B defects. Some weeks that list overruns a page
And customer complaints listed can also overrun. Especially when some engineer has written a "War and piece" type status update
We have a "crawl-chart" metric page where an engineering team uploads a png file. And sometimes they make it taller than they should. Then we have to scroll down 5% to see the X axis. Lots of silly examples.
When people make a nice presentation they do not use Foswiki at all. We use it for meetings where we show dynamic content to management. That is where Foswiki really shows its value because the project managers....
can go unprepared and just show an autogenerated presensation with schedules and metrics and bug lists etc
[13:09]
MichaelDaumMichaelDaum checking in the fixes to slidepe [13:16]
LavrThat is super Michael! Thanks. [13:16]
MichaelDaumeven our beginners start here slideshow had overflows due to lengthy slides [13:17]
GithubBot[distro] MichaelDaum pushed 2 new commits to master: http://git.io/vZm1L
distro/master 3d2b20b MichaelDaum: Item13685: added support for scrolling slides...
distro/master efdb83e MichaelDaum: Merge branch 'master' of github.com:foswiki/distro
[13:24]
***GithubBot has left [13:24]
FoswikiBothttp://foswiki.org/Tasks/Item13685 [ Item13685: SlideShowPlugin no longer allows scrolling down when the page is a little longer than the display ] [13:24]
LavrJust pulled in the git update. I still cannot scroll [13:26]
MichaelDaumyour slidshow.js and slideshow.js.gz are probably outdated [13:26]
LavrAh I need to re-pseudo install? [13:27]
MichaelDaumy [13:27]
LavrSo that is why my attempts lead to nowhere [13:27]
gac410hm Aren't your pseudo-installed files just symlinks? Or is it copying. [13:29]
LavrMichael. Great fix. Scroll bars only show when you need them and you only scroll within current slide. Much better than the old 1.1.9 SlideShowPlugin.
I can see that I should update my default slide template to something close to the BeginnersStartHere. Very nice with the buttons fixed to the bottom
[13:30]
MichaelDaumat least it doesnt look foolish anymore ... fit for purpose [13:33]
Lavryes. Really cool now. Thanks [13:33]
gac410Hi all ... anything left needed for 2.0.2 or should I go ahead with the build? [13:47]
LavrI would build 2.0.2 now. The worst things are fixed and people that are on 2.0.0 or 2.0.1 really needs that 2.0.2 [13:52]
gac410Thanks Kenneth, yeah I was coming to same conclusion. I've got to review all the plugin changes and make sure versions were bumped appropriately. [13:53]
LavrOne of the next things I want to try is a conversion of my entire data set (a copy) to UTF. Any traps for young players I need to watch out? [13:54]
gac410Don't attempt to convert System web. ;)
also bulk_copy doesn't copy any file that isn't offically known to Store. (subdirectories, hidden .prefix files, _prefix files, ..._
So if you are using .htaccess for access control, for ex, those need to be re-established.
[13:54]
LavrNah. I use a clean Apache config setup [13:55]
MichaelDaumgac410, let me disable the TopicTitle [13:56]
gac410MichaelDaum: okay [13:56]
MichaelDaumhum which item wasit
ah gottit
[13:56]
gac410Last blocker Item13629 [13:56]
FoswikiBothttp://foswiki.org/Tasks/Item13629 [ Item13629: Hide "Title" field in natedit when unused ] [13:56]
LavrThanks Michael for taking time to also get that one in 2.0.2.
I re-headlined the ERP item so it has a better description of the release note list
Item13570: EditRowPlugin does not work on page with TABLE macro
[13:57]
FoswikiBothttp://foswiki.org/Tasks/Item13570 [ Item13570: EditRowPlugin does not work on page with TABLE macro ] [13:59]
GithubBot[distro] MichaelDaum pushed 1 new commit to master: http://git.io/vZmbN
distro/master bd82487 MichaelDaum: Item13629: hide "Title" field by default
[14:01]
***GithubBot has left [14:01]
....... (idle for 34mn)
gac410jmk0: saveFile / readFile in 2.0.2 will go back to saving raw by default.
Added a flag to specify that utf8 encoding is required.
[14:35]
Lavrgac410 we have some silly bugf [14:36]
gac410y?
I prefer to think of them as amusing features
[14:36]
Lavrwhen you create a new topic by typing its name in URL and then saving it - it gets a parent which is AdminToolsCategory
I just saw it now
My guess is that the default template in System web has this parent
[14:36]
gac410right. That one is really annoying. Might even be a task for it. I tried to fix it and struck out.
Right.
[14:37]
jmk0gac410: that's not really what I wanted to hear, but it's not really my decision either [14:38]
gac410jmk0: I thought that's what you wanted
Default is now compatible with 1.1.9
[14:38]
LavrThe default topic template must not have a parent [14:39]
gac410ah... didn't think of that approach. [14:39]
LavrI cannot remember the name of the topic that defines the default template [14:40]
jmk0I said over and over that saveFile shouldn't be used at all, really shouldn't even exist because it's dangerous in that it implies a level of safety that simply is not there
the encoding was a trivial issue, it's the lack of access serialization that makes it bad
[14:40]
gac410jmk0, we can NOT remove API. we can announce its deprecation. And adding locking is a feature request. [14:41]
jmk0fine, like I said, it's not what I wanted to hear, but not my decision
IMO it is dangerously broken
do with that what you will
[14:42]
gac410It is used by a number of extensions, I opened a separate task to add serialization.
The project has specific guidance on these things. It would be chaos if we just deleted API that is believed is dangerous. We have a deprecation process. And a feature request process. Addling locking is a feature. Removing is deprecation.
And for better or worse that API has been there since TWiki release whatever.
The loggers never had locking either. That was just added in 2.0
[14:42]
LavrMost plugins use it to write to a temporary file in their workspace. And it works fine for them because each instance write in their own unique file. And as George says. it is plugin API. [14:46]
jmk0all I can say is that I will not use this API [14:47]
gac410That's fine, there is nothing that says that anyone has to use any API. Some we strongly recommend - topic manipulation for ex. [14:48]
LavrNo need to. it is not an API that calls any code inside Foswiki. It just does what you can do straight in Perl. But removing it breaks many plugins. No need to break people's plugins. [14:48]
gac410But the working area APIs ... not widely used anyway. [14:48]
LavrAnd you cannot fix them because many of them are not public.
Where the heck do we keep the template topic for a new topic? I cannot find it
[14:49]
gac410Lavr, I don't think it's the template topic. I think it has to do with the defaults in the web topic creator.
lemme look a bit.
[14:50]
LavrWe used to have such a topic. it was one of those things I tailored. gettting rid of that darn stupid default signature [14:51]
gac410ArthurClemens reworked some of the web topic creator stuff iirc.
"simpler" to tailor. ... meaning it's utterly too complex for me :D
WebCreateNewTopicTemplate.txt ... I think
That's the topic, but I removed the parent and I still get a parent. I think it's because of the way the form is built from include components.
[14:51]
LavrI cannot see how it can be that. A template topic would be an empty topic with a * -- %WIKINAME% - %SERVERTIME% or something like that
In 1.1.9 it was WebTopicEditTemplate.txt
And it still is. And there is your parent
I could not find it because I looked for %WIKINAME% and it is %WIKIUSERNAME% that is used. All we need is to remove the parent meta
I am creating a task
[14:56]
gac410Yup that fixes it. Great. I looked several times to figure this out and kept being confused by the WebCreateNewTopicComponents.txt [15:00]
LavrHere is the Item if you want to check in the fix Item13686: New topics get AdminToolsCategory as parent [15:01]
FoswikiBothttp://foswiki.org/Tasks/Item13686 [ Item13686: New topics get AdminToolsCategory as parent ] [15:01]
gac410Do you want to check it in? [15:02]
LavrSure [15:02]
GithubBot[distro] KennethLavrsen pushed 1 new commit to master: http://git.io/vZYnq
distro/master 982bf89 KennethLavrsen: Item13686: New topics get AdminToolsCategory as parent...
[15:05]
***GithubBot has left [15:05]
LavrAll done [15:06]
gac410Thanks Kennety
Kenneth
(grr... sorry, fingers not working well today)
[15:06]
LavrMine never does ;-) [15:10]
***gac410 sets mode: +v WikiRingBot [15:17]
.... (idle for 15mn)
ChanServ sets mode: +o CDot [15:32]
.......... (idle for 47mn)
GithubBot[distro] gac410 pushed 1 new commit to master: http://git.io/vZYHw
distro/master 27b268c George Clark: Item13504: Update plugin versions for Foswiki 2.0.2
[16:19]
***GithubBot has left [16:19]
FoswikiBothttp://foswiki.org/Tasks/Item13504 [ Item13504: Documentation changes Foswiki 2.0.x / 2.1.0 ] [16:19]
........ (idle for 36mn)
GithubBot[distro] gac410 pushed 2 new commits to master: http://git.io/vZOJT
distro/master 456e5af George Clark: Item13504: Prepare for release
distro/master 6fbd385 George Clark: Item13505: xgettext run, no string changes
[16:55]
***GithubBot has left [16:55]
FoswikiBothttp://foswiki.org/Tasks/Item13504 [ Item13504: Documentation changes Foswiki 2.0.x / 2.1.0 ]
http://foswiki.org/Tasks/Item13505 [ Item13505: Translations for Foswiki 2.0.x / 2.1.0 ]
[16:55]
...... (idle for 29mn)
gac410Hm... Some of the TestCases for EditTable still have some issues.
TestCases/TTestCases/TestCaseEditTableMacrosInMacrosTestCases/TestCaseEditTableMacrosInMacrosestCaseEditTableMacrosInMacros
er... TestCases/TestCaseEditTableMacrosInMacros
4th table, edittable macro edits an empty table
I'm not going to hold up 2.0.2 though. These are still an improvement.
[17:24]
......... (idle for 44mn)
Hm. MichaelDaum. I'm unable to save the configuration on Foswiki 2.0.2-RC1. Timestamp: 09/08/2015 02:07:36 PM
Error: TypeError: obj is undefined
Source File: http://.../pub/System/JQueryPlugin/jquery-2.1.4.js
[18:09]
.... (idle for 17mn)
GithubBot[distro] gac410 pushed 1 new commit to master: http://git.io/vZOw5
distro/master c4703e9 George Clark: Item13560: Don't check Spec files if bootstrapping....
[18:26]
***GithubBot has left [18:26]
FoswikiBothttp://foswiki.org/Tasks/Item13560 [ Item13560: configure does not set initial values when extensions are installed with an external package manager ] [18:26]
.... (idle for 16mn)
gac410False alarm. ... can't seem to recreate the javascript error. :( [18:42]
....... (idle for 33mn)
Foswiki.org is now running 2.0.2-RC1 I'll let this soak 24 hours and then build and release 2.0.2 tomorrow. [19:15]
MichaelDaum. The upgrade to 2.0.2 on foswiki.org reverted what looks to be a local change to edit.natedit.tmpl
Ah... maybe you manually hid the topicmeta template on f.o?
[19:20]
.... (idle for 15mn)
GithubBot[distro] gac410 pushed 1 new commit to master: http://git.io/vZOhp
distro/master 3f32109 George Clark: Item000: Build 2.0.2-RC1
[19:36]
***GithubBot has left [19:36]
FoswikiBothttp://foswiki.org/Tasks/Item000 [ Item000 ] [19:36]
GithubBot[distro] gac410 tagged FoswikiRelease02x00x02_RC1 at 9d24cd5: http://git.io/vZOjJ [19:36]
***GithubBot has left [19:36]

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)