I don't get how MVC1 works in Swing2. Technically it's probably more MVP3, but it's the model that I'm confused about.
Let's say I have the typical Person object with various properties such as name, age, height, eye color, etc. Now if I want to present the Person object properties on a GUI, I can't just have the Person be the model. I have to use the models specific to the GUI elements (Document model, ComboBoxModel, ListModel, ButtonModel, etc), and then somehow tie my Person in with these 'models'.
Does this mean I have two models? Like, yo dawg I heard you like models inside models? Or is this just a case of Adapter pattern4?
Just ignore all the ENTERPRISE BULLSHITE and do what makes sense.
Name:
Anonymous2009-06-11 4:48
I like Mr.Satori because he is a programmer like me, except he reached Satori. Oh god, I wish I could reach Satori too ;_;
Mr.Satori also dislikes ENTERPRISE BULLSHIT and he is kawaii. And there are EXPERT PROGRAMMERS in /prog/ and that's good because I like EXPERT PROGRAMMING and I will never be one. Why am I such a looser ?!
Mr.Satori is like my dream programmer he has a HAVE YOU READ YOUR SICP TODAY face I love that. He is also nice why aren't real programmers nice?! I got my core dumped a lot of times but I love Mr.Satori and he wouldn't let my pointers go segfault because he's so nice and cool.
We would tune fishes all day and watch SICP lectues and other cool programming material on TV, and we would code in LISP because LISP is good. I wish I could code in LISP.
So Jabba‘s controller protocols are named *Model, and the standard implementations actually contain data rather than binding to it? How silly.
Still, you should be able to implement them in a proper controller class without much trouble.