I rolled out an upgrade to Sidewalk today, and after a few hiccups, everything looks to be working now. Mainly this was to update the code from Build 36 to 41. But we decided to add bug tracking while I was in there.

Any discussion topic can now be promoted to a "ticket" and tracked like a typical bug report. There is a new Tickets tab in the header which provides a dedicated view for tickets. Its a pretty simple model, but this should help make sure things don't fall through the cracks. So if you come across any type of issue, please post to the forum so we can keep track of them. Currently only Brian, Kevin, or myself can promote topics to tickets.

Also I added support for topic and type/slot links in comments:

See this [topic]`#400'
This [method]`sys::DateTime.toStr` on DateTime

I had to touch alot of moving parts, so if anything looks broken, let me know. If you have issues logging in or posting, make sure you're cache is flushed. I already know all the docs are missing the Tickets tab - that will be fixed when we do the next build.

Very interesting. That should keep things organized.

Can just anyone promote their own topic? Or does it need to be done by a mod?

I also notice that the Collapse/Expand all sidebar now floats. Sometimes the little things bring a lot of joy ;-)

Only moderators can promote topics right now.

Maybe I can try for Ticket #1 in the system. :-)

In the RichText mods that Brian (I think) posted just over a week ago, adding support for tracking scrollbar events (with hbar and vbar). I've been using it for a week in what I'm doing, and thanks. It works fine when you scroll the view by actually using the scrollbar, but if you hit pagedown or arrowdown to navigate instead, then no Scrollbar.onModify() message happens.

The scrollbar itself is moving as it should, and the richtext works right, but just the key handling isn't triggering the Scrollbars to send an onModify event.

I'm not needing it too bad yet, but sooner or later I'll have to do something about it; in the meantime it probly oughta be tracked.

Simplest possible testcase is, go to flux/fluxText/fan/TextEditor.fan, in the onLoad method after richText is constructed add something like

richText.vbar.onModify.add(|Event e| { echo(e) } )

(hope that syntax is right, off top of my head). Then open a file in Flux, and on scrollwheel you'll see echos and on pagedowns you won't.

Andy and I laid out the Sidewalk model about a year ago, and we are still flushing it out. It is a bit of an experiment - but I really like the idea of tying together discussions/issues/changelogs into a cohesive whole.

So the process to start tracking an issue is to simply start a new discussion, pretty much exactly like we've been doing already. I will be moving a couple things I've been tracking out of sight into Sidewalk.

I'm not needing it too bad yet, but sooner or later I'll have to do something about it; in the meantime it probly oughta be tracked.

Kevin, can you start a new topic for this? Thanks.

I'm not sure I like seeing the bug tracking mixed in with the discussions. Maybe discuss needs a optional filter to exclude bugs, or maybe it needs another tab.

Personally, I like it so far. Some discussions were already really unlabeled bug reports anyway. Maybe some easy filter system would be nice, but I highly recommend against a new tab.

And it might be nice to save the filter state in the user profile, if we do go that route.