A major portion of Quanta's push to be DTD agnostic is dependent upon ease of use for each separate DTD. To that end, the toolbars in Quanta have been extended a great deal. Toolbars are easy enough to understand. You click onthe button and you get an associated action from that button. The really cool part here is that you can define your own actions in Quanta.
Using toolbars in Quanta is incredibly simple. Selecting the Toolbars (Alt+l) menu item reveals options to load, save, add and email toolbars.
Loading and saving toolbars is pretty straight forward. When you choose to load a toolbar, you may choose from one of the three workspaces in Quanta.
One of the most exciting new features of Quanta toolbars is that you can email them directly from Quanta. When you do so, Quanta bundles all of the actions and the toolbar information into a zipped tar archive then pushes it out via KMail. Once you receive a toolbar in email, you can save it anywhere and load it into Quanta like any other toolbar!
As previously mentioned, toolbars in Quanta are primarily maanged through the Toolbars menu item. Usability and creation are somewhat different. Creation is deferred to an as there is more involved there. Usability will be discussed now.
Using toolbars is quite simple. You click on the icon of the desired tag or and one of three possibilities occur: the tag is inserted (optionally with a closing tag) (e.g. the bold HTML tag), a tag dialog is activated letting you fill in the multiple tag features in a dialog box (e.g. the anchor HTML tag), and lastly, an action is activated that does something nifty for your current file/project/whatever. For the first, I'll give no example as it is easy enough to understand. As to the second and third, read on...
Tag dialogs are defined in XML and stored in a tags subdirectory under your .kde subdirectory or with the Quanta distribution wherever you put that. I bring this up only to note that, if you find yourself doing tedious and redundant typing for a particular tag that isn't in Quanta, you can add it. Anyway, a tag dialog looks just like this:
This happens to be the anchor tag referenced above. If you know anything about HTML, you'll notice that that's just about all the attributes you can have for an anchor. Notice the tabs above for i18n and Events. Now all you do is fill in the blanks for those items you want in your anchor, click ok and, voila!, you have a well formed anchor set down at the current cursor position.
As for scripting actions, if you create two files in your home directory with the following contents, you'll have a fun surprise.
dt.actions
<!DOCTYPE actionsconfig> <actions> <action icon=“mini-book1.png” type=“script” name=“usr_1” \ text=“Shell” > <script output=“message” error=“message” \ input=“none” >xterm</script> </action> </actions>
dt.toolbar
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd"> <kpartgui name="quanta" version="2"> <ToolBar tabname="My1stToolbar" name="dt" > <text>My1stToolbar</text> <Action name="usr_1" /> </Toolbar> </kpartgui>