Hi,
we are looking into using another component set than the v2 architecture.
However we don't want to switch over and over again, and frankly as the
architecture developer I dont want anything to do with components at all.
So I was thinking about a setup where I write component interfaces such as
IComboBox and a set of wrappers such as V2ComboBoxAdapter implements
IComboBox.
Next a designer creates a view, and puts something in his view like (im
making it up as I'm typing) :
getComboBox (id:String):IComboBox {
return AbstractFactory.create (V2Adapters.COMBO_BOX, _root.cbPersons);
}
In terms of being independent of my views, I can just start putting an app
together and if the designer dude wants to skin it differently or use a
whole other component set he is free to do so, even mix and match is an
option.
The main thing I'm wondering about is whether I'm gruesomely
overcomplicating things and just causing a heckload of work for no good
reason other than that I am not familiar with a single very good component
set that satisfies all the designer needs (I'm not saying they don't exist,
I'm saying I don't have enough experience in any of them to make a
wellformed decision, and don't really have the time to test them one by
one:)).
Hope this makes any sense!
greetz
JC
_______________________________________________
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
