Lib 0.51 needs reconstruction

[GoogleCodeExporter]

The poko framework and cms is great, but the 0.51 version needs some
reconstruction and the MakeTemplates.hx needs some tweaks. I will attach my
version of the lib, but I will write down all the changes which should be
addressed in the next release.

The src folder should be eliminated and both poko and site sources should
be moved to the lib root in order to be accessible through a simple -lib
poko switch, people shouldn't have to copy the sources in the project
directories. The makeTemplates sources folder could be moved to a tools
folder and the design folder should go into the www/_src_ folder. All the
compile code should go into the www/_src_ folder too. With these changes
you can achieve that the user should only copy the www folder to his/her
project folder, launch the compile code there, and all the code will
compile into that directory.

MakeTemplates.hx is Windows only in the 0.51 release! Instead of calling
the temploc2.exe file, you should call neko and the temploc2.n file inside
the haxelib folder. That eliminates the OS dependant binaries. The filepath
strings should be processed with care too, because the Windows backslashes
throw errors in Linux (and probably in MacOSX too). And because the layout
of the poko lib is changed and the site sources and templates are kept in
the haxelib directory, you should introduce a new attribute in
MakeTemplates.n which we can use if we want to compile the core mtt files.
I called this attribute -includecms. If includecms is set, we get the
recurse function to crawl through the site directory in the poko lib
directory. To make this successful, the MakeTemplates.hx was radically
changed, the recurse function takes two arguments: one basepath argument,
and one optional path argument. The items get into the items array relative
to the basepath, so the cleanUp function is obsolate.

Another small changes are the removed .bat files, which again are Windows
things, everyone can make a Linux alternative of course, but you too could
use Ant or Makefiles which are OS independent. It's cool that you included
the fla source of the logo, but a more opensource fileformat would be cool,
I made an svg file with inkscape. Your logo uses an Adobe font, which you
probably want to change because of licensing issues, I used the Soul Papa
font which is free and somewhat resembles your choice.

If the things above are badly explained please have a look at my version of
the plugin (successfully tested on WinXP and Debian Lenny). It would be
great if you would address the haxelib usability and cross operating system
issues in the next release!

Original issue reported on code.google.com by gabor.udvari on 23 May 2009 at 9:31

Attachments:

• poko-0.51-reconstructed.zip

[GoogleCodeExporter]

Hi,

Sorry for the long delay in replying. It's great to have someone else input on 
this 
whole crazy thing.

Version 0.7 is quite a lot different than 0.5, though with a pretty easy 
upgrade path 
that you should be able to work out.

We've cleaned it up a whole lot and generally for our projects run it in a 
completely 
different way. I think we have to do a new release to show this, but the idea 
at least 
is that we have Poko seperate from the CMS seperate from the site src files.

Calling temploc2.n - good idea.

.bat file - yeah probably best to go with a .n haXe now I think about it - 
seeing as it 
should all really be haXe based.

Logo - SVG would be best I thinks.

Original comment by tar...@gmail.com on 22 Feb 2010 at 6:42

[GoogleCodeExporter]

Would also love to know how you've been using it, if at all.

Original comment by tar...@gmail.com on 22 Feb 2010 at 6:43