Hi,
Bean writes:
> The current menu system is a little chaotic, the various components
> are mixed together which make it difficult to maintain and extend.
> Therefore, I propose a new design which seperates model, view and
> controller.
>
> Model. It's the menu items. Currently, menu are added
On Fri, 2009-06-26 at 16:31 +0200, Robert Millan wrote:
> Btw, what is MVC anyway? :-)
http://en.wikipedia.org/wiki/Model-view-controller
It's a popular design pattern in designing business applications, which
discourages hardcoding the rules (business logic) into the data
structures and the user
Btw, what is MVC anyway? :-)
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
__
On Thu, 2009-06-25 at 23:54 +0800, Bean wrote:
> Once the official version is out, people could start creating theme
> files, which make it more difficult to change the format. I think it'd
> be better if we can make it right the first time.
I tend to agree with Robert here. It's more important
On Thu, Jun 25, 2009 at 3:50 PM, Colin D Bennett wrote:
> Robert Millan wrote on Thursday 25 June 2009:
> > On Thu, Jun 25, 2009 at 12:07:18PM +0800, Bean wrote:
> > > Hi,
> > >
> > > The current menu system is a little chaotic, the various components
> > > are mixed together which make it diffic
Bean wrote:
Implement the menu viewer in lua. Colin's patch already make extensive
use of lua, so perhaps we can just standardize the interface a little
bit, and make it easier to write components using either c or lua.
and (out of order,)
Use xml to store data. With Colin's graphic menu path
Bean wrote on Thursday 25 June 2009:
> On Thu, Jun 25, 2009 at 10:25 PM, Robert Millan wrote:
> > On Thu, Jun 25, 2009 at 06:50:55AM -0700, Colin D Bennett wrote:
> >> > Isn't Colin already working on a redesign of the menu?
> >>
> >> Yes, but I haven't drastically changed the design of the core me
On Thu, Jun 25, 2009 at 10:25 PM, Robert Millan wrote:
> On Thu, Jun 25, 2009 at 06:50:55AM -0700, Colin D Bennett wrote:
>> > Isn't Colin already working on a redesign of the menu?
>>
>> Yes, but I haven't drastically changed the design of the core menu system
>
> In general, I'm not happy with th
On Thu, Jun 25, 2009 at 06:50:55AM -0700, Colin D Bennett wrote:
> > Isn't Colin already working on a redesign of the menu?
>
> Yes, but I haven't drastically changed the design of the core menu system
In general, I'm not happy with this kind of drastical changes specially at
this time. We're s
On Thu, Jun 25, 2009 at 9:50 PM, Colin D Bennett wrote:
> Robert Millan wrote on Thursday 25 June 2009:
>> On Thu, Jun 25, 2009 at 12:07:18PM +0800, Bean wrote:
>> > Hi,
>> >
>> > The current menu system is a little chaotic, the various components
>> > are mixed together which make it difficult to
Robert Millan wrote on Thursday 25 June 2009:
> On Thu, Jun 25, 2009 at 12:07:18PM +0800, Bean wrote:
> > Hi,
> >
> > The current menu system is a little chaotic, the various components
> > are mixed together which make it difficult to maintain and extend.
> > Therefore, I propose a new design whic
On Thu, Jun 25, 2009 at 12:07:18PM +0800, Bean wrote:
> Hi,
>
> The current menu system is a little chaotic, the various components
> are mixed together which make it difficult to maintain and extend.
> Therefore, I propose a new design which seperates model, view and
> controller.
>
> Model. It'
Hi,
The current menu system is a little chaotic, the various components
are mixed together which make it difficult to maintain and extend.
Therefore, I propose a new design which seperates model, view and
controller.
Model. It's the menu items. Currently, menu are added using menuitem
statement,
13 matches
Mail list logo
