Would you check some of these rather old bugs to suggest what to do,
please? Maybe some can be RESOLVED FIXED by now or need a question.
Please leave your reply on the bug web page - I might not see replies
to this mail. Ideally, tell irc.oftc.net #koha know that you're
looking at a bug.
http://b
I agree with you that, each template should fit with the same html, css code,
which is added by user in, for example, opacheader, opaccredit... i think we
need more works to focus on this. i would love to learn how to write a patch
and take a part in this. In relation with template, do you think
> Consequently, I think the next version of Koha should unify the
> templates of the prog and CCSR themes.
I agree. I don't have any ideas brewing for the visual redesign aspect
of it, but I would really like the OPAC template to use a more modern
CSS framework (not YUI) and have a fully-responsiv
Galen Charlton
> Consequently, I think the next version of Koha should unify the
> templates of the prog and CCSR themes. If we decide to continue
> offering both appearances as stock options, the visual and layout
> differences between the two should be managed strictly through the use
> of CSS.
On Mon, Apr 8, 2013 at 1:02 PM, Ian Walls wrote:
> I'm on the side of moving to Koha 4.0, and then looking into a
> browser-based means of upgrading the system from there. Firefox, Chrome,
> Dokuwiki and most mobile apps do not require any kind of additional process
> to upgrade; you just click
I'm on the side of moving to Koha 4.0, and then looking into a
browser-based means of upgrading the system from there. Firefox, Chrome,
Dokuwiki and most mobile apps do not require any kind of additional process
to upgrade; you just click the button, and it works (or you look up, and
it's updated,
I think the key thing to do is to provide a consistent and well documented
set of template variables that do not change within any given version.
This is a pretty common practice for many CMS and other templatable
systems. That way, we always know what parts we have to work with.
This would great
Dear Koha kommunitarians,
I'm harvesting news for this month's newsletter. Please send me by the 18th
anything you think your fellow community members might like to know about.
"News" can be as short as a sentence or as long as a paper. I especially
encourage you to send me a line or two for the
Hi,
At present we distribute two OPAC themes with Koha, "prog" and CCSR.
I like both of them, though it is nice having a mobile theme in the
shape of CCSR.
That said: in my view having two stock themes is going to present us
with a long-term maintenance problem, even nightmare. Any template
cha
Hello David
As a librairian, I completely agree with you.
Changing from 3 to 14 or 16 will raise a many questions, and vendors and
Koha staff in libraries will spend a LOT of energy and time on
explaining the change.
M. Saby
David Cook a écrit :
I agree with Marcel and Owen. I don't think it
Hi,
Not to nitpick, but won't numbering Koha with 4.x open possibilities
of confusion with that other prop. product with a similar sounding
name and version numbering?
just wondering aloud :)
cheers
--
Indranil Das Gupta
Phone : +91-98300-20971
Blog: http://indradg.randomink.org/blog
IRC
Yes, lots of patches, and
- it would be difficult to find a RM for 1 year,
- libraries would not be happy if they have to wait 1 year to see their
sponsored devs pushed in master,
- the update from 3.0 to 3.2 (2 years...) seems to be a very very bad
memory for lot of people (I think at that time
12 matches
Mail list logo
