So I''ve looked over the Typo code and concluded that: a) Typo is AWESOME, thus I''ll refrain from making my own blog engine from scratch b) Typo is not a drop-in plugin or "engine" as it is right now c) I''m going to turn it in to an engine. Given this latter conclusion, I have a couple of questions: 1. The software app I''m building at syncPEOPLE needs to have multiple blogs. I''ve considered forcing a one-to-one relationship on categories so that each category is its own "blog", but that just doesn''t seem right. Does anyone have code that turns Typo in to a multiple-blog Blog? 2. Is there a recommended way of keeping a "Typo Engine Branch" up to date while still maintaining changes necessary to enginify it? My current take on the matter is that SVK is going to do the job... though it''s a bit over my head. I''ll have to look back on the archives for Jeremy Kemper''s excellent "Quick Start" post. An alternative (if there''s interest by the Typo core team--Tobias?) is to make an official branch on leetsoft''s repo. In fact, it might even be in everyone''s best interest to convert the TRUNK in to an engine and make the "default install" just a dummy Rails app that drops the Typo Engine in. That would be very cool. Duane Johnson (canadaduane)
On 11/4/05, Duane Johnson <duane.johnson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> So I''ve looked over the Typo code and concluded that: > > a) Typo is AWESOME, thus I''ll refrain from making my own blog engine > from scratch > b) Typo is not a drop-in plugin or "engine" as it is right now > c) I''m going to turn it in to an engine. > > Given this latter conclusion, I have a couple of questions: > > 1. The software app I''m building at syncPEOPLE needs to have multiple > blogs. I''ve considered forcing a one-to-one relationship on > categories so that each category is its own "blog", but that just > doesn''t seem right. Does anyone have code that turns Typo in to a > multiple-blog Blog? > > 2. Is there a recommended way of keeping a "Typo Engine Branch" up to > date while still maintaining changes necessary to enginify it? My > current take on the matter is that SVK is going to do the job... > though it''s a bit over my head. I''ll have to look back on the > archives for Jeremy Kemper''s excellent "Quick Start" post. An > alternative (if there''s interest by the Typo core team--Tobias?) is > to make an official branch on leetsoft''s repo. > > In fact, it might even be in everyone''s best interest to convert the > TRUNK in to an engine and make the "default install" just a dummy > Rails app that drops the Typo Engine in. That would be very cool. > > Duane Johnson > (canadaduane) > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >Re 2: This would be great. I''ve been working on an app that I built on typo, but my code base ended being quite divergent and a little bit larger then typos, so I think I got it a bit backwards. Nick -- Nicholas Van Weerdenburg
Duane - sounds great. Let me know if you have any trouble building your Engine :) - james On 11/4/05, Nicholas Van Weerdenburg <vanweerd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> On 11/4/05, Duane Johnson <duane.johnson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > So I''ve looked over the Typo code and concluded that: > > > > a) Typo is AWESOME, thus I''ll refrain from making my own blog engine > > from scratch > > b) Typo is not a drop-in plugin or "engine" as it is right now > > c) I''m going to turn it in to an engine. > > > > Given this latter conclusion, I have a couple of questions: > > > > 1. The software app I''m building at syncPEOPLE needs to have multiple > > blogs. I''ve considered forcing a one-to-one relationship on > > categories so that each category is its own "blog", but that just > > doesn''t seem right. Does anyone have code that turns Typo in to a > > multiple-blog Blog? > > > > 2. Is there a recommended way of keeping a "Typo Engine Branch" up to > > date while still maintaining changes necessary to enginify it? My > > current take on the matter is that SVK is going to do the job... > > though it''s a bit over my head. I''ll have to look back on the > > archives for Jeremy Kemper''s excellent "Quick Start" post. An > > alternative (if there''s interest by the Typo core team--Tobias?) is > > to make an official branch on leetsoft''s repo. > > > > In fact, it might even be in everyone''s best interest to convert the > > TRUNK in to an engine and make the "default install" just a dummy > > Rails app that drops the Typo Engine in. That would be very cool. > > > > Duane Johnson > > (canadaduane) > > _______________________________________________ > > Rails mailing list > > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > > http://lists.rubyonrails.org/mailman/listinfo/rails > > > > Re 2: This would be great. I''ve been working on an app that I built on > typo, but my code base ended being quite divergent and a little bit > larger then typos, so I think I got it a bit backwards. > > Nick > -- > Nicholas Van Weerdenburg > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >