[Ledger-smb-devel] Preparing 1.5-rc1 documentation / analysing where to put the various docs

2016-05-07 Thread Erik Huelsmann
Before starting to write the various docs, while thinking where to put them, I decided to have a look at our webtraffic (made available by our Drupal hoster Freelock.com: http://piwik.freelock.com/). In April, nearly 60% of our traffic entered the site through the front page. Funny fact: of the re

[Ledger-smb-devel] ledgersmb.org traffic analysis & SourceForge AddOns repository

2016-05-07 Thread Erik Huelsmann
Hi all, Over the years, a number of AddOns have been developed for LedgerSMB 1.3. These are stored at SourceForge in the AddOns repository. These probably haven't been updated enough to be applicable to 1.4. Now, why do I start about this? I'm wondering if we should move these to GitHub (and if

[Ledger-smb-devel] Changes to the ledgersmb.org website

2016-05-07 Thread Erik Huelsmann
Hi John, In preparation of the 1.5 release, I've been looking at ways to publish installation instructions and notes. While doing so, I found that there wasn't really a structure for showing installation instructions on the ledgersmb.org site. Under the Documentation menu item in the Main menu, t

[Ledger-smb-devel] (Switching to) "cpanfile" to declare dependencies for 'cpanm'?

2016-05-07 Thread Erik Huelsmann
As I'm writing the installation instructions for 1.5, I have David's reaction to Marjan in the back of my head where my advise to use ```cpanm``` to install the dependencies for LedgerSMB works a bit too well, pulling in all the dependencies we added for our BDD testing framework. My thinking is t

Re: [Ledger-smb-devel] Last technical issue for 1.5-rc1 -- RFC

2016-05-07 Thread Chris Travers
On Thu, May 5, 2016 at 10:17 AM, Erik Huelsmann wrote: > Hi all, > > The last technical issue that we have left for 1.5-rc1 in the issue > tracker is #854 (https://github.com/ledgersmb/LedgerSMB/issues/854): > Included templates not loaded from the database. > > Now, I think I can fix this issue

Re: [Ledger-smb-devel] Changes to the ledgersmb.org website

2016-05-07 Thread John Locke
(resend from my subscribed email address...) Hi, I've made the following changes: * Allowed much bigger user pictures to upload, but set a server-side preset (the unused Square Thumbnail) to resize user pictures to 44x44, which is what 4em generated in Chrome) * Turned on "Panelizer" and appl

Re: [Ledger-smb-devel] Last technical issue for 1.5-rc1 -- RFC

2016-05-07 Thread Erik Huelsmann
> > >> Then again, if we're going to be using Dojo widgets more and more, we'll >> be able to use the Dojo template engine to build the page client side. If >> that's the case, then do we - long term - still need a (blazingly fast) >> server side template engine? (There's an issue about this with a

[Ledger-smb-devel] Questions due to writing 1.5 installation instructions: "standalone" / "TeX::Encode" / REST ?

2016-05-07 Thread Erik Huelsmann
Hi all, Due to trying to write a comprehensive list of instructions people should run to install LedgerSMB 1.5, I now have a number of questions: 1. Our Makefile.PL lists CGI::Emulate::PSGI as a dependency under the Starman server. It's my perception though that in order to run 1.5, you need Pla

Re: [Ledger-smb-devel] (Switching to) "cpanfile" to declare dependencies for 'cpanm'?

2016-05-07 Thread David G
Hi Erik, From our previous discussions on IRC I think this is the only sensible way to go. David G On 07/05/16 23:33, Erik Huelsmann wrote:

Re: [Ledger-smb-devel] ledgersmb.org traffic analysis & SourceForge AddOns repository

2016-05-07 Thread David G
Hi Erik, I'd say yes, lets move them to GitHub, and each addon in a separate repository, but not owned by the ledgersmb github user. Instead lets create a ledgersmb-addons user and home each addon under that This allows a couple of benefits, especially as th

Re: [Ledger-smb-devel] Last technical issue for 1.5-rc1 -- RFC

2016-05-07 Thread David G
Hi Erik, Chris, Once again, as we've discussed on IRC, I think that separating our templating for UI and doc generation makes sense, sticking to TT for doc generation for now, and moving as rapidly as possible to Dojo for the UI which I believe we are well on the way