Refactoring before 1.0

4 messages - 149 views

Hi all,

We know that Kuix users community is growing, and it's a very good news for ths project.

But before release it as 1.0 we want to refactor some widget names to glue to a global naming convention.

For example ScrollContainer could be replace by ScrollPane, Choice inner RadioButton and Screen will be replaced by ChoiceRadioButton and ChoiceScreen.

Then my question here is to know if thoses changes could affect a lot your work ?

We would like to release a clean 1.0.

 

Widget tags refactoring :

  •   scrollcontainer *become* scrollpane
  •   scrollcontainercontainer *become* scrollpanecontainer
  •   screen's topbar become screentopbar
  •   screen's bottombar become screenbottombar
  •   choice's screen become choicescreen
  •   choice's radiobutton become choiceradiobutton
  •   tabbuttonscontainer become tabfolderbuttonscontainer
  •   defaulttabitem become tabfolderdefaulttabitem
  •   tabitemcontainer become tabfoldercontainer
  •   popupmenu *become* menupopup

In this case all internal widget tags start with their parent tag name.

 

Hi Bo,

thanks again, this situation is an example that you do a seriuos work, in my situation don´t affect because I´m trying the framework and a clean release is a good news.

Yes it's our ambition to clean has we can the first real Kuix release ;)