Editing User:Mafm
From BRL-CAD
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 26: | Line 26: | ||
= ToDo = | = ToDo = | ||
− | + | <pre>[2008-07-01 20:30:08] <brlcad> should work on improving/finishing that build system integration some more too ;) | |
− | + | [2008-07-01 20:31:28] <brlcad> saving users the need to hunt/download is only a small piece of the reason for including the deps, it should build them if it doesn't find a suitable system version | |
− | + | [2008-07-01 20:32:04] <brlcad> also, your cmake files presently assume pkg-config, that shouldn't be assumed | |
− | + | [2008-07-01 20:32:13] <brlcad> (nor required) | |
− | + | [2008-07-01 20:34:38] <mafm> I'm no expert in building systems, but that could take weeks :S | |
− | + | [2008-07-01 20:35:39] <mafm> "but" is alias to "but I think" and "because of that" at the same time :) | |
− | + | [2008-07-01 20:35:45] <brlcad> I don't think anyone here would call themselves a cmake expert :) | |
− | + | [2008-07-01 20:37:03] <brlcad> it is something that needs to happen earlier rather than later given this tool is intended to become pretty fundamental eventually | |
− | + | [2008-07-01 20:37:37] <brlcad> minimally document the need somewhere (TODO), but poke on it when you can | |
− | + | [2008-07-01 20:37:56] <mafm> but I could spend much time with it and miss the milestones with gsoc | |
− | + | [2008-07-01 20:39:14] <brlcad> i understand, that doesn't change the pressing need for it .. | |
− | + | [2008-07-01 20:39:23] <brlcad> the longer it's ignored, the harder it will be for whomever does try it | |
− | + | [2008-07-01 20:39:57] <brlcad> it's part of coding complete | |
− | + | [2008-07-01 20:40:22] <brlcad> if the build doesn't work cleanly, it's not really usable yet to most of our devs | |
− | + | [2008-07-01 20:40:45] <mafm> I see | |
− | + | [2008-07-01 20:41:47] <brlcad> e.g. I can't imagine bob readily being willing to futz with three different build systems plus pkg-config, cmake, and scons | |
− | + | [2008-07-01 20:42:29] <brlcad> we're used to *zero* effort unless you want to change away from defaults | |
− | + | [2008-07-01 20:43:49] <brlcad> it's not top-priority in front of the milestone tasks, but it's probably #2 or #3 to have a default-functioning build system regardless of system deps | |
− | + | [2008-07-01 20:44:22] <mafm> that's fine, but I don't think that it's in the scope of the project to rework whatever building system the dependencies decide to use | |
− | + | [2008-07-01 20:44:38] <brlcad> so at least document it is what I'm saying, maybe work on it if you take a break from coding | |
− | + | [2008-07-01 20:44:41] <mafm> especially being an experimental project | |
− | + | [2008-07-01 20:45:38] <brlcad> fyi, I don't see this as an experiement -- a prototype, sure .. but one with an exceptionally high probability of becoming the foundation for a new GUI | |
− | + | [2008-07-01 20:46:26] <brlcad> you'd have to mess up in several big ways for it to be wasted effort :) | |
− | + | [2008-07-01 20:47:36] <mafm> it seems to me that you're relaying on somebody with a weak knowledge of building for such a foundation :P | |
− | + | [2008-07-01 20:48:15] <brlcad> not relying, just don't want you to blow it off entirely as not your problem | |
− | + | [2008-07-01 20:49:58] * starseeker prods CIA | |
− | + | [2008-07-01 20:50:02] <brlcad> wasn't saying drop what you're doing to work on it, just keep it in mind and poke on it when you can .. and document where things are at</pre> | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | <pre>[2008-07-01 20:30:08] | ||
− | <brlcad> should work on improving/finishing that build system integration some more too ;) | ||
− | [2008-07-01 20:31:28] | ||
− | <brlcad> saving users the need to hunt/download is only a small piece of the reason for including the deps, it should build them if it doesn't find a suitable system version | ||
− | [2008-07-01 20:32:04] | ||
− | <brlcad> also, your cmake files presently assume pkg-config, that shouldn't be assumed | ||
− | [2008-07-01 20:32:13] | ||
− | <brlcad> (nor required) | ||
− | |||
− | [2008-07-01 20:34:38] | ||
− | <mafm> I'm no expert in building systems, but that could take weeks :S | ||
− | [2008-07-01 20:35:39] | ||
− | <mafm> "but" is alias to "but I think" and "because of that" at the same time :) | ||
− | |||
− | [2008-07-01 20:35:45] | ||
− | <brlcad> I don't think anyone here would call themselves a cmake expert :) | ||
− | [2008-07-01 20:37:03] | ||
− | <brlcad> it is something that needs to happen earlier rather than later given this tool is intended to become pretty fundamental eventually | ||
− | [2008-07-01 20:37:37] | ||
− | <brlcad> minimally document the need somewhere (TODO), but poke on it when you can | ||
− | |||
− | [2008-07-01 20:37:56] | ||
− | <mafm> but I could spend much time with it and miss the milestones with gsoc | ||
− | |||
− | [2008-07-01 20:39:14] | ||
− | <brlcad> i understand, that doesn't change the pressing need for it .. | ||
− | [2008-07-01 20:39:23] | ||
− | <brlcad> the longer it's ignored, the harder it will be for whomever does try it | ||
− | [2008-07-01 20:39:57] | ||
− | <brlcad> it's part of coding complete | ||
− | [2008-07-01 20:40:22] | ||
− | <brlcad> if the build doesn't work cleanly, it's not really usable yet to most of our devs | ||
− | |||
− | [2008-07-01 20:40:45] | ||
− | <mafm> I see | ||
− | |||
− | [2008-07-01 20:41:47] | ||
− | <brlcad> e.g. I can't imagine bob readily being willing to futz with three different build systems plus pkg-config, cmake, and scons | ||
− | [2008-07-01 20:42:29] | ||
− | <brlcad> we're used to *zero* effort unless you want to change away from defaults | ||
− | [2008-07-01 20:43:49] | ||
− | <brlcad> it's not top-priority in front of the milestone tasks, but it's probably #2 or #3 to have a default-functioning build system regardless of system deps | ||
− | |||
− | [2008-07-01 20:44:22] | ||
− | <mafm> that's fine, but I don't think that it's in the scope of the project to rework whatever building system the dependencies decide to use | ||
− | |||
− | [2008-07-01 20:44:38] | ||
− | <brlcad> so at least document it is what I'm saying, maybe work on it if you take a break from coding | ||
− | |||
− | [2008-07-01 20:44:41] | ||
− | <mafm> especially being an experimental project | ||
− | |||
− | [2008-07-01 20:45:38] | ||
− | <brlcad> fyi, I don't see this as an experiement -- a prototype, sure .. but one with an exceptionally high probability of becoming the foundation for a new GUI | ||
− | [2008-07-01 20:46:26] | ||
− | <brlcad> you'd have to mess up in several big ways for it to be wasted effort :) | ||
− | |||
− | [2008-07-01 20:47:36] | ||
− | <mafm> it seems to me that you're relaying on somebody with a weak knowledge of building for such a foundation :P | ||
− | |||
− | [2008-07-01 20:48:15] | ||
− | <brlcad> not relying, just don't want you to blow it off entirely as not your problem | ||
− | [2008-07-01 20:50:02] | ||
− | <brlcad> wasn't saying drop what you're doing to work on it, just keep it in mind and poke on it when you can .. and document where things are at</pre> | ||
= Log = | = Log = | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== July == | == July == | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
July 2: | July 2: | ||
Line 324: | Line 86: | ||
* Fix of many small glitches, doxygen documentation, cleanups and renamings for consistency. | * Fix of many small glitches, doxygen documentation, cleanups and renamings for consistency. | ||
* Starting to look into Ogre geometries. | * Starting to look into Ogre geometries. | ||
− | * Screenshot of the Day: http:// | + | * Screenshot of the Day: http://wainu.ii.uned.es/~mafm/brlcad/brlcad_rbgui_20080626-1.png |
June 25: | June 25: | ||
− | * Usability enhancements to CommandOverlay and Console, such as sharing history and commands of CommandOverlay being reflected in the Console panel. Screenshot: http:// | + | * Usability enhancements to CommandOverlay and Console, such as sharing history and commands of CommandOverlay being reflected in the Console panel. Screenshot: http://wainu.ii.uned.es/~mafm/brlcad/brlcad_rbgui_20080625-1.png |
* Spent half the afternoon investigating and fixing a problem with Ogre Singleton intantiations. It turns out that their implementation allows you to create objects from classes which are Singletons, and that kinds of cause weird problems. | * Spent half the afternoon investigating and fixing a problem with Ogre Singleton intantiations. It turns out that their implementation allows you to create objects from classes which are Singletons, and that kinds of cause weird problems. | ||
June 24: | June 24: | ||
− | * Working on the implementation and redesign of many things in the GUI front (see screenshot for visual reference: http:// | + | * Working on the implementation and redesign of many things in the GUI front (see screenshot for visual reference: http://wainu.ii.uned.es/~mafm/brlcad/brlcad_rbgui_20080624-1.png ): |
** New Window Manager class, to act as high level decision-maker about layout; and things like taking into account created windows (and deciding which ones to show in taskbar), so I think that "assimilates" the Taskbar class too, and thus I removed it as separate class. | ** New Window Manager class, to act as high level decision-maker about layout; and things like taking into account created windows (and deciding which ones to show in taskbar), so I think that "assimilates" the Taskbar class too, and thus I removed it as separate class. | ||
** New panel in the top, which will be used for context operations, setting fullscreen modes and things like that. | ** New panel in the top, which will be used for context operations, setting fullscreen modes and things like that. | ||
Line 340: | Line 102: | ||
June 23: | June 23: | ||
* Watching again the video about "ideal interaction", for inspiration and to create a list of ideas to implement. I would like to have a chat about this though, to see the differences that we need to apply to our program. | * Watching again the video about "ideal interaction", for inspiration and to create a list of ideas to implement. I would like to have a chat about this though, to see the differences that we need to apply to our program. | ||
− | * Starting to implement a taskbar, to mimic the interaction shown with the video. Screenshot: http:// | + | * Starting to implement a taskbar, to mimic the interaction shown with the video. Screenshot: http://wainu.ii.uned.es/~mafm/brlcad/brlcad_rbgui_20080623-1.png |
June 20: | June 20: | ||
Line 367: | Line 129: | ||
June 12: | June 12: | ||
− | * More work in the Console, getting lines to wrap instead of being cut; and fixing RBGui (with several hours of reasearch involved) so autorepeat does use an initial delay and you can actually write individual characters (instead of 'aaaaaaaa' when you press the key for only 200ms). See the screenshot of the day: http:// | + | * More work in the Console, getting lines to wrap instead of being cut; and fixing RBGui (with several hours of reasearch involved) so autorepeat does use an initial delay and you can actually write individual characters (instead of 'aaaaaaaa' when you press the key for only 200ms). See the screenshot of the day: http://wainu.ii.uned.es/~mafm/brlcad/brlcad_rbgui_20080612-1.png |
* A bit of work reorganizing code, making Doxygen documentation, removing leaks (even if the objects only are to be removed when the application closes anyway) and the like. | * A bit of work reorganizing code, making Doxygen documentation, removing leaks (even if the objects only are to be removed when the application closes anyway) and the like. | ||
* I wrote to RBGui guys to know if they're interested in patches to support at least my platform (Debian GNU/Linux, amd64 -- but at least Linux and POSIX systems by extension) instead of having to maintain private patches. | * I wrote to RBGui guys to know if they're interested in patches to support at least my platform (Debian GNU/Linux, amd64 -- but at least Linux and POSIX systems by extension) instead of having to maintain private patches. | ||
Line 373: | Line 135: | ||
June 11: | June 11: | ||
− | * Today I continued working in the Console, now at least the history functionality and the way to create and position windows it is basically stable (can be changed easily, but I mean that it's not a hack-ish/example-ish application). Screenshot: http:// | + | * Today I continued working in the Console, now at least the history functionality and the way to create and position windows it is basically stable (can be changed easily, but I mean that it's not a hack-ish/example-ish application). Screenshot: http://wainu.ii.uned.es/~mafm/brlcad/brlcad_rbgui_20080611-1.png |
* OIS (the input library) is giving problems with auto-repeat, a problem that already had several years ago: it disables auto-repeat from X, so the rest of the applications in that DISPLAY that capability, and if the application crashes before OIS restores it, you have to reset it by hand. This looks unacceptable to me, but I haven't devised any solution yet. | * OIS (the input library) is giving problems with auto-repeat, a problem that already had several years ago: it disables auto-repeat from X, so the rest of the applications in that DISPLAY that capability, and if the application crashes before OIS restores it, you have to reset it by hand. This looks unacceptable to me, but I haven't devised any solution yet. | ||
Line 380: | Line 142: | ||
June 9: | June 9: | ||
− | * Still working in the example application, but now it looks much better -- documented, code style, reorganizing things, making cursor visible (wasn't there in the POSIX version at least)... Screenshot: http:// | + | * Still working in the example application, but now it looks much better -- documented, code style, reorganizing things, making cursor visible (wasn't there in the POSIX version at least)... Screenshot: http://wainu.ii.uned.es/~mafm/brlcad/brlcad_rbgui_20080609-1.png |
June 8: | June 8: |