Tuesday, September 12, 2006

web ide pet project progress

well i've been making slow but sure progress on my new pet project in my lunch hours.
I've got the first bit of functionality woring pretty much how i want. you can now enter code in pretty much any language i can think of, click a button and it will be higlighted and displayed to you so that you continue editing.

Im pretty happy with this apart from the fact that the fckeditor rich text box that i use seems to be defaulting to a specific size. and no matter how i manipulate the html around it, it won't get any bigger.

I've got most of the layout sorted now, its basically 4 table cells. one for your code, one to display all the other people cwatching you code, one to display the code of someone you have selected from the list of watchers and finaly one to display "other stuff", at the moment this may just be a list of files associated with the project.

Which brings me onto the next thing i'm thinking about, really getting down my db design. i've been thinking it'd be nice if you could have a Project, which could have many files (maybe classes, maybe not) related to it.

i've also been thinking about how the relationships between developers and projects will work. that seems to be a many to many relationship (a developer can work on many projects and a project may have many developers) so it'll need what i call an intermediary table.

But the bit i'm not sure how to implement is the idea of having public and private projects, a developer may start a projects and not care who watches, on the flip side a developer may start up a project and only want specific people to be able to participate on the project.
maybe this is getting into role based territory, if you are authenticated and in a specific role then you can view the project?

but then who assigns the roles? maybe when a developer creates a project they get presented with a list of developers, from that they themselves can assign the roles?

which then moves me onto the another thign i'll have to tackle. i've yet to get to grips with the whole asp.net 2 role/membership/profile providers model. mainly cos i think its a bit wank, in terms of blobfying the data, so you can't write queries against it. but maybe this is the answer for what i need to do.

i think i feel some reading coming on

No comments: