Moreover, mucoadhesive preparations included in the European Pharmacopoeia 7.4 (2012) have encouraged researchers to utilize the advantages of the technique in drug delivery research ( 4). carvedilol, lidocaine, salbutamol, and miconazole as buccoadhesive films/patches have been referenced in scientific texts ( 2, 3). Experimental evidences on better therapeutic efficacy of drug molecules viz. dose accuracy, small and compact size, local or systemic action, swift absorption of the drug, ease of withdrawal in urgent situation, controlled and/or sustained release, prevention of gastric degradation or first-pass effect, and comparatively better stability than other buccoadhesive systems (cream, gel, ointment) ( 1). These formulations (films and patches) are the representative systems of transdermal patches and have many advantages viz. Stability studies revealed no significant ( P < 0.05) variation in physicomechanical characteristics.īuccoadhesive systems are one of the novel formulation techniques, where polymers play a central role. Films were compatible with oral probiotic microorganisms. Film GM4 exhibited 98 ± 2% in vitro drug release and 85 ± 8% ex vivo drug permeation in 12 h with controlled diffusion mechanism. Erosion behavior of films was observed in swelling and SEM studies. Buccoadhesion was also influenced by particle size (adsorption theory) and swelling (wetting theory). Increase in polymer concentration augmented zeta potential of polymeric matrix-mucin mixture and exhibited strong buccoadhesion (electrical theory). Drug-polymer interaction was examined by FTIR and DSC analysis. The tabindex being in there was actually what got me thinking about fields with attributes in arrays, because based on the raw HTML, there's no way to easily remove tabindex="%d" if you don't want it.The present study aimed to develop buccoadhesive film of glimepiride with unique combination of polymers and to investigate its effect(s) on physicomechanical parameters, drug-release, and permeation of films. Media buttons right now force us to leave it in, but it's a PITA to keep with the sprintf() needing to occur, and really they shouldn't be forced on forms because most won't want it (and shouldn't use it). It makes sense to me that you'd want to say I want array( 'title', 'content' ) and taxonomies => array( 'post_tag', 'category' ), and it should build that for you into a form.Īlso, tabindex. I'd rather not see big chunks of HTML getting processed as arguments, because then it is much more difficult to pick and choose which you want, or to customize them, etc. I think I maybe went a little too far with 14966.2.diff, but I do see a use case for hidden fields to be processed as an array - doing it otherwise seems weird. My big questions now are how to implement field creation and what not. Though maybe there is a need for get_terms_to_edit() if indeed a $post is passed. Beyond that, we don't have much use for which I can revert. If the form is passed a $post, then so be it, but that's up to the developer. Let's kill media button handling and move that to a hook for the dashboard module in particular. Thinking about this more, we pulled in the stuff from the admin so we could generate auto-drafts.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |