sunuml-developers Mailing List for SunUML

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

<a href="http://doningram.com/images/uploads/thumbs/02efpk.html"> http://doningram.com/images/uploads/thumbs/02efpk.html</a>
Hey all,

End of year are always busy :)

Nevertheless I stumbled on some projects that could help us.
Especially wxShapeFramework which seems interesting enough to use as code
base for our project
but this would mean switching to C++ ...

What do you think?

I put those projects on the page :
http://sunuml.wiki.sourceforge.net/Related+Projects

Regards

* UmlPad  [http://web.tiscali.it/ggbhome/umlpad/umlpad.htm] - WxWidgets
based UML Editor. Source code available under GPL. Available diagrams: Use
case, Class, Sequence, State and Activity.

* wxShapeFramework (wxSF) [http://sourceforge.net/projects/wxsf/] -
library/framework based on wxWidgets which allows easy development of
software applications manipulating with graphical objects (shapes).

* ClassBuilder [
http://members.lycos.nl/JimmyVenema/ClassBuilder/ClassBuilder.htm] -
freeware CASE tool targeted at the C++ developer, reverse capability. [[
https://sourceforge.net/projects/classbuilder|Open Source]] zlib/libpng
License.

* Code Blocks [http://www.codeblocks.org] - Excellent cross platform
wxWidgets based IDE. Some wants to create an uml plugin for it [
http://forums.codeblocks.org/index.php?topic=9769.0;topicseen].

* Gaphor [http://gaphor.devjavu.com/] - UML modelling tool written in
Python. But dependent on Zope & GTK+. http://www.ohloh.net/p/gaphor

>
> I think this should be in the wiki :D
>

Done.
It was a bit late yesterday :)

On Tue, Nov 11, 2008 at 5:04 PM, Steven Gay <laz...@gm...> wrote:

> Hello All,
>
> As we all agree we are talking to much about coding style.
> So we shall use the following style:
>
>
>    - CamelCase for class names.
>    - mixedCase for methods and variables *except* when required such as
>    overloading wx methods.
>
>
> Regards,
> Steven

I think this should be in the wiki :D

Hello All,

As we all agree we are talking to much about coding style.
So we shall use the following style:

   - CamelCase for class names.
   - mixedCase for methods and variables *except* when required such as
   overloading wx methods.

Regards,
Steven

Hi,

> 
> Mhhh... I read too fast. You really want to use mixedCase for classes?
> 

I don't think that the mixedCase was meant to used for classes. Like I understand the last comments, all developers agree with the fact to use CamelCase for classes, right?

I also agree with the compromise to "inherit" the standard of extended classes and use our own standard for clean new classes.

> 
> PS: I always wonder why defining the coding style & project folder layout
> takes so much time... and if the leader should impose it :/
> 

Steven, you have to decide such things because someone HAS TO decide. There are a lot of opinions and practises. But I think we all are willing to use any standard whatever would be established :)

Define some standard and we will follow ... probably ... ;)

Reeny

-------- Original-Nachricht --------
> Datum: Tue, 11 Nov 2008 11:58:53 +1100
> Von: "Steven Gay" <laz...@gm...>
> An: sun...@li...
> Betreff: Re: [Sunuml-developers] Local source directories and the CamelCase	topic

> >
> > I think that maybe a point in the middle will be better.
> >>
> >> - Use CamelCase methods when the class we make extends directly from a
> >> wxPython class, because if you override methods from the upperclass you
> >> are forced to use that standard, and I think all methods should have
> the
> >> same standard inside a class. This should be used for example on a
> >> subclass of wx.Frame.
> >>
> >> - Use mixedCase standard when making our own classes and model classes.
> >> I would prefer to use this standard everywhere but on the other classes
> >> it would be prone to error mixing the standards.
> >
> >
> > OK - I will wiki this.
> >
> 
> Mhhh... I read too fast. You really want to use mixedCase for classes?
> 
> I will let you decide tell me when you all agree :)
> 
> Just a comment. The fact that you are forced to use the CamelCase when
> overridding mix well with the mixedCase standard as it identifies clearly
> the methods that are overiding a base library versus our own methods. I
> still don't see the advantage of the CamelCase approach but as I said:
> tell
> me when you agree for a style.
> 
> PS: I always wonder why defining the coding style & project folder layout
> takes so much time... and if the leader should impose it :/
> 
> Regards,
> Steven

-- 
GMX Download-Spiele: Preizsturz! Alle Puzzle-Spiele Deluxe über 60% billiger.
http://games.entertainment.gmx.net/de/entertainment/games/download/puzzle/index.html

I agree! I searched for some useful tools and IDEs but I can't decide, which is really useful for programming python. It would be great if I can get some tips.

reeny

-------- Original-Nachricht --------
> Datum: Mon, 10 Nov 2008 15:28:05 -0600
> Von: "Johan Chaves Saborío" <joh...@gm...>
> An: sun...@li...
> Betreff: [Sunuml-developers] Development tools

> Hi,
> 
> What tool do you use to edit your python files? any graphical editor for
> wxPython?
> 
> I think we should add a wiki page with the "favorite" tools :D

-- 
"Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail

I agree.

Regards,

Ricardo

  _____  

From: Steven Gay [mailto:laz...@gm...] 
Sent: Lunes, 10 de Noviembre del 2008 18:43
To: sun...@li...
Subject: Re: [Sunuml-developers] Local source directories and the
CamelCasetopic

short question: Should we create the source code in a directory named
"/sunuml/src" (it's the way I know)?
Someone - I don't know anymore who - started to store python source code in
"/sunuml/core".

If we want to put all source in a folder then sunuml/src is cleaner.

However it depends if we want to divide our code in sub parts: such as
compiled modules .pyc as you would do for C++ dlls.

In this case the following is very nice (for c++ projects) because it
permits to use simple relative paths for includes :

/sunuml/core/src/core/
/sunuml/core/build/

/sunuml/utilities/src/utilities/
/sunuml/utilities/build/

You then include with  include "core/xxx.py" or "utilities/yyy.py".

Using such a structure would permit us to create stable compiled modules....
and avoid that we rebuild all at each small modifications.

See one of my projects
http://www.opengameengine.org/wiki/index.php?title=Project_Structure#Oge_fol
ders_structure

Shall we structure our project around modules from the start?

Note: the .pyc being copied in a common sunuml/lib  (folder which must not
be committed).

I think that maybe a point in the middle will be better.

- Use CamelCase methods when the class we make extends directly from a
wxPython class, because if you override methods from the upperclass you
are forced to use that standard, and I think all methods should have the
same standard inside a class. This should be used for example on a
subclass of wx.Frame.

- Use mixedCase standard when making our own classes and model classes.
I would prefer to use this standard everywhere but on the other classes
it would be prone to error mixing the standards.

OK - I will wiki this.

Hey all,

Frankly, I don't care which standard is used, as long as we all use (not
necessarily agree upon) the same. Personally, I prefer the Java convention:
CamelCase for all classes and mixedCase for almost everything else (ie
member variables and methods). But I don't want to add yet another option.

Steve, I'm afraid you've got to decide on this one and go ahead. I don't see
it as imposition but leadership.

Regards,

Ricardo

>
> I think that maybe a point in the middle will be better.
>>
>> - Use CamelCase methods when the class we make extends directly from a
>> wxPython class, because if you override methods from the upperclass you
>> are forced to use that standard, and I think all methods should have the
>> same standard inside a class. This should be used for example on a
>> subclass of wx.Frame.
>>
>> - Use mixedCase standard when making our own classes and model classes.
>> I would prefer to use this standard everywhere but on the other classes
>> it would be prone to error mixing the standards.
>
>
> OK - I will wiki this.
>

Mhhh... I read too fast. You really want to use mixedCase for classes?

I will let you decide tell me when you all agree :)

Just a comment. The fact that you are forced to use the CamelCase when
overridding mix well with the mixedCase standard as it identifies clearly
the methods that are overiding a base library versus our own methods. I
still don't see the advantage of the CamelCase approach but as I said: tell
me when you agree for a style.

PS: I always wonder why defining the coding style & project folder layout
takes so much time... and if the leader should impose it :/

Regards,
Steven

short question: Should we create the source code in a directory named
> "/sunuml/src" (it's the way I know)?
> Someone - I don't know anymore who - started to store python source code in
> "/sunuml/core".
>

If we want to put all source in a folder then sunuml/src is cleaner.

However it depends if we want to divide our code in sub parts: such as
*compiled
modules* .pyc as you would do for C++ dlls.

In this case the following is very nice (for c++ projects) because it
permits to use simple relative paths for includes :

/sunuml/core/*src/core/*
/sunuml/core/build/

/sunuml/utilities/*src/utilities/*
/sunuml/utilities/build/

You then include with  include "core/xxx.py" or "utilities/yyy.py".

Using such a structure would permit us to create stable compiled modules....
and avoid that we *rebuild all* at each small modifications.

See one of my projects
http://www.opengameengine.org/wiki/index.php?title=Project_Structure#Oge_folders_structure

Shall we structure our project around modules from the start?

Note: the .pyc being copied in a common *sunuml/lib*  (folder which must not
be committed).

I think that maybe a point in the middle will be better.
>
> - Use CamelCase methods when the class we make extends directly from a
> wxPython class, because if you override methods from the upperclass you
> are forced to use that standard, and I think all methods should have the
> same standard inside a class. This should be used for example on a
> subclass of wx.Frame.
>
> - Use mixedCase standard when making our own classes and model classes.
> I would prefer to use this standard everywhere but on the other classes
> it would be prone to error mixing the standards.

OK - I will wiki this.

If I ever get the time to do any coding again, vi.  Unless there's a 
decent IDE with vi style editing that I'm not aware of.

Johan Chaves Saborío wrote:
> Hi,
>
> What tool do you use to edit your python files? any graphical editor 
> for wxPython?
>
> I think we should add a wiki page with the "favorite" tools :D
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Sunuml-developers mailing list
> Sun...@li...
> https://lists.sourceforge.net/lists/listinfo/sunuml-developers
>   

I am using Eclipse + PyDev, but I guess everyone their own preferences.

________________________________
From: Johan Chaves Saborío <joh...@gm...>
To: sun...@li...
Sent: Monday, 10 November, 2008 21:28:05
Subject: [Sunuml-developers] Development tools

Hi,

What tool do you use to edit your python files? any graphical editor for wxPython?

I think we should add a wiki page with the "favorite" tools :D

I uploaded the documentation for GUI/Plugin framework as a .doc document.

Because the Steven had problems opening the uml from StarUML, tell me 
what do you think. It's a pretty basic class diagram.

Regards
Javier

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I use Komodo IDE 5. It's really good and free also.<br>
<br>
There is a comercial version, but the free version has all the basic
features (project managment, autocomplete, debugging, profiling, etc)<br>
<br>
Johan Chaves Sabor&iacute;o escribi&oacute;:
<blockquote
 cite="mid:7b5...@ma..."
 type="cite">Hi,<br>
  <br>
What tool do you use to edit your python files? any graphical editor
for wxPython?<br>
  <br>
I think we should add a wiki page with the "favorite" tools :D<br>
  <pre wrap="">
<hr size="4" width="90%">
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
<a class="moz-txt-link-freetext" href="http://moblin-contest.org/redirect.php?banner_id=100&url=/">http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/</a></pre>
  <pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Sunuml-developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Sun...@li...">Sun...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/sunuml-developers">https://lists.sourceforge.net/lists/listinfo/sunuml-developers</a>
  </pre>
</blockquote>
</body>
</html>

Yes a src directory is better.

I agree with you about naming attributes and methods. But Aidar is right 
in a way, we will be using wsPython alot.

I think that maybe a point in the middle will be better.

- Use CamelCase methods when the class we make extends directly from a 
wxPython class, because if you override methods from the upperclass you 
are forced to use that standard, and I think all methods should have the 
same standard inside a class. This should be used for example on a 
subclass of wx.Frame.

- Use mixedCase standard when making our own classes and model classes. 
I would prefer to use this standard everywhere but on the other classes 
it would be prone to error mixing the standards.

Regards
Javier

Doreen Strowinski escribió:
> Hi,
>
> short question: Should we create the source code in a directory named "/sunuml/src" (it's the way I know)?
> Someone - I don't know anymore who - started to store python source code in "/sunuml/core".
>
> What's the right way now?
>
>
> BTW:
> To contribute to the current discussion: I prefer the coding style like (I'm a mainly Java coder ...):
>
>  _anyPrivateField
>
>  anyPublicField
>
>  OwnConstructor()
>
>  functionOrMethod()
>
>
> Many opinions ... ! Steve, I'm afraid that you have to decide again ;)
>
>
> Reeny
>   

Hi,

What tool do you use to edit your python files? any graphical editor for
wxPython?

I think we should add a wiki page with the "favorite" tools :D

Hi, 

I have written a small prototype of a toolbox. Just to get a feel of AUI manager.
The icons are from StarUML.
The buttons on a toolbox are slightly modified BitmapTextToggleButton which draw bitmaps and text left-aligned.
This is a prototype, not something worth commiting to SVN.
I do agree with Steven then we need to start with design first.

Regards,
Aidar Talibzhanov

Hi,

short question: Should we create the source code in a directory named "/sunuml/src" (it's the way I know)?
Someone - I don't know anymore who - started to store python source code in "/sunuml/core".

What's the right way now?

BTW:
To contribute to the current discussion: I prefer the coding style like (I'm a mainly Java coder ...):

 _anyPrivateField

 anyPublicField

 OwnConstructor()

 functionOrMethod()

Many opinions ... ! Steve, I'm afraid that you have to decide again ;)

Reeny
-- 
"Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail

Hi Javier,

How about the following compromise:
we use mixedCase style for variables (prepended with _ for private) and
use CamelCase for methods - the same style as wxWidgets.
"Something(parameter)"  shouldn't cause any confusion as it is clearly a constructor call.
Any method calls will either have self. or <variable>. in front.

Regards,
Aidar Talibzhanov

----- Original Message ----
From: Javier Capanegra <ja...@ya...>
To: sun...@li...
Sent: Friday, 7 November, 2008 18:29:47
Subject: Re: [Sunuml-developers] wxPython/wxWidgets help

They are really similar. Maybe wxPython style will be better because we 
will be working alot with that library.

Although I'm against using methods with CamelCase. If we select an 
standard it should be mixedCase or words_sepparated_with_underscores.

Using CameCase will be really confusing. For example if you see the code 
"Something(paramter)" you won't know if it is creating an object of 
class Something or calling the function Something. This is specially 
true in Python because you don't put "new" in front of the class name to 
create an instance, just the class name.

Regards
Javier

Aid...@ba... escribió:
> The issue is that wxPython follows wxWidgets style for class and method
> names. 
> As we are building with wxPython I think we should follow their style. 
>
> Regards,
> Aidar
> _______________________________________________
>
> This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays. Any views or opinions presented are solely those of the author and do not necessarily represent those of Barclays. This e-mail is subject to terms available at the following link: www.barcap.com/emaildisclaimer. By messaging with Barclays you consent to the foregoing.  Barclays Capital is the investment banking division of Barclays Bank PLC, a company registered in England (number 1026167)
 with its registered office at 1 Churchill Place, London, E14 5HP.  This email may relate to or be sent from other members of the Barclays Group.
> _______________________________________________
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Sunuml-developers mailing list
> Sun...@li...
> https://lists.sourceforge.net/lists/listinfo/sunuml-developers
>
>  

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Sunuml-developers mailing list
Sun...@li...
https://lists.sourceforge.net/lists/listinfo/sunuml-developers

They are really similar. Maybe wxPython style will be better because we 
will be working alot with that library.

Although I'm against using methods with CamelCase. If we select an 
standard it should be mixedCase or words_sepparated_with_underscores.

Using CameCase will be really confusing. For example if you see the code 
"Something(paramter)" you won't know if it is creating an object of 
class Something or calling the function Something. This is specially 
true in Python because you don't put "new" in front of the class name to 
create an instance, just the class name.

Regards
Javier

Aid...@ba... escribió:
> The issue is that wxPython follows wxWidgets style for class and method
> names. 
> As we are building with wxPython I think we should follow their style. 
>
> Regards,
> Aidar
> _______________________________________________
>
> This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays. Any views or opinions presented are solely those of the author and do not necessarily represent those of Barclays. This e-mail is subject to terms available at the following link: www.barcap.com/emaildisclaimer. By messaging with Barclays you consent to the foregoing.  Barclays Capital is the investment banking division of Barclays Bank PLC, a company registered in England (number 1026167) with its registered office at 1 Churchill Place, London, E14 5HP.  This email may relate to or be sent from other members of the Barclays Group.
> _______________________________________________
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Sunuml-developers mailing list
> Sun...@li...
> https://lists.sourceforge.net/lists/listinfo/sunuml-developers
>
>   

The issue is that wxPython follows wxWidgets style for class and method
names. 
As we are building with wxPython I think we should follow their style. 

Regards,
Aidar
_______________________________________________

This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays. Any views or opinions presented are solely those of the author and do not necessarily represent those of Barclays. This e-mail is subject to terms available at the following link: www.barcap.com/emaildisclaimer. By messaging with Barclays you consent to the foregoing.  Barclays Capital is the investment banking division of Barclays Bank PLC, a company registered in England (number 1026167) with its registered office at 1 Churchill Place, London, E14 5HP.  This email may relate to or be sent from other members of the Barclays Group.
_______________________________________________

Hey Javier,

> 4 spaces is the default for tab now. 8 spaces was the default before, 
> it says that is for old code.
ok - for me.

> Should we use mixed case function names instead of words sepparated by 
> underscores?
>
> That's the only objection I have to that standard
I prefer also mixedCase.
Btw this is what I proposed on the 
http://sunuml.wiki.sourceforge.net/Rules+%26+Coding+Style+Convention page ;)

What do the others think?

Steven

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
4 spaces is the default for tab now. 8 spaces was the default before,
it says that is for old code.<br>
<br>
I think we should use PEP8.<br>
<br>
Should we use mixed case function names instead of words sepparated by
underscores?<br>
<br>
That's the only objection I have to that standard<br>
<br>
Steven Gay escribi&oacute;:
<blockquote
 cite="mid:ad8...@ma..."
 type="cite"><br>
  <br>
  <div class="gmail_quote">
  <blockquote class="gmail_quote"
 style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">For
toolbox we can use FoldPanelBar class (comes with wxPython).</blockquote>
  <div><br>
ok - it true that you can have two panel open at the same time. Which
avoid the StarUML behavior of having to reopen all them all the time.<br>
  <br>
  <br>
  <br>
  </div>
  <blockquote class="gmail_quote"
 style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Code
style: I think we should follow wxPython style guide (<a
 moz-do-not-send="true"
 href="http://wiki.wxpython.org/wxPython%20Style%20Guide"
 target="_blank">http://wiki.wxpython.org/wxPython%20Style%20Guide</a>)<br>
  </blockquote>
  <br>
Arghh... wxPython doesn't follow the Python guidelines but the wx style
:(<br>
  <br>
The Python patch styles guidelines: <a moz-do-not-send="true"
 href="http://www.python.org/dev/patches/style/">http://www.python.org/dev/patches/style/</a><br>
  <br>
  </div>
  <div style="margin-left: 40px;"><i>A tab
character should <em>always</em> be equivalent to 8 spaces, not 4 as
is
the default in most editors on Mac and Windows.) <strong
 style="font-weight: normal;">Make sure all
lines fit in 78 columns.</strong> When submitting C code, don't use C++
style (//) comments. Write function and method calls like this; <b>foo(arg1,
arg2);</b><br>
  </i></div>
  <br>
  <a moz-do-not-send="true"
 href="http://www.python.org/dev/peps/pep-0257/">http://www.python.org/dev/peps/pep-0257/</a><br>
  <a moz-do-not-send="true" href="http://www.python.org/dev/peps/">http://www.python.org/dev/peps/</a><br>
  <a moz-do-not-send="true"
 href="http://www.python.org/dev/peps/pep-0008/">http://www.python.org/dev/peps/pep-0008/</a><i><br>
  </i><br>
Should we follow wxPython or Python ?<br>
  <br>
IMO Python as it is the <b>language</b> we choice but I will follow
the majority... :/<br>
  <br>
Regards,<br>
Steven<br>
  <pre wrap="">
<hr size="4" width="90%">
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
<a class="moz-txt-link-freetext" href="http://moblin-contest.org/redirect.php?banner_id=100&url=/">http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/</a></pre>
  <pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Sunuml-developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Sun...@li...">Sun...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/sunuml-developers">https://lists.sourceforge.net/lists/listinfo/sunuml-developers</a>
  </pre>
</blockquote>
</body>
</html>

For toolbox we can use FoldPanelBar class (comes with wxPython).

ok - it true that you can have two panel open at the same time. Which avoid
the StarUML behavior of having to reopen all them all the time.

Code style: I think we should follow wxPython style guide (
> http://wiki.wxpython.org/wxPython%20Style%20Guide)
>

Arghh... wxPython doesn't follow the Python guidelines but the wx style :(

The Python patch styles guidelines: http://www.python.org/dev/patches/style/

*A tab character should always be equivalent to 8 spaces, not 4 as is the
default in most editors on Mac and Windows.) Make sure all lines fit in 78
columns. When submitting C code, don't use C++ style (//) comments. Write
function and method calls like this; foo(arg1, arg2);
*

http://www.python.org/dev/peps/pep-0257/
http://www.python.org/dev/peps/
http://www.python.org/dev/peps/pep-0008/*
*
Should we follow wxPython or Python ?

IMO Python as it is the *language* we choice but I will follow the
majority... :/

Regards,
Steven

2008	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep (3)	Oct (27)	Nov (35)	Dec (1)
2012	Jan	Feb	Mar	Apr (1)	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec

sunuml-developers Mailing List for SunUML

sunuml-developers — StarUML developers