Janko Mivšek wrote:
> Rob Rothwell wrote:
>
> > At that point, do you have "Aida Gadgets"?!
>
> Good point! How to name those things? So far all more complex elements
> are put in Aida-Components. But things like AutocompleteField is more
> like widgets, while name "components" should be reserved for standalone
> application components. And at the end we have an App with many views,
> and those are web pages for the user. So, how to name things in Aida not
> to introduce too much confusion?
Very good question.
And Rob brought up some good points.
Names of things are going to be dependent on how you want to define the
item. Once you have a clear definition, naming should be easier. There
are too many things in programming where the names and definitions are
used in too many varying ways to have concrete I think some other
questions to consider are:
understanding.
I think for Aida, a definition should accompany anything which is given
a name, so that we have clear boundaries. This will make learning and
understanding much easier. And it will also help in naming code and
other items as we progress.
A few other questions. Because often times, good answers come from good
questions.
How does this item interact with others?
Is it dependent or depended upon?
Can it stand alone?
Is this item intended to be an integrated part of Aida or its platform?
Or is this item intended to be an extension to Aida or its platform?
What is its use case?
I think if we can answer these things, then it will enable a good
factoring of Aida and its platform for building web applications.
Hope this helps.
Jimmie
_______________________________________________
Aida mailing list
[hidden email]
http://lists.aidaweb.si/mailman/listinfo/aida
Locked
