New starter..

[Graham]

Hi - I've been using wikidpad for a while now - adding various
suggestions to poor Michael's todo list. I thought that I'd get off my
butt, and use Wikidpad development - as a tool for learning Python
etc. After all - if I want a change badly enough - I should be willing
to put some effort into building it.

OK - at the risk of being a burden - How do I get the source code from
the SVN repository - under Linux? (Only Windows is covered in the
Wiki). Befoe I do this - will that fact that I want to use Linux as a
development platform cause any problems to anyone else?

What's your general way of working? - create a personal branch and
update it - and ask Michael to merge changes into the trunk when they
are stable?

So - newbie questions - I hope this isn't a problem
Thanks
Graham

[StefanB]

On Sep 11, 7:18 pm, Graham <gandalfmeis...@gmail.com> wrote:


> OK - at the risk of being a burden - How do I get the source code from
> the SVN repository - under Linux?

You can download the source code from http://wikidpad.sourceforge.net/
(currently wikidPad 2.0beta07 source code or wikidPad 1.9rc08 source
code). Extract the files to a directory in your home directory. Change
to that directory and start WikidPad with "python wikidpad". Make sure
you have python-wxgtk2.8 and python >= 2.3 installed. You don't need
the source files installed to create extensions. Starting WikidPad
from a command prompt gives you the error messages (if any) that you
need to improve your extensions.

(Only Windows is covered in the
> Wiki). Befoe I do this - will that fact that I want to use Linux as a
> development platform cause any problems to anyone else?

There are some extensions that come with warnings, like
http://trac.wikidpad2.webfactional.com/wiki/CmdLineIns, but generally
I don't think that extensions would cause any harm to computers.
However, it is always a good idea to test the extensions in different
operating systems before making them public, since some python code
works in Linux and not in Windows and vice versa.

>
> What's your general way of working? - create a personal branch  and
> update it - and ask Michael to merge changes into the trunk when they
> are stable?

If I need a feature I develop it and use it for myself. I seldom
publish it, mostly because I'm a newbie myself and my work consists of
pretty ugly code. I look into other extensions and the WikidPad source
files to get the code I need for my extensions, modify it and then run
it from the user_extensions directory. I never ask Michael to merge it
into the source, but publishing extensions on the WikidPad wiki is
probably a good idea to encourage other users to improve.

[StefanB]

On Sep 14, 7:37 am, StefanB <steff...@gmail.com> wrote:
> I never ask Michael to merge it
> into the source, but publishing extensions on the WikidPad wiki is
> probably a good idea to encourage other users to improve.

Of course I mean "to encourage other users to improve _the
extensions_" ;)

[Graham]

Many thanks for the feedback. As I'm completely new to Python it will
probably be a while before I produce anything of value to anyone. I
guess extensions are the best way to start, but some of my ideas are
probably primarily related to the core code base.
But - small steps first...
Graham