Note to self: FairyBrier
Mar. 29th, 2005 01:34 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
elfsFairyBrier is a UML modelling tool specifically for programmatic website developers. By viewing each page as an object with a definitive heirarchy with contractual preconditions and alternative targets if those preconditions are not met, FairyBrier allows the programmer to craft a session-managed website using only a mouse and a couple of gestures.
FairyBrier supports four levels of interaction: (1) A schematic view, which shows the pages as icons with UML decorations for their roles. (2) A role view, in which page names and their decorations are visible. (3) The storyboard view, in which links and stereotypes for the different pages come into view. (4) The page view, in which individual pages, their contents, preconditions, and off-view requirements are listed and accessible.
FairyBrier is expected to be able to save its state. It is also expected, in the end, to create a website skeleton compatible with JSP, PSP, or PHP.
I haven't written any code for this yet, but it's on my list, and I needed a place to keep it in my mind. This is as good a place as any.
FairyBrier supports four levels of interaction: (1) A schematic view, which shows the pages as icons with UML decorations for their roles. (2) A role view, in which page names and their decorations are visible. (3) The storyboard view, in which links and stereotypes for the different pages come into view. (4) The page view, in which individual pages, their contents, preconditions, and off-view requirements are listed and accessible.
FairyBrier is expected to be able to save its state. It is also expected, in the end, to create a website skeleton compatible with JSP, PSP, or PHP.
I haven't written any code for this yet, but it's on my list, and I needed a place to keep it in my mind. This is as good a place as any.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2005-03-29 09:46 pm (UTC)^__^
I alread construct most of my websites from raw XML using XSL/XST to generate the individual pages and links, though in a very basic way. It had occurred to me that one ought to be able to take a UML description and trannsform it to the neccessaarry XML directly using XST. A graphical tool similar to the old Net Objects Fusion tool that generated the UML, and then ran transforms to create the site (rather then the crapy htnml that Fusion used to create) would be cool.
no subject
Date: 2005-03-29 10:12 pm (UTC)I really wish I had all the time in the world to do this stuff, but unfortunately far too often it feels like, um, work.
no subject
Date: 2005-04-01 03:11 am (UTC)I once had a job writing the middleware portion of the very thing you describe: a platform for building web applications out of a diagramming tool and an underlying toolkit COM+ objects.
Thing is, this wasn't a software company, and the project wasn't for a platform to build any web app, but a very specific, actual web app. So, it didn't fly, due to deadline and budgetting constraints.
Still, it was a good idea in theory, and it's nice to see the theory finally becoming a reality 4 years later.
no subject
Date: 2005-03-30 04:58 am (UTC)Sounds familiar...
Date: 2005-04-02 10:31 pm (UTC)Just wait. The next version will probably involve having a rat dancing on your keyboard. :-)
// Frank