Community

General discussion

Locked

Workspace. addon idea...

By Jaqui ·
and Question..

When is the Shared Project functionality going to be implemented? any timeline on it?

for a test of that, why not have some members collaborate on a site script that duplicates TR's, with the feature requests that have been most frequently asked for.

it may require adding something like cvs or subversion tools to the workspace though.
[ or one member putting a version control server space up for it. ]
if that happens then that same box could also be used as a platform for testing the script with.

since this script could become part of the foundation for further TR improvements, I doubt that such a project would ever become visible to the general membership, which is why I posted the idea in here.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

hey you

by Jaqui In reply to I would love to help

welcome to TRI !!!!


we don't know what the TR powers that be are going to require yet, so we can't really make any decisions on the technical aspects yet.

Collapse -

Thanks and I am Glad

by stargazerr In reply to hey you

This idea of yours is brilliant ... :)

Whatever the technical aspects might be ... I would love to help. This is a great opportunity to learn and put stuff into practise.

]:)

Collapse -

well I do know

by Jaqui In reply to Thanks and I am Glad

that I'll push for the script to generate pages that are xhtml1.0-strict standard.
and that we can validate them error free.
even for the css used for layout..validate that also.

usefull end user documentation, simple install and configure, some things are pretty obvious as to goals to work on..

we have to pick either mysql or postgresql for the database to work with, since those are what's available. But TR doesn't use either so the correct db access data will have to be available for all database engines. [ configure that during the install stage, so only one real set of connection data is used. ]

each module will be able to work off it's own database, if so desired by site owner.
[ actually a good thing to do, so that if you have a high traffic site, it can break apart the heavier traffic area(s) into separate database engines / servers and improve the service ]

Collapse -

Incidentally

by stargazerr In reply to well I do know

I must have either forgotten or my memory wiped clean. What Database "does" TR use?

]:)

Collapse -

several

by Jaqui In reply to Incidentally

It hasn't ever been formally put out for public knowledge.

but I do beleive that it's 4 different engines, all MS os based.
sybase, mssql / ms server 2003 being some that I vaugely remember being mentioned

Collapse -

optional crap

by apotheon In reply to well I do know

I'm interested in including Javascript (even perhaps AJAX) that degrades gracefully. I'm also interested in making sure that it can work with flatfile databases that are human-readable, as well, if someone wants to run it that way. In fact, it might make sense to code up a separate database-interface module. The data model should be decoupled from the rest of it anyway, for best design, so that's not really a stretch.

I'm also suddenly thinking that a remote CLI interface would be pretty damned spiff. What I wouldn't give to be able to compose my blog posts in Vim and just enter a command to have it post. Wow.

Ooh, that reminds me -- blog posts. We need a more-seamless means of being able to sync up blog posts between TR and other blogs. I'm not entirely sure how to make it "more seamless" than RSS, though, without serious security issues.

Collapse -

are you writing these down?

by Jaqui In reply to optional crap

this is getting bigger and bigger..

We are going to have to go after basic functionality, then add the features, or we'll get nowhere.

sqllite uses flat files, so making sure it can work with that gets the flat file functionality... partially

as to syncing blogs, that would be a combination, of server settings between both blog hosts. if they don't have the same interval for updating, then the import will be delayed to fit the export.

I do think TR set the update delay themselves.

adding support for uploading a file as a blog entry might be better than opening a console, as if the host is windows based you wouldn't have vim to work with.
[ os agnostic script..remember ]

Collapse -

re: CLI

by apotheon In reply to optional crap

I was just thinking of providing a server interface for a local client using SSH, or something like that. The client side configuration need not even be known to the server.

re: writing it down
Heck no. I type.

Collapse -

technical stuff

by apotheon In reply to I would love to help

Nobody knows yet what language(s) we'll be using, whether we'll be building on any frameworks, and so on. We don't even know yet what license we'll use, though I'm hoping for CCD CopyWrite's next version.

I do know that it would be insane to make it any kind of platform-specific, or make it require anything on the client side other than a browser that handles standards-compliant markup. That's not to say there won't be CSS and Javascript involved, but they'll need to degrade gracefully.

I'm going to go put on my asbestos suit now, before Jaqui notices I mentioned Javascript.

Collapse -

~evil grin~

by Jaqui In reply to technical stuff

abstestos doesn't work..when you are in a blast furnace. ]:)

geez, next you'll want it sprinkled liberally with frontpage extentions and flash.

<dropping 100 tonnes of napalm on apotheon>

Related Discussions

Related Forums