Comments on: PocoWebWidgets – We need your help! http://pocoproject.org/blog/?p=93 News and discussion for the POCO Community Thu, 09 May 2013 12:05:16 +0200 http://wordpress.org/?v=2.8.5 hourly 1 By: alex http://pocoproject.org/blog/?p=93&cpage=1#comment-255 alex Wed, 13 Feb 2008 10:32:19 +0000 http://appinf.com/poco/blog/?p=93#comment-255 One thing I think we could learn from it is support for scenarios when Javascript is not available. May prove useful to keep that mode in WebWidgets. Alex One thing I think we could learn from it is support for scenarios when Javascript is not available. May prove useful to keep that mode in WebWidgets.

Alex

]]> By: Boris http://pocoproject.org/blog/?p=93&cpage=1#comment-254 Boris Wed, 13 Feb 2008 00:45:53 +0000 http://appinf.com/poco/blog/?p=93#comment-254 The following project is related and might be of interest: http://ddj.com/cpp/206401952 The following project is related and might be of interest: http://ddj.com/cpp/206401952

]]> By: guenter http://pocoproject.org/blog/?p=93&cpage=1#comment-253 guenter Sat, 11 Aug 2007 14:13:03 +0000 http://appinf.com/poco/blog/?p=93#comment-253 I have moved WebWidgets into the Sandbox, where it belongs ;-) I have moved WebWidgets into the Sandbox, where it belongs ;-)

]]> By: alex http://pocoproject.org/blog/?p=93&cpage=1#comment-252 alex Thu, 09 Aug 2007 13:02:53 +0000 http://appinf.com/poco/blog/?p=93#comment-252 There are tasks for every level of skill. For example, what I am currently doing is enabling Data to deal with Unicode. It's not a rocket science, just a lot of manual work - every ODBC call that traffics in strings has to be wrapped in two versions - Unicode and ANSI. There's abundance of examples throughout POCO on how to do it. Prior to doing this, since I do not deal with Unicode, I even didn't know in detail what Unicode is. I had a remote idea, that's all. So, I've read few docs, figured out what's all that UTF8/UTF-16 mess about, studied existing code and now I know something. There's no rocket science in any of this. It's all just hard work and commitment. I realize people have lives and contributing is definitely a time consuming activity. We are just hoping to get more people step up and speed it a bit - there are many things we'd like to see in POCO and see it soon, Web GUI being one of them. But, given the current workforce pool, things can only move as fast as they can. There are tasks for every level of skill. For example, what I am currently doing is enabling Data to deal with Unicode. It’s not a rocket science, just a lot of manual work – every ODBC call that traffics in strings has to be wrapped in two versions – Unicode and ANSI. There’s abundance of examples throughout POCO on how to do it. Prior to doing this, since I do not deal with Unicode, I even didn’t know in detail what Unicode is. I had a remote idea, that’s all. So, I’ve read few docs, figured out what’s all that UTF8/UTF-16 mess about, studied existing code and now I know something. There’s no rocket science in any of this. It’s all just hard work and commitment.

I realize people have lives and contributing is definitely a time consuming activity. We are just hoping to get more people step up and speed it a bit – there are many things we’d like to see in POCO and see it soon, Web GUI being one of them. But, given the current workforce pool, things can only move as fast as they can.

]]> By: paschal http://pocoproject.org/blog/?p=93&cpage=1#comment-251 paschal Wed, 08 Aug 2007 20:52:55 +0000 http://appinf.com/poco/blog/?p=93#comment-251 Alex, You are over estimating my abilities. Believe me, you don't want my code in Poco. You won't be happy... Alex,
You are over estimating my abilities. Believe me, you don’t want my code in Poco. You won’t be happy…

]]> By: alex http://pocoproject.org/blog/?p=93&cpage=1#comment-250 alex Wed, 08 Aug 2007 18:18:53 +0000 http://appinf.com/poco/blog/?p=93#comment-250 Paschal, The original post says it all: "If you feel you can help, don’t hesitate! PocoWebWidgets needs your input!" Paschal,

The original post says it all:

“If you feel you can help, don’t hesitate! PocoWebWidgets needs your input!”

]]> By: paschal http://pocoproject.org/blog/?p=93&cpage=1#comment-249 paschal Tue, 07 Aug 2007 00:03:21 +0000 http://appinf.com/poco/blog/?p=93#comment-249 Now that Guenter has signed on the design that piggy-backs on existing Ajax frameworks, Ext JS in particular, what happens next? Now that Guenter has signed on the design that piggy-backs on existing Ajax frameworks, Ext JS in particular, what happens next?

]]> By: guenter http://pocoproject.org/blog/?p=93&cpage=1#comment-248 guenter Fri, 03 Aug 2007 12:20:01 +0000 http://appinf.com/poco/blog/?p=93#comment-248 Just looked at ExtJS, and it really looks nice. Exactly what I have been looking for. License seems to be fine, too. Just looked at ExtJS, and it really looks nice. Exactly what I have been looking for. License seems to be fine, too.

]]> By: alex http://pocoproject.org/blog/?p=93&cpage=1#comment-247 alex Tue, 24 Jul 2007 17:10:00 +0000 http://appinf.com/poco/blog/?p=93#comment-247 One more thing that occurred to me - shouldn't WebWidgets be in sandbox SVN rather than in the main trunk? Not that it matters that much, but it may confuse people implicitly indicating production readiness of the library. One more thing that occurred to me – shouldn’t WebWidgets be in sandbox SVN rather than in the main trunk?

Not that it matters that much, but it may confuse people implicitly indicating production readiness of the library.

]]> By: alex http://pocoproject.org/blog/?p=93&cpage=1#comment-246 alex Mon, 23 Jul 2007 20:29:43 +0000 http://appinf.com/poco/blog/?p=93#comment-246 It is my understanding that LGPL is some sort of compromise between BSD and GPL - you can use code free of charge in any way and for any purpose as long as you are only using it (i.e. "linking" with it - that's why 'L' originally stood for "Library". If you modify the LGPL-ed code, then you have the obligation to give the modifications back to community. As for the scripting, if you would say take ExtJS, add your code and distribute the whole thing obfuscated, you'd be violating the license. At any rate, I do not see obstacles for ExtJS being used in conjunction with POCO. But, to know for sure, I guess we'd need an army of lawyers to think about it at $500/hr rate ;-). It is my understanding that LGPL is some sort of compromise between BSD and GPL – you can use code free of charge in any way and for any purpose as long as you are only using it (i.e. “linking” with it – that’s why ‘L’ originally stood for “Library”. If you modify the LGPL-ed code, then you have the obligation to give the modifications back to community.
As for the scripting, if you would say take ExtJS, add your code and distribute the whole thing obfuscated, you’d be violating the license.
At any rate, I do not see obstacles for ExtJS being used in conjunction with POCO. But, to know for sure, I guess we’d need an army of lawyers to think about it at $500/hr rate ;-) .

]]>