Lib finder Timeline - Revision history

Byo at 19:41, 28 March 2008

2008-03-28T19:41:32Z

Byo at 12:14, 3 January 2008

2008-01-03T12:14:47Z

Byo at 12:14, 3 January 2008

2008-01-03T12:14:11Z

Byo at 22:56, 1 January 2008

2008-01-01T22:56:30Z

Byo at 21:24, 1 January 2008

2008-01-01T21:24:32Z

Byo: New page: Timeline for lib_finder: {| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%; table-lay...

2007-12-30T23:49:48Z

New page: Timeline for lib_finder: {| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%; table-lay...

New page

Timeline for lib_finder:

{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%; table-layout: fixed;"
|- style="background: #ececec;"
! style="width: 15em" | Task
! Description
! style="width: 7em" | Estimated time
! style="width: 5em" | Finished
|-
! Predefined libraries
| style="text-align: left;" | Currently lib_finder allow to search for libraries and search filters can be defined in configuration files. But if someone provides library which is already set-up and this information in sure and constant, it should also be able to provide final library configuration using simillar scheme to search filters. Additionally, such library settings could give possibility to store dorectories relatively to code::blocks' directory which will allow to build some portable usb-drive C::B
| 1 day
| {{no}}
|-
! Support for multiple configuration directories
| style="text-align: left;" | Library search filters are stored in xml files located in some settings directory. Currently only one directory is scanned when those files are loaded. But it's known that on some systems (f.ex. unix) there may be more than one directory with data. A set of directories should be read, not only one.
| 1 hour
| {{no}}
|-
! Library synonymes
| style="text-align: left;" | Each library sould be accessible using more than one name. This could be usefull because even now there are different names for libraries when using lib_finder settings and pkg-config ones.
| 1 day
| {{no}}
|-
! Type of library result
| style="text-align: left;" | Structure LibraryResult should have extra field called type which would be: pkg-config, predefined or detected. By providing type, all results, no matter whether stored or detected from pkg-config could use one structure. That would greatly ease things in future when other possible sources would be added
| 1 day
| {{no}}
|-
! Edition of library results
| style="text-align: left;" | There should be ability to view all known libraries and edit detected ones. That could help finding mistakes etc. It could also be usefull to set order of libraries.
| 1 day
| {{no}}
|-
! Detection of used libraries
| style="text-align: left;" | By scanning #include lines it should be easy to detect what libraries should be included with project to compile it without problems. It could be also added into HeaderFixup plugin (available using through scripting or something)
| 2 days
| {{no}}
|-
! Separate configuration for build targets
| style="text-align: left;" | Each build target should have it's own set of libraries and there should be one global set of libraries.
| 1 day
| {{no}}
|-
! Library version support
| style="text-align: left;" | When declaring that project use library, it should be possible to set some version filters (and other kinds of filters)
| 1 week
| {{no}}
|-
! Search results priorities
| style="text-align: left;" | Search results should have priorities. Pkg-config libraries would have the lowest priority, next would be predefined results, detected libraries could have any priority declared in detection filter files. That would help finding better results.
| 1 week
| {{no}}
|-
! Set custom variables when detecting libs
| style="text-align: left;" | There could be some extra option which would set value of variable, it shouldn't be possible only from path
| 1 hour
| {{no}}
|-
! Integration with scripting system
| style="text-align: left;" | Some procedures (like adding library to project) should be availble in scripting system. That would allow to use lib_finder in project wizards and invoke it from other plugins.
| 1 hour
| {{no}}
|-
|}

@@ Line 31: / Line 31: @@
 | style="text-align: left;" | There should be ability to view all known libraries and edit detected ones. That could help finding mistakes etc. It could also be usefull to set order of libraries.
 | 1 day
-| {{no}}
+| {{yes}}
 |-
 ! Detection of used libraries

@@ Line 26: / Line 26: @@
 | style="text-align: left;" | Structure LibraryResult should have extra field called type which would be: pkg-config, predefined or detected. By providing type, all results, no matter whether stored or detected from pkg-config could use one structure. That would greatly ease things in future when other possible sources would be added
 | 1 day
-| {{no}}
+| {{yes}}
 |-
 ! Edition of library results

@@ Line 11: / Line 11: @@
 | style="text-align: left;" | Currently lib_finder allow to search for libraries and search filters can be defined in configuration files. But if someone provides library which is already set-up and this information in sure and constant, it should also be able to provide final library configuration using simillar scheme to search filters. Additionally, such library settings could give possibility to store dorectories relatively to code::blocks' directory which will allow to build some portable usb-drive C::B
 | 1 day
-| {{no}}
+| {{yes}}
 |-
 ! Support for multiple configuration directories

@@ Line 61: / Line 61: @@
 | style="text-align: left;" | Some procedures (like adding library to project) should be availble in scripting system. That would allow to use lib_finder in project wizards and invoke it from other plugins.
 | 1 hour
-| {{no}}
+| {{yes}}
 |-
 ! Background search