I guess i meant sticking framework features :) so i should be able to just use that stuff outside the CMS also. Because i encountered some issues i was wondering what is the best approach, but that also depends on what kind off project it is...
So am i right, for instance, you should be able to place custom content type listing outside the CMS in a website with ft:objectadmin? Or use the code of an custom type's edit page with ft:wizard etc outside the CMS in a website? Thanks. On Dec 18, 6:45 am, Blair McKenzie <[email protected]> wrote: > What kind of features do you want to add? > > Not sure what you mean by sticking the webtop features into the project. > > Blair > > On Thu, Dec 17, 2009 at 11:21 AM, Marco van den Oever < > > [email protected]> wrote: > > Hi all, currently i am building in webtop features into a project, but > > i am wondering, what is the best approach? > > > Put webtop features into project directly? > > > Or to stick to the framework and just customize the webtop css? > > > Any opinions? Thanks! > > > -- > > You received this message cos you are subscribed to "farcry-dev" Google > > group. > > To post, email: [email protected] > > To unsubscribe, email: > > [email protected]<farcry-dev%[email protected]> > > For more options:http://groups.google.com/group/farcry-dev > > -------------------------------- > > Follow us on Twitter:http://twitter.com/farcry -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry
