Home - BeBytes Info - Submit App - Your Account - Links - Contact Us

Version Beta 7
Contact Publisher
Version History
Other Reviews
Send Updates
  Submitted by: Wildman

Date Posted:
Last Updated:
Page Views:
User Rating:
awaiting votes..  

About Shirley:

28/05/2001 - Shirley 0.1 Beta 7
email: daniel@technofetishist.com

Shirley is a visual form editor for BeOS 5.0 (Intel)

The form editor itself is easy to use (especially for anybody who has used
any tools like Borland's Delphi or C++ Builder for Windows). Select the component
you want from the toolbar at the top, drop the component onto your window, and there
it is. The property inspector can then be used to modify any properties of the
components on the form.

Components on a form can be moved and resized using the keyboard. Select the component and
then press the command key (Alt or Ctrl depending on how BeOS is configured) and one of the
arrow keys. The component will move. If the Shift key is held down as well the component will
be resized. Pressing the Escape key will select a component's parent.

NOTE: Any components whose name start with the '_' character will be ignored by
the Shirley visual design tools because some of the BeOS controls contain other controls
and they all have '_' as the first character of their names.
Also any properties you set take effect immediatly, so if you set the B_QUIT_ON_WINDOW_CLOSE
flag, and close the window Shirley will exit. I will be fixing this in a future release.

When you are ready to save your window, choose the save menu item from the menu bar,
type the name of the class you want to represent this window, and Shirley will
create the files necessary to allow your form to be shown by your application.

Shirley will create three files. For example if you saved your form as TestWindow
then you will see the file TestWindow.frm, TestWindowBase.cpp and TestWindowBase.h.
To use this form in an application you will need to create a subclass of the class
TestWindowBase as follows

#include "TestWindowBase.h"

class TestWindow : public TestWindowBase {
virtual void MessageReceived(BMessage* message);

If the Message property of a BInvoker object is used it is no longer necessary to associate
BMessages with your various buttons, check boxes and other controls, as this will be done
for you by Shirley.

Constructing an instance of the TestWindow class and then calling the Show() method
should result in you seeing the form you created.

If you use the Hint property you need to add ToolTip.cpp to your project (or build script).
This file can be found in the shirley/src/HintAddon directory.

I'd like to thank Alan Ellis for his help in finding some of the more nasty bugs in Shirley and
for getting my mind thinking down the path necessary for the custom code generators
to come into existance.

If you have any questions feel free to email me at either of the addresses
mentioned above. I hope to have some more documentation, and maybe even a tutorial
in a future release of Shirley.


Daniel Parnell

Latest Version

Details about this version:
(no information provided)

Intel (BeOS5)     (338.7K)

Most Popular
1. BeAIM - 4846
2. BePDF - 4528
3. Paladin - 4418
4. OpenTracker - 4175
5. AMD PCnet32 - 4143
6. nVidia 3D Driver - 3878
7. nVidia Driver - 3869
8. VMWare PCnet/PCI - 3793
9. Firefox - 3666
10. Duke Nukem 3D - 3501
11. ATI Radeon - 3479
12. Basilisk II - 3446
13. Sequitur - 3409
14. Traker.Newfs - 3409
15. SPICE - 3361
16. AbiWord - 3157

Account Status
  You are not logged in.