#foswiki 2016-09-25,Sun

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

WhoWhatWhen
***gac410 has left [05:04]
.............. (idle for 1h9mn)
ChanServ sets mode: +o CDot [06:13]
........... (idle for 54mn)
GuilainC_away is now known as GuilainC [07:07]
......... (idle for 40mn)
ChanServ sets mode: +o Lynnwood__ [07:47]
...................................................................... (idle for 5h45mn)
ChanServ sets mode: +o gac410 [13:32]
............... (idle for 1h12mn)
GuilainC is now known as GuilainC_away [14:44]
..................... (idle for 1h40mn)
Lynnwood__I wonder how hard it would be to integrate one of the js/html5 drawing packages into Foswiki, basically just enabling saving image into topic.
http://www.draw2d.org/ or https://github.com/jgraph/draw.io
[16:24]
FoswikiBot[ GitHub - jgraph/draw.io: Source to www.draw.io ] [16:24]
gac410Would be nice to have a replacement for JHotDraw ... There have been several complaints about demise of java in the browser, but nobody willing to take on a replacement. [16:26]
Lynnwood__indeed. I've got a new client that wants to have simple wiring diagrams in wiki. They have used TWikiDrawPlugin in the past. I'm looking for alternative. [16:27]
gac410gac410 is trying to categorize the "new" tasks, Awful job. Some are fixed but never closed. We really need to do a better job of managing / updating / assigning and closing tasks. [16:28]
Lynnwood__It would seem that it should not be too hard to hijack attach url to save a generated file. [16:29]
gac410Or use ajax interface with something like TopicInteractionPlugin
There are 474 tasks in "New" status that really should be confirmed, closed, or set to "Needs Developer" :P
[16:29]
..... (idle for 24mn)
Lynnwood__gac410 i'll see if i can whittle away at some of those this week.
I guess it would be useful to try and replicate to confirm of not.
[16:57]
gac410Yeah. It's such a mixed bag of mess. If the plugin wasn't released in foswiki, (really old stuff) I've been either setting to NeedsDeveloper,. but usually NoAction
The ones worth confirming are core bugs, Default extension bugs, or relatively popular plugins
Other thing to check is if there are commits, see if they actually made it into a release of core or the extension. I'm finding quite a few that were fixed but not closed.
Very helpful is "git tag --contains <hash> or git branch --contains <hash> which will tell you if a commit made it into a branch or into a tagged release.
'tis a painful process :P
[16:58]
...... (idle for 25mn)
Here's one reported by you Lynnwood__ ... Item4715 That plugin was never released on Foswiki, changing to No Action. :D [17:26]
FoswikiBothttps://foswiki.org/Tasks/Item4715 [ Item4715: MultiEditPlugin not working with 4.2 ] [17:26]
..................................... (idle for 3h1mn)
***GuilainC_away is now known as GuilainC [20:27]
...................... (idle for 1h49mn)
GuilainC is now known as GuilainC_away [22:16]

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