Re: [Pythoncad-developer] Test on new canvas render

[Matteo B. <mat...@bo...>]

We do not know how long the wiki site will work...
It's under a private server and we do not know how long can host our
project.
Best think will be to move the wiki page on sourceforge and write the
use case there..

What do you think ?

Regards,
Matteo



On Tue, 2010-02-02 at 07:15 +0530, Yagnesh Desai wrote:
> Why do we need to create such documents
> we can use issue tracker or wiki which has better
> visibility and control.
> 
> On Tue, Feb 2, 2010 at 4:41 AM, Gertwin Groen <ger...@gm...> wrote:
> > Hi All,
> >
> > I have made a start with the use cases.
> > I have put them in the repository: "R38/pythoncad/Doc/use cases"
> >
> > The document "use cases.odt" contain a list of use cases, for each use
> > case there is one file.
> > I made a start with the use case "share point.odt", take a look at it.
> > If you have remarks, add them to the document.
> >
> > If you mis a use case list it in "use cases.odt" and create a new
> > skeleton "new use case.odt" document.
> >
> > We should describe all the actions etc. that the user can do in PythonCAD.
> > Please assist me to write the use cases, use many pictures for new
> > dialogs (glade mock-ups or made with the gimp, doesn't care).
> >
> > This way we can create a consistent user interface and forces us to
> > think about the implementation.
> > Also this can act as an input for the user manual.
> > We can assign use cases to each other and to new developers.
> >
> > Regards,
> > Gertwin
> >
> >
> >
> >
> > 2010/2/1 Matteo Boscolo <mat...@bo...>:
> >> Hi all,
> >>
> >> I think that implementing pyGui take a lot of time, and the code command are not the some of gtk.
> >> I do not make any deep analysis but it seems to me that we are going to make a lot of work to migrate in pygui.
> >> Even if the installation require 2 setup in windows pygui and pywin32 (ok may be the installation is easier the pygtk but for common windows user will be difficult).I do not test pygui but it seems that not a lot of people are using it.
> >> And with pygui you are using a more layer of code ..(Bad performance)
> >> May be it will be a good choice if we start from zero ...
> >> For my point of view the best choice is to stay on gtk and became more skilled to deploy installer package that are very easy to use for windows user add mac user.
> >> Have a look at https://sourceforge.net/projects/py2exe/ this package is able to create an a single axe file starting from a python script.
> >> I will make some test if it works for pythoncad and let you know.
> >>
> >>
> >> Regards,
> >> Matteo
> >>
> >>
> >> -----Original Message-----
> >> From: Yagnesh Desai [mailto:yn...@gm...]
> >> Sent: 01 February 2010 06:20
> >> To: ger...@gm...
> >> Cc: Matteo Boscolo
> >> Subject: Re: Re: Test on new canvas render
> >>
> >> Front End related
> >>
> >> 1. I feel PYGUI is gr8 as it seems more native [and above all its PYTHON]
> >>
> >> 2. opengl may be very fast but needs more non python codes to
> >> integrate, we are 2D CAD
> >> and need to attract more CAD engineers than Programmers. We will leave
> >> 3D for FreeCAD and
> >> other existant projects.
> >>
> >> 3. GTK we may stick to it till next 1 or 2 release, by the time new
> >> solution is available.
> >>
> >>
> >>>>>
> >> My additions to the decision list:
> >>
> >>
> >> opengl:
> >> good think:
> >> very fast
> >> in case we want to go on 3d no change of the way we show the entity
> >> bad think:
> >>
> >> we need to learn how it works (personally i never use it)
> >> installation problem we need more pakage to make it works
> >> as gertwin say on mac we get some trouble (see remark).
> >>
> >> Remark:
> >> 1) We can use the PyGui library, no additional install needed.
> >> 2) Or we can create a separate OpenGL window which is not embedded in
> >> the application.
> >> Pros:
> >> Usable on all platforms, view is not dependent on a toolkit.
> >> We can define multiple views in which the user can work on different
> >> parts of the drawing (like the old MicroStation V4).
> >> Multiple screens can be effectively used by multiple graphical views.
> >> cons:
> >> Looks a little old fashioned, see some thing like:
> >> http://geuz.org/gmsh/gallery/screenshot.png
> >>
> >>
> >>
> >> gtk with displaylist:
> >> good think:
> >> no need to change the way that we draw the entity
> >> it's no so slow if we build some smart algorithm
> >> bad think:
> >>
> >> at the moment no bad think in mind
> >> No real time zooming and panning possible, only on small parts of the drawing.
> >>
> >>
> >
> 
> 
> 
> -- 
> Best regards
> 
> Yagnesh Desai
> 
> Save a tree...please don't print this e-mail.
>