Found 6 entries.
A recent commit on Lollysite has enabled me to import old blog posts from my other sites. Yep, you heard right, I’m going to concentrate all my blogging prowess here.
This includes my old entries from:
I hope that once the migrations are done, and I redirect the traffic from those sites here, I’ll be more consistently posting. Also, I’m reaching the stage where I’m understanding AppEngine a little more and actually have less things to do for Lollysite now.
BTW, I’m now also writing my blog entries in Textile instead of my proprietary (but open source) wiki markup Phliky
It’s very nice. Finally, I find a wiki-type markup language I like.
Labels: phliky, textile, appengine, blog, kapiti-geek-nz, retire-at-40
Inserted: 2009-12-23 09:32 (2 years, 1 month ago)
About Welly and Coding.
I chilled at work drinks on Friday, met a few friends for coffee on Saturday and had a pot luck dinner that evening. Went to see Wellington Phoenix thrash Sydney FC 3-0 on Sunday and enjoyed sitting and watching a film in the evening for the first time in ages.
Also, I'm back into coding (lots) again. I did quite a bit in the last couple of weeks - not on Zaapt but on KiwiWriters - some major things including timezone support, member challenges and fixing up lots of other little things no-one really notices.
With some smaller improvements being done for KiwiWriters I'm also adding a few things to Zaapt now too - in fact, I'm almost at the stage where I am re-factoring a few models and adding some new features rather than adding new models themselves. Maybe I'll reach version v0.1 one day. I still want to get some sort of photo gallery model in there first though. And Martyn has also suggested I put in roles for content-types too.
I should also write more documentation, as always.
Finally, I've also added Phliky to Ohloh too (see Phliky Page on Ohloh). I also received and gave out some Kudos :-)
After this brain dump, I should hit the sack.
Labels: phliky, zaapt, kiwi-writers, wellington
Inserted: 2007-07-24 00:10 (4 years, 7 months ago)
Phliky has had some improvements lately and is now on this server - quick test!
Phliky has had two things added to it recently:
Like this one:
: Coffee: Black hot drink Milk: White cold drink
Hopefully, they should work - fingers crossed. After all, I added nine extra tests to check the lists and two tests to check the definition lists.
Seems to work, except my CSS for the definition list is a bit out. Will be fixed another time :-)
Labels: phliky, css, unit-test
Inserted: 2006-10-10 22:47 (5 years, 4 months ago)
After uploading the executables yesterday, it now has packaging and has the heady status of being release v0.1!
Working with Google Code has been a joy so far. Not only can I use Subversion but I have also been playing with all of their groups pages too.
PgPatcher now has a \[p]{pgpatcher-discuss|http://groups-beta.google.com/group/pgpatcher-discuss} and \[p]{pgpatcher-commit|http://groups-beta.google.com/group/pgpatcher-commit} group each. Every time I commit, the latter group receives an email outlining which files have been changed.
Not only this, but for a different project, Phliky, in addition to the 'Discuss' and 'Commit' groups there is a new 'Issue' group which gets notified everytime an issue is changed in the issue tracker. It has taken a while to set up all these things, but now it's all working, I'm happy.
I guess my next step is to create a debian repository for all these packages.
Labels: phliky, pg-patcher, google-code, subversion
Inserted: 2006-10-10 22:30 (5 years, 4 months ago)
After three attempts last week and failing miserably, I finally added multi-level lists to Phliky. I'm on fire!
It's Sunday night, I've been hacking and ripping the rest of my CD collection all day (minus the tip trip and the face food stuffing) and I'm finally ready to go to bed in peace...
The reason why is that I finally added multi-level lists to Phliky. I have numerous automated tests to try it all out and my previous efforts were all failing on the 2nd half. This time, I added some code and ran the tests ... it was perfect.
I even added one more which was a little weird and it still worked. I'm not going to release it onto this website yet since I'll probably make a v0.2 for it and I'll try it out another time.
Now I need sleep but can rest happy I've cracked it.
Inserted: 2006-10-01 23:32 (5 years, 4 months ago)
After finding out about Google Code today, I decided to put one of my projects on there - Phliky.
So far, it's going well. I've created the project (\[p]{Phliky|http://code.google.com/p/phliky/}) and organised my repository. In true Google style, it has a very clear interface and is also easy to navigate.
Saying that, the interface is quite sparse at the moment though, but I think that it will be filled out as time goes on. As an example, when you click 'Settings' in the top right corner (to change your Subversion password), there are no links to get back to the 'Project Home' and the other 3 main tabbed pages.
There is an \[p]{Issue Tracker|http://code.google.com/p/phliky/issues/list} and they do mention in the \[p]{FAQ|http://code.google.com/hosting/faq.html} that they created it to be minimal but configurable. Looking at the configuration for the Issue Tracker, it makes perfect sense that you can add your own Open and Closed Status values and Issue Labels (which I guess is the same as tagging an entry). This way, you can make the tracker work exactly how you work, though they do already provide a decent set of defaults.
One great thing about \[p]{browsing the repository|http://phliky.googlecode.com/svn/} is that, as soon as you have commited a check-in, it is already updated with the latest Subversion Revision - no waiting round for the web accessible source to update.
One slight problem I had with the repository though was when I checked it
out using the URL I found, I didn't realise that it was already the trunk -
serves me right for not looking close enough. I'm used to checking out the
whole repository - trunk, branches, tags and all - so I ended up making
trunk/ (again), branches/ (again) and tags/ (again)! Bugger. A bit
of tidy-up later and I was good - am so glad it uses Subversion as opposed to CVS.
Overall then, I'm quote impressed and think that I'll like it even more in the future.
Labels: phliky, html, planet-catalyst
Inserted: 2006-08-10 22:22 (5 years, 6 months ago)