Yeah, I will do that...
I know too that gallery/clipart section is going to be necessary sometime here. But I feel weird about moving the focus off the application and onto what is created by it. Seems like that kind of content should be linked to people's personal sites.
Anyway...
Jon
On Wed, 2004-01-07 at 22:38, Bryce Harrington wrote:
Thanks Jon!
Can you also set up a permanent area on the main page for putting a few screenshot thumbnails? (c.f. docsys.sf.net.)
Bryce
On Wed, 7 Jan 2004, Jonathan Phillips wrote:
I got the screenshots covered! Already changed on the roadmap b4 this email. It might be nice though to get a couple of screenshots from OS X and win32 users...I'll be asking for those in a few...
Jon
On Wed, 2004-01-07 at 22:17, Bryce Harrington wrote:
Of the remaining tasks for the 0.37 release, there are a few items that we need volunteers for:
Create new screenshots for website
Review/remove obsolete (#if 0) code
Remove the SP prefixes and put into namespaces (e.g., SPFoobar -> Inkscape::Foobar)
Most of these don't require a lot of experience with the codebase or C/C++, but they do require a lot of effort, so what we'd like to do is divide up the work among many hands. If each of us puts a few cycles in, it should not take long to tag team them all to the ground.
- Creation of new screenshots is easy. Set up your desktop to look
spiffy, with something "interesting" going on with Inkscape. Perhaps most helpful is if each screenshot focused on a specific feature (especially new ones like booleans and inset/offset). We also want a very attractive one to put on the homepage. If you want to do this, make the screenshot and announce it on this list, and we'll add them to the website. You can post your screenshot to your own webserver, or email to me directly (not to the mailing list).
- Removing of the #if 0 code should be straightforward. There are
large sections of code in the codebase that have been fenced off with pre-processor macros so that they never get compiled in. Why are these chunks of code in there? By definition, they're not necessary so probably can just be deleted, and so that's the plan. However, we need them to be reviewed to make sure we're not deleting stuff that's important. If you want to look at this, I've broken out the work by subdir in the Roadmap, so go sign up there. Each item should be a couple hour's worth of work, max, I figure.
- Currently the code uses prefixes, but since we converted to C++ we
want to use proper namespaces. I.e., instead of SPFoobar we want to have Inkscape::Foobar (more or less). This can partly be done mechanically through scripts, but we also want to move things around in the process. Details about the namespaces to use are available from the SubsystemRearchitecture document in Wiki. If you're interested in working on this, contact Mental, or just go ahead and start submitting patches and we'll work things out as we go.
Thanks, Bryce
This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel