bitsyblog: roadmap.txt annotate

annotate roadmap.txt @ 19:8931c5b7e632

* fixing up index to display [in progress] * 404 if no logo

author	k0s <k0scist@gmail.com>
date	Sun, 25 Oct 2009 21:30:42 -0400
parents	e3823be6a423
children

rev	line source
0 e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	1 bitsyblog, middleware, and the roadmap to the future
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	2
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	3 the nice thing with working like software like bitsyblog is that the
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	4 intent of the software is clear. bitsyblog aims to provide a solution
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	5 for users to keep a log of their activities on the web. When thinking of
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	6 software in terms of the narrow intent of a component, it becomes much
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	7 easier to divine what sort of framework would look like around it and
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	8 how this framework might be applicable to other types of software.
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	9
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	10 Firstly, I noticed that the bitsyblog component app is not as small as
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	11 it could be. bitsyblog provides a multi-user solution to (personal)
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	12 blogging. This level of solution should exist, but thinking in terms
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	13 of components it is easy to see that users may want a personal blog
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	14 that is not multi-user. lammy wants a blog on his desktop computer.
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	15 When at his computer, he probably wants to be logged in all the time
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	16 (always accept connections from 127.0.0.1). He doesn't want other
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	17 people to be able to make a blog there. When not at his desktop, he
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	18 wants to be able to login and post through the web and maybe used the
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	19 blogme.py script too. In bitsyblog terms, '/lammy'
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	20 becomes '/' and all urls ('preferences', 'post', 'css/') become
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	21 relative to this. Doing this involves separating out the individual
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	22 blog components from the multi-user component and probably having
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	23 different .ini files from which to run paste.
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	24
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	25 I've also realized that the way I handle CSS is a solution to a
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	26 problem that has nothing to do with bitsyblog. The other items in
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	27 preferences ('date', 'subject', but not 'friends' which has to do with
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	28 roles) are about formatting the blog posts. The CSS is about themeing
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	29 pages which has nothing to do with blog posts. So what is needed is a
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	30 CSS component, which is possibly linked to from the preferences page.
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	31 Lets put this at '/lammy/css'. This pages may have the fields for
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	32 preferences, but also provides an interface for managing the CSS. A
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	33 user may want to delete CSS or edit them, render the current page with
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	34 a selected stylesheet or what's in the editor, or render an arbitrary web page
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	35 This is like CSS zen garden, but more interactive, and
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	36 (optionally) allowing the user to save the CSS and apply it to their
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	37 pages. I can also imagine, in a 2.0 version, an implementation that
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	38 allows permits transforming of CSS to suitable to theming a page with
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	39 a stylesheet intended for another page. One has a stylesheet with a
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	40 bunch of rules. Using javascript, one mouses over the DOM of the
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	41 other page. The rules are modified in order to applied to the
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	42 appropriate container on the page. This sounds much like what
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	43 deliverance is supposed to do, and maybe it could be utilized for this
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	44 intent, though perhaps the intents are different and its better not to
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	45 use it (to be investigated).
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	46
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	47 Both of the above components fall into a general pattern: there is a
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	48 component which is the multi-user blog manager. Lets call this
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	49 bitsyblog. There are microcomponents, the single-user blog (lets call
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	50 this microblog) and the CSS zen garden component which lets you play
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	51 with stylesheets (I dub thee samadhi). microblog and samadhi can live
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	52 on their own, in which case they live at '/', or they might be managed
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	53 by an external component -- microblog by bitsyblog, or samadhi
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	54 by...not really sure, either a microblog instance or bitsyblog. In
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	55 the latter case, they need to know where they live. I'm not sure what
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	56 provides the rewrite rule telling them where they live. Ian? Ethan?
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	57 There are a few configuration type details -- like auth, whether
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	58 samadhi needs to know about where to put these CSS files or how
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	59 bitsyusers can fetch them, but essentially if you give these the
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	60 appropriate path, they should be able to work relatively
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	61 independently.
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	62
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	63 In a different class of components are comments and tagging. While it
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	64 is easy to imagine bitsyblog managing comments and tags, it is also
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	65 fairly easy to see that these services really don't need to know what
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	66 is being commented or tagged on. For commenting, I imagine an app
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	67 similar to smokesignals, but with a different persistence model. Lets
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	68 call it commentator. Commentator is a javascript app with no
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	69 intrinsic URLs. Given a set of rules (for instance, "allow commenting
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	70 on <div>s with an id attribute) a block of text is shown as the last child
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	71 of each <div> (or conditionally on mouseover). This will initially
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	72 say something like "No comments \| Add a comment" where each of these
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	73 do what you think ('N comments' displays the comments, 'Add a comment'
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	74 gives a textarea where you can say your mind). When a comment is
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	75 added, it is put in a database (presumedly SQL, though really on a
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	76 super-simple db is necessary) with the URL and/or id
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	77 as its key. When the page is loaded, the text of the page is examined
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	78 on response and the appropriate comments are displayed. It is also
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	79 necessary to have some sort of mapping optionally between URL and id
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	80 to another URI, as blog posts both are displayed as part of the user's
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	81 entire blog and also have a unique URL. Notice that nothing here is
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	82 particularly unique to blogs. Commenting on <div>s or <p>s in a wiki
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	83 page is essentially the same (though in this case, it might be better
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	84 to comment on the entire page, as these may not have ids and the page
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	85 can be editted all willy-nilly like that. Commenting on individual
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	86 <p>s and <div>s is, however, a really nice thing to have, so in a 2.0
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	87 type incarnation of commentator, this should be added regardless of
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	88 the difficulty). If bitsyblog was part of a
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	89 site with a wiki, then commentator could deal with them both nicely.
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	90 Optionally, one might specify the rule that if an item had comments,
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	91 it either could not be deleted or that an alert would pop up before
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	92 deletion with [Confirm] and [Cancel] buttons. This is easy to do if a
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	93 browser could do a DELETE request and things behaved all RESTful.
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	94 Otherwise, this would also be a non-trivial problem.
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	95
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	96 Tagging is very similar to commentator, though it might have a few
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	97 intrinsic URLs too. You specify a similar set of rules concerning
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	98 what can be tagged ("all <div>s with ids in /%(user)s/ and
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	99 /%(user)s/200*") and a method pointing the ids to URLs. Then you have
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	100 a database, which again is pretty simple and again in its simplest
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	101 form could be a dictionary. Though here, the tags are the keys and
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	102 the URLs are the values. You could also record number of tags per
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	103 item, specify whether non-authenticated members can tag, etc. As the
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	104 first or last child of each (say) <div>, you have what it has been
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	105 tagged with, maybe weighted by how many times it has been tagged. You
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	106 have a URL for searching by tags, maybe on a per-path basis ("I want
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	107 to see all the tags under /k0s that have been tagged with 'cats' and
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	108 'cute'"). You could also have a URL for the tag cloud. Again, what
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	109 is being tagged is pretty divorced from the tagging component itself
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	110 (lets call it tagit, unless that name is taken).
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	111
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	112 I have presented samadhi as being managed by bitsyblog or microblog
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	113 and commentator and tagit living outside of bitsyblog in the
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	114 middleware stack. I've done this because this "feels right" to me
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	115 right now, though I reseve my right to change my mind about it. The
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	116 thing I want emphasize is the difference in the two approaches:
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	117
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	118 * When a WSGI app is "managed" by another component app, the manager
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	119 has to know about the managed app and dispatch the appropriate
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	120 information (request, etc) to it, though in doing so it has the
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	121 opportunity to have more control over the URL structure and what the
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	122 component app does. It is also easier to return HTML this way.
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	123
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	124 * When a WSGI "app" is used as middleware and needs to markup the
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	125 returned page in HTML, this is conducive to using javascript in
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	126 order to insert nodes into the DOM dynamically, presumedly based on
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	127 some rule set. Alternatively, the middleware may decompose the page
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	128 with lxml and insert HTML where it needs to go that way. In this
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	129 approach, the middleware need not have a URL (this may be
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	130 preferable).
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	131
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	132 It is not necessarily clear to me at this time which approach is
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	133 better for different apps. I have put commenting and tagging in the
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	134 latter category because commenting and tagging on web pages seems
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	135 divorced (save by a rule set) from what is being commented on or
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	136 tagged. I have put microblog in the first category because it is
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	137 clearly in the same layer of software as bitsyblog, and some
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	138 management tasks will be necessary even for microblog. samadhi I put
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	139 in the first category as well (though I hesistate right now) because
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	140 otherwise the rewriting of URLs makes me nervous. Perhaps there is
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	141 need of a WSGI dispatcher that fetches apps based on some sort of rule
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	142 concerning the URL? Also, it seems
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	143 necessary to put the CSS on user data. This could also be
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	144 accomplished the other way: 1. abstract out members and roles
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	145 (teamroler?) and store the data (CSS, etc) on them here; 2. have
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	146 samadhi write a defined set of urls (how defined? not sure) including
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	147 the stylesheets that it knows about, presumedly putting the 'foo'
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	148 stylesheet at '/lammy/css/foo.css'. This still involves samadhi
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	149 knowing something about the url structure, and now it is dependent on
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	150 the user/role thing, though this could be a configuration option.
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	151
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	152 This is the middleware story. Other things could also be done
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	153 internally to bitsyblog and its supporting software to make the
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	154 experience more seamless.
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	155
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	156 I am bothered by the fact that the logic supporting the form and user
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	157 settings is somewhat divorced. Ideally, rendering the form should do
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	158 all the validation and return the settings in a sensible way to use.
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	159 I don't think this is hard -- the settings.py should just be
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	160 incorporated into markup.form. This goes some ways to reinventing
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	161 things like formencode and zope.schema, so if we can get these to do
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	162 what we want, maybe we shouldn't write our own. But at cursory
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	163 glance, formencode won't and zope.schema isn't easily usable outside
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	164 of zope. So maybe rolling our own isn't bad.
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	165
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	166 There's more middleware, but its hidden and is a bad coupling (that
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	167 is, the app will depend on the middleware unless its done cleverly).
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	168 The site nav does not appear on '/login' or '/join' (or any url not
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	169 specified internally to bitsyblog, for that matter). It would be
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	170 conceivable to have a SiteNav middleware that (either through
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	171 javascript or lxml decomposition) writes the site nav at the top of
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	172 the screen. bistyblog and bitsyauth would have to know about this
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	173 though, so that they could add the relevent links into environ. Maybe
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	174 this isn't horrible, but it seems so. Likewise, the site css doesn't
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	175 show up here. Should it? Is this another piece of middleware or part
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	176 of samadhi?
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	177
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	178 An important piece of middleware should involve members and roles. I
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	179 really don't want to write this one, but I would like to consume it.
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	180 It should live just inside of bitsyauth and make the users.py file
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	181 unnecessary. It might be better to sit on this one until last.
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	182
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	183 So should be bitsyblog 2.0.
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	184 There are a few other streamlining things (see the TODO.txt), but if
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	185 all of this was implemented, bitsyblog would be a rich web experience
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	186 that was highly componentized with each of the components doing one
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	187 thing well. Moreso, since coupling is avoided, save through
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	188 configuration, auth, and other loose links, each of these components
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	189 could be used independently of bitsyblog or turned off without
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	190 undesirable consequences.
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	191
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	192 At least as much as being a good blogging app, bitsyblog is about
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	193 elegant design and component architecture. This roadmap shows what is
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	194 possible in terms of having a fully functional blogging application
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	195 with middleware that can be used outside of just bitsyblog. To take
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	196 the other end of the spectrum, wordpress says "Hey, write plugins that
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	197 will make me work better." As a programmer, I really hate this
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	198 approach. If I write a commenting plugin for wordpress, then I have
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	199 just that. If I want to use it to comment on a wiki page, I'm out of
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	200 luck. If I write commenting middleware, then it can be used for any
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	201 WSGI app with minimal configuration. As a programmer, I generally
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	202 want the freedom to assemble a webapp however I want. With this
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	203 freedom comes some work, but for me its a worthy sacrifice. As a web
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	204 consumer, I understand that site administrators want out of the box
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	205 solutions. bitsyblog will offer this too. The default deployment of
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	206 bitsyblog will pull down commentator, samadhi, and tagit and have an
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	207 .ini file pointing to the appropriate factory to create the chain of
e3823be6a423 initial commit of bitsyblog, from https://svn.openplans.org/svn/standalone/bitsyblog/trunk/ k0s <k0scist@gmail.com> parents: diff changeset	208 middleware to have all of these pieces in place. There is no contradiction.

Mercurial > hg > bitsyblog

annotate roadmap.txt @ 19:8931c5b7e632