From: Ian B. <ia...@co...> - 2004-04-07 04:25:24
|
OK, the repository is more-or-less set up, now waiting for someone to use it. You can check it out in all its empty glory: svn co svn://w4py.org I don't know what we'll put in there. Thoughts? The only contents are a document which outlines how the repository can be used (still open for discussion, of course). I don't think you need a user account until you try to check something in. Feel free to ask for one -- I think we can treat this somewhat like the sandbox. (Should we move the sandbox into this?) The user account process is entirely manual, including setting passwords and the sort, but is separate from Unix user accounts. Subversion is very easy to pick up if you have CVS experience. In my own experience, it is comfortable but feels quite slick and polished in comparison to CVS (despite Subversion's young age). And who needs arch if we give out promiscuous user accounts? (Well, that might cause problems, but I think we should deal with any problems when they come up and not worry about them now) -- Ian Bicking | ia...@co... | http://blog.ianbicking.org |
From: Eric R. <th...@er...> - 2004-04-09 20:44:57
|
Guys, I put together another sample layout. Let me know what you think. http://www.webwareforpython.org/~eradman/ Eric Radman |
From: Scott R. <sc...@to...> - 2004-04-09 20:58:25
|
I like it quite a but, but http://www.webwareforpython.org/~eradman/Home/design1/graphics/corner_tr.png sits a number of pixels lower than the corner, ruining the effect. FireFox 0.8 (Screenshot: http://tinyurl.com/2pbsf ) |
From: Ian B. <ia...@co...> - 2004-04-09 21:17:58
|
Scott Russell wrote: > I like it quite a but, but > > http://www.webwareforpython.org/~eradman/Home/design1/graphics/corner_tr.png > > sits a number of pixels lower than the corner, ruining the effect. FireFox 0.8 > > (Screenshot: http://tinyurl.com/2pbsf ) I notice this when I scale up the font size, though not until then -- but perhaps you have a higher (lower?) DPI than I. I like design 2 a bit better than 1, and those more than 3. My first reaction is that I like the brightness. Though when I look back on it a second time, the black seems nicer. Oh, I don't know. I think the top bar on 1 and 2 make the site seem like more of a "place" than the bar in design 3 (which feels more like a simple "page", if that makes sense). Or maybe it's just the serif font in design 3. But I actually like them all. Also, I think the only interesting pieces for the sidebar would be MiddleKit, PSP, and WebKit -- at least the only ones that need to be so prominently highlighted. But just three items would make for too small a bar. I like putting the documentation in the forfront, but it would probably need to be organized differently. It will be a lot easier for us to maintain if they are also text links. And if we're going to host this on Webware, should we be doing something fun and dynamic? I can't think of anything for the front page that would make any sense, though. Ian |
From: Shayne O. <sh...@pe...> - 2004-04-10 04:09:35
|
Maybe a dynamic 'comminity projects' ticker. Like somewhere where new webware projects are mooted and appear. This'd give the impression of a dynamic and used software community. I also like the search facilities on the php page. Right up front and in yer face. -- Shayne O'Neill http://perth.indymedia.org I know how hard it is for you to put food on your family." ----George W. Bush On Fri, 9 Apr 2004, Ian Bicking wrote: > Scott Russell wrote: > > I like it quite a but, but > > > > http://www.webwareforpython.org/~eradman/Home/design1/graphics/corner_tr.png > > > > sits a number of pixels lower than the corner, ruining the effect. FireFox 0.8 > > > > (Screenshot: http://tinyurl.com/2pbsf ) > > I notice this when I scale up the font size, though not until then -- > but perhaps you have a higher (lower?) DPI than I. > > I like design 2 a bit better than 1, and those more than 3. My first > reaction is that I like the brightness. Though when I look back on it a > second time, the black seems nicer. Oh, I don't know. I think the top > bar on 1 and 2 make the site seem like more of a "place" than the bar in > design 3 (which feels more like a simple "page", if that makes sense). > Or maybe it's just the serif font in design 3. But I actually like them > all. > > Also, I think the only interesting pieces for the sidebar would be > MiddleKit, PSP, and WebKit -- at least the only ones that need to be so > prominently highlighted. But just three items would make for too small > a bar. I like putting the documentation in the forfront, but it would > probably need to be organized differently. It will be a lot easier for > us to maintain if they are also text links. > > And if we're going to host this on Webware, should we be doing something > fun and dynamic? I can't think of anything for the front page that > would make any sense, though. > > Ian > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Webware-discuss mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webware-discuss > |
From: Eric R. <th...@er...> - 2004-04-10 07:53:03
|
On 16:16 Fri 09 Apr , Ian Bicking wrote: > And if we're going to host this on Webware, should we be doing something > fun and dynamic? I can't think of anything for the front page that > would make any sense, though. Ian, Perhaps we could build a home page that is essentially a moderated Wiki portal. This would turn webwareforpython.org home page into interactive news/idea/documentation/source code site. The archive of Wiki updates could then be pruned and rolled into current documentation. In my mind this Wiki-home-portal site would blend features of: - User contributed documentation (http://www.php.net/manual/en/) - Searchable Forums (http://forums.gentoo.org/) - User-based information and access (http://my.yahoo.com/) - Repository for reusable components (http://cpan.org/) If this were to work properly a small group of wiki managers would take turns reviewing and cutting, and committing new Wiki posts. We don't need useless material! The paradigm shift that I'm talking about is transitioning from the idea of "home page" to "portal". Are you tracking with this idea or am I in orbit? Eric Radman th...@er... |
From: Ian B. <ia...@co...> - 2004-04-11 08:30:54
|
On Apr 9, 2004, at 4:16 PM, Ian Bicking wrote: > And if we're going to host this on Webware, should we be doing > something fun and dynamic? I can't think of anything for the front > page that would make any sense, though. To respond to myself -- some sort of syndication could work here. Right now I have the Wiki producing RSS, and we could create feeds for other items as well, like the mailing list and CVS, and perhaps including general Python sources, like the PyPI feed. We could aggregate different feeds differently -- keeping dedicated spots for Webware-specific feeds, showing other feeds in an aggregated form. -- Ian Bicking | ia...@co... | http://blog.ianbicking.org |
From: Eric R. <th...@er...> - 2004-04-10 04:08:20
|
The corner does move out of place, but it's not sized wrong--if you decrease your font size to normal it looks right. If we decide on a design we'll take the time to debug the designs. :-) Eric On 16:58 Fri 09 Apr , Scott Russell wrote: > I like it quite a but, but > > http://www.webwareforpython.org/~eradman/Home/design1/graphics/corner_tr.png > > sits a number of pixels lower than the corner, ruining the effect. FireFox 0.8 > > (Screenshot: http://tinyurl.com/2pbsf ) > |
From: Jason H. <ja...@pe...> - 2004-04-11 22:48:19
|
On Fri, 2004-04-09 at 16:44, Eric Radman wrote: > Guys, > I put together another sample layout. Let me know what you think. Great work, Eric! I like the #4 the best -- I far prefer the sans-serif fonts, and I like how there is more space (compared to #1 and #2) in the "content area" part of the page. For the logo, I prefer the font used in #1 and #2 to the handwritten all-caps version in #3 and #4. peace, Jason |
From: Ian B. <ia...@co...> - 2004-04-10 08:15:38
|
On Apr 10, 2004, at 3:51 AM, Eric Radman wrote: > On 16:16 Fri 09 Apr , Ian Bicking wrote: >> And if we're going to host this on Webware, should we be doing >> something >> fun and dynamic? I can't think of anything for the front page that >> would make any sense, though. > > Perhaps we could build a home page that is essentially a moderated > Wiki portal. > This would turn webwareforpython.org home page into interactive > news/idea/documentation/source code site. The archive of Wiki updates > could > then be pruned and rolled into current documentation. > > In my mind this Wiki-home-portal site would blend features of: > - User contributed documentation (http://www.php.net/manual/en/) This tends to be annotation-style, which may be somewhat different. Though ZWiki has an idea of commenting on a page vs. editing it -- but in reality it's just append vs. edit, and someone with editing permissions can rearrange the whole thing as they see fit. > - Searchable Forums (http://forums.gentoo.org/) Is a good full text search sufficient? > - User-based information and access (http://my.yahoo.com/) I think this is too optimistic -- we're not daily destination, after all. The exception would be RSS feeds, which I very much like. > - Repository for reusable components (http://cpan.org/) In an ad hoc way this could be the Wiki, especially if we allow attachments or binary pages. > If this were to work properly a small group of wiki managers would > take turns > reviewing and cutting, and committing new Wiki posts. We don't need > useless > material! I'm not that worried about bad material. Out-of-date material, certainly, but that's kind of a separate issue -- well, it takes some editorial work on people to keep the house clean. > The paradigm shift that I'm talking about is transitioning from the > idea of > "home page" to "portal". > > Are you tracking with this idea or am I in orbit? I'm certainly interested in all this. I've been working quite a bit on a Wiki in the last couple days (in the w4py repository), and I feel optimistic about using it fairly expansively. ReST is a real markup language, and I think is high enough quality to be the canonical format for documentation -- something that a lot of other Wiki markups don't achieve. It's not good at complex layout, but it's good for content, so I think most content pages could be adapted into reST form, and non-Wiki pages are allowed for. I'm also putting it in place so that one domain can use the same content as another domain, but with different controls. So webwareforpython.org could appear static, but wiki.webwareforpython.org could allow editing, which would be immediately reflected on the other site. Even more granular control would be possible. With some more metadata, we could probably do whatever we wanted. E.g., we'd want to mark documentation differently from user pages or brainstorm pages -- but instead of creating separate hierarchies, we can simply annotate pages to reflect their role(s) in the system. Right now I've just started converting our current Wiki pages over to reST, which is kind of tedious, but once it's done I'll be able to better see how it works for a real site. Once I've done that I'll set it up on the w4py server; hopefully this weekend. -- Ian Bicking | ia...@co... | http://blog.ianbicking.org |
From: Shayne O. <sh...@pe...> - 2004-04-10 08:29:27
|
I've had a couple of ideas on some of this (kinda off AND on topic) I'd really like to see a 'webware parts' type setup ,perhaps as a plugin, where theres a central repository of pre written objects that page designer could drop into his/her own design to achieve various functionalities that'd otherwise have to take a rewrite. If you could imagine;- Theres a central repository anyone can drop objects into. A 'testing' so to speak. Folks can then check em out and see if they are kosher, or require a little fixing, or even scrapping. Then they are moved into a 'tested' repository. An interface in the webware admin, can retrieve this, and say "Hey I'd like a little email client to stick in this intranet thing I'm doing". Click a button, and it downloads and puts it into a directory somewhere. CPAN style really. If theres essentially a style guide, with an apropriatley *simple* template, auth, and rendering structure behind it, someone could then drop into the servlet;- mailclient = webwareparts.mailclient() mailclient.init(self.request(),templatefile,auth,configfile) self.render(mailclient.render()) .. or something like that. As webware grows, these components will become more common, and eventually big projects will reduce down to the same sort of simplicity RAD environs like delphi and boa-constructor provide. Something to mull over. I *could* write the code for that (later, big project to finish first), though you may notice I'm not using the full webware kit yet. Still learning. **ANYWAY** An rdf capacity would be handy (hidden agenda: I need an rdf class) and a forum would be nice. I wonder what the logistics of porting squishdot from zope is? Thats a plenty fine little news/forum system. -- Shayne O'Neill http://perth.indymedia.org I know how hard it is for you to put food on your family." ----George W. Bush On Sat, 10 Apr 2004, Ian Bicking wrote: > On Apr 10, 2004, at 3:51 AM, Eric Radman wrote: > > On 16:16 Fri 09 Apr , Ian Bicking wrote: > >> And if we're going to host this on Webware, should we be doing > >> something > >> fun and dynamic? I can't think of anything for the front page that > >> would make any sense, though. > > > > Perhaps we could build a home page that is essentially a moderated > > Wiki portal. > > This would turn webwareforpython.org home page into interactive > > news/idea/documentation/source code site. The archive of Wiki updates > > could > > then be pruned and rolled into current documentation. > > > > In my mind this Wiki-home-portal site would blend features of: > > - User contributed documentation (http://www.php.net/manual/en/) > > This tends to be annotation-style, which may be somewhat different. > Though ZWiki has an idea of commenting on a page vs. editing it -- but > in reality it's just append vs. edit, and someone with editing > permissions can rearrange the whole thing as they see fit. > > > - Searchable Forums (http://forums.gentoo.org/) > > Is a good full text search sufficient? > > > - User-based information and access (http://my.yahoo.com/) > > I think this is too optimistic -- we're not daily destination, after > all. The exception would be RSS feeds, which I very much like. > > > - Repository for reusable components (http://cpan.org/) > > In an ad hoc way this could be the Wiki, especially if we allow > attachments or binary pages. > > > If this were to work properly a small group of wiki managers would > > take turns > > reviewing and cutting, and committing new Wiki posts. We don't need > > useless > > material! > > I'm not that worried about bad material. Out-of-date material, > certainly, but that's kind of a separate issue -- well, it takes some > editorial work on people to keep the house clean. > > > The paradigm shift that I'm talking about is transitioning from the > > idea of > > "home page" to "portal". > > > > Are you tracking with this idea or am I in orbit? > > I'm certainly interested in all this. I've been working quite a bit on > a Wiki in the last couple days (in the w4py repository), and I feel > optimistic about using it fairly expansively. ReST is a real markup > language, and I think is high enough quality to be the canonical format > for documentation -- something that a lot of other Wiki markups don't > achieve. It's not good at complex layout, but it's good for content, > so I think most content pages could be adapted into reST form, and > non-Wiki pages are allowed for. > > I'm also putting it in place so that one domain can use the same > content as another domain, but with different controls. So > webwareforpython.org could appear static, but wiki.webwareforpython.org > could allow editing, which would be immediately reflected on the other > site. Even more granular control would be possible. > > With some more metadata, we could probably do whatever we wanted. > E.g., we'd want to mark documentation differently from user pages or > brainstorm pages -- but instead of creating separate hierarchies, we > can simply annotate pages to reflect their role(s) in the system. > > Right now I've just started converting our current Wiki pages over to > reST, which is kind of tedious, but once it's done I'll be able to > better see how it works for a real site. Once I've done that I'll set > it up on the w4py server; hopefully this weekend. > > -- > Ian Bicking | ia...@co... | http://blog.ianbicking.org > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Webware-discuss mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webware-discuss > |
From: Jason H. <ja...@pe...> - 2004-04-12 18:55:33
|
On Sat, 2004-04-10 at 03:15, Ian Bicking wrote: > On Apr 10, 2004, at 3:51 AM, Eric Radman wrote: > > - User-based information and access (http://my.yahoo.com/) > I think this is too optimistic -- we're not daily destination, after > all. The exception would be RSS feeds, which I very much like. Speaking of RSS, it would be very cool to create "Planet Webware" (see http://planet.gnome.org), an aggregate of blogs of people who talk about Webware (among other things). I visit the gnome, debian and python planets regularly. As the planet code is written in Python it would probably be a snap to integrate it into our site. -- Jason D. Hildebrand ja...@pe... |