RooJSolutions en RSS: RooJSolutions - /index.php 150 150 GitLive - Branching - Merging 2019-01-03 00:00:00 <a href="">Article originally from rooJSolutions blog</a><br/> <div>As things have slowed down in the new year, I've decided to give this blog a sparkle of life briefly. So if you are interested in engaging our services feel free to send us a message. As we have spare capacity at present.</div><div>Almost 9 years ago, I created a little application called <a href="">gitlive</a>, it's aim was to replicate our old subversion environment, where we mounted the subversion server over webdav, and whenever we saved files, they where automatically committed to the revision control system.</div> PDO_DataObject Released 2016-10-28 00:00:00 <a href="">Article originally from rooJSolutions blog</a><br/> <div>Coding was complete last month, and has a huge test suite to covering a large proportion of the features. This should mean that replacing DB_DataObjects will be pretty easy.</div><div>You can either just checkout the code from github &nbsp;/ <a href="">PDO_DataObject</a> , or use the pear channel&nbsp;</div><pre>#pear channel-discover<br>#pear install roojs/PDO_DataObject-0.0.1&nbsp;</pre><h3>Documentation</h3><div>Browse around here &nbsp;<a href=""></a></div><div>I revived my old PHP_CodeDoc code &nbsp;(That needs publishing). It seemed simpler than trying to use any of the other tools out there. It's a pretty simple tool to extract structure, and documentation comments from the PHP source code. I added a small amount of code to export to our 'Roo UI bjs toolkit format'&nbsp;</div><div>The generated files are pure JSON, and mostly contain the contents from the comments un-formatted. I decided that doing the Markdown conversion in JavaScript was far simpler (I refactored <a href=""></a> slightly for use with our libraries)</div><div>There are a few other tweaks I made, using `@category` to group the documentation, and writing category pages (using roobuilder), then putting it all together the index.js file loads the parts, and renders the manual.</div><div>This week I finished tidying up the rendering on mobile, and making sure all the comments render nicely using markdown. The result should be a nice easy to read and use manual.</div><div><br></div> PDO_DataObject is under way 2016-08-17 00:00:00 <a href="">Article originally from rooJSolutions blog</a><br/> Work has started on revamping my PEAR package <a href="">DB_DataObject</a>, While it's served well over the years, and I still use it every day.. We have been funded to create a new version, which runs on <a href="">PDO</a>.<div><br></div><div>There is a <a href="">Migration plan</a>&nbsp;in the github repo for <a href="">PDO_DataObject</a>, I have currently completed the first two blocks, and almost the third block. But the key features are</div><div><ul><li>General Compatibility to DB_DataObject with a few exceptions - &nbsp;methods relating to PEAR::DB have been removed, and replaced with PDO calls</li><li>New simpler configuration methods, with some error checking</li><li>A complete test suite - which we will apply to DB_DataObject to ensure compatibility</li><li>Chaining for most methods so this works<br></li></ul><span style="font-family: &quot;Courier New&quot;;white-space: pre">$data = PDO_DataObject::Factory('mytable') -&gt;autoJoin() -&gt;where("somevalue not like 'fred%'") -&gt;limit(100) -&gt;fetchAll();</span><br><ul><li>Exceptions by default (PEAR is an optional dependency - not required)</li><li>It should be FAST!!! - standard operations should require ZERO other classes - so no loading up a complex set of support classes. &nbsp;(odd or exotic features will be moved to secondary classes)</li></ul><div>Feel free to watch the repo (we are using auto commit, so the commits are pretty meaningless at present)</div></div><div><br></div> Mass email Marketing and anti-spam - some of the how-to.. 2015-11-19 00:00:00 <a href="">Article originally from rooJSolutions blog</a><br/> <p>I'm sure I've mentioned on this blog (probably a few years ago), that we spent about a year developing a very good anti-spam tool. The basis of which was using a huge number of mysql stored procedures to process email as it is accepted and forwarded using an exim mail server.</p><p>The tricks that it uses are numerous, although generally come from best practices these days.</p><p>The whole process starts off with creating a database with</p><p></p><ul><li>'known' servers it has talked to before&nbsp;</li><li>'known' domains it has dealt with before.</li><li>'known' email address it has dealt with before.</li></ul><p></p><p><br></p><p>If an email / server / domain combo is new and not seen before, then apart from greylisting, and delaying the socket connections we also have a optional manual approval process. (using the web client).</p><p>Moving on from that we have a number of other tricks, usually involving detecting url links in the email and seeing if any of the email messages that have been greylisted (with different 'from') are also using that url.</p><p>On top of this, is a Web User interface to manage the flow and approvals of email. You can see what is in the greylist queue, set up different accounts for different levels of protection (either post-delivery approval, or pre-delivery approval etc..)</p><p>This whole system is very effective, when set up correctly. It can produce zero false negatives, and after learning for a while, is pretty transparent to the operations of a company. (email me if you want to get a quote for it, it's not that expensive...)</p><p>So after having created the best of breed anti-spam system, in typical fashion, we get asked to solve the other end.. getting large amounts emails delivered to mailing lists.</p><p><b>If you are looking for help with your mass email marketing systems, don't hesitate to contact us <a href=""></a></b></p><p>Read on to find out how we send out far to many emails (legally and efficiently)</p> Hydra - Recruitment done right 2015-11-16 00:00:00 <a href="">Article originally from rooJSolutions blog</a><br/> <div> <span>For the last few months we have been finishing up the first round of work on the <a href="">Hydra Jobs platform</a>. Something, along with the founders we think is quite revolutionary idea in IT recruitment.&nbsp;</span> </div> <div> <br> </div> <div> Key to it's design is the idea that the first step in finding someone is not putting up an advert, and expecting a shitstorm of resume's that are totally unconnected to the requirements. Taking a step back and realizing that as an employer, you would rather do a search for all the available candidates, than risk the time and wasted effort in sorting though unrelated piles of CV's.</div> <div> <br> </div> <div> We have spent the last 9 months working to get this to a MVP. The platform is now running, and the business operations are now underway.</div> <div> <br> </div> <div> So to make this work, the first step on Hydra was to design a set of Questions that could enable a detail search to work. What we ended up with is probably the easiest, yet comprehensive way of entering your profile data so it can be matched efficiently with companies recruiting staff.</div> <div> <br> </div> <div> It has been an interesting few months getting Hydra up and going, now we are over the hump of the work, <b> we are looking for more interesting projects to take on, so if you know of any, please <a href="">contact us</a>. </b> </div> <div> <br> </div> <div> Read on for some of the tricks we used to make this project, one of the best recruitment platforms around.</div> <div> <br> </div> <div></div> More on syntax checking vala - and a nice video 2015-05-20 00:00:00 <a href="">Article originally from rooJSolutions blog</a><br/> <div> As I wrote last week. I had added full syntax checking to the editor. So it runs a full compile check as you type.</div> <div>Here's a nice video of it working...</div> <div> <iframe width="420" height="315" src="" frameborder="0" allowfullscreen=""></iframe> </div> <div> <br> </div> <div> After the initial joy of adding this to code, I soon realized it had a fatal flaw, read on to find out more..</div> <div> <br> </div> Fetching Resources from github in the App Builder and fake web servers 2015-05-09 00:00:00 <a href="">Article originally from rooJSolutions blog</a><br/> <div>My final words this week on the builder - handling resources, and fake web servers</div><div><br></div><div>While I talked in the other posts about how the builder extracts the API for various components from the libvala library and the vapi files, some information that the builder requires has to be manually, created or fetched from other locations.</div><div><br></div><div>When the Builder was written in seed, it basically looked at the source code directory, and read files relative to the source code. For the Vala version however, it's not expected to know about the source code directory, so I had to use a different approach.</div><div><br></div> libvala testing code and extracting API from the vapis 2015-05-08 00:00:00 <a href="">Article originally from rooJSolutions blog</a><br/> <div>And the next part in the series. Gir and Vala structures, Nothing like a slow day to write a few blog posts.&nbsp;</div><div><br></div><div>The App Builder was originally designed to build applications using seed (the gobject introspection webkit javascript engines bindings), One of the key elements of how this was done involved introspecting the Gtk API, and extracting all the properties, signals and class structure.</div><div><br></div><div>In this post I will go through the history of how I extracted the API information on Gtk, initially from Gobject introspection and GIR files, upto the current version which uses libvala to get the correct API direct from the vapi files.</div><div><br></div><div><br></div>