I get more and more the impression from this 'plugin development' reference in this tread and the other thread(s) ( http://ofbiz.markmail.org/message/6r4qnuu5v2c2aes2) that there is a vision that revolves around something not living in the trunk branch of the OFBiz repo.
If I am correct, we should revisit the discussion of separate repos for components (Ron called it sub projects). The whole idea behind the code of web help integration into cmssite led to: - pre-emptive code implementation in trunk/specialpurpose/cmssite - a dev branch being created to work on the new feature If people want to work on having a proof of concept or a new feature, they should do in outside forks, dev branches, etc before the community decides on the added value to our adopters (meaning: to have it in trunk) and what more needs to be done before before it can live in trunk. The trunk should not be regarded as the development environment of any contributor regarding new features and wishes. We should have learned by now that all these pre-emptive code implementations lead to unused bloatware, that (often) lead to clean-up expeditions afterwards. Best regards, Pierre Smits ORRTIZ.COM <http://www.orrtiz.com> OFBiz based solutions & services OFBiz Extensions Marketplace http://oem.ofbizci.net/oci-2/ On Wed, Jul 20, 2016 at 10:58 AM, Sharan Foga <[email protected]> wrote: > Hi Jacques > > My preference would be the second option - to make the Webhelp into some > type of plug in, as that makes it more flexible, for languages etc. > > I did do an initial analysis of the latest version of the Webhelp addon > from Nereide with all the files it uses but I need a developer to help me > implement it as I don't have the technical knowledge to do it. I did have > access to their repo so can check again for any updates. I'd be happy to > work on it but wouldn't be confident doing any code changes. so would need > to work with someone. > > Thanks > Sharan > > > > On 20/07/16 10:31, Jacques Le Roux wrote: > >> Hi All, >> >> With https://issues.apache.org/jira/browse/OFBIZ-7906 "Have a Gradle >> build file for the cmssite component" Pierre Smits suggests to put back the >> jars needed by the Webhelp . >> >> We already discussed lengthy about Webhelp solution and I know some >> persons are not for it, at least as it's currently integrated in OFBiz. >> >> Within https://issues.apache.org/jira/browse/OFBIZ-6644 "Webhelp >> umbrella task" Sharan said 4 days ago "I'd like to look at the Webhelp >> again in relation to the new trunk with Gradle to see how it could be >> incorporated." >> >> I also know that the Nereides team (Nicolas and Gil are among them) has a >> beside solution (called addon) based on the Webhelp work. There is also a >> Webhelp branch >> https://svn.apache.org/repos/asf/ofbiz/branches/webhelp-2012-12-07 . >> >> So I'd like to know what are the opinions of the community members about >> this subject. Should we? >> >> 1) Keep the Webhelp as is in OFBiz, improve and really use it (so begin >> by applying OFBIZ-7906 patch) >> >> 2) Put the Webhelp in a (next coming) plugin component (ie out of the >> cmssite component). This would release the dependency to the cmssite >> component but I fear this needs more work but I'd need confirmation from >> the Nereides team. >> >> 3) Drop the Webhelp >> >> I hope nobody is for the point 3, because I remember the hard work we did >> with Tom (Burns) and the current help is ugly compared with what the >> Webhelp can deliver (ie more than what we saw already which was already a >> great achievement IMO) >> >> Thanks in advance for your feedback >> >> Jacques >> >> >
