|
From: Lark <la...@fe...> - 2000-07-12 04:33:26
|
Since I get a daily digest of the messages, I'll simple answer everything in
one messgage.
From: Rob Tsuk <ro...@ts...>
> I have the PowerPlant UI skills needed to implement the Scribia UI. Before I
> get started I was wondering what UI is desired? Should I just clone Scribus?
I think the Scribus interface would be an excellent starting point. In
general, I'd like to get Scribia to be feature-identical to Scribus before
adding (large) new parts. Then again, people will work on whatever they
think most interesting, as it should be :-).
From: Pugwash <pu...@ac...>
> Hi Scribia developers! So what's the next step? I've subscribed to the mailing
> list so now what? Do I register as a new user on the sourceforge site?
Depends. If you just want to grab the source and compile it, you can get it
via anonymous CVS, without the need to register with sourceforge.
If you'd like to actively develop Scribia (i.e. make larger code changes
you'd like to contribute back to me/us) I will add you as a developer. For
that, you will need to do these steps:
1. sign up with sourceforge
2. tell me your sourceforge user name, so I can add you as a developer
3. open a customer service item with sourceforge, and ask them to set up CVS
"pserver" access to the scribia CVS repository (SSH does not work on the
Mac)
After that, you have read/write access to the CVS repository. Cyguns and
Rob: If you'd like, I'll set this up for you as well, of course.
Since I don't know if people have used CVS before, here are some short
things you should know:
commit log entries are your friend, please take the time to describe
changes made to the code
never check in code that has known bugs, or worse, does not compile
(people will get angry if they'll have to fix your bugs after they have
CVS updated your changes)
try to use the indentation style of the rest of the sources for new
things/changes (I've tried to stick to the "Mac way" of indentation and
naming things as much as I could figure it out; it's not perfect)
include the HEADER file (Documentation folder) at the top of each new
source file, it has some magic CVS tags in it that auto-insert the commit
log, current version, etc. (it also has the disclaimer)
The copyright will change ("soon") from "Lark" to something like "The
Scribia Developers".
Other good news: Cygnus just let me know he can compile now :-) For other
people looking for MoreFiles 1.4.9 that is needed for Scribia: It is part of
one of the CW PowerPlant examples (I think a debugging example?) I'm unclear
on the copyright, maybe we can even redistribute it with Scribia and simply
make it part of the CVS tree?
Talking about the CVS tree: I've replaced the binary project file
(Scribia.mcp) with an XML text export of the project file (Scribia.mcp.xml).
I hope this will make it easier to maintain it under CVS - is anybody
opposed to this? (It's a little more work, since you'll have to remember to
import/export this file if it changes.)
From: Rob Tsuk <ro...@ts...>
> Attached is a copy of CScribiaDoc.cp that fixes the crash bug. I would check
> it in myself but I don't have write access to CVS.
Great! I'll check it in right away.
See above for the steps to get CVS write access.
Lark
|