http://bugzilla.moblin.org/show_bug.cgi?id=5633


pohly <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED




--- Comment #13 from pohly <[email protected]>  2009-09-01 01:25:05 ---
(In reply to comment #12)
> The next solution makes sense. Could you help review the fix for this issue? 
> The branch is 'origin/bug5633'.
> Also info.m_outgoingScript is enabled. I have tested it. Also works.

Merged. I changed the description of the new m_incoming/outgoingScript fields.
Repeating the variable name doesn't add much new information. At the very
least, use different words because that sometimes makes the meaning clearer. In
this case, there's quite a bit that can be said about these fields:

-        /** name of incoming script */
+        /**
+         * One or more Synthesis script statements, separated
+         * and terminated with a semicolon. Can be left empty.
+         *
+         * If not empty, then these statements are executed directly
+         * before converting the current item fields into
+         * a single string with MAKETEXTWITHPROFILE() in the sync source's
+         * <beforewritescript> (see SyncSourceBase::getDatastoreXML()).
+         *
+         * This value is currently only used by sync sources which
+         * set m_profile.
+         */
         std::string m_incomingScript;

-        /** name of outgoing script */
+        /**
+         * Same as m_incomingScript, but used directly after
+         * converting a string into fields with PARSETEXTWITHPROFILE()
+         * in <afterreadscript>.
+         */

-- 
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues

Reply via email to