jforum 3 look & feel

[Migrated From Jforum.net]

hi all;i am using jforum 2.0.

for jforum 3 i was wondering about its look & feel. is it going to be slick with an 'AJAX style' look and cool new Javascript stuff like all the new websites we see around us? or are you going to keep the old look and feel?

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]

[Migrated From Jforum.net]

Yes, an improvement would be great.

For the very first betas, wel'll for sure use the current layout, so we can keep focused on the functionalities and code stability.

After that, we can work on the UI.

Do you have suggestions / sites we can look at, as example?

Rafael
[originally posted on jforum.net by Rafael Steil]

[Migrated From Jforum.net]

well;
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]

[Migrated From Jforum.net]

I have an Asynchronous Javascript library of my own that I could cede to JForum turning its licence into JForum's BSD revised.

I think I can starting translating few screens but I'm going to need help from Designer, is there any one to help me on this stuff?


D�rico Filho
[originally posted on jforum.net by dericofilho]

[Migrated From Jforum.net]

What does this library do?

Rafael
[originally posted on jforum.net by Rafael Steil]

[Migrated From Jforum.net]

Well it implements few AJAX patterns such Schedulling and Periodic Refresh (Listener Pattern).

It has few methods for retrieving a WebService data into variables, either XML or JSON.

The whole idea behind it is AVOID reloading.
[originally posted on jforum.net by dericofilho]

[Migrated From Jforum.net]

How does you library differs from Prototype, Scriptaculous, MooTools and Behaviour?

Rafael
[originally posted on jforum.net by Rafael Steil]

[Migrated From Jforum.net]

Hi Rafael,


Well, the Prototype.js is a very rich javascript library, and I like it a lot. The main benefit using it is we'll have the Browsers' JS extended to a almost-complete OO language. If we're going to make a very dramatic change in JForum 3's L&F, and break down support for legacy browsers and text browsers, Prototype.js and Prototype's Add-on Scriptacolous are excelent choices. However Prototype.js is as big as 65KB and Script.aculo.us, 132KB. Hei Rafael, you'd really like it there's an UnitTest.js. :-)

MooTools is a library that aims the same target of Prototype.js, it extends Javascript to turn it into a OO complete language. However it doesn't go as far as Prototype.js. MooTools extends JS' Object object and create a Class object only; Prototype.js extends Object, Number, String, Form, Array, and implements few AJAX Patterns such TimedObserver.

Behaviour and Script.aculo.us offer objects for Fluid Animations, Drag'n'Drop and Dynamic Page Part updates.


My library on the other hand, does not aim to extend Javascript to turn it into OO language, or offer interface objects such Drag'n'Drop. It offers objects for dealing with Data Exchange to the server.

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]

[Migrated From Jforum.net]

Have you thought about using Apache Wicket for your UI to get around JS issues?
[originally posted on jforum.net by tandem]

[Migrated From Jforum.net]

What JS issues?

Rafael
[originally posted on jforum.net by Rafael Steil]