The first feature extraction - Tab Highlighter

[PikachuEXE]

https://addons.mozilla.org/zh-TW/firefox/addon/tab-kit-tab-highlighter/

It contains only a few features about highlighting a tab
I am just trying to build a basic structure of extension that can be reused
So that I can extract more features into different pieces(extensions) more easily

This extension is restartless
You can try its effect by installing it and turn off the corresponding options in TabKit
This extension's options can be changed in Addon Manager

[Hossy]

Is this the start of a complete rewrite?

--
You received this message because you are subscribed to the Google Groups "TabKit 2nd Edition" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tabkit-2nd-edit...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[PikachuEXE]

Yup
First copy some features into new extensions
Then remove the features extracted from TK2

I hope that makes it easier to maintain the code left (and maybe get some helper?)
And also separate extensions can be released with different pace

Hossy於 2013年3月29日星期五UTC+8上午9時26分47秒寫道：

[Tomasz Miodek]

I would only suggest that even though the extensions are to be split, their scopes should be clearly defined to avoid double work (and overlaping) in future. It would be also advisable on a page of each extension (including the mozilla add-on information page) to provide information about other extensions that are more or less linked to it.
I don't know github functionality. I it possible to create a kind of "program" that will hold all the extensions and keep track of information that refer to all "projects"?

2013/3/29 PikachuEXE <pikac...@gmail.com>

--

[PikachuEXE]

I will put link for all extracted extensions once finished
But now I am just testing the result

But thanks for the suggestion :)


I can make the repo look like rails (one repo, multiple extensions)
Then it might eliminate the need of interlinking

But those extensions can be used separately (although some requires the core, TK2)
So I don't want the issues of different extensions to be mixed together

I think I will just go for interlinking

[Hossy]

Too soon to suggest a new feature (tab grouping)?

 

I don’t mean with colors, I mean with tabs.  So, if you have more than one “tab group,” you’d have a top row of tabs (tab groups).  The second row would be all the tabs in that groups.  These tabs would be what we are used to and see now.

 

There was an old extension that is no longer developed that did this and I really miss it.

 

It was great to have a work tab, personal tab, and different project tabs to organize my browsing easily.  Much better than using separate windows, especially since you can’t title them.

--

[Tomasz Miodek]

Hossy,

try using vertical, not horizontal tabs in TabKit2.
You can have multiple levels of tabs (with indents - a kind o f a tab tree).
I understand your suggestion and it sounds good but using tab tree might be a temporary workaround for the time used to refactor the code.

Best regards

2013/3/30 Hossy <ho...@hossy.com>

[PikachuEXE]

I can break down the extension or fix something
But developing a new feature is out of my time and ability

That's why I am trying to breaking down the extension
When there is another extension does tab grouping differently,
you can still have some features of TabKit

[PikachuEXE]

0.2.0 is out!
Added the ability to make tab and tab bar's background solid (forgot to add them in 0.1.0)

  - Feature: Make Tab bar's background solid (useful when using Tab Kit's tree mode)
  - Feature: Make Tabs' background solid (Not sure what was this for, but it was in Tab Kit)


One good thing about the extension with extracted features
It passes Mozilla full review much easier, and the updates are processed faster
This new version is released on Mozilla within a day! (After I have submitted it)
But maybe it's because that the extension is small (which is still good)