11:40 p.m.
We just finished splitting the additional icon themes into a new repo,
and integrating icon-themes into edit-utils. That is now pushed.
How exactly should we push the icon-theme-list package? Should we make a
new bitbucket repo, and then somehow "give" it to the XEmacs user on
bitbucket?
Thanks for all your help teaching us how to make and upload packages;
it's been a great learning experience.
Sincerely,
Byrel and Steve Mitchell
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
11:13 a.m.
steven Mitchell <smitchel(a)bnin.net> writes:
We just finished splitting the additional icon themes into a new
repo,
and integrating icon-themes into edit-utils. That is now pushed.
How exactly should we push the icon-theme-list package? Should we make a
new bitbucket repo, and then somehow "give" it to the XEmacs user on
bitbucket?
Thanks for all your help teaching us how to make and upload packages;
it's been a great learning experience.
I think the path we want to encourage is that you create a repository
under your own Bitbucket account, and let one of use have one last look
at it before cloning it over to the XEmacs account. Does that work for
you?
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
9:13 a.m.
I would strongly *PREFER* someone look at it before entering it into the
code base.
Even several someones.
What we pushed yesterday for the buffer-colors and icon-themes is code
working here,
for months, on two machines, which hardly represents all configurations
out there by
any stretch.
I was unhappy about pushing the icon-themes without the extra themes.
It really doesn't
show what it does without a few themes to try it out on. I really need
to get a Bitbucket
repository this morning for extra icon themes, and get it uploaded so
reviewers can use the
extra icons to actually see what it does. The two default themes in the
package itself,
text-icons and default icons, each of which has only 1 size, isn't
enough to put it through
it's paces. Might even have errors that way too.
One question: will one of you give us the go ahead to push the changes?
Or do we wait
for a week(or 2) with no requests for us to change things to push it? I
expect us to make
mistakes--this is the first time we are doing most of the package stuff.
Today is Byrel's last day home before going back to grad school. We can
do bug fixes, etc
in the meantime, but large sections of code probably will have to wait
till May.
We will get a bitbucket repository for the icon-themes-list with the 3
themes and Icons
in it, up this morning.
steven Mitchell <smitchel(a)bnin.net> writes:and integrating icon-themes
into edit-utils.
I think the path we want to encourage is that you create a
repository
under your own Bitbucket account, and let one of use have one last look
at it before cloning it over to the XEmacs account. Does that work for
you?
Happy to cooperate, just please show us the way things need to be done.
Is this path for new packages only? Or does it include improvements to
existing
packages as well, and diffs to documentation, and website stuff? I am
thinking
about the update to xpm-mode that we pushed a couple of weeks ago, should we
have put that in a repository first?
Thanks,
Steve Mitchell
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
4:41 p.m.
steven Mitchell <smitchel(a)bnin.net> writes:
> I think the path we want to encourage is that you create a
repository
> under your own Bitbucket account, and let one of use have one last look
> at it before cloning it over to the XEmacs account. Does that work for
> you?
>
Happy to cooperate, just please show us the way things need to be done.
Is this path for new packages only?
Just for new packages.
Or does it include improvements to existing packages as well, and
diffs to documentation, and website stuff? I am thinking about the
update to xpm-mode that we pushed a couple of weeks ago, should we
have put that in a repository first?
No, you did everything right. Again, we're happy to have you help with
XEmacs.
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
1:50 p.m.
steven Mitchell <smitchel(a)bnin.net> writes:
We just finished splitting the additional icon themes into a new
repo,
and integrating icon-themes into edit-utils. That is now pushed.
Just a note that this will not work with xemacs-gtk. The Gtk toolbar
uses "stock" images for the toolbar, which should pick up the current
theme. There are Gtk function to add new stock images, but I haven't
tried them yet.
Perhaps if the stock item name is actually a file, then I could load
that directly. Currently, I use a hash table mapping toolbar-icon names
to stock icons.
`gtk-toolbar-stock-icons' (buffer: toolbar-gtk.c, mode: C)
Variable:
value: see below
Map from toolbar function name to Gtk stock icon name for toolbar icons.
value:
#<hash-table :size 12/29 :data (toolbar-replace "gtk-find-and-replace"
toolbar-info "gtk-help" toolbar-print "gtk-print" toolbar-cut
"gtk-cut" ...) 0xd>
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
4700
days inactive
4704
days old
4 comments
3 participants
participants (3)
-
Jeff Sparkes -
Michael Sperber -
steven Mitchell