Notices tagged with theme, page 2

mk

OK, I think these queue things in jQuery are beginning to fallinto place. At least I understand now why my first code (only implicitly using a queue) ended up being asynchronous. Now first #dinner, and then I'll try my own queueing #theme #hacking :)

mk

I made it out of my #hammock. no solution to my toolbar button problem in my #theme yet :(

mk

trying to solve a hard little problem in my #theme - and falling asleep while trying to think it through: #thatwontwork but maybe I'll solve it in my sleep...

mk

when scripting, it helps if you type variable names correctly. :-/ #theme #hacking

mk

YAY! finally solved another problem (creating a new plugin-theme integration mechanism) in my #Piwigo #theme #hacking - need to work it out now, but the basic wiring is in place and works. \o/ I feel like celebrating and maybe "taking a day off" tomorrow (I still have sewing and crocheting to do :))

mk

well, let's try to properly implement these 'popmenu' buttons, now that I've worked out *how* to do that. #theme #hacking

mk the federated universe , Time Zone Appropriate Farewell

after a lot of poking around #piwigo code, I now know what to do in my #theme - #tomorrow :) good night !tzaf !fediverse!

mk

I've (finally) worked out a new construction for my reveal-on-hover button which in turns reveals an actions menu on hover; this one doesn't leave traces in various browsers on "unhover". Yay! Now I need to convert them all to this new construct (and make them handle a click instead of only hover as well) - slightly more code, but works much better: still a win! #theme #hacking Firster: to the supermarket!

mk

jQuery is so easy to use, it's also very easy to make stupid mistakes after you haven't used it in anger for a long time :( (problem solved now :)) #theme #hacking

mk

yay, major step forward: my fancy plugin-theme integration mechanism works! now a second #tea, and then f\urther implement my mechanism! #theme #hacking \o/

mk sazius

@sazius morning! more tea sounds like a good idea! - going to do some major reconstruction surgery on my #theme and plugins today...

mk

Not a lot of code today - but I learned and figured out a lot of things. Getting a much better idea how Piwigo works and what I can and cannot do in a theme (or a plugin for that matter). Still #Piwigo is easy to dive into and then gradually learn - I like that a lot. #theme #hacking

mk

so, I fixed a few problems again. now, #breakfast, and then some other #theme #hacking

mk the federated universe , Time Zone Appropriate Farewell

well, enough for today (#yesterday already!) - I had some problems but still made good progress on my #theme #hacking. good night !tzaf !fediverse :)

mk

no HTML5 renaming as yet: I hit a logical #snag: the main 'category' page can contain albums (subcategories) as well as photo thumbnails - each with its own pagination. ugh. Need to work out first how to do that cleanly and user-friendly. #theme #hacking #piwigo

mk

OK, <div id="content"> is now <main id="content"> all over the place (with one exception: HTML mail - I'm not sure how much compliance I can expect in that environment (anyone?), so I'm conservative there). Next: some <section>s, <nav>s and <menu>s #HTML5 #theme #hacking #piwigo

mk beer

completely separate navbar areas from content (instead of including them in content), solved some hairy problems, and further tweaked appearance of pagination bar. time to implement some #HTML5 <section>s and a <main> for the content. first, a !beer - I think I deserve one now :) #theme #hacking #piwigo

mk tazman

@tazman on my second #tea already, trying to solve a hard-to-find problem in a #piwigo plugin (and/or my #theme) :(

mk

oh, ick. I had nicely (and hierarchically) reorganized my stylesheet. Now I find doing that I managed to override specific rules with more generic ones, instead of the other way round. *sigh* #theme #hacking

mk

breaking my head over tags that are opened in one #template and closed in another (again) - this is nearly always a sign of bad technical #theme design and makes structure hard to understand; reorganizing things once again! #iwillgetthereintheend

mk jk

@jk it's complicated all right: the presence of each lower level depends on a toolbar action in a level above - essentially a 'drill down' operation. It took me a lot of time to really understand that and get it coded consistently (and even, using Smarty, add an extra bottom margin only on the bottom headerBar) #theme #chiselingaway

mk

so, let's "turn on" some more new HTML5 element names in mt #piwigo #theme... nav, main, section (I'll do menu later). first question to solve: do I use one nav element containing 1-3 'bars', or do I create a section with 1-3 nav elements?

mk

how lovely - the way I've been coding toolbars with 'popover' boxes maps exactly to how HTML5 suggests using menu and menuitems #theme #hacking #html5 #thingsfallingintoplace

mk

damn. I just accidentally closed a Chromium window with countless tabs I'm using while #theme #hacking - and that closing somehow nearlyt brought down my whole desktop :(

erkanyilmaz question

trend from your home timeline (where you follow 330 users): #reading #ebooks #they_dont_want_you_to | #crypto #hacking | #fediverse #tzag | #tpp | #theme | #listening

mk

so, after I eat this bread with really tasty turkish Pfeffersalami :) I'll be ready to kill off a load of almost-the-same JavaScripts and replace them with a single much smaller one :D #theme #hacking

mk

for now, reams of comments in my stylesheet and templates, but I have finally worked out a way to correctly position 'popover' boxes (triggered by a toolbar button) *without* needing JavaScript to calculate its position! JS now only needs to do show/reveal (and I can make it work (less nicely) without JS at all. #breakthrough #theme #hacking \o/