Bioequivalence and Bioavailability Forum

Dear Detlew,

❝ ❝ ... Luv told me: 3,000 USD for each of DissoXpress, IvivcXpress, PK-Xpress. If you are going for whole package the cost would be even lesser. Yearly support charges: 20% of license cost per client. Much cheaper than Phoenix and slightly below Kinetica.

❝

❝ Compared with SAS this is a "Schnäppchen".

Indeed. Update on the price (a German friend asked for a quotation last July):

Description                  License type   USD per client
PKXpress                     Professional   4,000
(Pharmacokinetic Software)                  (Four Thousand Dollars Only) [sic]

The above price includes:

1. License cost and installation help remotely.
   
2. Initial training of 2 day.

Yearly support Charges will be @ 25% of the License cost per client. The YSS will be applicable from the 2^nd year from the date of installation.

❝ It's a nightmare to answer to some posters which have mastered the (list)(/list) construct in between the list points, especially if the list is also hierarchical. And some posters are using this to the excess .

Terribly sorry. Besides Shuanghe I guess you are talking about the forum’s admin, right?
My reason for using list, indents, etc.: I love semantics. Semantically there is a difference between

• foo
  
• bar

or

1. foo
   
2. bar

and

1. foo
2. bar

❝ Is there a way to simplify matters?

Realistically – no. You see similar effects in other boards/forums when replying as well. Here the quoted text (starting with » ) consist of the block-element <pre></pre> which contains an inline child-ele­ment <cite></cite> (hey, seman­tics!). Lists within this element are not allowed. Breaking of list-BB­Codes in a reply is a side-effect of how they are processed in the PHP-script (tries hard to pro­duce valid HTML). Theoretically it would be possible to use <blockquote></blockquote> (which can con­­tain other block-elements). Would mean a major rewrite of the scripts. Not in the near future.
In sophisticated forums (like the SelfHTML Forum) it is possible to use plain HTML-tags instead of BB­Codes. Then the structure will be kept in the reply. But:

• Users have to know HTML. If they use wrong tags or screw up the nesting the page will not be valid any more. If a page is not valid the browser has to “guess” what might have been meant. Can work in browser A and show only a blank page in browser B.
  
• Nasty things are possible in HTML (JavaScript- or even SQL-injections). Needs careful automatic inspection and cleaning of code. The technical background is demanding. Nothing for a hobby-coder like me.

❝ I struggle since hours with an answer post to Yours.

Sorry. Next time don’t worry. I can edit your post.

A suggestion (if you are using Firefox):
I use the Add-on It’s All Text! for many years. It provides a small button next to the textarea which opens an editor:

You can configure it to your needs:

I use Notepad2 as editor. It takes two clicks to get rid of the list-BBCodes and replace the [*] with something else:

❝ Another wish: If I adapt the edit area to greater dimensions and press than PREVIEW it shrinkens to it's standard size. Is it possible to change this behavior?

That’s not possible very, very difficult. The (X)HTML 1.0 standard on this site (and the current HTML 5 as well) require that the <textarea>-tag has attributes for width and height. The con­struct is <textarea cols="xx" rows="yy" name="foo" id="bar"></textarea> where xx and yy are the number of mono­spaced characters (were 78 and 25; changed to 95 and 30). These attributes are mandatory since users may have their own style-sheet or switched off CSS completely. The forum’s stylesheet already con­tains the CSS 3.0 property

textarea {
  resize: both;
}

You are lucky because your browser is able to resize the textarea (bloody IEs* can’t…). But since that happens in the client, the server does not “know” that when deli­vering the page again (in the default width).
One wild possibility would be to wrap the textarea with JavaScript, calculate the current width relative to the viewport’s from the respective DOM-nodes, send the information to the server when you click Preview, the server modifies the <cols>-attribute in the deli­vered HTML and (optionally) saves the information in a cookie. Tough job.

---

• If you are using IE: Sorry folks – get a CSS 3.0-compliant browser! In IE it would require a Java­Script-library like jQuery to simulate this property. I will not force the ~90% of our users who don’t use IE to download such a monster.