Skip to main content

Changing User Interface modes in Openbravo 3.0


OpenbravoERP 3.0 has brought a radical change to its User interface in its latest release 3.0. But like ardent developers I felt the 2.50 User Interface to be more suited for rapid development and I like the 2.50-3.0 Compatibility User interface for regular working. The buttons and the overall setup was pretty cool in it. Just when I thought there was no way to switch back, I came across this wiki linkhttp://wiki.openbravo.com/wiki/ERP/3.0/Developers_Guide/How_To_Switch_to_Classic_Mode.
Though by default the users are provided with the 3.0 user interface, they have the option of reverting to the 2.50 User Interface mode or the 2.50-3.0 compatibility mode.I will present a simple screen shot of each mode and discuss its pro's and con's.
2.50 User Interface Mode:

2.50 User Interface Mode
2.50 User Interface Mode
Type the Url like this in your browser to switch to the Classic User interface.
http://localhost:8040/openbravo/security/Menu.html?noprefs=true
Pros:
  • Clean User Interface.
  • Classic left side menus
Cons:
  • Limited space for actual content
  • Design pretty old
  • Not much suitable for fast editing
2.50-3.0 Compatibility mode:


2.50-3.0 Compatibility Mode
2.50-3.0 Compatibility Mode
Pros:
  • Web based look
  • Clean UI, more space for actual content
  • Widgets for integrating other web services
Cons:
  • Not suitable for fast editing
  • Menu structures are difficult to fathom for 2.50 users.
3.0 latest User Interface:


3.0 RC4 latest User interface
3.0 RC4 latest User interface
Pros:
  • Edit in grid.
  • View child simultaneously.
  • Data operations like excel, formulae, adding runtime columns
  • User configurable widgets for Ob data.
Cons:
  • Buttons on top are little unclear at times when they have to be done in a sequence
  • The buttons errors out many times when tried in form mode. Works properly in grid mode.
  • The form alignment is still messy when there are more fields with display logics involved(compared to the other 2 versions)
  • Not Developer friendly  (I did not find the field sequence tab at all, at times edit in grid did not save, when i tried deleting multiple values it shows success, but records are not deleted)
Having said all this, I think the 3.0 is the future and I am sure they will clear the bugs and make it the preferred UI for many like me.And with more and more User Interface enhancements, I think working with Openbravo would be more like gaming than working..:)
Happy Working...

Comments

Popular posts from this blog

My 10 years in Application Development

It's been around 10 years since I started programming. May be a bit more, if I have to include my first attempts at C programming in school. But it would be a grave insult to call remembering ten lines of code and just replicating it to put a star on the screen. I also did a course on Visual basic, but it was more gimmicks that Application development. But it was truly in the year 2007 when I started my Master in Computer Applications that I found a new flare for developing applications. 
I was very late to computers in general and even when I joined my Masters, computers were not really accessible to me. But when I joined my Masters where one is actually expected to hone the skills which they already have, but in case it was were I was learning the skills, initially it was very difficult. I was not sure what computers had for me nor I had a natural flair for programming. But the thing about computers that attracted me was the visual medium it gave. Initially it was just a door t…

Changing Timezone in Postgresql, Ubuntu

Timezone and locale are integral concepts that one should be aware of when implementing a System. For example. if you create a database in PostgreSql, it will use the default System settings for the database. Lets say you have a server in UK and your client is US. If the client tries to retrieve the current date or time, it is going to show the UK time and not the US one.
Today I encountered a different issue in our client place where the Ubuntu timezone and PostgreSql timezone were showing a incorrect values. Instead of Indian Standard Time (IST) it was showing Pacific Daylight Time(PDT). These are the steps that I followed to change the timezone to IST in PostgreSql and Ubuntu.
Changing timezone in Ubuntu:
sudo dpkg-reconfigure tzdataYou will be prompted to choose the continent and then the area. Provided screen shots where we configure the location.
Use TAB key to navigate to the OK button and then press Enter.

The changes will get reflected immediately. To check it you can open a n…

கிறுக்கனின் கிறுக்கல்கள் - அழுகையின் சிறப்பு

அழுகை என்பதை வெறுத்தவன் நான்... என்னை ஒரு நாள் பிரிந்திருக்க முடியாமல் , கைப்பேசியில் நீ சிந்திய உன் கண்ணீர் ஓசை என் காதில் கேட்கும் வரை...

பின்குறிப்பு: கிறுக்கனின் கிறுக்கல்கள் எங்கிருந்தோ தழுவப்பட்டது போல் தோன்றினால் கிறுக்கன் ( நான் உண்மையை ஏற்றுக்கொள்பவன்..:) ) பொறுப்பல்ல. கிறுக்கனின் கிறுக்கல்களில் வரும் கிறுக்கல்கள் யாவும் என் சிறய மூளையில் உதித்ததே ஆகும்.  Inspirations could have been drawn from somewhere else, but its the execution that counts....Isn't it ?