nanodesigner-developers

[Nanodesigner-developers] User Interface Component

[Fuji H. <fo...@gm...>]

Hi Team,

I noticed in the NanoWiki posting for "Software Development" we are
using a version tag for our code that includes author/version/date
(I'm guessing this is for CVS/Subversion).  I am wondering if it is a
good idea to keep track of the original author AND the person who last
modified and committed the code into the repository.  It might be nice
to see who the original designer was and also nice to see who has made
any recent changes.  I think debugging will benefit if we can see who
touched the code last.

Secondly, I have been looking at the specifications that are posted in
NanoWiki for the UI Component.  The MVC design pattern might be a good
choice when implementing the GUI.  It is always a good idea to plan
out the OO design before jumping into code.  I will try to get some
brainstorming ideas posted into NanoWiki sometime this week.  If
anyone else has design ideas about the UI Component let us know, maybe
some quick UML diagrams might help too.

Thanks,

-Fuji

Re: [Nanodesigner-developers] User Interface Component

[<sw...@us...>]

Fuji Hakayito wrote:

>I noticed in the NanoWiki posting for "Software Development" we are
>using a version tag for our code that includes author/version/date
>(I'm guessing this is for CVS/Subversion).  I am wondering if it is a
>good idea to keep track of the original author AND the person who last
>modified and committed the code into the repository.  It might be nice
>to see who the original designer was and also nice to see who has made
>any recent changes.  I think debugging will benefit if we can see who
>touched the code last.
> =20
>

My first idea, as you know, was not to add *any* authors because I=20
thought it would become too complex to acknowledge every single=20
contribution to a certain class. After some thought I changed my mind=20
because it would be too elaborate to track down the person who=20
introduced a bug (as you mentioned).
I think it would be easier if the person who created a certain class=20
stays responsible of that class at all times. Other people who want to=20
change something in that class should send/discuss their modifications=20
with the person in charge of the class. As it is the original writer=20
he/she, I think, is the most knowledgeable person to assess if the=20
change 'fits' in the overall design of the part he is working on.
If for some reason the original writer does not want the responsibility=20
of that class anymore it can be transferred to someone else. If *that*=20
person changes something in that class he can add his name as a=20
co-author unless it would be a complete rewrite of course.

>Secondly, I have been looking at the specifications that are posted in
> =20
>
> NanoWiki for the UI Component. The MVC design pattern might be a good
> choice when implementing the GUI. It is always a good idea to plan
> out the OO design before jumping into code. I will try to get some
> brainstorming ideas posted into NanoWiki sometime this week. If
> anyone else has design ideas about the UI Component let us know, maybe
> some quick UML diagrams might help too.

I think the MVC design pattern is the best choice, yes.
Just in case there are people who are not familiar with Java design=20
patterns I will see if I can find an ebook and add it to the main=20
=91developers only=92 page to download asap.

Val=E8re

Re: [Nanodesigner-developers] User Interface Component

[Elie De B. <el...@de...>]

> > NanoWiki for the UI Component. The MVC design pattern might be a good
> > choice when implementing the GUI. It is always a good idea to plan
> > out the OO design before jumping into code. I will try to get some
> > brainstorming ideas posted into NanoWiki sometime this week. If
> > anyone else has design ideas about the UI Component let us know, maybe
> > some quick UML diagrams might help too.
>=20
> I think the MVC design pattern is the best choice, yes.
> Just in case there are people who are not familiar with Java design=20
> patterns I will see if I can find an ebook and add it to the main=20
> =91developers only=92 page to download asap.
>=20
> Val=E8re

An ebook covering design patterns in java is freely available at:

http://www.patterndepot.com/put/8/JavaPatterns.htm


greetings
Elie

Re: [Nanodesigner-developers] User Interface Component

[Javier F. <jv...@ya...>]

Hi everyone.

> I think it would be easier if the person who created
> a certain class 
> stays responsible of that class at all times. Other
> people who want to 
> change something in that class should send/discuss
> their modifications 
> with the person in charge of the class. As it is the
> original writer 
> he/she, I think, is the most knowledgeable person to
> assess if the 
> change 'fits' in the overall design of the part he
> is working on.
> If for some reason the original writer does not want
> the responsibility 
> of that class anymore it can be transferred to
> someone else. If *that* 
> person changes something in that class he can add
> his name as a 
> co-author unless it would be a complete rewrite of
> course.

This is in principle not a bad idea. However, I do not
know how well it will work at the end. The person in
charge of the class may lose interest and slow down
the development process. Additionally, a developer
will not feel completely free to colaborate because
someone else is already in charge of what this person
wants to help with. Who knows. It may perfectly work
for this proyect. I really hope so.

> > The MVC design
> pattern might be a good
> > choice when implementing the GUI. It is always a
> good idea to plan
> > out the OO design before jumping into code.

I completely agree with you. I think we need some
initial plan of how we will structure the project. MVC
is the best option.


		
__________________________________
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail 

Re: [Nanodesigner-developers] User Interface Component

[<sw...@us...>]

Hi Javier,

>This is in principle not a bad idea. However, I do not
>know how well it will work at the end. The person in
>charge of the class may lose interest and slow down
>the development process. Additionally, a developer
>will not feel completely free to colaborate because
>someone else is already in charge of what this person
>wants to help with. Who knows. It may perfectly work
>for this proyect. I really hope so.
> =20
>
I do not think there is a perfect solution to these matters, not in an=20
open source project with volunteers anyway.  In case there are disputes=20
or delays it is the project manager (yours truly) who will resolve the=20
issue.  I also expect volunteers to act in a responsible way.
=20
Val=E8re