my persoanl take on this is that the look & feel should progress... (like you guys added this nice flash menu on the top of the jforum site - which could also be implemented with any of the new JS frameworks around such as moo tools, yui, prototype, scriptaculous, etc...).
thanks in advance. [originally posted on jforum.net by gkatz]
i dont actually have a forum software example but all you need to do is check the 'web2.0' sites around you. my favorite look is the blackish dark grey sites same as you did here in jforum on the left menu. 'web2.0' is a big thing with ajax and all but i dont think its a must to use all those technologies yet i do think that a makeover for jforum basic look is kinda needed to atract new installations. even a simple new template with a little JS tricks would do the trick.
thanks. [originally posted on jforum.net by gkatz]
Behaviour and Script.aculo.us offer objects for Fluid Animations, Drag'n'Drop and Dynamic Page Part updates.
For instance, there's a Webservice which returns a JSON that represents its state, I have a function called FetchAjaxValue that allows us to invoke a Webservice like a local function.
It has patterns implemented for browser buffering in order to control the traffic and load on the server, good for applications like Google Suggest - do-as-you-type.
Nowadays I'm playing Google and developing a distributed class for MapReduce execution on web browsers. JS4Fun. :-)
Thus, I think our choice depends upon a simple, nonetheless dramatic decision - are we going to support old browsers on it? If so, as my class it's only here to help the data go in and out the server. It's a good choice.
If we are going to look ahead and keep 2.1 branch taking care of old folks, let's use Prototype.js and Scriptacolous for the rich interfaces.
What's our support policy? [originally posted on jforum.net by dericofilho]