Going towards haxelib
1 view
Skip to first unread message
Andreas Söderlund
Nov 14, 2009, 8:35:43 AM11/14/09
to haxig...@googlegroups.com
Sorry about the spam on this list... Hopefully googles filters will learn soon, if not I have to make this an invitation group.
Anyway, I'm making progress on the haxelib experiment. The decision is made now, it'll be a haxelib since it's such a nice tool. The "run.n" file is perfect for making all the initalization, building, testing etc. So in the next version you'll install it just like this:
haxelib install haxigniter
haxelib haxigniter run init
...and you'll have a ready-to-go project structure in a directory of your choice. Sounds good?
There are two things I'm thinking about now, maybe you can help me out with some ideas:
1. Some of the libraries are depending on the (subclassed) Application instance, and I'm thinking whether to make it a singleton or not. It would be nice to just specify a static Url.redirect() instead of instantiating with the practically implicit Application instance first, but I know that the singleton is considered an antipattern. What do you think? Is there a scenario where more than one application could be run at the same time?
2. It would be really nice if the user could run the unit tests from command line, like "haxelib haxigniter run unittests". Unfortunately I don't know the class the user wants to run. It'll be inherited from haxigniter.tests.TestRunner but the subclass package and name is unknown. I was thinking about specifying it as an argument, then generate code on-the-fly and run with Neko. But maybe you have a better idea?
/Andreas
Anyway, I'm making progress on the haxelib experiment. The decision is made now, it'll be a haxelib since it's such a nice tool. The "run.n" file is perfect for making all the initalization, building, testing etc. So in the next version you'll install it just like this:
haxelib install haxigniter
haxelib haxigniter run init
...and you'll have a ready-to-go project structure in a directory of your choice. Sounds good?
There are two things I'm thinking about now, maybe you can help me out with some ideas:
1. Some of the libraries are depending on the (subclassed) Application instance, and I'm thinking whether to make it a singleton or not. It would be nice to just specify a static Url.redirect() instead of instantiating with the practically implicit Application instance first, but I know that the singleton is considered an antipattern. What do you think? Is there a scenario where more than one application could be run at the same time?
2. It would be really nice if the user could run the unit tests from command line, like "haxelib haxigniter run unittests". Unfortunately I don't know the class the user wants to run. It'll be inherited from haxigniter.tests.TestRunner but the subclass package and name is unknown. I was thinking about specifying it as an argument, then generate code on-the-fly and run with Neko. But maybe you have a better idea?
/Andreas
Reply all
Reply to author
Forward
0 new messages