RBC - Refactored BLT Components - Initial Release
in [TCL]
|
Prev: starpack icon mystery solved - tclkit.ico missing from tclkitsh-8.5.7-win32.upx.exe
Next: Announce: Runtime Library 3.0 Gestalt Items 1.1 and Hugelist 1.4,Tcl-Mode for XCode
From: Bob Techentin on 12 Oct 2009 16:34 On Oct 12, 11:46 am, MSEdit <mse...(a)gmail.com> wrote: > > Do you have any Idea how/if/when the missing parts (zoomstack, > crosshairs, activelegend) will be added ? Zoomstack won't work because I didn't ask the students to refactor 'busy.' I haven't made any effort to that end. (yet) To the best of my knowledge, active legends and crosshairs are in there. There are automated tests for those features. (Although I haven't personally tried them.) > I saw in the Readme that the undergraduates have graduated. Are they > still helping out ? I'm not expecting help from the students. I got what I wanted, and they graduated. :-) Bob
From: Donal K. Fellows on 12 Oct 2009 20:43 On 12 Oct, 10:46, MSEdit <mse...(a)gmail.com> wrote: > I have been looking for a replacement to the tabs mechanism/interface > but the users realy like it. ttk::notebook does not gracefully handle > what happens when there is no more space for the tabs (bwidget scrolls > as per FireFox) and blt adds multiple layers. You'll want to argue that with Joe English. AIUI, he feels that if there are too many tabs for them to fit on the screen at once, you shouldn't be using a tabbed notebook. (I'm sympathetic to this PoV; I hate the other two...) > The tabsset functionality is for switching between multiple elements > which are not necessarily pages. I have downloaded the Busy stuff > already. You can use a ttk notebook for that if you give it a style that doesn't have the actual tabs... Donal.
From: MSEdit on 13 Oct 2009 04:24 I don't understand the connection between zoomstack and busy. The graph widget is severly limited without the zoomstack ability to zoom in on regions of the graph. I just quickly tried the active legends and crosshairs because the graph demos for BLT use them (as well as me) I will look through the source to see how they are accessed and try again. What does Joe English suggest as a UI concept to replace the tabs, all the browsers use tabs and I don't see anyone saying its not good to open more than 10 pages. I use tabs in an editor and find that visually and conceptually it is an easy way to switch between files, I use a list too but that does not work as well. Scrolling the tabs with the mouse wheel is infinitly preferable however than the multi-tier tabs. I actually use the tabs to switch between BLT graphs in a MDI system which works well. Again I cannot use ttk::notebook for dynamic page systems (pages added/removed by the user actions) because I cannot tell my users 'its best not to open too many as it does not look too good'. I can understand that Joe does not appreciate lots of tabs but this rules out the use of the ttk::notebook for these systems. Scrolling tabs also take up much less screen real-estate than a tree/listbox. Martyn
From: Bob Techentin on 13 Oct 2009 07:58 On Oct 13, 3:24 am, MSEdit <mse...(a)gmail.com> wrote: > I don't understand the connection between zoomstack and busy. The > graph widget is severly limited without the zoomstack ability to zoom > in on regions of the graph. > > I just quickly tried the active legends and crosshairs because the > graph demos for BLT use them (as well as me) I will look through the > source to see how they are accessed and try again. > I don't understand it, either. The student team had their heads in the code. Since they've moved on, I guess it is up to me to figure it out. I see crosshair functions in the automated tests. The BLT_Crosshairs script was omitted from the library directory. I only just tried a graph demo yesterday. It would work without those script calls, and replacing table geometry management with grid. Maybe if I work with those demo scripts a bit, I can figure out if those parts might work. Bob
From: Uwe Klein on 13 Oct 2009 08:11
Bob Techentin wrote: > On Oct 13, 3:24 am, MSEdit <mse...(a)gmail.com> wrote: > >>I don't understand the connection between zoomstack and busy. The >>graph widget is severly limited without the zoomstack ability to zoom >>in on regions of the graph. >> >>I just quickly tried the active legends and crosshairs because the >>graph demos for BLT use them (as well as me) I will look through the >>source to see how they are accessed and try again. >> > > > I don't understand it, either. The student team had their heads in > the code. Since they've moved on, I guess it is up to me to figure it > out. afair the bltZoomStack stuff is (completely) contained in graph.tcl i.e. it is implemented as scriptonly same goes for some other features. # grep -i proc\ *blt:: graph.tcl proc blt::LegendSelections { w } { proc blt::legend::SetSelectionAnchor { w tagOrId } { proc blt::legend::MoveFocus { w elem } { proc blt::ActivateLegend { graph } { proc blt::DeactivateLegend { graph } { proc blt::HighlightLegend { graph } { proc blt::Crosshairs { graph {event "Any-Motion"} {state "on"}} { proc blt::InitStack { graph } { proc blt::ZoomStack { graph {start "ButtonPress-1"} {reset "ButtonPress-3"} } { proc blt::PrintKey { graph {event "Shift-ButtonRelease-3"} } { proc blt::ClosestPoint { graph {event "Control-ButtonPress-2"} } { proc blt::AddBindTag { widget tag } { proc blt::RemoveBindTag { widget tag } { proc blt::FindElement { graph x y } { proc blt::FlashPoint { graph name index count } { proc blt::GetCoords { graph x y index } { proc blt::MarkPoint { graph index } { proc blt::DestroyZoomTitle { graph } { proc blt::PopZoom { graph } { proc blt::PushZoom { graph } { proc blt::ResetZoom { graph } { proc blt::ZoomTitleNext { graph } { proc blt::ZoomTitleLast { graph } { proc blt::SetZoomPoint { graph x y } { proc blt::MarchingAnts { graph offset } { proc blt::Box { graph } { proc blt::ResetPostScript { graph } { uwe |