History of bitweaverFAQ
{maketoc maxdepth=2 title="Questions" class=bitweaverfaq}
---
if you see any errors on this page or if you would like to add some wisdom, please register and edit the page by clicking on the edit icon.
! Releases
!! How do i get the latest and greatest of bitweaver?
you need access to CVS. to set up cvs and how to use it, please view:
bitweaverCVS
!! How can i get hold of packages that haven't been released yet?
try accessing [/builds/packages] and see if the package is available for testing. if it's not available there, you can get it using cvs. for a list of available packages, you can check out CVSROOT and look in the modules file. with most packages, the cvs module name is _bit_<package> (e.g.: use _bit_wiki for the wiki)
!! What is happening in CVS? How stable is CVS?
CSV branch R1 is considered stable and only bugfixes are going into R1. we have got a database schema as well as an api lockdown. This means that you can update using the cvs R1 branch without much concern. obviously, we're not miracle workers and we suggest you backup your file / database before upgrading (expecially after a prolonged period). for upgrade instructions, please view bitweaverUpgrade
---
! Upgrades
!! What files should i take care of when upgrading?
please view bitweaverUpgrade for details
!! How do i upgrade bitweaver to the latest version?
please view bitweaverUpgrade for details
---
! Documentation
!! Where can i find Documentation on package X?
in the packages administration screen ( Administration --> Kernel --> Packages ), there is a description of all packages and a link to the relevant page on bitweaver. if the page does not exist here, it is likely that there is no decent documentation for that given package. in this case, you could create such a wiki page requesting for information from the author or someone using the package.
!! Where can i find Documentation on feature X?
our inline help provides a brief description in virtually all forms and input areas. should something not be clear, please search this site for the feature you don't understand. chances are that it's been answered somewhere. if you find an answer to your question, please add the __question__ and __answer__ to this page for others to use.
!! Where can i find Developers Documentation?
* PHPDoc: [/doc/php/]
* Doxygen: [/doc/dox/]
* Developers FAQ: [/blogs/12]
---
! Theming
!! how the hell do i create a new theme?
we have an extensive ThemeTutorial, which gives you an outline how our themes work, how you create a theme. it even includes some basic css rules should you not have much experience with css.
---
! Developement
!! How do i start my own package?
we have some useful documentation on how to start your own package and how to get started on the SamplePackage page.
!! How do i share a package?
you have written a package and you want to share it with others? currently we don't have a dedicated method / area for this, and we only use cvs to organise our packages. if you drop by IRC, we can have a chat about how and what you want to share.
---
if you see any errors on this page or if you would like to add some wisdom, please register and edit the page by clicking on the edit icon.
! Releases
!! How do i get the latest and greatest of bitweaver?
you need access to CVS. to set up cvs and how to use it, please view:
bitweaverCVS
!! How can i get hold of packages that haven't been released yet?
try accessing [/builds/packages] and see if the package is available for testing. if it's not available there, you can get it using cvs. for a list of available packages, you can check out CVSROOT and look in the modules file. with most packages, the cvs module name is _bit_<package> (e.g.: use _bit_wiki for the wiki)
!! What is happening in CVS? How stable is CVS?
CSV branch R1 is considered stable and only bugfixes are going into R1. we have got a database schema as well as an api lockdown. This means that you can update using the cvs R1 branch without much concern. obviously, we're not miracle workers and we suggest you backup your file / database before upgrading (expecially after a prolonged period). for upgrade instructions, please view bitweaverUpgrade
---
! Upgrades
!! What files should i take care of when upgrading?
please view bitweaverUpgrade for details
!! How do i upgrade bitweaver to the latest version?
please view bitweaverUpgrade for details
---
! Documentation
!! Where can i find Documentation on package X?
in the packages administration screen ( Administration --> Kernel --> Packages ), there is a description of all packages and a link to the relevant page on bitweaver. if the page does not exist here, it is likely that there is no decent documentation for that given package. in this case, you could create such a wiki page requesting for information from the author or someone using the package.
!! Where can i find Documentation on feature X?
our inline help provides a brief description in virtually all forms and input areas. should something not be clear, please search this site for the feature you don't understand. chances are that it's been answered somewhere. if you find an answer to your question, please add the __question__ and __answer__ to this page for others to use.
!! Where can i find Developers Documentation?
* PHPDoc: [/doc/php/]
* Doxygen: [/doc/dox/]
* Developers FAQ: [/blogs/12]
---
! Theming
!! how the hell do i create a new theme?
we have an extensive ThemeTutorial, which gives you an outline how our themes work, how you create a theme. it even includes some basic css rules should you not have much experience with css.
---
! Developement
!! How do i start my own package?
we have some useful documentation on how to start your own package and how to get started on the SamplePackage page.
!! How do i share a package?
you have written a package and you want to share it with others? currently we don't have a dedicated method / area for this, and we only use cvs to organise our packages. if you drop by IRC, we can have a chat about how and what you want to share.