Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search

[REBOL] Re: REBOL : Pure OOP project ?

From: robert:muench:robertmuench at: 10-Apr-2002 9:51

> -----Original Message----- > From: [rebol-bounce--rebol--com] [mailto:[rebol-bounce--rebol--com]]On Behalf Of > Christian Morency > Sent: Wednesday, April 10, 2002 1:57 AM > To: [rebol-list--rebol--com] > Subject: [REBOL] Re: REBOL : Pure OOP project ? > I agree that OOP is not the key to rebol-usage-pattern, at the moment ;) But > for large projects it could benefits.
OOP didn't solved the software-component-reuse problem, it makes it sometimes a bit easier if you have a good designer in your team. But anyway... it's an option and maybe we have it available one day.
> Could you further explain your "aggregated" pattern for object in rebol ?
Well, it's no rocket sience. At the moment I design my reblets like this: 1. I use objects for aggregating data. These objects are version-controled. 2. I add business-object-evolution code. This code can transform my data objects from one version to the next. So updating my inner data structure won't break any old data-files. IMO that's very important, if you publish several versions, you can assure that all of these will be used somewhere. Don't expect people to always use your latest version. 3. I use one object for all the VID stuff for one mask/dialog/frame. This includes the layout and all kind of supporting functions needed. Further I only have two functions to travel from objects to gui and backward: object_to_gui and gui_to_object. 4. I have a set of global functions that are generic enough so that these can be used from all GUI objects. Like finding, adding, deleting, changing an object. For VID I use the sub-panel pattern. I have one main window with a box that get's resized and assigned new layouts.
> Each widget should be developped by one person, but I think the coordination > could be from the mailing list...
Sorry, but I don't agree. IMO the widget should be developed by all of us who are interested but being coordinated by one person. The coordination is the critical part as you have to check that the widget will be plug-in able into the bigger picture, the RSL (Rebol Standard Library). For me the concept how to use Rebol, create libraries and lightweight frameworks (that's in short design- and programming style and guideline) is the base to start with. If we got a (democratic) agreed concept building all the widgets should be quite fast with all the people here. At the moment I have to read the widget sources, alter them to fit into my architecture, alter words atc. But if the widget gets updated... I'm lost and need to start over again. Robert