think tank forum

ttf development » branching

lucas's avatar
14 years ago
link
lucas
i ❤ demo
there are a few versions of ttf i want.

i want one with all of the basic features and simple edits. i think many people would find this software extremely useful.

i also want a version with fully versioned edits and archive "deletes." this would stay true with the OCD concept while remaining minimal.

then i want a version that really starts to branch out into an intuitive ui. it would go beyond traditional forum software concepts and truly become a canvas for a social spattering of words. anything goes here.

should i really have three branches of ttf? or should i just keep moving forward, forgetting about the earlier, more minimalist versions?
asemisldkfj's avatar
14 years ago
link
asemisldkfj
the law is no protection
this is tough. I like all of the different "versions" you've proposed, but I think it would kind of suck to maintain three separate branches of code.

you could release "feature packs" like the versioned edits and archiving as an add-on that the user could place right on top of the existing, basic ttf software. I'm not sure how you could accomplish this. you could release it as some kind of patch to the basic code or create some kind of plugin framework. I'm not sure of other options.

the third branch sounds really awesome. I think this would be easier to create as an add-on since it wouldn't mess with existing functionality so much as it would add new functionality.
lucas's avatar
14 years ago
link
lucas
i ❤ demo
each version will be significantly different, so i'd rather not just do the "add-ons" or "patches."

this is where i need real CS training--properly structuring software (architecture?) is difficult.

i think we'll just figure it out when we get there. but i really do want to go back and create a super-simple ttf with simple edits and deletes. god knows i wont ever use it, though. :)
asemisldkfj's avatar
14 years ago
link
asemisldkfj
the law is no protection
super simple would be nice. I just think doing the three separate branches would mean maintaining a lot of redundant code. maybe it would be huge identical blobs of code across all three branches, in which case it wouldn't be so bad I guess. but if a good amount of code across branches was slightly different or something it might get annoying.
lucas's avatar
14 years ago
link
lucas
i ❤ demo
really, though, the maintaining is minimal. and they would be more different than alike.
asemisldkfj's avatar
14 years ago
link
asemisldkfj
the law is no protection
I guess if you plan on kind of having a "final" product for at least the simplest branch, it wouldn't be so bad.