been a while since i posted... too long a while...

anyway:

forms

forms have undergone a major reorganisation and redesign. i've put quite a bit of effort into making bitweaver more userfriendly. i have started adding various notes to input areas throughout bitweaver forms. for this we have come up with a new standard for forms in templates. instead of using the commonly used tables, we've come up with a set of divs and spans that simplify this type of dynamic data considera…

i have tested this suggestion and MSIE can't collapse the menus using the internal js. this means that we're stuck with the current system of using links which have the setting
display: block;
in the css.

i'm looking into the possibility of using other methods, which would be more compatible with browsers that don't support / have disabled js.

on this toppic, i think it's high time to work on alternatives for browsers without js. currently it's virtually impossible to navigate the site…

i think we should move to a list method of menus rather than using the current method of link with with the class definition:
display: block;

this is to avoid rendering difficulties browsers that don't support display: block;

if we use something like:



this would render ok even with no css settings.

styling would be specific and easy as we…

so...

should we decide what method we want to use to have good and simple styling possibilities?

should we:

• use smarty to generate css files, allowing for easy (but probably somewhat limited) modification of css files?
• start converting our templates to xml and then parsing those? this would allow for identification of each and every 'box' on the page enabling positioning and placing them wherever needed using css. i don't think this will ever happen but would probably be the most fle

…

current things that are being done, and are to be done in the near future include:

• use tikicon instead of static img tags for icons throughout bitweaver. this will be done in ReleaseOne to avaoid firther usettling of bonnie before the imminent release.
  • this includes updating icon location, names and appearance where required.
    • icons are moved to respective packages, globally used icons such as edit or delete are stored in /kernel.
• update pages with listing to use the new functi

…