-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

So far... I really do enjoy using webware and python to create my web 
applications.

One of the things I love about webware... is that it allows me to design my 
applications in much the same way I would using Apache Turbine... But with 
webware things are a LOT simpler.

Unfortunately Webware has this really unfinished feeling to it.

Not that this is a bad thing, by all means. And normally I LOVE looking for 
projects that have this kind of feeling to them... so I could jump in and 
help in any way I can.

But it seems lately I just have less and less time to actually get really 
involved with projects like this =/ Especially considering I already have my 
hands tied up with a couple other side projects =) (I recently became one of 
the developers for LWJGL for example)

Not to mention the fact that I have been trying to use webware in another side 
project of mine. (which is where my recent fixes to webware came from.)

Unfortunately Webware, WebKit specifically, seems broken or lacking 
functionality in a few places where I really need it to work.

So considering this, I am really not sure what to do.

So looking at my options... I see a couple possibilities.

1) Work with Stuart in fixing the path issues we have been running into.
2) Move my project over to Turbine
3) Move to a different style of web programming/language

Of course I like Option 1. But my main concern is time. I don't know how much 
time I would have to dedicate to this type of thing. Especially when it seems 
like most of my free time lately is just during the weekends.

Option 2 is very plausable... My main problem with it though is that Turbine 
is a bit ah.... overly complex... I like a lot of the ideas and methods they 
allow for designing a web application, unfortunatly... there is a LOT of work 
that has to be done just to get a simple site going.

Option 3.... I don't like at all really. Over the last 3 years I have of 
professional web development I have grown quite tired of some of the 
traditional ways of writing web software. This is one of the reasons why I 
like the Model 2+1 methodology provided by turbine so much. Especially when 
using the pull model, instead of the push model.

Not to mention the fact I would prefer staying within one of my favorite 
languages, python and java.

Now of course, I mention all of this so I could hear your opinion. What do you 
guys think?

I think Option 1 is workable... but it will require some time before my 
application is really working.

For the most part... The things I would like to see addressed are:
1) The ability for PSP pages to extend other PSP pages. (Not a bug of  
course... But it would really help in separating design and logic)
2) The weird path issues resolved.

Of course, I have looked into Cheetah for handling issue number 1. But ah... 
the lack of dynamic recompilation is a bit of an issue for me. Maybe I am 
just too lazy... but I always end up forgetting to recompile things. So when 
I make a couple small changes to a page and try to view them... I end up 
wondering why the changes did not take effect. =)

- -- 
Luke Holden
eBI Solutions
Main: (949) 387-5182
Email: [EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+IiRc3q5xXfLZTQkRAm33AJ49Wa9ZJoRRHDLb28+n/fwSvFtA1QCeLHmi
+lkDBKle9TO/BeoHJsBZZDg=
=x7F+
-----END PGP SIGNATURE-----



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-devel

Reply via email to