Re: GSOC git push pull to plone.app.theming

On 5 Mar 2014, at 8:50 pm, krishnatejaperannagari <[email protected]> wrote:

> Thanks for the information sir. Just wanna ask you few questions:
> 
> 1.When we make changes to the theme are those changes saved to the
> rules.xml, html, css files that are present in the theme folder  or are they
> stored in the zodb files like data.fs that can be opened onlt by zope
> interface.

I'm not sure what you mean. Any changes you make via the plone.app.theming web interface are already saved to the ZODB not to files on a disk. The goal here is to also save them as a commit in a ZODB git repository that can then be pulled from and also pushed to.

> 
> 2.Went through the code you sent me.Git hub provides an api
> http://developer.github.com/v3/ <http://developer.github.com/v3/>  that uses
> the http protocol to interact with the files and it canbe  used with
> python.I guess using this api to send and receive data from git would be a
> good idea. What is your opinion regarding this.

I'm curious why do you think github has relevance to this task?

> 
> looking forward to hear from you.,
> 
> 
> 
> 
> --
> View this message in context: http://plone.293351.n2.nabble.com/GSOC-git-push-pull-to-plone-app-theming-tp7564752p7570404.html
> Sent from the Core Developers mailing list archive at Nabble.com.
> 
> ------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works. 
> Faster operations. Version large binaries.  Built-in WAN optimization and the
> freedom to use Git, Perforce or both. Make the move to Perforce.
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> _______________________________________________
> Plone-developers mailing list
> Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/plone-developers


------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk