| 01:16:20 | SmokeyD: | wildintellect: you around? |
| 01:16:30 | wildintellect: | about to sleep but yes |
| 01:16:56 | SmokeyD: | I just woke up : ) Mind me asking for your opinion once more? |
| 01:17:10 | wildintellect: | has anything changed? |
| 01:17:32 | SmokeyD: | not really, I just though that it might be nice to develop the fuinctionality that we are missing in python |
| 01:17:54 | SmokeyD: | and then if we want to add it to geonetwork or geoserver, compile it with Jython to java bytecode for use in those apps |
| 01:18:05 | wildintellect: | that's one way to do it |
| 01:18:29 | wildintellect: | Tyler and I both thought it could simply generate data for those apps and push it to them |
| 01:18:59 | wildintellect: | I do like the python idea though since I can reuse the code in a desktop app too |
| 01:19:17 | SmokeyD: | yeah that would be possible as well. But I thought that if you want a webinterface to the code, it might be nicer to include it in pre-existing webapps insdtead of creating a new one |
| 01:19:58 | wildintellect: | even your way it could be the same, the web part of it is separate from the backend that actually processes the files |
| 01:20:12 | wildintellect: | so we can toss various frontends on it all we want |
| 01:20:18 | SmokeyD: | yeah, that is what I thought |
| 01:21:02 | SmokeyD: | I like geonetwork and geoserver in general. It would be a shame to create an extra frontend if you can use pre-exisint ones. On the other hand it would be great to use the same code not only in those webinterfaces, but also in other apps |
| 01:21:06 | SmokeyD: | hence the jpython solution |
| 01:21:25 | SmokeyD: | *jython |
| 01:21:47 | SmokeyD: | that way you could use the code in both python an java apps |
| 01:22:14 | SmokeyD: | I'll contact geonetwork and geoserver people. See what they have to say |
| 01:22:43 | SmokeyD: | wildintellect: thanks for the input and sleep well |
| 01:22:48 | wildintellect: | ya, I've installed both of those, but it hasn't been clear how to really customize them |
| 01:23:26 | wildintellect: | their inner workings seem complicated |
| 01:23:37 | SmokeyD: | ok |
| 01:23:51 | SmokeyD: | I'll check out the source code on them. See if I can understand it at all : ) |
| 01:24:22 | wildintellect: | on other news I did play more with django today |
| 01:24:29 | wildintellect: | wow it's pretty easy to use |
| 01:37:15 | SmokeyD: | wildintellect: ok, cool. I'll check it out too |
| 01:38:45 | SmokeyD: | wildintellect: the reason I didn't yet is that I had the idea that you have to do everything their way, or forget about Django. The reason I liked pylons ( and turbogears which runs pylons under the hood since version 2 ) is that you can plug in everything you like from templating language, to object-relational mapper, form generation and validation, authentication, etc/ |
| 01:39:19 | wildintellect: | it's not that different |
| 01:39:23 | SmokeyD: | ok |
| 01:40:12 | SmokeyD: | wildintellect: can you deviate in Django from the default ORM or the templating engine? |
| 01:40:52 | wildintellect: | oh probably, I haven't gotten that far |
| 01:41:01 | SmokeyD: | I'll check it out for myself instead of bothering you with those questions : ) |